- From: CVS User lsilli <cvsmail@w3.org>
- Date: Sun, 01 Sep 2013 20:52:10 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-xhtml-author-guide
In directory roscoe:/tmp/cvs-serv20885/html-xhtml-author-guide
Modified Files:
html-xhtml-authoring-guide.html
Log Message:
Fixing bug 20707
--- /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html 2013/09/01 20:34:07 1.117
+++ /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html 2013/09/01 20:52:10 1.118
@@ -79,6 +79,7 @@
<section id="introduction" class="informative">
<h2>Introduction</h2>
+ <section class="value"><h3>Value</h3>
<p>
It is often valuable to be able to serve HTML5 documents that are also well formed XML documents.
An author may, for example, use XML tools to generate a document, and they and others may process the document using XML tools.
@@ -89,6 +90,24 @@
Other permissible MIME types are <code>text/xml</code>, <code>application/xml</code>,
and any MIME type whose subtype ends with the four characters "<code>+xml</code>". [[!XML-MT]]
</p>
+ </section>
+<section id="scope">
+ <h3>Scope</h3>
+<p> All web content need not be authored in <a>polyglot markup</a> and it is primarily an option for authors wanting to increase the robustness of their documents.
+ As such, <a title="polyglot markup">polyglot markup</a> may work best, and be beneficial option, in controlled environments and for authoring tools.
+<a title="polyglot markup">Polyglot markup</a> is ideal for publishing when there's a strong desire to serve both HTML and XML tool chains
+without simultaneously having to maintain dual copies of the content: one in HTML and a second in XHTML.
+In addition, a single <a>polyglot markup</a> output requires less infrastructure to produce than to produce both HTML and XHTML output for the same content.
+<a title="polyglot markup">Polyglot markup</a> is also be beneficial when lightweight processes—such as
+quick testing or even hand-authoring—are applied to content intended to be published both as HTML and XHTML,
+especially if that content is not sent through a tool chain.</p>
+
+<p class="note">XML-based HTML tools or systems intended for the most general
+ contexts of use cannot depend on polyglot input: for maximum flexibility,
+ such tools should use the technique of using an HTML parser that produces
+ an XML-compatible DOM or event stream.</p>
+
+</section>
</section>
<section id="syntax">
<h2>The syntax of polyglot markup</h2>
@@ -119,15 +138,7 @@
as non-quirks mode is closest to XML-mode rendering, in regard to both DOM and CSS.
<a title="polyglot markup">Polyglot markup</a> results in the same encoding and the same language in both HTML-mode and XML-mode.
</p>
- <p>
- All web content need not be authored in <a>polyglot markup</a>.
- <a title="polyglot markup">Polyglot markup</a> is ideal for publishing when there's a strong desire to serve both HTML and XML tool chains
- without simultaneously having to maintain dual copies of the content: one in HTML and a second in XHTML.
- In addition, a single <a>polyglot markup</a> output requires less infrastructure to produce than to produce both HTML and XHTML output for the same content.
- <a title="polyglot markup">Polyglot markup</a> is also be beneficial when lightweight processes—such as
- quick testing or even hand-authoring—are applied to content intended to be published both as HTML and XHTML,
- especially if that content is not sent through a tool chain.
- </p>
+
<p>
<a title="polyglot markup">Polyglot markup</a>, itself being valid HTML5,
supports extensibility as it is defined in
Received on Sunday, 1 September 2013 20:52:11 UTC