hixie: Clarify the encoding aliases mess. (whatwg r3368)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2500&r2=1.2501&f=hhttp://html5.org/tools/web-apps-tracker?from=3367&to=3368
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2500
retrieving revision 1.2501
diff -u -d -r1.2500 -r1.2501
--- Overview.html 7 Jul 2009 04:31:21 -0000 1.2500
+++ Overview.html 7 Jul 2009 08:26:20 -0000 1.2501
@@ -4503,13 +4503,29 @@
<p class="example">For instance, "GB_2312-80" and "g.b.2312(80)" are
considered equivalent names.</p>
- <hr><p>When a user agent would otherwise use an encoding specified by a
- label given in the first column of the following table to either
- convert content to Unicode characters or convert Unicode characters
- to bytes, it must instead use the encoding given in the cell in the
- second column of the same row. When a byte or sequence of bytes is
- treated differently due to this encoding aliasing, it is said to
- have been <dfn id="misinterpreted-for-compatibility">misinterpreted for compatibility</dfn>.</p>
+<!-- this bit will be replaced by actual alias registrations in due course -->
+
+ <p>In addition, user agents must support the aliases given in the
+ following table, so that labels from the first column are treated as
+ equivalent to the labels given in the corresponding cell from the
+ second column on the same row.</p>
+
+ <table><caption>Additional character encoding aliases</caption>
+ <thead><tr><th> Alias <th> Corresponding encoding <th> References
+ <tbody><tr><td> x-sjis <td> Windows-31J <td>
+ <a href="#references">[SHIFTJIS]</a>
+ <a href="#references">[WIN31J]</a>
+ <tr><td> Windows-932 <td> Windows-31J <td>
+ <a href="#references">[WIN31J]</a>
+ <tr><td> x-x-big5 <td> Big5 <td>
+ <a href="#references">[BIG5]</a>
+ </table><!-- end of bit that will be replaced by actual alias registrations in due course --><hr><p>When a user agent would otherwise use an encoding given in the
+ first column of the following table to either convert content to
+ Unicode characters or convert Unicode characters to bytes, it must
+ instead use the encoding given in the cell in the second column of
+ the same row. When a byte or sequence of bytes is treated
+ differently due to this encoding aliasing, it is said to have been
+ <dfn id="misinterpreted-for-compatibility">misinterpreted for compatibility</dfn>.</p>
<table><caption>Character encoding overrides</caption>
<thead><tr><th> Input encoding <th> Replacement encoding <th> References
@@ -4543,8 +4559,6 @@
<tr><td> US-ASCII <td> Windows-1252 <td>
<a href="#references">[RFC1345]</a>
<a href="#references">[WIN1252]</a>
- <tr><td> x-x-big5 <td> Big5 <td>
- <a href="#references">[BIG5]</a>
</table><p class="note">The requirement to treat certain encodings as other
encodings according to the table above is a <a href="#willful-violation">willful
violation</a> of the W3C Character Model specification, motivated