- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 14 Aug 2009 04:04:25 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv10020 Modified Files: Overview.html Log Message: Try to help the cadence of the introduction. (whatwg r3610) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2800 retrieving revision 1.2801 diff -u -d -r1.2800 -r1.2801 --- Overview.html 14 Aug 2009 03:13:39 -0000 1.2800 +++ Overview.html 14 Aug 2009 04:04:21 -0000 1.2801 @@ -1291,11 +1291,11 @@ "HTML5" document by Web browsers.<p>The second concrete syntax uses XML, and is known as "XHTML5". When a document is transmitted with an <a href="#xml-mime-type">XML MIME type</a>, such as <code><a href="#application-xhtml-xml">application/xhtml+xml</a></code>, then it is - processed by an XML processor by Web browsers, and treated as an - "XHTML5" document. Authors are reminded that the processing for XML - and HTML differs; in particular, even minor syntax errors will - prevent an XML document from being rendered fully, whereas they - would be ignored in the "HTML5" syntax.<p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all + treated as an "XHTML5" document by Web browsers, which means that it + will be handled by an XML processor. Authors are reminded that the + processing for XML and HTML differs; in particular, even minor + syntax errors will prevent an XML document from being rendered + fully, whereas they would be ignored in the "HTML5" syntax.<p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all represent the same content. For example, namespaces cannot be represented using "HTML5", but they are supported in "DOM5 HTML" and "XHTML5". Similarly, documents that use the <code><a href="#the-noscript-element">noscript</a></code>
Received on Friday, 14 August 2009 04:04:33 UTC