W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 9264] Provide a way to prevent Content-Language from acting as language fallback

From: <bugzilla@wiggum.w3.org>
Date: Thu, 18 Mar 2010 23:23:17 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NsP3d-0001re-Ig@wiggum.w3.org>

--- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>  2010-03-18 23:23:16 ---
(In reply to comment #0)
> Variant 1:  [...]
> Variant 2: []

Variant 3: Stick the finger in soil  (orientate yourself about reality): 

Is it realistic that all browsers start to look at the first META element?
When? Currently, all browsers that look at the META content-language look at
the *last* element, if there are more than one. 

And of these (which includes IE), only Mozilla makes use of this element when
it contains more than one language.

Hence a solution to this problem could be that 

A) Forget about requiring user agents to look a the first META content-language
element first.   
B) On an edge, validators should give a warning *especially* when META
content-language contains only one language.
C)  Spec should advice that, whenever server and/or META is used to send the
content-language, and when the document needs to use an empty lang="" to set an
element to "unknown language" (in other words: when you want to have full
control) then there should always be a last, white-space filled, META
content-language element in the code. 

In particular: If we really ask all user agents to change themselves and look
at the first META content-language element, then we should take a deeper look
at it and make more and more useful changes than that.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 18 March 2010 23:23:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:47 UTC