- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 27 Oct 2009 20:09:46 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv26593 Modified Files: Overview.html Log Message: Blacklist another encoding. Couldn't find a reference for it though. (whatwg r4367) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3499 retrieving revision 1.3500 diff -u -d -r1.3499 -r1.3500 --- Overview.html 27 Oct 2009 19:51:36 -0000 1.3499 +++ Overview.html 27 Oct 2009 20:09:43 -0000 1.3500 @@ -10427,13 +10427,15 @@ string. Authors should not use such encodings, which are known to include JIS_C6226-1983<!-- aka JIS-X-0208, x-JIS0208 -->, JIS_X0212-1990<!-- aka JIS-X-0212 -->, HZ-GB-2312<!-- has crazy - handling of ASCII "~" -->, encodings based on ISO-2022<!-- + handling of ASCII "~" -->, JOHAB <!-- a supplementary encoding in KS + C 5601-1992 Annex 3 (= KS X 1001:1998 Annex 3) --> (Windows code + page 1361), encodings based on ISO-2022<!-- http://krijnhoetmer.nl/irc-logs/whatwg/20090628#l-422 and http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-October/023797.html - -->, and encodings based on EBCDIC. Furthermore, authors must not use - the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall into - this category, because these encodings were never intended for use - for Web content. + -->, and encodings based on EBCDIC. Furthermore, authors must not + use the CESU-8, UTF-7, BOCU-1 and SCSU encodings, which also fall + into this category, because these encodings were never intended for + use for Web content. <a href="#refsRFC1345">[RFC1345]</a><!-- for the JIS types --> <a href="#refsRFC1842">[RFC1842]</a><!-- HZ-GB-2312 --> <a href="#refsRFC1468">[RFC1468]</a><!-- ISO-2022-JP --> @@ -10445,7 +10447,7 @@ <a href="#refsUTF7">[UTF7]</a> <a href="#refsBOCU1">[BOCU1]</a> <a href="#refsSCSU">[SCSU]</a> - <!-- no idea what to reference for EBCDIC, so... --> + <!-- no idea what to reference for JOHAB or EBCDIC, so... --> <p>Authors should not use UTF-32, as the HTML5 encoding detection algorithms intentionally do not distinguish it from UTF-16. <a href="#refsUNICODE">[UNICODE]</a><p class="note">Using non-UTF-8 encodings can have unexpected results on form submission and URL encodings, which use the
Received on Tuesday, 27 October 2009 20:12:17 UTC