[html5] r3264 - [e] (0) Collect more references together.

whatwg at whatwg.org whatwg at whatwg.org
Mon Jun 15 16:58:57 PDT 2009
Previous message: [html5] r3263 - [e] (0) WAVE reference? Also, fix wording to make all three freqs required.
Next message: [html5] r3265 - [e] (0) CSSOM-related cleanup. The term 'alternative style sheet sets' is no lon [...]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Author: ianh
Date: 2009-06-15 16:58:55 -0700 (Mon, 15 Jun 2009)
New Revision: 3264

Modified:
   index
   source
Log:
[e] (0) Collect more references together.

Modified: index
===================================================================
--- index	2009-06-15 23:39:01 UTC (rev 3263)
+++ index	2009-06-15 23:58:55 UTC (rev 3264)
@@ -10276,11 +10276,11 @@
 
   <h5 id=charset><span class=secno>4.2.5.5 </span>Specifying the document's character encoding</h5>
 
-  <!-- XXX maybe the rest should move to "writing html" section,
-  though if we do then we have to duplicate the requirements in the
+  <!-- READ ME WHEN EDITING: if we ever move this to the "writing
+  HTML" section, then we have to duplicate the requirements in the
   parsing section for conformance checkers, and we have to make sure
   that the requirements for charset="" apply even in XML, for the
-   polyglot hack -->
+   polyglot hack. -->
 
   <p>A <dfn id=character-encoding-declaration>character encoding declaration</dfn> is a mechanism by
   which the character encoding used to store or transmit a document is
@@ -10293,8 +10293,7 @@
    character encoding used to serialize the file.</li>
 
    <li>The value must be a valid character encoding name, and must be
-   the preferred name for that encoding. <a href=#refsIANACHARSET>[IANACHARSET]</a> <!-- XXX
-   http://www.iana.org/assignments/character-sets --></li>
+   the preferred name for that encoding. <a href=#refsIANACHARSET>[IANACHARSET]</a></li>
 
    <li>The character encoding declaration must be serialized without
    the use of <a href=#syntax-charref title=syntax-charref>character references</a>
@@ -10327,10 +10326,11 @@
   state</a>, then the character encoding used must be an
   <a href=#ascii-compatible-character-encoding>ASCII-compatible character encoding</a>.</p>
 
-  <p>Authors should not use JIS_X0212-1990, x-JIS0208, and encodings
-  based on EBCDIC. Authors should not use UTF-32. Authors must not use
-  the CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a href=#refsCESU8>[CESU8]</a> <a href=#refsUTF7>[UTF7]</a> <a href=#refsBOCU1>[BOCU1]</a> <a href=#refsSCSU>[SCSU]</a></p>
-  <!-- XXX ref JIS_X0212-1990, x-JIS0208, EBCDIC, UTF-32 -->
+  <p>Authors should not use JIS-X-0208 <!-- x-JIS0208 -->
+  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), and encodings based
+  on EBCDIC. Authors should not use UTF-32. Authors must not use the
+  CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a href=#refsRFC1345>[RFC1345]</a><!-- for the JIS types --> <a href=#refsUTF32>[UTF32]</a> <a href=#refsCESU8>[CESU8]</a> <a href=#refsUTF7>[UTF7]</a> <a href=#refsBOCU1>[BOCU1]</a> <a href=#refsSCSU>[SCSU]</a></p> <!-- no idea what to reference for
+  EBCDIC, so... -->
 
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
@@ -70000,6 +70000,8 @@
   <!-- REFS
 
   [BIG5] Institute for Information Industry, "Chinese Coded Character Set in Computer ", March, 1984
+  [BOCU1] http://www.unicode.org/notes/tn6/
+  [CESU8] http://www.unicode.org/unicode/reports/tr26
   [COMPUTABLE] On computable numbers, with an application to the Entscheidungsproblem. Alan M. Turing. In Proceedings of the London Mathematical Society, series 2, volume 42, pages 230-265. London Mathematical Society, 1937. http://www.turingarchive.org/browse.php/B/12 (referenced: 2007-03-03)
   [EUCKR] Korea Industrial Standards Association, "Hangul Unix Environment," Korean Industrial Standard, 1992, Ref. No. KS C 5861-1992.
   [GBK] http://www.iana.org/assignments/charset-reg/GBK
@@ -70010,9 +70012,12 @@
   [IANACHARSET] http://www.iana.org/assignments/character-sets
   [ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
   [RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
+  [SCSU] http://www.unicode.org/unicode/reports/tr6/
   [SHIFTJIS] JIS X0208:1997
   [TIS620] http://www.iana.org/assignments/charset-reg/tis-620 OR http://www.nectec.or.th/it-standards/std620/std620.htm
   [UNICODECASE] Unicode Standard Annex #21, Case Mappings
+  [UTF32] http://www.unicode.org/unicode/reports/tr19/
+  [UTF7] http://www.ietf.org/rfc/rfc2152.txt
   [UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching
   [WAVE] http://en.wikipedia.org/wiki/WAV ?
   [WEBADDRESSES] http://www.w3.org/html/wg/href/draft (for now) (but only for now, for now)

Modified: source
===================================================================
--- source	2009-06-15 23:39:01 UTC (rev 3263)
+++ source	2009-06-15 23:58:55 UTC (rev 3264)
@@ -10689,11 +10689,11 @@
 
   <h5 id="charset">Specifying the document's character encoding</h5>
 
-  <!-- XXX maybe the rest should move to "writing html" section,
-  though if we do then we have to duplicate the requirements in the
+  <!-- READ ME WHEN EDITING: if we ever move this to the "writing
+  HTML" section, then we have to duplicate the requirements in the
   parsing section for conformance checkers, and we have to make sure
   that the requirements for charset="" apply even in XML, for the
-  <meta charset=""> polyglot hack -->
+  <meta charset=""> polyglot hack. -->
 
   <p>A <dfn>character encoding declaration</dfn> is a mechanism by
   which the character encoding used to store or transmit a document is
@@ -10709,8 +10709,7 @@
 
    <li>The value must be a valid character encoding name, and must be
    the preferred name for that encoding. <a
-   href="#refsIANACHARSET">[IANACHARSET]</a> <!-- XXX
-   http://www.iana.org/assignments/character-sets --></li>
+   href="#refsIANACHARSET">[IANACHARSET]</a></li>
 
    <li>The character encoding declaration must be serialized without
    the use of <span title="syntax-charref">character references</span>
@@ -10749,12 +10748,15 @@
   state</span>, then the character encoding used must be an
   <span>ASCII-compatible character encoding</span>.</p>
 
-  <p>Authors should not use JIS_X0212-1990, x-JIS0208, and encodings
-  based on EBCDIC. Authors should not use UTF-32. Authors must not use
-  the CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a
-  href="#refsCESU8">[CESU8]</a> <a href="#refsUTF7">[UTF7]</a> <a
-  href="#refsBOCU1">[BOCU1]</a> <a href="#refsSCSU">[SCSU]</a></p>
-  <!-- XXX ref JIS_X0212-1990, x-JIS0208, EBCDIC, UTF-32 -->
+  <p>Authors should not use JIS-X-0208 <!-- x-JIS0208 -->
+  (JIS_C6226-1983), JIS-X-0212 (JIS_X0212-1990), and encodings based
+  on EBCDIC. Authors should not use UTF-32. Authors must not use the
+  CESU-8, UTF-7, BOCU-1 and SCSU encodings. <a
+  href="#refsRFC1345">[RFC1345]</a><!-- for the JIS types --> <a
+  href="#refsUTF32">[UTF32]</a> <a href="#refsCESU8">[CESU8]</a> <a
+  href="#refsUTF7">[UTF7]</a> <a href="#refsBOCU1">[BOCU1]</a> <a
+  href="#refsSCSU">[SCSU]</a></p> <!-- no idea what to reference for
+  EBCDIC, so... -->
 
   <p>Authors are encouraged to use UTF-8. Conformance checkers may
   advise against authors using legacy encodings.</p>
@@ -82555,6 +82557,8 @@
   <!-- REFS
 
   [BIG5] Institute for Information Industry, "Chinese Coded Character Set in Computer ", March, 1984
+  [BOCU1] http://www.unicode.org/notes/tn6/
+  [CESU8] http://www.unicode.org/unicode/reports/tr26
   [COMPUTABLE] On computable numbers, with an application to the Entscheidungsproblem. Alan M. Turing. In Proceedings of the London Mathematical Society, series 2, volume 42, pages 230-265. London Mathematical Society, 1937. http://www.turingarchive.org/browse.php/B/12 (referenced: 2007-03-03)
   [EUCKR] Korea Industrial Standards Association, "Hangul Unix Environment," Korean Industrial Standard, 1992, Ref. No. KS C 5861-1992.
   [GBK] http://www.iana.org/assignments/charset-reg/GBK
@@ -82565,9 +82569,12 @@
   [IANACHARSET] http://www.iana.org/assignments/character-sets
   [ISO885911] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=28263
   [RFC1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, Rationel Almen Planlaegning, June 1992.
+  [SCSU] http://www.unicode.org/unicode/reports/tr6/
   [SHIFTJIS] JIS X0208:1997
   [TIS620] http://www.iana.org/assignments/charset-reg/tis-620 OR http://www.nectec.or.th/it-standards/std620/std620.htm
   [UNICODECASE] Unicode Standard Annex #21, Case Mappings
+  [UTF32] http://www.unicode.org/unicode/reports/tr19/
+  [UTF7] http://www.ietf.org/rfc/rfc2152.txt
   [UTS22] http://unicode.org/reports/tr22/#Charset_Alias_Matching
   [WAVE] http://en.wikipedia.org/wiki/WAV ?
   [WEBADDRESSES] http://www.w3.org/html/wg/href/draft (for now) (but only for now, for now)
Previous message: [html5] r3263 - [e] (0) WAVE reference? Also, fix wording to make all three freqs required.
Next message: [html5] r3265 - [e] (0) CSSOM-related cleanup. The term 'alternative style sheet sets' is no lon [...]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Commit-Watchers mailing list