On Tue, Dec 21, 2021 at 8:35 AM Niels Liisberg <nli@xxxxxxxxxxxxxxxxx> wrote:

.. So if you see the same error for your file the use
CHGATR OBJ('/tmp/utf8error.txt') ATR(*CCSID) VALUE(1252)
.. to bring it back to window-1252 (latin-1)

I'd like to discourage people from thinking of Windows-1252 and
Latin-1 as the same encoding. By now everyone is probably familiar
with the "smart (curved) quotes" encoding problem.

Well, the difference between Windows-1252 and Latin-1, combined with
people mistakenly thinking they are equivalent encodings, is PRECISELY
why this problem occurs.

See

https://i18nqa.com/debug/bug-iso8859-1-vs-windows-1252.html

I will say that IBM and others "who should know better" don't help to
make this distinction clear, given that they are, at best, sloppy with
the terminology they use, even in apparently official published
materials.

John Y.

As an Amazon Associate we earn from qualifying purchases.

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