13394 2011-07-27 17:56:33 +0000 i18n-ISSUE-74: Remove Content-Language meta from polyglot 2013-10-30 21:37:33 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC All RESOLVED FIXED P2 normal --- 1 public-i18n-core eliotgra eliotgra mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51566 0 public-i18n-core 2011-07-27 17:56:33 +0000 7.2 Language Attributes http://www.w3.org/TR/html-polyglot/#language-attributes "For the mechanism to actually set a fallback language, however, it has to locate either an http-equiv="Content-Language" declaration on the meta element or an HTTP Content-Language: header, either of whose content value is no more and no less than exactly one language tag. Note that although the mechanism can locate either the meta element or the header, the meta element is considered first." Content-Language meta is now non-conforming in HTML5. We think this has two implications for the polyglot spec: 1. the spec should clearly state that "Polyglot markup does not use the meta element with an http-equiv attribute in the Content Language state." 2. since the polyglot spec already requires the lang+xml:lang attributes if an http header or meta uses Content-Language with a single language value (to override the value), the whole of the paragraph containing the text quoted above is (interesting but) irrelevant. We think the paragraph should be dropped. 53159 1 mike 2011-08-04 05:07:12 +0000 mass-move component to LC1 53200 2 mike 2011-08-04 05:07:34 +0000 mass-move component to LC1 95580 3 eliotgra 2013-10-30 21:37:33 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted I believe that this bug has previously been fixed, and so I am marking it so. The current editor's draft states: When specifying the language mapping of an element, polyglot markup uses both the lang and the xml:lang attributes. Neither attribute is to be used without the other, and polyglot markup maintains identical values for both lang and xml:lang. The root element SHOULD always specify the language, or else HTML’s fallback language effect may step in and cause the language to vary depending on whether the document is consumed as XML (where the fallback language is not required to work) or consumed via file URI (where fallback language via external HTTP Content-Language would not work). Note that the internal http-equiv="Content-Language meta element is non-conforming in HTML5. For more, see e.g. HTML5’s language determination rules. http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html#language-attributes When specifying the language mapping of an element, polyglot markup uses both the lang and the xml:lang attributes. Neither attribute is to be used without the other, and polyglot markup maintains identical values for both lang and xml:lang. The root element SHOULD always specify the language, or else HTML’s fallback language effect may step in and cause the language to vary depending on whether the document is consumed as XML (where the fallback language is not required to work) or consumed via file URI (where fallback language via external HTTP Content-Language would not work). Note that the internal http-equiv="Content-Language meta element is non-conforming in HTML5. For more, see e.g. HTML5’s language determination rules.