[html5] r3334 - [e] (0) Yet more attempts to make the ASCII-compatible definition clear.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-28 04:28:22 -0700 (Sun, 28 Jun 2009)
New Revision: 3334

Modified:
   index
   source
Log:
[e] (0) Yet more attempts to make the ASCII-compatible definition clear.

Modified: index
===================================================================
--- index	2009-06-28 10:57:08 UTC (rev 3333)
+++ index	2009-06-28 11:28:22 UTC (rev 3334)
@@ -1700,12 +1700,13 @@
 
   <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 that is
-  a superset of US-ASCII (specifically, ANSI_X3.4-1968) for bytes in
-  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?
-  -->, ignoring the second and later bytes of multibyte sequences. <a href=#refsRFC1345>[RFC1345]</a></p>
+  <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 class=note>This includes such exotic encodings as Shift_JIS and
   variants of ISO-2022, even though it is possible for bytes like 0x70

Modified: source
===================================================================
--- source	2009-06-28 10:57:08 UTC (rev 3333)
+++ source	2009-06-28 11:28:22 UTC (rev 3334)
@@ -725,13 +725,13 @@
 
   <h4>Character encodings</h4>
 
-  <p>An <dfn>ASCII-compatible character encoding</dfn> is one that is
-  a superset of US-ASCII (specifically, ANSI_X3.4-1968) for bytes in
-  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?
-  -->, ignoring the second and later bytes of multibyte sequences. <a
-  href="#refsRFC1345">[RFC1345]</a></p>
+  <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 class="note">This includes such exotic encodings as Shift_JIS and
   variants of ISO-2022, even though it is possible for bytes like 0x70