W3C home > Mailing lists > Public > public-html-diffs@w3.org > June 2009

If you find a declaration while decoding as UTF-16, then ignore it. It can only be correct if it is not giving a different encoding, in which case it's not useful anyway. (credit: kp) (whatwg r3205)

From: poot <cvsmail@w3.org>
Date: Sat, 6 Jun 2009 10:30:16 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090606013017.2AE222BBFE@toro.w3.mag.keio.ac.jp>
If you find a declaration while decoding as UTF-16, then ignore it. It
can only be correct if it is not giving a different encoding, in which
case it's not useful anyway. (credit: kp) (whatwg r3205)

Diffs for this change per section: 
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2358.html#change-the-encoding

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2357&r2=1.2358&f=h
http://html5.org/tools/web-apps-tracker?from=3204&to=3205

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2357
retrieving revision 1.2358
diff -u -d -r1.2357 -r1.2358
--- Overview.html	6 Jun 2009 01:18:15 -0000	1.2357
+++ Overview.html	6 Jun 2009 01:28:46 -0000	1.2358
@@ -53610,6 +53610,12 @@
    pass found that the encoding sniffing algorithm described in the
    earlier section failed to find the right encoding.</li>
 
+   <li>If the encoding that is already being used to interpret the
+   input stream is a UTF-16 encoding, then set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
+   <i>certain</i> and abort these steps. The new encoding is ignored;
+   if it was anything but the same encoding, then it would be clearly
+   incorrect.</li>
+
    <li>If the new encoding is a UTF-16 encoding, change it to
    UTF-8.</li>
Received on Saturday, 6 June 2009 01:30:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:08:57 UTC