[html5] r3331 - [] (0) Allow Shift_JIS to be treated as ASCII-compatible. (bug 6858)

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-28 03:10:34 -0700 (Sun, 28 Jun 2009)
New Revision: 3331

Modified:
   index
   source
Log:
[] (0) Allow Shift_JIS to be treated as ASCII-compatible. (bug 6858)

Modified: index
===================================================================
--- index	2009-06-28 08:26:58 UTC (rev 3330)
+++ index	2009-06-28 10:10:34 UTC (rev 3331)
@@ -1705,9 +1705,21 @@
   the set 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?
-  -->. <a href=#refsRFC1345>[RFC1345]</a></p>
+  -->, ignoring cases where those bytes would be part of multibyte
+  sequences. <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.</p>
 
+  <!--
+   We'll have to change that if anyone comes up with a way to have a
+   document that is valid as two different encodings at once, with
+   different <meta charset> elements applying in each case.
+  -->
+
+
   <h4 id=resources><span class=secno>2.1.6 </span>Resources</h4>
 
   <p>The specification uses the term <dfn title="">supported</dfn> when referring

Modified: source
===================================================================
--- source	2009-06-28 08:26:58 UTC (rev 3330)
+++ source	2009-06-28 10:10:34 UTC (rev 3331)
@@ -730,9 +730,21 @@
   the set 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?
-  -->. <a href="#refsRFC1345">[RFC1345]</a></p>
+  -->, ignoring cases where those bytes would be part of multibyte
+  sequences. <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.</p>
 
+  <!--
+   We'll have to change that if anyone comes up with a way to have a
+   document that is valid as two different encodings at once, with
+   different <meta charset> elements applying in each case.
+  -->
+
+
   <h4>Resources</h4>
 
   <p>The specification uses the term <dfn title="">supported</dfn> when referring