v6r1 info center (search for "file encoding" and link is for "File.encoding
values and System i5 CCSID"
It's not that they are necessarily, different - but 2 entries
UTF8 1208 UTF-8 (IBM CCSID 1208, which is not yet available on the
System i5 platform)
UTF-16 1200 Sixteen-bit UCS Transformation Format, byte order
identified by an optional byte-order mark
UTF-16BE 1200 Sixteen-bit Unicode Transformation Format, big-endian
UTF-16LE 1200 Sixteen-bit Unicode Transformation Format, little-endian
UTF-8 1208 Eight-bit UCS Transformation Format
----- Original Message -----
From: "Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, October 12, 2012 9:58 PM
Subject: Re: Parse error ... not well formed token
In my EXPAT_H copy book, I named the constant XML_ENC_UTF8, because you
can't put a dash in an RPG variable name. It's not possible to make a
constant or variable named XML_ENC_UTF-8 in RPG.
But, yes, it means UTF-8 (Which is the official name).
Not sure where in the Information Center it says that "UTF8" and "UTF-8"
mean something different. Can you provide me with a link?
On 10/12/2012 8:44 PM, franz400 wrote:
I am still confused by sometimes seeing "UTF-8" and in your code "UTF8"..
In the infocenter (under encoding) it seemed to treat these as different
definitions. Any differences?
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact