[html5] r3204 - [] (0) When parsing UTF-16 tentatively, if the new encoding is UTF-16, then don' [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jun 5 18:18:10 PDT 2009
Author: ianh
Date: 2009-06-05 18:18:08 -0700 (Fri, 05 Jun 2009)
New Revision: 3204
Modified:
index
source
Log:
[] (0) When parsing UTF-16 tentatively, if the new encoding is UTF-16, then don't treat it as UTF-8.
Modified: index
===================================================================
--- index 2009-06-06 00:19:13 UTC (rev 3203)
+++ index 2009-06-06 01:18:08 UTC (rev 3204)
@@ -59741,10 +59741,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
@@ -59754,6 +59751,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
@@ -71009,6 +71009,7 @@
Justin Sinclair,
Kai Hendry,
Kartikaya Gupta,
+ Kornél Pál,
Kristof Zelechovski,
黒澤剛志 (KUROSAWA Takeshi),
Kyle Hofmann<!-- Ozob -->,
Modified: source
===================================================================
--- source 2009-06-06 00:19:13 UTC (rev 3203)
+++ source 2009-06-06 01:18:08 UTC (rev 3204)
@@ -73417,9 +73417,6 @@
<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
that is already being used to interpret the input stream, then set
the <span title="concept-encoding-confidence">confidence</span> to
@@ -73430,6 +73427,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
@@ -83715,6 +83715,7 @@
Justin Sinclair,
Kai Hendry,
Kartikaya Gupta,
+ Kornél Pál,
Kristof Zelechovski,
黒澤剛志 (KUROSAWA Takeshi),
Kyle Hofmann<!-- Ozob -->,
More information about the Commit-Watchers
mailing list