[html5] r2502 - [ct] (0) Lower-case the DOCTYPE name so that UAs can do case-sensitive matches o [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2008-12-01 18:45:15 -0800 (Mon, 01 Dec 2008)
New Revision: 2502

Modified:
   index
   source
Log:
[ct] (0) Lower-case the DOCTYPE name so that UAs can do case-sensitive matches on interned strings instead of case-insensitive matches. DOCTYPE name is now lowercase in the DOM (to match XHTML case -- might as well keep the differences minimal).

Modified: index
===================================================================
--- index	2008-12-02 02:30:27 UTC (rev 2501)
+++ index	2008-12-02 02:45:15 UTC (rev 2502)
@@ -46925,6 +46925,12 @@
    <i>force-quirks flag</i> to <i>on</i>. Emit the token. Switch to
    the <a href=#data-state>data state</a>.</dd>
 
+   <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
+   <dd>Create a new DOCTYPE token. Set the token's name to the
+   lowercase version of the input character (add 0x0020 to the
+   character's code point). Switch to the <a href=#doctype-name-state>DOCTYPE name
+   state</a>.</dd>
+
    <dt>EOF</dt>
    <dd><a href=#parse-error>Parse error</a>. Create a new DOCTYPE token. Set its
    <i>force-quirks flag</i> to <i>on</i>. Emit the token. Reconsume
@@ -46950,6 +46956,11 @@
    <dd>Emit the current DOCTYPE token. Switch to the <a href=#data-state>data
    state</a>.</dd>
 
+   <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
+   <dd>Append the lowercase version of the input character (add 0x0020
+   to the character's code point) to the current DOCTYPE token's
+   name. Stay in the <a href=#doctype-name-state>DOCTYPE name state</a>.</dd>
+
    <dt>EOF</dt>
    <dd><a href=#parse-error>Parse error</a>. Set the DOCTYPE token's
    <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
@@ -47743,16 +47754,17 @@
    <dt>A DOCTYPE token</dt>
    <dd>
 
-    <p>If the DOCTYPE token's <code title="">name</code> is not an
-    <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the string "<code title="">HTML</code>", or if the token's public identifier is
-    neither missing nor equal to the string
-    "<code>XSLT-compat</code>", or if the token's system identifier is
-    not missing, then there is a <a href=#parse-error>parse error</a> (this is the
-    <dfn id=doctype-parse-error>DOCTYPE parse error</dfn>). Conformance checkers may, instead
-    of reporting this error, switch to a conformance checking mode for
-    another language (e.g. based on the DOCTYPE token a conformance
-    checker could recognize that the document is an HTML4-era
-    document, and defer to an HTML4 conformance checker.)</p>
+    <p>If the DOCTYPE token's <code title="">name</code> is not a
+    <a href=#case-sensitive>case-sensitive</a> match for the string "<code title="">html</code>", or if the token's public identifier is
+    neither missing nor a <a href=#case-sensitive>case-sensitive</a> match for the
+    string "<code>XSLT-compat</code>", or if the token's system
+    identifier is not missing, then there is a <a href=#parse-error>parse
+    error</a> (this is the <dfn id=doctype-parse-error>DOCTYPE parse
+    error</dfn>). Conformance checkers may, instead of reporting this
+    error, switch to a conformance checking mode for another language
+    (e.g. based on the DOCTYPE token a conformance checker could
+    recognize that the document is an HTML4-era document, and defer to
+    an HTML4 conformance checker.)</p>
 
     <p>Append a <code>DocumentType</code> node to the
     <code>Document</code> node, with the <code title="">name</code>

Modified: source
===================================================================
--- source	2008-12-02 02:30:27 UTC (rev 2501)
+++ source	2008-12-02 02:45:15 UTC (rev 2502)
@@ -53545,6 +53545,12 @@
    <i>force-quirks flag</i> to <i>on</i>. Emit the token. Switch to
    the <span>data state</span>.</dd>
 
+   <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
+   <dd>Create a new DOCTYPE token. Set the token's name to the
+   lowercase version of the input character (add 0x0020 to the
+   character's code point). Switch to the <span>DOCTYPE name
+   state</span>.</dd>
+
    <dt>EOF</dt>
    <dd><span>Parse error</span>. Create a new DOCTYPE token. Set its
    <i>force-quirks flag</i> to <i>on</i>. Emit the token. Reconsume
@@ -53575,6 +53581,11 @@
    <dd>Emit the current DOCTYPE token. Switch to the <span>data
    state</span>.</dd>
 
+   <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
+   <dd>Append the lowercase version of the input character (add 0x0020
+   to the character's code point) to the current DOCTYPE token's
+   name. Stay in the <span>DOCTYPE name state</span>.</dd>
+
    <dt>EOF</dt>
    <dd><span>Parse error</span>. Set the DOCTYPE token's
    <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
@@ -54467,17 +54478,18 @@
    <dt>A DOCTYPE token</dt>
    <dd>
 
-    <p>If the DOCTYPE token's <code title="">name</code> is not an
-    <span>ASCII case-insensitive</span> match for the string "<code
-    title="">HTML</code>", or if the token's public identifier is
-    neither missing nor equal to the string
-    "<code>XSLT-compat</code>", or if the token's system identifier is
-    not missing, then there is a <span>parse error</span> (this is the
-    <dfn>DOCTYPE parse error</dfn>). Conformance checkers may, instead
-    of reporting this error, switch to a conformance checking mode for
-    another language (e.g. based on the DOCTYPE token a conformance
-    checker could recognize that the document is an HTML4-era
-    document, and defer to an HTML4 conformance checker.)</p>
+    <p>If the DOCTYPE token's <code title="">name</code> is not a
+    <span>case-sensitive</span> match for the string "<code
+    title="">html</code>", or if the token's public identifier is
+    neither missing nor a <span>case-sensitive</span> match for the
+    string "<code>XSLT-compat</code>", or if the token's system
+    identifier is not missing, then there is a <span>parse
+    error</span> (this is the <dfn>DOCTYPE parse
+    error</dfn>). Conformance checkers may, instead of reporting this
+    error, switch to a conformance checking mode for another language
+    (e.g. based on the DOCTYPE token a conformance checker could
+    recognize that the document is an HTML4-era document, and defer to
+    an HTML4 conformance checker.)</p>
 
     <p>Append a <code>DocumentType</code> node to the
     <code>Document</code> node, with the <code title="">name</code>