[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unicode problem



John,

The first hit on a Google search with UTF-16 (LE) CCSID resulted in the link 
http://www-01.ibm.com/software/globalization/ccsid/ccsid_registered.jsp

This list links CCSID 1203 with UTF-16 LE.

Any other CCSID should also be available on this link.

Kind regards.

Loek Maartens.

----- Original Message ----- 
From: "John Clark(Hotmail)" <jaclark40@xxxxxxxxxxx>
To: "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, March 19, 2010 3:34 PM
Subject: Re: Unicode problem


> Scott,
>
> Regarding whether or not it's UTF-8, the only reason I thought it was that
> is because the person that generated the file told me it was that.  I have
> no other proof that it's UTF-8.  I also know that when I used CCSID 1208,
> the file parsed correctly.
>
> Do you know what the CCSID is for UTF-16 (LE).  If so, I can try it.
>
> John
>
>
> ----- Original Message ----- 
> From: "Scott Klement" <sk@xxxxxxxxxxxxxxxx>
> To: "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Friday, March 19, 2010 4:54 AM
> Subject: Re: Unicode problem
>
>
>> Answering my own question, I guess.
>>
>> I noticed that the QlgTransformUCSData() API lets you transfer between
>> various flavors of Unicode. I could code a routine that translates
>> UTF-16LE (with or without BOM) to UTF-16, then use the standard iconv()
>> to convert it to UTF-8.
>>
>> While I'm at it, I could support UTF-32 and UTF-32LE.
>>
>> Sounds like fun.
>>
>>
>> Scott Klement wrote:
>>> Hi Thomas,
>>>
>>>> The first 2 BOM bytes clearly indicate UTF-16 (LE) because they match
>>>> the
>>>> UTF-16 (LE) signature given at:
>>>
>>> Yes, I agree.  I wrote a program (long time ago) that detects the
>>> encoding of an XML document, and it came to the same conclusion that you
>>> did...  UTF-16LE.
>>>
>>> And Expat understood and read/parsed that encoding without any problems
>>> on my box.  So I don't know why the OP had problems?
>>>
>>> But for certain, it's not UTF-8, and the OP's assertion that he "fixed"
>>> the problem by using CCSID 1208 doesn't make sense.  It's absolutely not
>>> UTF-8.
>>>
>>> Do you know if IBM i has a CCSID for UTF-16LE?  Searching around I found
>>> a page that says CCSID 1202 is UTF-16le, but that CCSID doesn't appear
>>> to be supported on i.   (Fortunately, Expat doesn't use the IBM i text
>>> conversion routines, it has it's own.)
>>> -----------------------------------------------------------------------
>>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>>> http://www.scottklement.com/mailman/listinfo/ftpapi
>>> -----------------------------------------------------------------------
>>>
>>
>> -----------------------------------------------------------------------
>> This is the FTPAPI mailing list.  To unsubscribe, please go to:
>> http://www.scottklement.com/mailman/listinfo/ftpapi
>> -----------------------------------------------------------------------
>>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------- 

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------