- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 29 Jun 2009 23:29:17 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv10495 Modified Files: Overview.html Log Message: Be less judgmental about certain encodings... (bug 6858) (whatwg r3341) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2479 retrieving revision 1.2480 diff -u -d -r1.2479 -r1.2480 --- Overview.html 29 Jun 2009 11:24:24 -0000 1.2479 +++ Overview.html 29 Jun 2009 23:29:14 -0000 1.2480 @@ -1551,11 +1551,12 @@ to support do things outside that range? -->, ignoring bytes that are the second and later bytes of multibyte sequences, all correspond to single-byte sequences that map to the same Unicode - characters as those bytes in ANSI_X3.4-1968 (US-ASCII). <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. It excludes such encodings as UTF-7, - UTF-8+names, UTF-16, HZ-GB-2312, GSM03.38, and EBCDIC variants.</p><!-- + characters as those bytes in ANSI_X3.4-1968 (US-ASCII). <a href="#references">[RFC1345]</a><p class="note">This includes such encodings as Shift_JIS and + variants of ISO-2022, even though it is possible in this encodings + for bytes like 0x70 to be part of longer sequences that are + unrelated to their 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 Monday, 29 June 2009 23:29:26 UTC