- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 28 Jun 2009 10:53:52 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv5327 Modified Files: Overview.html Log Message: Elaborate on the rules for ASCII-compatible encodings (see last checkin). (credit: pt) (whatwg r3332) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2471 retrieving revision 1.2472 diff -u -d -r1.2471 -r1.2472 --- Overview.html 28 Jun 2009 10:10:40 -0000 1.2471 +++ Overview.html 28 Jun 2009 10:53:50 -0000 1.2472 @@ -1540,11 +1540,11 @@ 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 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 + -->, ignoring the second and later bytes 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><!-- + interpretation as ASCII. It excludes such encodings as UTF-7, + 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 document that is valid as two different encodings at once, with different <meta charset> elements applying in each case.
Received on Sunday, 28 June 2009 10:54:02 UTC