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

git-svn-id: http://svn.whatwg.org/webapps@3331 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 28, 2009 · bdae7b7 · bdae7b7
1 parent de42b9a
commit bdae7b7
Show file tree

Hide file tree

Showing 2 changed files with 26 additions and 2 deletions.
diff --git a/index b/index
@@ -1705,7 +1705,19 @@ a.<a href=#dom-uda-protocol title=dom-uda-protocol>protocol</a> = 'https'; // ch
   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>

diff --git a/source b/source
@@ -730,7 +730,19 @@ a.<span title="dom-uda-protocol">protocol</span> = 'https'; // change just the s
   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>