× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2012

Re: Creating UTF-16 LE Unicode files for BI system

On Tue, Jun 26, 2012 at 7:06 PM, sjl <sjl_abc@xxxxxxxxxxx> wrote:
I also forgot to mention that only 13488, 1200 and
1208 are supported, at least on V5R4.
CCSID's 1202, 1203, 1204 [and others] are
not supported.

It appears that it may be necessary for me to write
a program which uses the
QlgTransformUCSData() [Transform UCS Data]
API to convert the data:

That is probably your safest bet, though the difference between
little-endian and big-endian is just the byte order of the "words".
You could roll your own without too much difficulty.

John

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.