Re: Interesting results when writing to an IFS file

I would prefer that you declared to the world

"YOU START USING UNICODE RIGHT NOW, OR..."

UTF8 is the answer to JSON as JSON wants a UTF8 encoding of the data. But
the real need is to use some encoding of Unicode -- whether it be UCS2,
UTF8, or UTF16 (UTF16 being my personal preference when I have a choice).

Bruce (definitely tongue in check here, but I wouldn't want people thinking
UTF8 is the answer to everything -- the varying length nature of the
character encodings can be a real pain when working with non-varying
database definitions)

On Wed, Apr 13, 2011 at 6:33 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>wrote:

Henrik,

On 4/13/2011 5:51 PM, Henrik Rützou wrote:

you said "I mean, JSON isn't typically ASCII, it's UTF-8!"
you didn't say "JSON HAS TO BE IN UTF".

So... I wasn't forceful enough?

LISTEN UP, PETE! EITHER YOU START USING UTF-8 RIGHT NOW, OR IT'S
CURTAINS FOR YA, BUDDY. ISO-8859-1 IS PURE, CONCENTRATED EVIL.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.