- From: <bugzilla@jessica.w3.org>
- Date: Mon, 14 Mar 2011 21:09:38 +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|REOPENED |RESOLVED Resolution| |FIXED --- Comment #5 from Eliot Graff <eliotgra@microsoft.com> 2011-03-14 21:09:38 UTC --- Changes made. Draft now incorporates language to fix 12278, as well as to resolve this bug: ]] 6.5.1.1 Content-Language 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 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. Polyglot markup must declare both the xml:lang as well as the lang attributes on the root element when there is a Content-Language (http-equiv pragma or HTTP header) whose value is exactly a single language tag. By declaring the language attribute on the root element, polyglot markup avoids a difference between XML and HTML in regard to Content-Language. Note For the sake of simplicity and expediency, content to be delivered as polyglot markup may always include both the xml:lang as well as the lang attributes on the root element. [[ Thanks so much. 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 21:09:40 UTC