Re: meta content-language

Thinking about languages, i tend to identify a minimum of three language 
categories:


1) language of content

2) user interface language (which may or may not be the same as the 
language), some sites and web applications allow users to choose/change 
the UI language. This may or may not affect the language of content viewed.

3) language of source code documentation and inline source code comments 
(which may or may not be the same as the UI language or content language)


but then i guess i rarely work on monolingual sites, so these 
distinctions are more important.


Andrew



Richard Ishida wrote:

>> From: Felix Sasaki [mailto:fsasaki@w3.org]
>> Sent: 28 August 2008 02:16
>>     
> ...
>   
>>> disallowing it, why not simply  propose that it be treated as equivalent
>>>       
> to
>   
>>> an HTTP header declaration, and clearly specify that browsers can use
>>>       
> the
>   
>>> initial item in any sequence of values for the meta content-language as
>>>       
> a
>   
>>> fallback for the default text-processing language where there is no
>>>       
> language
>   
>>> attribute.
>>>       
>> just to be sure: you mean "where there is no language attribute at the
>> <html> element", right?
>>     
>
> Well, if there were a language attribute on the html element the meta
> information would only be used if there was a comment or anything else
> outside the <html>.  If there wasn't a language attribute on the <html>
> element, the meta information would be applicable down each branch of the
> document tree until a language attribute was encountered.
>
> RI
>
>
>   

-- 
Andrew Cunningham
Vicnet Research and Development Coordinator
State Library of Victoria
328 Swanston Street
Melbourne VIC 3000

Ph: +61-3-8664-7430
Fax: +61-3-9639-2175

Email: andrewc@vicnet.net.au
Alt email: lang.support@gmail.com

http://home.vicnet.net.au/~andrewc/
http://www.openroad.net.au
http://www.vicnet.net.au
http://www.slv.vic.gov.au

Received on Thursday, 28 August 2008 07:25:33 UTC