[html5] r3335 - [c] (0) Yet more tinkering of the ASCII-compatible definition. Also, discourage [...]

whatwg at whatwg.org whatwg at whatwg.org
Sun Jun 28 17:35:22 PDT 2009


Author: ianh
Date: 2009-06-28 17:35:21 -0700 (Sun, 28 Jun 2009)
New Revision: 3335

Modified:
   index
   source
Log:
[c] (0) Yet more tinkering of the ASCII-compatible definition. Also, discourage ISO-2022-* due to the potential for XSS.

Modified: index
===================================================================
--- index	2009-06-28 11:28:22 UTC (rev 3334)
+++ index	2009-06-29 00:35:21 UTC (rev 3335)
@@ -67,7 +67,7 @@
   <div class=head>
    <p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <h1>HTML 5</h1>
-   <h2 class="no-num no-toc" id=draft-standard-—-date:-01-jan-1901>Draft Standard — 28 June 2009</h2>
+   <h2 class="no-num no-toc" id=draft-standard-—-date:-01-jan-1901>Draft Standard — 29 June 2009</h2>
    <p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -1700,19 +1700,20 @@
 
   <h4 id=character-encodings><span class=secno>2.1.5 </span>Character encodings</h4>
 
-  <p>An <dfn id=ascii-compatible-character-encoding>ASCII-compatible character encoding</dfn> is one in which
-  bytes 0x09, 0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F,
-  0x41 - 0x5A, and 0x61 - 0x7A<!-- is that list ok? do any character
-  sets we want to support do things outside that range?  -->, ignoring
-  bytes that are the second and later bytes of multibyte sequences,
-  map to the same Unicode characters as those bytes in ANSI_X3.4-1968
-  (US-ASCII). <a href=#refsRFC1345>[RFC1345]</a></p>
+  <p>An <dfn id=ascii-compatible-character-encoding>ASCII-compatible character encoding</dfn> is a
+  single-byte or variable-length encoding in which the bytes 0x09,
+  0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F, 0x41 - 0x5A,
+  and 0x61 - 0x7A<!-- is that list ok? do any character sets we want
+  to support do things outside that range?  -->, ignoring bytes that
+  are the second and later bytes of multibyte sequences, all
+  correspond to single-byte sequences that map to the same Unicode
+  characters as those bytes in ANSI_X3.4-1968 (US-ASCII). <a href=#refsRFC1345>[RFC1345]</a></p>
 
   <p class=note>This includes such exotic encodings as Shift_JIS and
   variants of ISO-2022, even though it is possible for bytes like 0x70
   to be part of longer sequences that are unrelated to their
   interpretation as ASCII. It excludes such encodings as UTF-7,
-  UTF-16, HZ-GB-2312, GSM03.38, and EBCDIC variants.</p>
+  UTF-8+names, UTF-16, HZ-GB-2312, GSM03.38, and EBCDIC variants.</p>
 
   <!--
    We'll have to change that if anyone comes up with a way to have a
@@ -10464,10 +10465,24 @@
   <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), and encodings based
-  on EBCDIC. Authors should not use UTF-32. Authors must not use the
-  CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a href=#refsRFC1345>[RFC1345]</a><!-- for the JIS types --> <a href=#refsUTF32>[UTF32]</a> <a href=#refsCESU8>[CESU8]</a> <a href=#refsUTF7>[UTF7]</a> <a href=#refsBOCU1>[BOCU1]</a> <a href=#refsSCSU>[SCSU]</a></p> <!-- no idea what to reference for
-  EBCDIC, so... -->
+  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), encodings based on
+  ISO-2022<!-- http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422
+  -->, and encodings based on EBCDIC. Authors should not use
+  UTF-32. Authors must not use the CESU-8, UTF-7, BOCU-1 and SCSU
+  encodings.
+  <a href=#refsRFC1345>[RFC1345]</a><!-- for the JIS types -->
+  <a href=#refsRFC1468>[RFC1468]</a><!-- ISO-2022-JP -->
+  <a href=#refsRFC2237>[RFC2237]</a><!-- ISO-2022-JP-1 -->
+  <a href=#refsRFC1554>[RFC1554]</a><!-- ISO-2022-JP-2 -->
+  <a href=#refsRFC1922>[RFC1922]</a><!-- ISO-2022-CN and ISO-2022-CN-EXT -->
+  <a href=#refsRFC1557>[RFC1557]</a><!-- ISO-2022-KR -->
+  <a href=#refsUTF32>[UTF32]</a>
+  <a href=#refsCESU8>[CESU8]</a>
+  <a href=#refsUTF7>[UTF7]</a>
+  <a href=#refsBOCU1>[BOCU1]</a>
+  <a href=#refsSCSU>[SCSU]</a>
+  <!-- no idea what to reference for EBCDIC, so... -->
+  </p>
 
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
@@ -48853,6 +48868,7 @@
   <p class=XXX>...</p>
 
 
+
   <div class=impl>
 
   <h4 id=appcache><span class=secno>6.9.2 </span>Application caches</h4>

Modified: source
===================================================================
--- source	2009-06-28 11:28:22 UTC (rev 3334)
+++ source	2009-06-29 00:35:21 UTC (rev 3335)
@@ -725,19 +725,21 @@
 
   <h4>Character encodings</h4>
 
-  <p>An <dfn>ASCII-compatible character encoding</dfn> is one in which
-  bytes 0x09, 0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F,
-  0x41 - 0x5A, and 0x61 - 0x7A<!-- is that list ok? do any character
-  sets we want to support do things outside that range?  -->, ignoring
-  bytes that are the second and later bytes of multibyte sequences,
-  map to the same Unicode characters as those bytes in ANSI_X3.4-1968
-  (US-ASCII). <a href="#refsRFC1345">[RFC1345]</a></p>
+  <p>An <dfn>ASCII-compatible character encoding</dfn> is a
+  single-byte or variable-length encoding in which the bytes 0x09,
+  0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F, 0x41 - 0x5A,
+  and 0x61 - 0x7A<!-- is that list ok? do any character sets we want
+  to support do things outside that range?  -->, ignoring bytes that
+  are the second and later bytes of multibyte sequences, all
+  correspond to single-byte sequences that map to the same Unicode
+  characters as those bytes in ANSI_X3.4-1968 (US-ASCII). <a
+  href="#refsRFC1345">[RFC1345]</a></p>
 
   <p class="note">This includes such exotic encodings as Shift_JIS and
   variants of ISO-2022, even though it is possible for bytes like 0x70
   to be part of longer sequences that are unrelated to their
   interpretation as ASCII. It excludes such encodings as UTF-7,
-  UTF-16, HZ-GB-2312, GSM03.38, and EBCDIC variants.</p>
+  UTF-8+names, UTF-16, HZ-GB-2312, GSM03.38, and EBCDIC variants.</p>
 
   <!--
    We'll have to change that if anyone comes up with a way to have a
@@ -10943,14 +10945,24 @@
   <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), and encodings based
-  on EBCDIC. Authors should not use UTF-32. Authors must not use the
-  CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a
-  href="#refsRFC1345">[RFC1345]</a><!-- for the JIS types --> <a
-  href="#refsUTF32">[UTF32]</a> <a href="#refsCESU8">[CESU8]</a> <a
-  href="#refsUTF7">[UTF7]</a> <a href="#refsBOCU1">[BOCU1]</a> <a
-  href="#refsSCSU">[SCSU]</a></p> <!-- no idea what to reference for
-  EBCDIC, so... -->
+  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), encodings based on
+  ISO-2022<!-- http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422
+  -->, and encodings based on EBCDIC. Authors should not use
+  UTF-32. Authors must not use the CESU-8, UTF-7, BOCU-1 and SCSU
+  encodings.
+  <a href="#refsRFC1345">[RFC1345]</a><!-- for the JIS types -->
+  <a href="#refsRFC1468">[RFC1468]</a><!-- ISO-2022-JP -->
+  <a href="#refsRFC2237">[RFC2237]</a><!-- ISO-2022-JP-1 -->
+  <a href="#refsRFC1554">[RFC1554]</a><!-- ISO-2022-JP-2 -->
+  <a href="#refsRFC1922">[RFC1922]</a><!-- ISO-2022-CN and ISO-2022-CN-EXT -->
+  <a href="#refsRFC1557">[RFC1557]</a><!-- ISO-2022-KR -->
+  <a href="#refsUTF32">[UTF32]</a>
+  <a href="#refsCESU8">[CESU8]</a>
+  <a href="#refsUTF7">[UTF7]</a>
+  <a href="#refsBOCU1">[BOCU1]</a>
+  <a href="#refsSCSU">[SCSU]</a>
+  <!-- no idea what to reference for EBCDIC, so... -->
+  </p>
 
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
@@ -55677,6 +55689,7 @@
   <p class="XXX">...</p>
 
 
+
   <div class="impl">
 
   <h4 id="appcache">Application caches</h4>




More information about the Commit-Watchers mailing list