- From: CVS User egraff <cvsmail@w3.org>
- Date: Fri, 18 Oct 2013 18:40:16 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-xhtml-author-guide
In directory roscoe:/tmp/cvs-serv5140
Modified Files:
html-xhtml-authoring-guide.html
Log Message:
Fixed linking errors found by ReSpec upgrade
--- /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html 2013/10/09 07:06:50 1.140
+++ /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html 2013/10/18 18:40:16 1.141
@@ -79,7 +79,7 @@
<section id="introduction" class="informative"><h2>Introduction</h2>
<p>It is sometimes 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.
- The language used to create documents that can be parsed by both HTML and XML parsers is called <a title="polyglot markkup">polyglot markup</a>.
+ The language used to create documents that can be parsed by both HTML and XML parsers is called <a title="polyglot markup">polyglot markup</a>.
<a title="polyglot markup">Polyglot markup</a> is the overlap language of documents that are both HTML5 documents and XML documents.
It is recommended that these documents be served as either <code>text/html</code> (if the content is transmitted to an HTML-aware user agent)
or <code>application/xhtml+xml</code> (if the content is transmitted to an XHTML-aware user agent).
@@ -114,8 +114,8 @@
that other relevant specs have not allready added. But it can work to <em>preserve</em> accessibility.</p>
<p>The motivation behind, and reason for <a title="polyglot markup">polyglot markup</a> to exist as a specification, is its widely supported
- <a title="robustness">robustness</a>. With <a title="robustness">robust</a> (also known as conservative) markup, authors can <q cite="http://www.w3.org/TR/WCAG20/#robust">
- maximize compatibility with current and future user agents</q> and authoring tools. [[!WCAG20]]</p>
+ <a title="robustness">robustness</a>. With <a title="robustness">robust</a> (also known as conservative) markup, authors can
+ <q cite="http://www.w3.org/TR/WCAG20/#robust">maximize compatibility with current and future user agents</q> and authoring tools. [[!WCAG20]]</p>
<p>Polyglot markup seeks to define constraints on the serialization of a DOM tree in a <a title="robustness">robust</a> manner that
is likely to retain semantics when said serialization is reparsed using a variety of parsers, be
@@ -150,7 +150,7 @@
don't match what the author intended.
</p>
<p class="note">
- Polyglot markup is not defined as ”robust markup” because the XML-based polyglot markup
+ Polyglot markup is not defined as "robust markup" because the XML-based polyglot markup
syntax is not the only way to increase <a title="robustness">robustness</a>.
For instance, an HTML validator or an authoring tool could require all tags to be closed even if
this is not required by the HTML syntax. But then again, <a title="polyglot markup">polyglot markup</a>, being valid
@@ -363,7 +363,7 @@
HTML parser itself automatically adds to the DOM</a> if the code doesn’t contain the tags for
them. However, since XML does not have a feature whereby elements with one or both tags that have been
omitted from the code (such as when start and end tags of <code>html</code> are omitted) are added to the DOM,
- omitting a tag in <a>polyglot markup</a> is equivalent of producing a not <a>well-formed</a> document or,
+ omitting a tag in <a>polyglot markup</a> is equivalent of producing a not well-formed document or,
if both tags are omotted, equivalent of not adding the element at all. Therefore, <a>polyglot markup</a> does not
operate with <a>optional tags</a>.</p>
@@ -727,14 +727,14 @@
<p>Syntactically, the polyglot subset is found by</p>
- <ul><li><em>either</em> <strong>limiting the content to <a>safe content</a></strong>, that
+ <ul><li><em>either</em> <strong>limiting the content to <dfn>safe content</dfn></strong>, that
is: text that gets interpreted the same way in HTML and in XML.</li>
<li><em>or</em> trying to <strong>even out the constraints differences</strong> by
wrapping the contents in a <code>CDATA</code> section. The <code>CDATA</code> code is then seen as text
by the HTML parser (and can thus interfere with the scripting or styling language!), while the XML parser sees the
content as text without markup semantics.</li></ul>
<p>Limiting the contents to <a>safe content</a> requires more planning and control over the code, but can be said to be
- more <a type="robustness">robust</a> than the <code>CDATA</code> option as it requires no extra, potentially
+ more <a title="robustness">robust</a> than the <code>CDATA</code> option as it requires no extra, potentially
breakable code to make the scripting or styling language work. The <code>CDATA</code> option on the
other hand, gives more freedom and robustness against various errors that can happen because the author isn’t
aware of the <a>safe content</a> limitations or because the code is inserted by a tool that is unable to
@@ -778,8 +778,7 @@
<figure>
<figcaption>An example of inline safe text content in <code>script</code></figcaption>
<pre class="example highlight"
- ><!-- The following the example is <a>polyglot markup</a> because there are no
-<a> ambiguous strings</a> within the <code>script</code> element. --><br
+ ><!-- The following the example is <a>polyglot markup</a> because there are no ambiguous strings within the <code>script</code> element. --><br
/><script>document.body.appendChild(document.createElement("div"));</script></pre>
</figure>
@@ -1059,7 +1058,7 @@
<p>For prefixed attributes, then, because the rules of <code>polyglot markup</code> as well as the HTML specification
itself dictates that the presence of a <code>xml:lang="foo"</code> must be accompanied with a corresponding
- <code>lang="foo"</code> attribute, then, in a conforming <a>polyglot</a> document, one can use the same
+ <code>lang="foo"</code> attribute, then, in a conforming <a title="polyglot markup">polyglot</a> document, one can use the same
approach as for the <code>xmlns</code> attribute.</p>
<pre class="example"><code class="css">[*|lang]{color:lime}</code></pre>
<p class="note">However, the requirement of <a>polyglot markup</a> to use both <code>xml:lang="foo"</code> and <code>lang="foo"</code>
@@ -1221,7 +1220,9 @@
</table>
<p>
- The following table makes use of the <code>col>/code> element and therefore uses the then required <code>colgroup</code> element as <code>col</code> element wrapper for, as described in the <a href="#required-elements">Required elements and tags</a> section.
+ The following table makes use of the <code>col</code> element and therefore uses the
+ then required <code>colgroup</code> element as <code>col</code> element wrapper for,
+ as described in the <a href="#required-elements">Required elements and tags</a> section.
</p>
<table>
<colgroup>
Received on Friday, 18 October 2013 18:40:17 UTC