[html5] r3932 - [e] (0) clarity Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7431

[whatwg at whatwg.org]

Author: ianh
Date: 2009-09-21 04:16:00 -0700 (Mon, 21 Sep 2009)
New Revision: 3932

Modified:
   index
   source
Log:
[e] (0) clarity
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7431

Modified: index
===================================================================
--- index	2009-09-21 10:57:52 UTC (rev 3931)
+++ index	2009-09-21 11:16:00 UTC (rev 3932)
@@ -52009,14 +52009,15 @@
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.</p>
 
-  <p class=note>This is a <a href=#willful-violation title="willful violation">willful
-  double violation</a> of RFC 2046, which requires all <code title="">text/*</code> types to support an open-ended set of
-  character encodings and only allows CRLF line breaks. These
-  requirements, however, are outdated; UTF-8 is now widely used, such
-  that supporting other encodings is no longer necessary, and use of
-  CR, LF, and CRLF line breaks is commonly supported and indeed
-  sometimes CRLF is <em>not</em> supported by text editors. <a href=#refsRFC2046>[RFC2046]</a></p> <!-- also RFC 2045 for charset
-  -->
+  <p class=note>This is a <a href=#willful-violation>willful violation</a> of two
+  aspects of RFC 2046, which requires all <code title="">text/*</code>
+  types to support an open-ended set of character encodings and only
+  allows CRLF line breaks. These requirements, however, are outdated;
+  UTF-8 is now widely used, such that supporting other encodings is no
+  longer necessary, and use of CR, LF, and CRLF line breaks is
+  commonly supported and indeed sometimes CRLF is <em>not</em>
+  supported by text editors. <a href=#refsRFC2046>[RFC2046]</a></p>
+  <!-- also RFC 2045 for charset -->
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string

Modified: source
===================================================================
--- source	2009-09-21 10:57:52 UTC (rev 3931)
+++ source	2009-09-21 11:16:00 UTC (rev 3932)
@@ -58760,16 +58760,15 @@
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.</p>
 
-  <p class="note">This is a <span title="willful violation">willful
-  double violation</span> of RFC 2046, which requires all <code
-  title="">text/*</code> types to support an open-ended set of
-  character encodings and only allows CRLF line breaks. These
-  requirements, however, are outdated; UTF-8 is now widely used, such
-  that supporting other encodings is no longer necessary, and use of
-  CR, LF, and CRLF line breaks is commonly supported and indeed
-  sometimes CRLF is <em>not</em> supported by text editors. <a
-  href="#refsRFC2046">[RFC2046]</a></p> <!-- also RFC 2045 for charset
-  -->
+  <p class="note">This is a <span>willful violation</span> of two
+  aspects of RFC 2046, which requires all <code title="">text/*</code>
+  types to support an open-ended set of character encodings and only
+  allows CRLF line breaks. These requirements, however, are outdated;
+  UTF-8 is now widely used, such that supporting other encodings is no
+  longer necessary, and use of CR, LF, and CRLF line breaks is
+  commonly supported and indeed sometimes CRLF is <em>not</em>
+  supported by text editors. <a href="#refsRFC2046">[RFC2046]</a></p>
+  <!-- also RFC 2045 for charset -->
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string