- From: poot <cvsmail@w3.org>
- Date: Sat, 24 Jan 2009 10:57:41 +0900 (JST)
- To: public-html-diffs@w3.org
Oops, Unicode characters can be up to six digits hex, not five. (whatwg r2704) 8.2.7 Coercing an HTML DOM into an infoset http://people.w3.org/mike/diffs/html5/spec/Overview.1.1874.html#coercing-an-html-dom-into-an-infoset 8.3 Namespaces http://people.w3.org/mike/diffs/html5/spec/Overview.1.1874.html#namespaces http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1873&r2=1.1874&f=h http://html5.org/tools/web-apps-tracker?from=2703&to=2704 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.1873 retrieving revision 1.1874 diff -u -d -r1.1873 -r1.1874 --- Overview.html 24 Jan 2009 01:52:27 -0000 1.1873 +++ Overview.html 24 Jan 2009 01:54:45 -0000 1.1874 @@ -43176,20 +43176,19 @@ 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 class=example>For example, the element name <code title="">foo<bar</code>, which can be output by the <a href=#html-parser>HTML parser</a>, 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 class=example>As another example, consider the attribute + well-formed XML element name, would be converted into <code 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 class=example>As another example, consider the attribute <code>xlink:href</code>. Used on a MathML element, it becomes, after being <a href=#adjust-foreign-attributes title="adjust foreign attributes">adjusted</a>, an attribute with a prefix "<code title="">xlink</code>" and a local name "<code title="">href</code>". However, used on an HTML element, 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 class=note>The resulting names from this conversion + becoming "<code title="">xlinkU00003Ahref</code>".<p class=note>The resulting names from this conversion conveniently can't clash with any attribute generated by the <a href=#html-parser>HTML parser</a>, since those are all either lowercase or those listed in the <a href=#adjust-foreign-attributes>adjust foreign attributes</a> @@ -43212,9 +43211,9 @@ <em>after</em> the <a href=#html-parser>HTML parser</a>'s rules have been applied. For example, a <code title=""><a::></code> start tag will be closed by a <code title=""></a::></code> end tag, and - never by a <code title=""></aU0003AU0003A></code> end tag, even + never by a <code title=""></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.<h3 id=namespaces><span class=secno>8.3 </span>Namespaces</h3><p>The <dfn id=html-namespace-0>HTML namespace</dfn> is: <code>http://www.w3.org/1999/xhtml</code><p>The <dfn id=mathml-namespace>MathML namespace</dfn> is: <code>http://www.w3.org/1998/Math/MathML</code><p>The <dfn id=svg-namespace>SVG namespace</dfn> is: <code>http://www.w3.org/2000/svg</code><p>The <dfn id=xlink-namespace>XLink namespace</dfn> is: <code>http://www.w3.org/1999/xlink</code><p>The <dfn id=xml-namespace>XML namespace</dfn> is: <code>http://www.w3.org/XML/1998/namespace</code><p>The <dfn id=xmlns-namespace>XMLNS namespace</dfn> is: <code>http://www.w3.org/2000/xmlns/</code><h3 id=serializing-html-fragments><span class=secno>8.4 </span>Serializing HTML fragments</h3><p>The following steps form the <dfn id=html-fragment-serialization-algorithm>HTML fragment serialization + actual element in the DOM with the name <code title="">aU00003AU00003A</code> for that start tag.<h3 id=namespaces><span class=secno>8.3 </span>Namespaces</h3><p>The <dfn id=html-namespace-0>HTML namespace</dfn> is: <code>http://www.w3.org/1999/xhtml</code><p>The <dfn id=mathml-namespace>MathML namespace</dfn> is: <code>http://www.w3.org/1998/Math/MathML</code><p>The <dfn id=svg-namespace>SVG namespace</dfn> is: <code>http://www.w3.org/2000/svg</code><p>The <dfn id=xlink-namespace>XLink namespace</dfn> is: <code>http://www.w3.org/1999/xlink</code><p>The <dfn id=xml-namespace>XML namespace</dfn> is: <code>http://www.w3.org/XML/1998/namespace</code><p>The <dfn id=xmlns-namespace>XMLNS namespace</dfn> is: <code>http://www.w3.org/2000/xmlns/</code><h3 id=serializing-html-fragments><span class=secno>8.4 </span>Serializing HTML fragments</h3><p>The following steps form the <dfn id=html-fragment-serialization-algorithm>HTML fragment serialization algorithm</dfn>. The algorithm takes as input a DOM <code>Element</code> or <code>Document</code>, referred to as <var title="">the node</var>, and either returns a string or raises an exception.<p class=note>This algorithm serializes the <em>children</em> of
Received on Saturday, 24 January 2009 01:58:17 UTC