[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 git-svn-id: http://svn.whatwg.org/webapps@4367 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 27, 2009 · 3c534ff · 3c534ff
1 parent 10ce3df
commit 3c534ff
Show file tree

Hide file tree

Showing 3 changed files with 24 additions and 18 deletions.
diff --git a/complete.html b/complete.html
@@ -11908,13 +11908,15 @@ <h5 id=charset><span class=secno>4.2.5.5 </span>Specifying the document's charac
   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 @@ <h5 id=charset><span class=secno>4.2.5.5 </span>Specifying the document's charac
   <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

diff --git a/index b/index
@@ -11726,13 +11726,15 @@ people expect to have work and what is necessary.
   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 @@ people expect to have work and what is necessary.
   <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

diff --git a/source b/source
@@ -12395,13 +12395,15 @@ people expect to have work and what is necessary.
   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 @@ people expect to have work and what is necessary.
   <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