html5/spec Overview.html,1.4186,1.4187

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv29428

Modified Files:
	Overview.html 
Log Message:
Some more references to UTF-8. (whatwg r5258)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4186
retrieving revision 1.4187
diff -u -d -r1.4186 -r1.4187
--- Overview.html	10 Aug 2010 00:58:38 -0000	1.4186
+++ Overview.html	10 Aug 2010 01:16:15 -0000	1.4187
@@ -11565,10 +11565,10 @@
   <a href="#attr-meta-http-equiv-content-type" title="attr-meta-http-equiv-content-type">Encoding declaration
   state</a>, then the character encoding used must be an
   <a href="#ascii-compatible-character-encoding">ASCII-compatible character encoding</a>.<p>Authors are encouraged to use UTF-8. Conformance checkers may
-  advise authors against using legacy encodings.<div class="impl">
+  advise authors against using legacy encodings. <a href="#refsRFC3629">[RFC3629]</a><div class="impl">
 
   <p>Authoring tools should default to using UTF-8 for newly-created
-  documents.</p>
+  documents. <a href="#refsRFC3629">[RFC3629]</a></p>
 
   </div><p>Encodings in which a series of bytes in the range 0x20 to 0x7E
   can encode characters other than the corresponding characters in the
@@ -44568,7 +44568,7 @@
   encoded using UTF-8. Data in application cache manifests is
   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">willful violation</a> of two
+  CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs. <a href="#refsRFC3629">[RFC3629]</a><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;
@@ -44698,7 +44698,7 @@
    a U+FFFD REPLACEMENT CHARACTER. <!--All U+0000 NULL characters must
    be replaced by U+FFFD REPLACEMENT CHARACTERs. (this isn't black-box
    testable since neither U+0000 nor U+FFFD are valid anywhere in the
-   syntax and thus both will be treated the same anyway)--></li>
+   syntax and thus both will be treated the same anyway)--> <a href="#refsRFC3629">[RFC3629]</a></li>
 
    <li><p>Let <var title="">base URL</var> be the <a href="#absolute-url">absolute
    URL</a> representing the manifest.</li>
@@ -53199,7 +53199,7 @@
   <h5 id="character-encodings-0"><span class="secno">8.2.2.2 </span>Character encodings</h5><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252
-  encodings, but may support more.</p>
+  encodings, but may support more. <a href="#refsRFC3629">[RFC3629]</a> <a href="#refsWIN1252">[WIN1252]</a></p>
 
   <p class="note">It is not unusual for Web browsers to support dozens
   if not upwards of a hundred distinct character encodings.</p>

Received on Tuesday, 10 August 2010 01:16:21 UTC