8088 2009-10-27 17:28:26 +0000 Change back the meaning of <meta http-equiv="Content-Language" content="FOO, BAR"> 2011-04-08 22:20:46 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-meta-http-equiv-content-language a11y, disputedSpec, WGDecision P2 major LC 1 xn--mlform-iua ian hsivonen ian ishida mike mjs public-html-admin public-html-wg-issue-tracking rubys w3c xn--mlform-iua public-html-bugzilla oldest_to_newest 29079 0 xn--mlform-iua 2009-10-27 17:28:26 +0000 http://www.w3.org/mid/op.u2gd6bq7idj3kv@simon-pieterss-macbook.local According to the draft, <meta http-equiv="Content-Language" content="en" > "sets the document-wide default language". As a consequence (?), the draft permits only one language tag in the content attribute. This represents a deviation from how it otherwise is used and specified - e.g. in HTML 4. The draft must say that it defines the languages of the intended audiences, and that it may be used in content negotiation and in search engines etc. And it must permit several languages to be specified. If the spec wants to express a way to decide the "document-wide default language", then one could define another META element variant for that purpose. Or one could define that the first listed language in the list of languages inside "content", represents the documument-wide lanuage. Thus, in in this example, the document-wide language is "en": <meta http-equiv="Content-Language" content="en,fr,sp" > References: http://www.w3.org/International/tutorials/language-decl/ 29123 1 ian 2009-10-27 20:31: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: Rejected Change Description: no spec change Rationale: This request doesn't match how the pragma is used in deployed content. 29130 2 xn--mlform-iua 2009-10-27 21:08:56 +0000 (In reply to comment #1) > Rationale: This request doesn't match how the pragma is used in deployed > content. Eventually, provide documentation for whatever you mean by that claim. 29191 3 mike 2009-10-29 03:04:18 +0000 raised in Tracker as Issue 88: http://www.w3.org/html/wg/tracker/issues/88 29195 4 hsivonen 2009-10-29 13:12:55 +0000 What's the a11y relevance of this bug? 29196 5 w3c 2009-10-29 13:55:25 +0000 Added the keyword #a11y because the document-wide default language is also relevant for the language selection in screenreaders. Admittedly to my knowledge currently no screenreader supports multiple language selection, but that doesn't mean that future versions don't do anything either. So this is a reminder that language definition does have relevance for screenreader software, to what extend multiple languages are relevant remains to be determined. 31307 6 mjs 2010-01-28 04:00:44 +0000 Removing TrackerRequest since this has already been escalated. 31801 7 cooper 2010-02-11 17:26:25 +0000 Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future. 40440 8 w3c 2010-10-01 15:05:26 +0000 Change proposal by W3C i18n WG awaiting decicion: http://www.w3.org/International/wiki/Htmlissue88 46839 9 rubys 2011-03-19 14:32:34 +0000 WG Decision: http://lists.w3.org/Archives/Public/public-html/2011Mar/0398.html 47291 10 ian 2011-04-08 22:14:09 +0000 I assume this is requesting that I apply the diff in: http://lists.w3.org/Archives/Public/public-html/2010Apr/0308 47292 11 ian 2011-04-08 22:15:56 +0000 The diff no longer applies cleanly, so I will attempt to manually apply it. The result may thus not be exactly as suggested in the diff. 47293 12 contributor 2011-04-08 22:20:46 +0000 Checked in as WHATWG revision r5980. Check-in comment: apply wg decision http://html5.org/tools/web-apps-tracker?from=5979&to=5980