[html5] r1271 - /
whatwg at whatwg.org
whatwg at whatwg.org
Thu Feb 28 00:05:49 PST 2008
Author: ianh
Date: 2008-02-28 00:05:49 -0800 (Thu, 28 Feb 2008)
New Revision: 1271
Modified:
index
source
Log:
[cwt] (2) ISO-8859-11 now treated as Win-874
Modified: index
===================================================================
--- index 2008-02-28 01:29:35 UTC (rev 1270)
+++ index 2008-02-28 08:05:49 UTC (rev 1271)
@@ -38398,14 +38398,16 @@
href="#refsIANACHARSET">[IANACHARSET]</a>
<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 <a href="#parse0" title="parse
+ 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 <a href="#parse0" title="parse
error">parse errors</a>.
- <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 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>User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU
encodings. <a href="#refsCESU8">[CESU8]</a> <a href="#refsUTF7">[UTF7]</a>
Modified: source
===================================================================
--- source 2008-02-28 01:29:35 UTC (rev 1270)
+++ source 2008-02-28 08:05:49 UTC (rev 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>
+ 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 ISO-8859-1 as Windows-1252
- is a willful violation of the W3C Character Model specification. <a
- href="#refsCHARMOD">[CHARMOD]</a></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
More information about the Commit-Watchers
mailing list