[html5] r1669 - /
whatwg at whatwg.org
whatwg at whatwg.org
Thu May 22 05:01:28 PDT 2008
Author: ianh
Date: 2008-05-22 05:01:28 -0700 (Thu, 22 May 2008)
New Revision: 1669
Modified:
index
source
Log:
[e] (0) Fold the encoding alias rules into one table, since it turns out the -11 thing was already there and I didn't notice...
Modified: index
===================================================================
--- index 2008-05-22 11:48:37 UTC (rev 1668)
+++ index 2008-05-22 12:01:28 UTC (rev 1669)
@@ -42047,18 +42047,10 @@
all the IANA-registered aliases. <a
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; 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="#parse1" title="parse
- error">parse errors</a>.
-
- <p>In addition, when a user agent would otherwise use an encoding given in
- the first column of the following table, it must instead use the encoding
- given in the cell in the second column of the same row. Any bytes that are
- treated differently due to this encoding aliasing must be considered <a
+ <p>When a user agent would otherwise use an encoding given in the first
+ column of the following table, it must instead use the encoding given in
+ the cell in the second column of the same row. Any bytes that are treated
+ differently due to this encoding aliasing must be considered <a
href="#parse1" title="parse error">parse errors</a>.
<table>
@@ -42098,11 +42090,35 @@
<td> GBK
- <td> <a href="#refsRFC1345">[RFC1345]</a> <a
+ <td> <a
+ href="#refsRFC1345">[RFC1345]</a><!-- XXX consider more direct reference? -->
+ <a
href="#refsGBK">[GBK]</a><!-- http://www.iana.org/assignments/charset-reg/GBK -->
<tr>
+ <td> ISO-8859-1
+
+ <td> Windows-1252
+
+ <td> <a
+ href="#refsRFC1345">[RFC1345]</a><!-- XXX consider more direct reference? -->
+ <a
+ href="#refsWin1252">[WIN1252]</a><!-- http://www.microsoft.com/globaldev/reference/sbcs/1252.htm -->
+
+
+ <tr>
+ <td> ISO-8859-11
+
+ <td> Windows-874
+
+ <td> <a
+ href="#refsRFC1345">[RFC1345]</a><!-- get reference from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263 -->
+ <a
+ href="#refsWin874">[WIN874]</a><!-- http://www.microsoft.com/globaldev/reference/sbcs/874.mspx -->
+
+
+ <tr>
<td> KS_C_5601-1987
<td> Windows-949
@@ -42116,8 +42132,7 @@
<td> Windows-874
- <td> <!-- XXX how about ISO-8859-11? --> <a
- href="#refsTIS620">[RFC1345]</a>
+ <td> <a href="#refsTIS620">[RFC1345]</a>
<!-- http://www.nectec.or.th/it-standards/std620/std620.htm --> <a
href="#refsWin874">[WIN874]</a><!-- http://www.microsoft.com/globaldev/reference/sbcs/874.mspx -->
@@ -42130,9 +42145,8 @@
<td> <a href="#BIG5">[BIG5]</a> <!-- XXX ? -->
</table>
- <p class=note>The requirement to treat certain ISO-8859 encodings as
- Windows encodings, and the requirement to alias certain encodings
- according to the table above, are willful violations of the W3C Character
+ <p class=note>The requirement to treat certain encodings as other encodings
+ according to the table above 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
Modified: source
===================================================================
--- source 2008-05-22 11:48:37 UTC (rev 1668)
+++ source 2008-05-22 12:01:28 UTC (rev 1669)
@@ -39711,19 +39711,11 @@
should support all the IANA-registered aliases. <a
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; 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>In addition, when a user agent would otherwise use an encoding
- given in the first column of the following table, it must instead
- use the encoding given in the cell in the second column of the same
- row. Any bytes that are treated differently due to this encoding
- aliasing must be considered <span title="parse error">parse
+ <p>When a user agent would otherwise use an encoding given in the
+ first column of the following table, it must instead use the
+ encoding given in the cell in the second column of the same row. Any
+ bytes that are treated differently due to this encoding aliasing
+ must be considered <span title="parse error">parse
errors</span>.</p>
<table>
@@ -39739,12 +39731,18 @@
<a href="#refsGB2312">[GB2312]</a><!-- XXX ? -->
<a href="#refsGBK">[GBK]</a><!-- http://www.iana.org/assignments/charset-reg/GBK -->
<tr> <td> GB_2312-80 <td> GBK <td>
- <a href="#refsRFC1345">[RFC1345]</a>
+ <a href="#refsRFC1345">[RFC1345]</a><!-- XXX consider more direct reference? -->
<a href="#refsGBK">[GBK]</a><!-- http://www.iana.org/assignments/charset-reg/GBK -->
+ <tr> <td> ISO-8859-1 <td> Windows-1252 <td>
+ <a href="#refsRFC1345">[RFC1345]</a><!-- XXX consider more direct reference? -->
+ <a href="#refsWin1252">[WIN1252]</a><!-- http://www.microsoft.com/globaldev/reference/sbcs/1252.htm -->
+ <tr> <td> ISO-8859-11 <td> Windows-874 <td>
+ <a href="#refsRFC1345">[RFC1345]</a><!-- get reference from http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263 -->
+ <a href="#refsWin874">[WIN874]</a><!-- http://www.microsoft.com/globaldev/reference/sbcs/874.mspx -->
<tr> <td> KS_C_5601-1987 <td> Windows-949 <td>
<a href="#refsRFC1345">[RFC1345]</a>
<a href="#refsWin949">[WIN949]</a><!-- http://www.microsoft.com/globaldev/reference/dbcs/949.mspx -->
- <tr> <td> TIS-620 <td> Windows-874 <td> <!-- XXX how about ISO-8859-11? -->
+ <tr> <td> TIS-620 <td> Windows-874 <td>
<a href="#refsTIS620">[RFC1345]</a> <!-- http://www.nectec.or.th/it-standards/std620/std620.htm -->
<a href="#refsWin874">[WIN874]</a><!-- http://www.microsoft.com/globaldev/reference/sbcs/874.mspx -->
<tr> <td> x-x-big5 <td> Big5 <td>
@@ -39752,10 +39750,9 @@
</tbody>
</table>
- <p class="note">The requirement to treat certain ISO-8859 encodings
- as Windows encodings, and the requirement to alias certain encodings
- according to the table above, are willful violations of the W3C
- Character Model specification. <a
+ <p class="note">The requirement to treat certain encodings as other
+ encodings according to the table above 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
More information about the Commit-Watchers
mailing list