CVS html5/html-polyglot

Update of /sources/public/html5/html-polyglot
In directory roscoe:/tmp/cvs-serv12892

Modified Files:
	html-polyglot.html 
Log Message:
Editorial changes outlined in bug 24451, comment 2.

--- /sources/public/html5/html-polyglot/html-polyglot.html	2014/02/02 01:02:25	1.25
+++ /sources/public/html5/html-polyglot/html-polyglot.html	2014/02/02 01:22:59	1.26
@@ -8,7 +8,7 @@
         var respecConfig = {
             specStatus:   "ED",
             shortName:    "html-polyglot",
-            publishDate:  "2014-01-16",
+            publishDate:  "2014-02-01",
             previousPublishDate:  "2010-10-19",
             // previousDiffURI:  "http://htmlwg.org/heartbeat/WD-html-polyglot-20131008/",
 previousMaturity:  "WD",
@@ -50,7 +50,7 @@
         The document is intended to be useful to web authors, in particular those who want to serve receivers without concern for whether they have XML or HTML parsers available.
         Such concerns may, for instance, arise in content syndication or when receivers are on legacy systems.
         HTML polyglots <a href="http://www.w3.org/html/wg/drafts/html/master/document-metadata.html#charset-0">facilitate migration to and from XHTML</a>,
-        including transition from legacy XML to HTML5, and this document serves to accurately specify the requirements of a UTF-8 based profile for such documents.
+        including transition from XML 1.x to HTML5, and this document serves to accurately specify the requirements of a UTF-8 based profile for such documents.
     </p>
     <p>
         No recommendation is made in this document or by the W3C regarding whether or not to publish polyglot content.
@@ -59,7 +59,7 @@
     </p>
     <p>
         This document is not a specification for user agents and creates no obligations on user agents.
-        Note that this recommendation does not define how HTML5-conforming user agents should process HTML documents.
+        Note that this document does not define how HTML5-conforming user agents should process HTML documents.
         Nor does it define the meaning of the Internet Media Type <code>text/html</code>.
         For user agent guidance and for these definitions, see [[!HTML5]] and [[!RFC2854]].
     </p>
@@ -139,7 +139,12 @@
         <ul>
             <li>a valid HTML document. [[!HTML5]]</li>
             <li>a <a href="http://www.w3.org/TR/2008/PER-xml-20080205/#sec-well-formed">well-formed XML</a> document. [[!XML10]]</li>
-            <li>identical DOMs when processed as HTML and when processed as XML, with some notable exceptions: HTML and XML parsers generate different DOMs for some <code>xml</code> (<code>xml:lang</code>, <code>xml:space</code>, and <code>xml:base</code>), <code>xmlns</code> (<code>xmlns=""</code> and <code>xmlns:xlink=""</code>), and <code>xlink</code> (such as <code>xlink:href</code>) attributes. XML requires and HTML5 permits these attributes in certain locations and the attributes are preserved by HTML parsers. The exception must not break the requirement to be a valid HTML document.
+            <li>identical DOMs when processed as HTML and when processed as XML, with some notable exceptions: 
+                HTML and XML parsers generate different DOMs for some <code>xml</code> (<code>xml:lang</code>, <code>xml:space</code>, and <code>xml:base</code>), 
+                <code>xmlns</code> (<code>xmlns=""</code> and <code>xmlns:xlink=""</code>), 
+                and <code>xlink</code> (such as <code>xlink:href</code>) attributes. 
+                XML requires and HTML5 permits these attributes in certain locations and the attributes are preserved by HTML parsers. 
+                The exception must not break the requirement to be a valid HTML document.
             </li>
         </ul>
         <p><a>Polyglot Markup</a> specifies a <dfn id="dfn-robust-syntax">Robust Syntax</dfn>, by which it is meant a syntax that maximizes support and minimizes authoring choice.</p>
@@ -192,7 +197,8 @@
         HTML requires UTF-8 to be explicitly declared to avoid <a href="http://www.w3.org/TR/html5/semantics.html#charset">fallback to a legacy encoding</a>. [[!HTML5]]
     </p>
     <p> For XML, UTF-8 is an <a href="http://www.w3.org/TR/2008/REC-xml-20081126/#charencoding">encoding default</a>.
-        As such, character encoding MAY be left undeclared in XML with the result that UTF8 is still supported [[!XML10]].
+        Documents served with an XML content type therefore do not need to use any of the HTML encoding declaration methods, 
+        although if the document might be interpreted as <code>text/html</code> it SHOULD do so.
     </p>
     <p>
         <a title="polyglot markup">Polyglot markup</a> declares the UTF-8 character encoding in the following ways, which may be used separately or
@@ -233,8 +239,8 @@
     </p>
 
     <p>
-        The <a href="http://www.w3.org/International/questions/qa-html-encoding-declarations">W3C Internationalization (i18n) Group recommends</a> to always include
-        a visible encoding declaration in a document, because it helps developers, testers, or translation production managers to check the encoding of a document visually.
+        The <a href="http://www.w3.org/International/questions/qa-html-encoding-declarations">W3C Internationalization (i18n) Group recommends</a> that one always include
+        a visible encoding declaration in an HTML document, because it helps developers, testers, or translation production managers to check the encoding of a document visually.
     </p>
     <!--End section: Specifying a Document's Character Encoding-->
 </section>

Received on Sunday, 2 February 2014 01:23:00 UTC