×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




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

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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