- From: <bugzilla@jessica.w3.org>
- Date: Mon, 14 Mar 2011 20:10:13 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12279 Eliot Graff <eliotgra@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #1 from Eliot Graff <eliotgra@microsoft.com> 2011-03-14 20:10:12 UTC --- Added the following to the polyglot spec as of the 14 MArch Editor's Draft: ]] 6.5.1 HTTP Headers and http-equiv Declarations The following HTTP headers and http-equiv declarations warrant special discussion in polyglot markup. Example http-equiv: <meta http-equiv="Content-Language" content="ru"/> HTTP header: Content-language: ru 6.5.1.1 Content-Language 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 Language Attributes. By declaring the language attribute on the root element, polyglot markup avoids the differences between XML and HTML in regard to Content-Language. 6.5.1.2 Content-Type The HTTP Content-Type: header has no extra rules or restrictions, whereas polyglot markup does not use the http-equiv="Content-Type" declaration on the <meta> element. For more specific information about using the HTTP Content-Type: header, see Specifying a Document's Character Encoding. [[ I believe that this satisfies the request in this bug, so I am resolving it as fixed. However, you beg a question in 6.5.1.1. Do you want to explain the differences between HTML and XML in regard to Content-Language? ]] By declaring the language attribute on the root element, polyglot markup avoids the differences between XML and HTML in regard to Content-Language. [[ If so, please reopen the bug with proposed text. I think it's probably enough to say there are differences, but if you want to be specific, I'll respect that. Thanks, Eliot -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 14 March 2011 20:10:16 UTC