[html5] r4367 - [e] (0) Blacklist another encoding. Couldn't find a reference for it though. Fix [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Oct 27 13:09:44 PDT 2009
Author: ianh
Date: 2009-10-27 13:09:40 -0700 (Tue, 27 Oct 2009)
New Revision: 4367
Modified:
complete.html
index
source
Log:
[e] (0) Blacklist another encoding. Couldn't find a reference for it though.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8085
Modified: complete.html
===================================================================
--- complete.html 2009-10-27 19:51:32 UTC (rev 4366)
+++ complete.html 2009-10-27 20:09:40 UTC (rev 4367)
@@ -11908,13 +11908,15 @@
string. Authors should not use such encodings, which are known to
include JIS_C6226-1983<!-- aka JIS-X-0208, x-JIS0208 -->,
JIS_X0212-1990<!-- aka JIS-X-0212 -->, HZ-GB-2312<!-- has crazy
- handling of ASCII "~" -->, encodings based on ISO-2022<!--
+ handling of ASCII "~" -->, JOHAB <!-- a supplementary encoding in KS
+ C 5601-1992 Annex 3 (= KS X 1001:1998 Annex 3) --> (Windows code
+ page 1361), encodings based on ISO-2022<!--
http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html
- -->, and encodings based on EBCDIC. Furthermore, authors must not use
- the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into
- this category, because these encodings were never intended for use
- for Web content.
+ -->, and encodings based on EBCDIC. Furthermore, authors must not
+ use the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall
+ into this category, because these encodings were never intended for
+ use for Web content.
<a href=#refsRFC1345>[RFC1345]</a><!-- for the JIS types -->
<a href=#refsRFC1842>[RFC1842]</a><!-- HZ-GB-2312 -->
<a href=#refsRFC1468>[RFC1468]</a><!-- ISO-2022-JP -->
@@ -11926,7 +11928,7 @@
<a href=#refsUTF7>[UTF7]</a>
<a href=#refsBOCU1>[BOCU1]</a>
<a href=#refsSCSU>[SCSU]</a>
- <!-- no idea what to reference for EBCDIC, so... -->
+ <!-- no idea what to reference for JOHAB or EBCDIC, so... -->
</p>
<p>Authors should not use UTF-32, as the HTML5 encoding detection
Modified: index
===================================================================
--- index 2009-10-27 19:51:32 UTC (rev 4366)
+++ index 2009-10-27 20:09:40 UTC (rev 4367)
@@ -11726,13 +11726,15 @@
string. Authors should not use such encodings, which are known to
include JIS_C6226-1983<!-- aka JIS-X-0208, x-JIS0208 -->,
JIS_X0212-1990<!-- aka JIS-X-0212 -->, HZ-GB-2312<!-- has crazy
- handling of ASCII "~" -->, encodings based on ISO-2022<!--
+ handling of ASCII "~" -->, JOHAB <!-- a supplementary encoding in KS
+ C 5601-1992 Annex 3 (= KS X 1001:1998 Annex 3) --> (Windows code
+ page 1361), encodings based on ISO-2022<!--
http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html
- -->, and encodings based on EBCDIC. Furthermore, authors must not use
- the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into
- this category, because these encodings were never intended for use
- for Web content.
+ -->, and encodings based on EBCDIC. Furthermore, authors must not
+ use the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall
+ into this category, because these encodings were never intended for
+ use for Web content.
<a href=#refsRFC1345>[RFC1345]</a><!-- for the JIS types -->
<a href=#refsRFC1842>[RFC1842]</a><!-- HZ-GB-2312 -->
<a href=#refsRFC1468>[RFC1468]</a><!-- ISO-2022-JP -->
@@ -11744,7 +11746,7 @@
<a href=#refsUTF7>[UTF7]</a>
<a href=#refsBOCU1>[BOCU1]</a>
<a href=#refsSCSU>[SCSU]</a>
- <!-- no idea what to reference for EBCDIC, so... -->
+ <!-- no idea what to reference for JOHAB or EBCDIC, so... -->
</p>
<p>Authors should not use UTF-32, as the HTML5 encoding detection
Modified: source
===================================================================
--- source 2009-10-27 19:51:32 UTC (rev 4366)
+++ source 2009-10-27 20:09:40 UTC (rev 4367)
@@ -12395,13 +12395,15 @@
string. Authors should not use such encodings, which are known to
include JIS_C6226-1983<!-- aka JIS-X-0208, x-JIS0208 -->,
JIS_X0212-1990<!-- aka JIS-X-0212 -->, HZ-GB-2312<!-- has crazy
- handling of ASCII "~" -->, encodings based on ISO-2022<!--
+ handling of ASCII "~" -->, JOHAB <!-- a supplementary encoding in KS
+ C 5601-1992 Annex 3 (= KS X 1001:1998 Annex 3) --> (Windows code
+ page 1361), encodings based on ISO-2022<!--
http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html
- -->, and encodings based on EBCDIC. Furthermore, authors must not use
- the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into
- this category, because these encodings were never intended for use
- for Web content.
+ -->, and encodings based on EBCDIC. Furthermore, authors must not
+ use the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall
+ into this category, because these encodings were never intended for
+ use for Web content.
<a href="#refsRFC1345">[RFC1345]</a><!-- for the JIS types -->
<a href="#refsRFC1842">[RFC1842]</a><!-- HZ-GB-2312 -->
<a href="#refsRFC1468">[RFC1468]</a><!-- ISO-2022-JP -->
@@ -12413,7 +12415,7 @@
<a href="#refsUTF7">[UTF7]</a>
<a href="#refsBOCU1">[BOCU1]</a>
<a href="#refsSCSU">[SCSU]</a>
- <!-- no idea what to reference for EBCDIC, so... -->
+ <!-- no idea what to reference for JOHAB or EBCDIC, so... -->
</p>
<p>Authors should not use UTF-32, as the HTML5 encoding detection
More information about the Commit-Watchers
mailing list