dbcs vs unicode -- MIDRANGE-L

× 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.

Subject: dbcs vs unicode
From: bvining@xxxxxxxxxxxx
Date: Fri, 10 Aug 01 12:27:39 CDT
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

The other CCSID is 61952.  The difference between the two is 61952
represents the encoding of Unicode Version 1 while 13488 is Unicode
Version 2 and later.

Because the AS/400 implemented UCS-2 in production mode long before
most other products, AS/400 got caught in the incompatible changes
introduced with Unicode Version 2 and so needed 61952 in order to
recognize data stored in the previous versions.

Everyone should be using 13488 these days...

Bruce

>
>Yes, UCS-2 has CCSID 13488 and another one unique to AS/400, not sure of
>that identifier now.
>

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.