Bugzilla – Bug 99
ISO-8859-11 now treated as Win-874
Last modified: 2008-03-20 16:11:13 CET
Index: source =================================================================== --- source (revision 1270) +++ source (revision 1271) @@ -35963,14 +35963,16 @@ href="#refsIANACHARSET">[IANACHARSET]</a></p> <p>When a user agent would otherwise use the ISO-8859-1 encoding, it - must instead use the Windows-1252 encoding, except that any bytes in - the range 0x80 to 0x9F must, in addition to being interpreted as per - the Windows-1252 encoding, be considered <span title="parse - error">parse errors</span>.</p> - - <p class="note">The requirement to treat ISO-8859-1 as Windows-1252 - is a willful violation of the W3C Character Model specification. <a - href="#refsCHARMOD">[CHARMOD]</a></p> + must instead use the Windows-1252 encoding; when a user agent would + otherwise use the ISO-8859-11 encoding, it must instead use the + Windows-874 encoding. In both cases, any bytes in the range 0x80 to + 0x9F must, in addition to being interpreted as per the Windows + encoding instead of as a control character, be considered <span + title="parse error">parse errors</span>.</p> + + <p class="note">The requirement to treat certain ISO-8859 encodings + as Windows encodings is a willful violation of the W3C Character + Model specification. <a href="#refsCHARMOD">[CHARMOD]</a></p> <p>User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a href="#refsCESU8">[CESU8]</a> <a