This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9426 - Define an algorithm for how to extract a language/languages from a comma separated content-language list
Summary: Define an algorithm for how to extract a language/languages from a comma sepa...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/semantic...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 22:41 UTC by Leif Halvard Silli
Modified: 2010-10-04 14:31 UTC (History)
4 users (show)

See Also:

Attachments

Description Leif Halvard Silli 2010-04-05 22:41:33 UTC 
Mozilla browsers extract a language even when the META content-language declaration or the HTTP content-language header contains a commma separated list.

The I18N working group has suggested to define that first language tag of such a list defines the content langauge.

Maciej has hinted that Webkit could be changed to behave the same way as Mozilla

http://www.w3.org/mid/7FB03D6A-0A22-4DFF-B351-FB85CDCCA9EC@apple.com
Comment 1 Ian 'Hixie' Hickson 2010-04-13 00:53:05 UTC 
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: Did Not Understand Request
Change Description: no spec change
Rationale: What is the use case?