W3C home > Mailing lists > Public > public-html-diffs@w3.org > September 2011

hixie: Comment out a 'willful violation' that is being fixed in the underlying specs. (whatwg r6575)

From: poot <cvsmail@w3.org>
Date: Fri, 23 Sep 2011 15:49:01 -0400
To: public-html-diffs@w3.org
Message-Id: <E1R7Bk5-0002zd-3r@jay.w3.org>
hixie: Comment out a 'willful violation' that is being fixed in the
underlying specs. (whatwg r6575)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5268&r2=1.5269&f=h
http://html5.org/tools/web-apps-tracker?from=6574&to=6575

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5268
retrieving revision 1.5269
diff -u -d -r1.5268 -r1.5269
--- Overview.html	23 Sep 2011 19:46:28 -0000	1.5268
+++ Overview.html	23 Sep 2011 19:48:47 -0000	1.5269
@@ -56215,15 +56215,6 @@
   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 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">8.2.2.2 </span>Character encodings</h5>
Received on Friday, 23 September 2011 19:49:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 September 2011 19:49:03 GMT