- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Mon, 19 Apr 2010 19:00:46 +0200
- To: www-international@w3.org
Leif Halvard Silli, Mon, 19 Apr 2010 18:17:05 +0200:
> Leif Halvard Silli, Mon, 19 Apr 2010 01:38:49 +0200:
>> CE Whitehead, Sun, 18 Apr 2010 19:19:15 -0400:
>>> Leif Halvard Silli, Sat, 17 Apr 2010 02:45:31 +0200
> …
>>> http://www.w3.org/International/questions/qa-no-language
…
> Btw, the article states that
>
> ]]
> On the very rare occasion when the whole document is in an undefined
> language it is better to just not declare the default language of the
> document.
> [[
>
> However, this advice does not help the slightest, if the user agent is
> inheriting a language from the Content-Language HTTP header or the
> HTTP-EQUIV meta element.
Clarification: In response to bugs I filed because of my change
proposal, [1] the HTML5 editor Ian Hickson told me that user agents
only need to update. And then, if they update, they will be able to
handle e.g. <html lang=""> correctly. However, the QA note from the
I18N WG says that it is (usually) not correct to apply the empty
lang="" on the root element in such cases. It is eventually better to
not declare any language than to explicitly un-declare the language.
And this also happens to be my own understanding.
For that reason, there should be a way - other than not using
Content-Language (on the server side) - for making sure that the user
agent does not inherit the language from Content-Language.
[1]
http://www.w3.org/html/wg/wiki/ChangeProposals/lang_versus_contentLanguage
--
leif halvard silli
Received on Monday, 19 April 2010 17:01:21 UTC