This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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/
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.
(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.
raised in Tracker as Issue 88: http://www.w3.org/html/wg/tracker/issues/88
What's the a11y relevance of this bug?
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.
Removing TrackerRequest since this has already been escalated.
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.
Change proposal by W3C i18n WG awaiting decicion: http://www.w3.org/International/wiki/Htmlissue88
WG Decision: http://lists.w3.org/Archives/Public/public-html/2011Mar/0398.html
I assume this is requesting that I apply the diff in: http://lists.w3.org/Archives/Public/public-html/2010Apr/0308
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.
Checked in as WHATWG revision r5980. Check-in comment: apply wg decision http://html5.org/tools/web-apps-tracker?from=5979&to=5980