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

Re: ISSUE-88 content-language: informal consensus check

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Thu, 29 Apr 2010 15:39:39 +0200
To: Maciej Stachowiak <mjs@apple.com>
Cc: "public-html@w3.org" <public-html@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, addison@lab126.com
Message-ID: <20100429153939292244.396eca9a@xn--mlform-iua.no>
Like the I18N WG, I have changed my mind - and have been revising my 
change proposal to reflect this. In essence, I now support the I18N 
WG's original proposal, which, in effect (on the spec) basically is 
identical with what Julian and Roy is saying.

Otherwise, what Addison says on behalf of the I18N WG, does not hold 
true: making Content-Language non-conforming will *not*, quote: 
"eliminate the confusing (and not useful) overlap in language 
declaration".

Making the META content-language non-conforming, will only move the 
"confusion" one step higher up. Because, the HTML5 spec is clear on the 
fact that HTML5 conforming user agents will inherit the language from 
the server whenever there isn't whether a @lang attribute nor a META 
content-language element.

Leif Halvard Silli

Maciej Stachowiak, Wed, 28 Apr 2010 21:09:42 -0700:
> 
> Since the I18N WG endorses this Change Proposal, and the editor also 
> agrees, I'd like to hear if anyone else would object to this as a 
> resolution to ISSUE-88. If no one objects, the Chairs will seek to 
> close this issue by amicable resolution. If there are objections, 
> then we will seek some other way to resolve this issue promptly, such 
> as using a survey.
> 
> Regards,
> Maciej
> 
> On Apr 28, 2010, at 3:12 PM, Phillips, Addison wrote:
> 
>> On 9 April 2010, Ian Hickson proposed [1] a solution to Issue-88 
>> that said in part:
>> 
>> --
>> SUMMARY
>> People are confused by the Content-Language pragma, so it should be made
>> non-conforming.
>> --
>> 
>> The Internationalization Core WG has officially endorsed this 
>> proposed solution [2]. Existing, legacy documents (and non-browser 
>> processes that use this markup) will not be harmed by this solution 
>> while this will eliminate the confusing (and not useful) overlap in 
>> language declaration.
>> 
>> (for I18N Core),
>> 
>> Addison
>> 
>> [1] http://lists.w3.org/Archives/Public/public-html/2010Apr/0308.html
>> [2] http://www.w3.org/2010/04/21-core-minutes.html#item04
>> 
>> Addison Phillips
>> Globalization Architect -- Lab126
>> Chair -- W3C Internationalization WG
>> 
>> Internationalization is not a feature.
>> It is an architecture.
>> 
>> 
> 
Received on Thursday, 29 April 2010 13:40:19 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:17 UTC