- From: poot <cvsmail@w3.org>
- Date: Fri, 18 Mar 2011 18:06:10 -0400
- To: public-html-diffs@w3.org
eliot: Removed quotation mark that got copied by mistake into the note edited in version 1.70 http://dev.w3.org/cvsweb/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html?r1=1.70&r2=1.71&f=h =================================================================== RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v retrieving revision 1.70 retrieving revision 1.71 diff -u -d -r1.70 -r1.71 --- html-xhtml-authoring-guide.html 18 Mar 2011 21:58:53 -0000 1.70 +++ html-xhtml-authoring-guide.html 18 Mar 2011 22:05:01 -0000 1.71 @@ -773,11 +773,8 @@ then <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> is required to specify the language mapping of the root element. According to <a href="http://dev.w3.org/html5/spec/semantics.html#attr-meta-http-equiv-content-language">Content language state</a> in [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>], the <code>http-equiv="content-language"</code> attribute on the <code><meta></code> element specifices the language of the root element - whenever its <code>content</code> attribute contains no more and no -less than exactly one language tag. - Therefore, not specifying the language mapping of the root element -would mean that HTML5 would interpret this as setting the default -language for the root element, while XML did not." + whenever its <code>content</code> attribute contains no more and no less than exactly one language tag. + Therefore, not specifying the language mapping of the root element would mean that HTML5 would interpret this as setting the default language for the root element, while XML did not. </p> <!--End section: Language Attributes-->
Received on Friday, 18 March 2011 22:06:12 UTC