Re: Chinese characters in an interface file

You are correct, I really should have said to define the column as Unicode
(either UTF-8 or UTF-16). My personal preference is to use UTF-16 (for no
particular reason other than perhaps habit from my CCSID 13488 days) but
either will preserve the data (which, in my mind, is the important part).

On Wed, May 13, 2020 at 5:28 PM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Wed, May 13, 2020 at 5:14 PM Bruce Vining <bruce.vining@xxxxxxxxx>
wrote:

I also agree with her in terms of "tossing" data is likely to become a
problem some day, but that could be handled. You would just need to
correctly identify/tag the data with the correct EBCDIC CCSID (or, if you
really want to do it right -- define the fields/columns as CCSID 1200
(UTF-16).

Why would UTF-16 be "right"? Why not just UTF-8 (CCSID 1208), if the
data is coming in as UTF-8?

To be clear, I believe you certainly could use UTF-16. I don't think
that would be *wrong*. But it would be nice to know the rationale
behind introducing another encoding that isn't already involved in the
process.

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com