[html5] r6575 - [e] (0) Comment out a 'willful violation' that is being fixed in the underlying [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-09-23 12:46:21 -0700 (Fri, 23 Sep 2011)
New Revision: 6575

Modified:
   complete.html
   index
   source
Log:
[e] (0) Comment out a 'willful violation' that is being fixed in the underlying specs.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13354

Modified: complete.html
===================================================================
--- complete.html	2011-09-23 19:44:01 UTC (rev 6574)
+++ complete.html	2011-09-23 19:46:21 UTC (rev 6575)
@@ -83877,16 +83877,18 @@
   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>
+<!--(removed this since the specs are being changed)
+  <p class="note">This algorithm is a <span>willful violation</span>
   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,
+  assumed to be ISO-8859-1 in the absence of a <span>character
+  encoding declaration</span> 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
+  absence of a <span>character encoding declaration</span> 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>
+  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>13.2.2.2 </span>Character encodings</h5>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252

Modified: index
===================================================================
--- index	2011-09-23 19:44:01 UTC (rev 6574)
+++ index	2011-09-23 19:46:21 UTC (rev 6575)
@@ -79302,16 +79302,18 @@
   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>
+<!--(removed this since the specs are being changed)
+  <p class="note">This algorithm is a <span>willful violation</span>
   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,
+  assumed to be ISO-8859-1 in the absence of a <span>character
+  encoding declaration</span> 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
+  absence of a <span>character encoding declaration</span> 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>
+  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>11.2.2.2 </span>Character encodings</h5>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252

Modified: source
===================================================================
--- source	2011-09-23 19:44:01 UTC (rev 6574)
+++ source	2011-09-23 19:46:21 UTC (rev 6575)
@@ -95037,6 +95037,7 @@
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+<!--(removed this since the specs are being changed)
   <p class="note">This algorithm is a <span>willful violation</span>
   of the HTTP specification, which requires that the encoding be
   assumed to be ISO-8859-1 in the absence of a <span>character
@@ -95046,8 +95047,8 @@
   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>Character encodings</h5>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252