- From: Richard Ishida <ishida@w3.org>
- Date: Thu, 29 Apr 2010 09:37:45 +0100
- To: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Phillips, Addison'" <addison@lab126.com>
- Cc: <public-html@w3.org>, <public-i18n-core@w3.org>
Hi Julian, I believe that this change proposal will actually *remove* any proposed changes to the syntax of the values for the meta element with Content-Language. (Please be sure you're looking at the right CP[1] of the several currently available.) The rules for parsing any legacy meta element for Content-Language in HTML5 will assume that it could have multiple, comma-separated values. This is no longer a proposal to reduce the syntax to support only one language value. What the proposal will do is greatly simplify the confusion around how to set the default language for text-processing and prevent further migration towards shoe-horning it into an alternative to the lang attribute. I think it is reasonable for HTML to declare that it will not support the Content-Language value of http-equiv, given the alternatives. RI [1] http://lists.w3.org/Archives/Public/public-html/2010Apr/0308 ============ Richard Ishida Internationalization Lead W3C (World Wide Web Consortium) http://www.w3.org/International/ http://rishida.net/ > -----Original Message----- > From: public-i18n-core-request@w3.org [mailto:public-i18n-core- > request@w3.org] On Behalf Of Julian Reschke > Sent: 29 April 2010 09:08 > To: Phillips, Addison > Cc: public-html@w3.org; public-i18n-core@w3.org > Subject: Re: Proposal to make Content-Language pragma non-conforming > altogether for ISSUE-88 (mark I) > > On 29.04.2010 00:12, 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 > > ... > > Again: the syntax inside meta/http-equiv is defined by the definitions > of the HTTP headers; not HTML. This is a layer violation. > > Add discussions for client-side handling of specific values if you want, > but don't break this feature. > > Best regards, Julian > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.814 / Virus Database: 271.1.1/2841 - Release Date: 04/28/10 > 19:27:00
Received on Thursday, 29 April 2010 08:38:18 UTC