W3C home > Mailing lists > Public > www-html@w3.org > September 2003

Re: Problem with LANG keyword

From: Paul <paul@chaos-studio.com>
Date: Thu, 25 Sep 2003 00:09:10 +0800
Message-ID: <001001c382b6$30ec5800$8801a8c0@meanbitch>
To: <www-html@w3.org>

would be nice to see this even for languages such as Chinese: simplified and
traditional as it has been an issue using both languages on one document,
problem I have seen is when using languages such as French with Chinese
where the Unicode characters interfere with each other like letters in
French displaying as Chinese characters.

so being able to define which is which would decrease the chances of this
happening

Paul

//979//Nan-Suzhou-Road//Space-301//Shanghai//200001//PRC//Office//(86)-21//6
360-5418//Fax//(86)-21//6350-7147//mp//130.2329.1471//paul@chaos-studio.com/
/
----- Original Message ----- 
From: "Johannes Koch" <koch@w3development.de>
To: "Reuven Nisser" <rnisser@ofek-liyladenu.org.il>
Cc: <www-html@w3.org>
Sent: Wednesday, September 24, 2003 11:37 PM
Subject: Re: Problem with LANG keyword


>
> Reuven Nisser wrote:
> > Hello,
> > I agree that my argument holds only when different languages use
different
> > alphabets. Yes, it's a limitation I can live with.
> >
> > Notice that the Content-Language META allows usage of more than one
> > language. It also defines that the order of the languages is important
and
> > represents "priorities".
>
>  From HTTP/1.1:
> 14.12 Content-Language
>
> Multiple languages MAY be listed for content that is intended for
> multiple audiences. For example, a rendition of the "Treaty of
> Waitangi," presented simultaneously in the original Maori and English
> versions, would call for
>
>         Content-Language: mi, en
>
> However, just because multiple languages are present within an entity
> does not mean that it is intended for multiple linguistic audiences. An
> example would be a beginner's language primer, such as "A First Lesson
> in Latin," which is clearly intended to be used by an English-literate
> audience. In this case, the Content-Language would properly only include
> "en".
>
>
> And I can't find anything about priorities in the section. According to
> the HTTP/1.1 spec, a document with hebrew text interspersed with english
> words, should be sent with
>    Content-Language: he
> because the intended audience is hebrew speaking people, not english
> speaking people.
> -- 
> Johannes Koch
> In te domine speravi; non confundar in aeternum.
>                              (Te Deum, 4th cent.)
>
Received on Wednesday, 24 September 2003 12:09:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:58 GMT