- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 06 Jun 2009 01:18:18 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv30777 Modified Files: Overview.html Log Message: When parsing UTF-16 tentatively, if the new encoding is UTF-16, then don't treat it as UTF-8. (whatwg r3204) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2356 retrieving revision 1.2357 diff -u -d -r1.2356 -r1.2357 --- Overview.html 6 Jun 2009 00:19:18 -0000 1.2356 +++ Overview.html 6 Jun 2009 01:18:15 -0000 1.2357 @@ -53600,10 +53600,7 @@ failed to find an encoding, or if it found an encoding that was not the actual encoding of the file.</p> - <ol><li>If the new encoding is a UTF-16 encoding, change it to - UTF-8.</li> - - <li>If the new encoding is identical or equivalent to the encoding + <ol><li>If the new encoding is identical or equivalent to the encoding that is already being used to interpret the input stream, then set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to <i>certain</i> and abort these steps. This happens when the @@ -53613,6 +53610,9 @@ pass found that the encoding sniffing algorithm described in the earlier section failed to find the right encoding.</li> + <li>If the new encoding is a UTF-16 encoding, change it to + UTF-8.</li> + <li>If all the bytes up to the last byte converted by the current decoder have the same Unicode interpretations in both the current encoding and the new encoding, and if the user agent supports @@ -64762,6 +64762,7 @@ Justin Sinclair, Kai Hendry, Kartikaya Gupta, + Kornél Pál, Kristof Zelechovski, 黒澤剛志 (KUROSAWA Takeshi), Kyle Hofmann<!-- Ozob -->,
Received on Saturday, 6 June 2009 01:18:23 UTC