eliot: 1.68 - 3/14 Edited section 6.5.1 per bugs 12278 and 12279 (comments 3 & 4)

eliot: 1.68 - 3/14 Edited section 6.5.1 per bugs 12278 and 12279
(comments 3 & 4)

http://dev.w3.org/cvsweb/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html?r1=1.67&r2=1.68&f=h

===================================================================
RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -d -r1.67 -r1.68
--- html-xhtml-authoring-guide.html 14 Mar 2011 20:03:20 -0000 1.67
+++ html-xhtml-authoring-guide.html 14 Mar 2011 21:03:45 -0000 1.68
@@ -14,7 +14,7 @@
    <a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a>
   </p>
   <h1 class="title" id="title">Polyglot Markup: HTML-Compatible XHTML Documents</h1>
-  <h2 id="w3c-editor-s-draft-14-march-2011">W3C Editor's Draft 14 March 2011</h2>
+  <h2 id="w3c-editor-s-draft-05-january-2011">W3C Editor's Draft 4 March 2011</h2>
   <dl>
    <dt>This version:</dt>
    <dd><a href="http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html">http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html</a></dd>
@@ -663,21 +663,27 @@
 
   <div id="http-headers-and-http-equiv" class="section">
   <h4><span class="secno">6.5.1 </span>HTTP Headers and http-equiv Declarations</h4>
-  <p>
-   The following HTTP headers and http-equiv declarations warrant special discussion in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
-  </p>
-   <pre class="example">http-equiv: <code>&lt;meta http-equiv="Content-Language" content="ru"/&gt;</code>
-HTTP header: <code>Content-language: ru</code></pre>
   
    <div id="content-language" class="section">
    <h5><span class="secno">6.5.1.1 </span>Content-Language</h5>
    <!-- TODO per bug 12279 XXX -->
    <p>
+    The following HTTP headers and <code>http-equiv</code> declarations warrant special discussion in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
+   </p>
+   <pre class="example">http-equiv: <code>&lt;meta http-equiv="Content-Language" content="ru"/&gt;</code>
+HTTP header: <code>Content-language: ru</code></pre>
+   <p>
     There are no direct issues with regard to the use of 
 Content-Language as long as the language attribute is declared on the 
 root element, 
     as described in <a href="#language-attributes">Language Attributes</a>. 
-    By declaring the language attribute on the root element, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> avoids the differences between XML and HTML in regard to Content-Language. 
+    <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> <em title="must" class="rfc2119">must</em> declare both the <code>xml:lang</code> as well as the <code>lang</code> attributes on the root element 
+    when there is a Content-Language (<code>http-equiv</code> pragma or HTTP header) whose value is exactly a single language tag.
+    By declaring the language attribute on the root element, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> avoids a difference between XML and HTML in regard to Content-Language. 
+   </p>
+   <p class="note">
+    For the sake of simplicity and expediency, content to be delivered as <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> <em title="may" class="rfc2119">may</em> always include both the <code>xml:lang</code> as well as the <code>lang</code> 
+    attributes on the root element. 
    </p>
 <!-- End section: Content-Language -->   
    </div>
@@ -1046,7 +1052,6 @@
 </div>
 
 
-
 <!-- Appendix -->
 <div id="acknowledgements" class="appendix section">
 <h2><span class="secno">A. </span>Acknowledgements</h2>

Received on Monday, 14 March 2011 21:04:58 UTC