On May 29, 2007, at 3:13 AM, Henri Sivonen wrote:
To avoid stepping on the toes of Charmod more than is necessary, I
suggest making it non-conforming for a document to have bytes in
the 0x80…0x9F range when the character encoding is declared to be
one of the ISO-8859 family encodings.
(UA conformance requires in some cases these bytes to be decoded in
a Charmod-violating way, but reality trumps Charmod for UA
conformance. While I'm at it: Surely there are other ISO-8859
family encodings besides ISO-8859-1 that require decoding using the
corresponding windows-* family decoder?)
I don't know of any ISO-8859 encodings requiring this, but for all
unicode encodings and numeric entity references compatibility
requires interpreting this range of code points in the WinLatin1 way.
Regards,
Maciej
