RE: Issue 88, content-language-multiple: change proposal

Hi Roy,

> Where is the word "pragma" coming from?  

I'm using pragma purely because that's how Ian refered to these things in
HTML5, and I thought I ought to be consistent with that.  See for example,
section 4.2.5.3, which is called "Pragma directives".
http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#p
ragma-directives

> My concern for HTML5 is that the orthogonality of http-equiv be preserved.
> I suggest you take the lead on the changes regarding language default and
> I'll construct a change that makes it clear what http-equiv means and why.

Sure, but just so that I'm clear, you mean to add wording about that in the
same change proposal, right ?

Shall I give you write access to the i18n wiki ?

RI

============
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 Roy T. Fielding
> Sent: 13 January 2010 19:33
> To: Richard Ishida
> Cc: public-i18n-core@w3.org; 'Leif Halvard Silli'; 'Michael (tm) Smith'
> Subject: Re: Issue 88, content-language-multiple: change proposal
> 
> On Jan 13, 2010, at 10:37 AM, Richard Ishida wrote:
> 
> > As a result of the i18n telecon discussion I have changed two things in
the
> change proposal:
> >
> > [1] Propose that 'document-wide default language' now be changed to
> 'Content Language pragma language' (not very beautiful, but most
accurate).
> >
> > [2] Added another impact:
> > "Establishes a clear precedence model for language declarations:
language
> attribute is stronger than HTTP or pragma (defined in HTML 4), pragma is
> stronger than HTTP (not clear in HTML 4)."
> 
> Hi Richard,
> 
> Where is the word "pragma" coming from?  I know what it means in
> computer
> language processing and in HTTP, but neither has anything to do with
> content-language and I find it very confusing.
> 
> My concern for HTML5 is that the orthogonality of http-equiv be preserved.
> I suggest you take the lead on the changes regarding language default and
> I'll construct a change that makes it clear what http-equiv means and why.
> 
> ....Roy
>

Received on Wednesday, 13 January 2010 19:47:19 UTC