W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2009

html5/spec Overview.html,1.3392,1.3393

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 21 Oct 2009 09:37:48 +0000
To: public-html-commits@w3.org
Message-Id: <E1N0Xdc-0004gg-64@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv17999

Modified Files:
	Overview.html 
Log Message:
Mention that sniffing the encoding violates HTTP. (whatwg r4248)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3392
retrieving revision 1.3393
diff -u -d -r1.3392 -r1.3393
--- Overview.html	21 Oct 2009 09:28:39 -0000	1.3392
+++ Overview.html	21 Oct 2009 09:37:44 -0000	1.3393
@@ -54638,6 +54638,15 @@
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class="note">This algorithm is a <a href="#willful-violation">willful violation</a>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <a href="#character-encoding-declaration">character
+  encoding declaration</a> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <a href="#character-encoding-declaration">character encoding declaration</a> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a href="#refsHTTP">[HTTP]</a> <a href="#refsRFC2046">[RFC2046]</a></p>
+
 
   <h5 id="character-encodings-0"><span class="secno">9.2.2.2 </span>Character encodings</h5><p class="XXX annotation"><b>Status: </b><i>Working draft</i></p>
 
Received on Wednesday, 21 October 2009 09:37:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 October 2009 09:37:52 GMT