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 16979 - i18n-ISSUE-119: provide example of language detection fallback
Summary: i18n-ISSUE-119: provide example of language detection fallback
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-07 18:08 UTC by Addison Phillips
Modified: 2016-04-19 21:54 UTC (History)
7 users (show)

See Also:


Attachments

Description Addison Phillips 2012-05-07 18:08:51 UTC
3.2.3.3 The lang and xml:lang attributes
http://www.w3.org/TR/html5/elements.html#the-lang-and-xml:lang-attributes

For this much discussed paragraph:

--
If none of the node's ancestors, including the root element, have either attribute set, but there is a pragma-set default language set, then that is the language of the node. If there is no pragma-set default language set, then language information from a higher-level protocol (such as HTTP), if any, must be used as the final fallback language instead. In the absence of any such language information, and in cases where the higher-level protocol reports multiple languages, the language of the node is unknown, and the corresponding language tag is the empty string.
--

Wouldn't an example be useful? I can imagine implementers not following what the heck we're talking about.
Comment 1 Ian 'Hixie' Hickson 2012-05-10 17:55:07 UTC
Any suggestions of a realistic example we could add here?
Comment 2 contributor 2012-07-18 07:08:36 UTC
This bug was cloned to create bug 17865 as part of operation convergence.
Comment 3 Travis Leithead [MSFT] 2016-04-19 21:54:52 UTC
HTML5.1 Bugzilla Bug Triage: Example added

https://github.com/w3c/html/pull/220
Feel free to tweak or offer suggestions/corrections. Will carry the conversation on in GitHub.

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!