[html5] r4304 - [e] (0) Refer to these encodings by their IANA names only to avoid confusing the [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-23 01:56:42 -0700 (Fri, 23 Oct 2009)
New Revision: 4304

Modified:
   complete.html
   index
   source
Log:
[e] (0) Refer to these encodings by their IANA names only to avoid confusing them with character sets.

Modified: complete.html
===================================================================
--- complete.html	2009-10-23 07:51:21 UTC (rev 4303)
+++ complete.html	2009-10-23 08:56:42 UTC (rev 4304)
@@ -11889,9 +11889,9 @@
   state</a>, then the character encoding used must be an
   <a href=#ascii-compatible-character-encoding>ASCII-compatible character encoding</a>.</p>
 
-  <p>Authors should not use JIS-X-0208 <!-- x-JIS0208 -->
-  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), HZ-GB-2312<!-- has
-  crazy handling of ASCII "~" -->, encodings based on ISO-2022<!--
+  <p>Authors should not use 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<!--
   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. Authors should not use UTF-32.

Modified: index
===================================================================
--- index	2009-10-23 07:51:21 UTC (rev 4303)
+++ index	2009-10-23 08:56:42 UTC (rev 4304)
@@ -11699,9 +11699,9 @@
   state</a>, then the character encoding used must be an
   <a href=#ascii-compatible-character-encoding>ASCII-compatible character encoding</a>.</p>
 
-  <p>Authors should not use JIS-X-0208 <!-- x-JIS0208 -->
-  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), HZ-GB-2312<!-- has
-  crazy handling of ASCII "~" -->, encodings based on ISO-2022<!--
+  <p>Authors should not use 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<!--
   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. Authors should not use UTF-32.

Modified: source
===================================================================
--- source	2009-10-23 07:51:21 UTC (rev 4303)
+++ source	2009-10-23 08:56:42 UTC (rev 4304)
@@ -12384,9 +12384,9 @@
   state</span>, then the character encoding used must be an
   <span>ASCII-compatible character encoding</span>.</p>
 
-  <p>Authors should not use JIS-X-0208 <!-- x-JIS0208 -->
-  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), HZ-GB-2312<!-- has
-  crazy handling of ASCII "~" -->, encodings based on ISO-2022<!--
+  <p>Authors should not use 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<!--
   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. Authors should not use UTF-32.