|
I replied with the following on midrange-l. What additional information
are you looking for?
CCSID 61952 corresponds to Unicode Version 1.1 while CCSID 13488
corresponds to Unicode Version 2.0 and later. The key difference is that
there was an incompatible redefinition of the Hangul Syllables Area that
would impact Korean users. The recommended CCSID to use is 13488, 1200, or
1208 (all Version 2.0 based) and not 61952. Back in V5R1 for instance the
Memo to Users documented that the Integrated File System was converting
from 61952.
If you are on V5R3 QSYS.LIB databases can be defined to contain UTF-8
(CCSID 1208) and UTF-16 (CCSID 1200) using DDS or SQL. UTF-32 is not
supported by database but can be used within an application by way of the
QlgTransformUCSData() API.
"James H H
Lampert"
<jamesl@xxxxxxxxx To
om> <mi400@xxxxxxxxxxxx>
Sent by: cc
mi400-bounces@mid
range.com Subject
[MI400] Unicode/UCS-2/UTF-16 --
OS/400 CCSIDs 61952 and 13488
11/03/2004 10:48
AM
Please respond to
MI Programming on
the AS400 /
iSeries
I didn't get much response on the MIDRANGE list, so once again
Does anybody know if there are any differences between the two OS/400
Unicode CCSIDs, 61952 and 13488?
Also, do UTF-8 and UTF-32 ever show up natively in QSYS.LIB database
files?
--
JHHL
_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.
As an Amazon Associate we earn from qualifying purchases.
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.