W3C home > Mailing lists > Public > public-html-diffs@w3.org > May 2009

fix some references (whatwg r3136)

From: poot <cvsmail@w3.org>
Date: Tue, 26 May 2009 19:10:53 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090526101053.A84E74649@toro.w3.mag.keio.ac.jp>
fix some references (whatwg r3136)

Diffs for this change per section: 
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2294.html#writing-cache-manifests
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2294.html#url-host-specific
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2294.html#url-character-encoding

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2293&r2=1.2294&f=h
http://html5.org/tools/web-apps-tracker?from=3135&to=3136

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2293
retrieving revision 1.2294
diff -u -d -r1.2293 -r1.2294
--- Overview.html	26 May 2009 09:53:41 -0000	1.2293
+++ Overview.html	26 May 2009 10:09:14 -0000	1.2294
@@ -4021,8 +4021,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="#references">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="#references">[RFC3986]</a></p>
 
   </div><div class="impl">
 
@@ -4148,8 +4148,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="#references">RFC3986</a> <a href="#references">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="#references">[RFC3986]</a> <a href="#references">[RFC3987]</a></p>
 
   </div><div class="impl">
 
@@ -44491,7 +44492,12 @@
   line-based. Newlines must be represented by U+000A LINE FEED (LF)
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.<p class="note">This is a <a href="#willful-violation" title="willful violation">willful
-  double violation</a> of RFC2046. <a href="#references">[RFC2046]</a><p>The first line of an application cache manifest must consist of
+  double violation</a> of RFC2046. <a href="#references">[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
   "MANIFEST", and either a U+0020 SPACE character, a U+0009 CHARACTER
   TABULATION (tab) character, a U+000A LINE FEED (LF) character, or a
Received on Tuesday, 26 May 2009 10:11:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:05 GMT