[html5] r3136 - [e] (0) fix some references

[whatwg at whatwg.org]

Author: ianh
Date: 2009-05-26 03:09:09 -0700 (Tue, 26 May 2009)
New Revision: 3136

Modified:
   index
   source
Log:
[e] (0) fix some references

Modified: index
===================================================================
--- index	2009-05-26 09:53:35 UTC (rev 3135)
+++ index	2009-05-26 10:09:09 UTC (rev 3136)
@@ -4516,8 +4516,8 @@
   manner distinct from the precise technical meaning it is given in
   RFC 3986. Readers familiar with that RFC will find it easier to read
   <em>this</em> specification if they pretend the term "URL" as used
-  herein is really called something else altogether. This is a <a href=#willful-violation>willful
-  violation</a> of RFC 3986. <a href=#refsRFC3986>RFC3986</a></p>
+  herein is really called something else altogether. This is a
+  <a href=#willful-violation>willful violation</a> of RFC 3986. <a href=#refsRFC3986>[RFC3986]</a></p>
 
   </div>
 
@@ -4646,8 +4646,9 @@
 
   </ol><!-- XXX we might want to define "server-based naming authority",
   it's not clear RFC3986 does a good job of defining that anymore
-  (earlier URI specs did) --><p class=note>These parsing rules are a <a href=#willful-violation>willful violation</a> of RFC
-  3986 and RFC 3987 to handle legacy content. <a href=#refsRFC3986>RFC3986</a> <a href=#refsRFC3987>RFC3987</a></p>
+  (earlier URI specs did) --><p class=note>These parsing rules are a <a href=#willful-violation>willful
+  violation</a> of RFC 3986 and RFC 3987 to handle legacy
+  content. <a href=#refsRFC3986>[RFC3986]</a> <a href=#refsRFC3987>[RFC3987]</a></p>
 
   </div>
 
@@ -49514,7 +49515,12 @@
   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 RFC2046. <a href=#refsRFC2046>[RFC2046]</a></p>
+  double violation</a> of RFC2046. <a href=#refsRFC2046>[RFC2046]</a></p> <!-- 2046 (and 2045) says that
+  charset="" is always allowed on text/*, but that harks back to the
+  old days before UTF-8 was widely used; 2046 also says that newlines
+  are always CRLF-delimited, which is not workable given the
+  widespread use of editors that use either lone LFs or lone CRs as
+  line break delimiters. -->
 
   <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-05-26 09:53:35 UTC (rev 3135)
+++ source	2009-05-26 10:09:09 UTC (rev 3136)
@@ -4081,8 +4081,9 @@
   manner distinct from the precise technical meaning it is given in
   RFC 3986. Readers familiar with that RFC will find it easier to read
   <em>this</em> specification if they pretend the term "URL" as used
-  herein is really called something else altogether. This is a <span>willful
-  violation</span> of RFC 3986. <a href="#refsRFC3986">RFC3986</a></p>
+  herein is really called something else altogether. This is a
+  <span>willful violation</span> of RFC 3986. <a
+  href="#refsRFC3986">[RFC3986]</a></p>
 
   </div>
 
@@ -4229,10 +4230,10 @@
   it's not clear RFC3986 does a good job of defining that anymore
   (earlier URI specs did) -->
 
-  <p class="note">These parsing rules are a <span>willful violation</span> of RFC
-  3986 and RFC 3987 to handle legacy content. <a
-  href="#refsRFC3986">RFC3986</a> <a
-  href="#refsRFC3987">RFC3987</a></p>
+  <p class="note">These parsing rules are a <span>willful
+  violation</span> of RFC 3986 and RFC 3987 to handle legacy
+  content. <a href="#refsRFC3986">[RFC3986]</a> <a
+  href="#refsRFC3987">[RFC3987]</a></p>
 
   </div>
 
@@ -56471,7 +56472,12 @@
 
   <p class="note">This is a <span title="willful violation">willful
   double violation</span> of RFC2046. <a
-  href="#refsRFC2046">[RFC2046]</a></p>
+  href="#refsRFC2046">[RFC2046]</a></p> <!-- 2046 (and 2045) says that
+  charset="" is always allowed on text/*, but that harks back to the
+  old days before UTF-8 was widely used; 2046 also says that newlines
+  are always CRLF-delimited, which is not workable given the
+  widespread use of editors that use either lone LFs or lone CRs as
+  line break delimiters. -->
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string