×
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.
Bruce Vining <bvining@xxxxxxxxxx> wrote:
V5R3 supports UTF-16 as CCSID 1200 and UTF-8 as CCSID
1208. These are in addition to the previous UCS-2
support with 13488 (and let's just forget 61952...).
And why should we "just forget about" 61952? Based on what
I've been reading today, it looks like I may have been
able to use 61952 to run Unicode field tests on our D02,
instead of having to transfer and re-encapsulate a *PGM
that came out of over 23000 lines of MI code for every
bloody damned iteration, (do I sound like I'm sick of
waiting 10 minutes for a RSTOBJ of one object to
complete?) and never knew it. (I'm convinced I must have a
barely-noticable case of dyslexia, as I could have sworn
the notes on CCSID 61952 said it was introduced in V3R1,
not V1R3.)
And what is gained by the addition of CCSID 1200?
And can SOMEBODY explain to me what the difference is
between UCS-2 and UTF-16? They both appear to be different
names for the exact same mapping of 2-byte binary values
into glyphs.
--
JHHL
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.
midrange.com
