NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 519 - Oops, Unicode characters can be up to six digits hex, not five.
Oops, Unicode characters can be up to six digits hex, not five.
Status: NEW
Product: Validator.nu
Classification: Unclassified
Component: HTML parser
HEAD
All All
: P2 normal
Assigned To: Nobody
http://svn.whatwg.org/webapps/source?...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-27 14:17 CEST by Henri Sivonen
Modified: 2009-11-23 17:17 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Sivonen 2009-05-27 14:17:47 CEST
Index: source
===================================================================
--- source	(revision 2703)
+++ source	(revision 2704)
@@ -60322,7 +60322,7 @@
   all element and attribute local names that the API wouldn't support
   to a set of names that <em>are</em> allowed, by replacing any
   character that isn't supported with the uppercase letter U and the
-  five digits of the character's Unicode codepoint when expressed in
+  six digits of the character's Unicode codepoint when expressed in
   hexadecimal, using digits 0-9 and capital letters A-F as the
   symbols, in increasing numeric order.</p>
 
@@ -60330,9 +60330,8 @@
   title="">foo&lt;bar</code>, which can be output by the <span>HTML
   parser</span>, though it is neither a legal HTML element name nor a
   well-formed XML element name, would be converted into <code
-  title="">fooU0003Cbar</code>, which <em>is</em> a well-formed
-  XML element name (though it's still not legal in HTML by any
-  means).</p>
+  title="">fooU00003Cbar</code>, which <em>is</em> a well-formed XML
+  element name (though it's still not legal in HTML by any means).</p>
 
   <p class="example">As another example, consider the attribute
   <code>xlink:href</code>. Used on a MathML element, it becomes, after
@@ -60342,7 +60341,7 @@
   it becomes an attribute with no prefix and the local name "<code
   title="">xlink:href</code>", which is not a valid NCName, and thus
   might not be accepted by an XML API. It could thus get converted,
-  becoming "<code title="">xlinkU0003Ahref</code>".</p>
+  becoming "<code title="">xlinkU00003Ahref</code>".</p>
 
   <p class="note">The resulting names from this conversion
   conveniently can't clash with any attribute generated by the
@@ -60381,10 +60380,10 @@
   <em>after</em> the <span>HTML parser</span>'s rules have been
   applied. For example, a <code title="">&lt;a::></code> start tag
   will be closed by a <code title="">&lt;/a::></code> end tag, and
-  never by a <code title="">&lt;/aU0003AU0003A></code> end tag, even
+  never by a <code title="">&lt;/aU00003AU00003A></code> end tag, even
   if the user agent is using the rules above to then generate an
   actual element in the DOM with the name <code
-  title="">aU0003AU0003A</code> for that start tag.</p>
+  title="">aU00003AU00003A</code> for that start tag.</p>