W3C home > Mailing lists > Public > www-international@w3.org > April to June 2008

RE: [Ltru] Language tag education and negotiation

From: CE Whitehead <cewcathar@hotmail.com>
Date: Tue, 6 May 2008 09:07:50 -0400
Message-ID: <BLU109-W3827C42A881398CB0D9FE2B3D60@phx.gbl>
To: <www-international@w3.org>





It could at least be recommended that translators indicate that the document is a translation in the keywords--when the author has access to the keywords (I just did that for one of my translations!)--until a better place is found in the document.

Also when a link back to the original version of a document is provided, that's helpful.

--C. E. Whitehead
cewcathar@hotmail.com 

> From: petercon@microsoft.com
>
>
> +1
>
>> -----Original Message-----
>> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of
>> Ira McDonald
>> Sent: Sunday, May 04, 2008 3:57 PM
>> To: Stephane Bortzmeyer; Ira McDonald
>> Cc: ltru@ietf.org; www-international@w3.org
>> Subject: Re: [Ltru] Language tag education and negotiation
>>
>> Hi Stephane,
>>
>> Actually, I think it's *not* work for RFC 4646 ter.
>>
>> The metadata for original versus translation doesn't belong in
>> a language tag. Continuing to add optional fields to language
>> tags is just going to make like for more difficult for all of us.
>>
>> Cheers,
>> - Ira
>>
>>
>> --
>> Ira McDonald (Musician / Software Architect)
>> Chair - Linux Foundation Open Printing WG
>> Blue Roof Music/High North Inc
>> email: blueroofmusic@gmail.com
>> winter:
>> 579 Park Place Saline, MI 48176
>> 734-944-0094
>> summer:
>> PO Box 221 Grand Marais, MI 49839
>> 906-494-2434
>>
>> On Sun, May 4, 2008 at 4:59 PM, Stephane Bortzmeyer 
>> wrote:
>>> On Sun, May 04, 2008 at 01:29:06PM -0700,
>>> Mark Davis  wrote
>>>
>>> a message of 185 lines which said:
>>>
>>>> Unfortunately, the specs are ill-defined regarding the q values.
>>>
>>> My main problem with language negotiation in HTTP, and the reason
>> why
>>> I did not configure my browser to list my favorite language (french)
>>> first, is that HTTP make no distinction between original and
>>> translated texts. If I say to the HTTP server "I prefer french, then
>>> english", I get, most of the time, poorly translated and/or
>>> out-of-date pages in french. (Just compare
>>> http://www.microsoft.com/en/us/ and http://www.microsoft.com/fr/fr/.)
>>>
>>> What I really would like to express is "I prefer original text in
>>> french or english, then translated text in one of these two
>>> languages." But that's work for RFC 4646 ter :-)
>>>
>>>
>>> _______________________________________________
>>> Ltru mailing list
>>> Ltru@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ltru
>>>
>> _______________________________________________
>> Ltru mailing list
>> Ltru@ietf.org
>> https://www.ietf.org/mailman/listinfo/ltru
>
Received on Tuesday, 6 May 2008 13:09:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:17 GMT