Allow Shift_JIS to be treated as ASCII-compatible. (bug 6858) (whatwg r3331)

Allow Shift_JIS to be treated as ASCII-compatible. (bug 6858) (whatwg
r3331)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6858

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2470&r2=1.2471&f=h
http://html5.org/tools/web-apps-tracker?from=3330&to=3331

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2470
retrieving revision 1.2471
diff -u -d -r1.2470 -r1.2471
--- Overview.html 28 Jun 2009 08:27:04 -0000 1.2470
+++ Overview.html 28 Jun 2009 10:10:40 -0000 1.2471
@@ -1540,7 +1540,15 @@
   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="#references">[RFC1345]</a><h4 id="resources"><span class="secno">2.1.6 </span>Resources</h4><p>The specification uses the term <dfn title="">supported</dfn> when referring
+  -->, ignoring cases where those bytes would be part of multibyte
+  sequences. <a href="#references">[RFC1345]</a><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
   to whether a user agent has an implementation capable of decoding
   the semantics of an external resource. A format or type is said to
   be <i>supported</i> if the implementation can process an external

Received on Sunday, 28 June 2009 10:11:38 UTC