Re: [Ltru] Consensus call: extlang

Leif Halvard Silli <lhs@malform.no> Tue, 03 June 2008 19:26 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 015693A6B99; Tue, 3 Jun 2008 12:26:45 -0700 (PDT)
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 662CA3A6B7A for <ltru@core3.amsl.com>; Tue, 3 Jun 2008 12:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level:
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BqqMyUrJKuMN for <ltru@core3.amsl.com>; Tue, 3 Jun 2008 12:26:43 -0700 (PDT)
Received: from lakepoint.domeneshop.no (lakepoint.domeneshop.no [194.63.248.54]) by core3.amsl.com (Postfix) with ESMTP id 190453A6AE1 for <ltru@ietf.org>; Tue, 3 Jun 2008 12:26:16 -0700 (PDT)
Received: from 10013.local (cm-84.208.108.246.getinternet.no [84.208.108.246]) (authenticated bits=0) by lakepoint.domeneshop.no (8.13.8/8.13.8) with ESMTP id m53JQDIi010219; Tue, 3 Jun 2008 21:26:13 +0200
Message-ID: <48459AD5.5000109@malform.no>
Date: Tue, 03 Jun 2008 21:26:13 +0200
From: Leif Halvard Silli <lhs@malform.no>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b1) Gecko/20060724 Thunderbird/2.0a1 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: "Phillips, Addison" <addison@amazon.com>
References: <01c301c8bbe5$8c2810c0$6801a8c0@oemcomputer><6.0.0.20.2.20080527170755.05bd89c0@localhost><002f01c8c024$0dcdb5c0$6801a8c0@oemcomputer><6.0.0.20.2.20080528163346.074fac80@localhost><001f01c8c122$0cbcae80$6801a8c0@oemcomputer><4D25F22093241741BC1D0EEBC2DBB1DA013A84C314@EX-SEA5-D.ant.amazon.com><007601c8c1bc$84d93920$6801a8c0@oemcomputer><104f01c8c1d8$94ad6f30$0a00a8c0@CPQ86763045110><30b660a20805291559x4f6243a8pecc7ee92c2a36d9c@mail.gmail.com><E19FDBD7A3A7F04788F00E90915BD36C13C251B4FC@USSDIXMSG20.spe.sony.com><30b660a20805300911j1713bff0xa7e8e468e039d42@mail.gmail.com> <1EEB09866D70AA48A93C0D9EB7237F0B014C231039@USSDIXMSG20.spe.sony.com> <008e01c8c5a7$1ba88b60$6801a8c0@oemcomputer> <4D25F22093241741BC1D0EEBC2DBB1DA013AABBD22@EX-SEA5-D.ant.amazon.com>
In-Reply-To: <4D25F22093241741BC1D0EEBC2DBB1DA013AABBD22@EX-SEA5-D.ant.amazon.com>
Cc: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] Consensus call: extlang
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Phillips, Addison 2008-06-03 20.32:

>> I share this concern.  It must be crystal clear that 'zh'
>> does NOT mean Mandarin, but rather any kind of Chinese.
> 
> +1
> 
>> Of course, there are cases where one might deliberately be
>> imprecise in tagging, but we should not be so
> 
> It is always permissible to tag Mandarin as 'zh'. It is also


I hear this a lot:

	«'zh' is for all Chinese. But it is permissible to use 'zh' for 
Mandarin.»

If you really want to emphasize that 'zh' is for all, then you 
must start saing that it is permissible to use 'zh' for Cantonese 
- because we allready know that it is allowed for Mandarine.

> permissible, within one's own application, to require that
> people who want something other than Mandarin to use a
> different tag than 'zh'. For example they can be required to
> use the tag (choose one: yue | zh-yue).

Then it is also permissible to require Mandarin users to use 'cmn'.

If we, as Doug said, "believe" in the macrolangauge thing, that it 
describes a real thing, then we should emphasize that it is not at 
all advicable to say that 'zh' means Cantonese or Mandarin in any 
context.

What we *should* say is that the Macrolanguage code should not be 
locked to any particular variety. Application developers should 
strive to keep it as a "free code" - a wild card that can be used 
by any of the encompassed languages.

By wild card I mean this: when I use Mac OS X with Nynorsk as 
preferred langgae, then 'no' should lean towards meaning 'nn'. 
That is: If a text editor is tagged as having 'no' interface, 
then, even if this in reality means that it is Bokmål, still, for 
deciding which spell checking dictionary to use as default (often 
this is synced with the GUI langauge), the application should 
default to 'nn'/Nynorsk. But if I run Mac OS X with Bokmål as 
preferred langauge, then 'no' should default to be interpreted as 
an alias for 'nb' - thus bokmål dictionaries should be picked.

The users will then have to accept that they cannot expect to have 
full control over the interface language of applications tagged as 
'no'. And this is not difficult. Users accept this easily. As long 
as you do not use 'no' but translate it in the user interface as 
'Nynorsk' or 'Bokmål'. Same for zh/Chinese, if it in some language 
is translated as 'Mandarin', then you will get user reactions if 
you use it for any thing else but Mandarin. Hence, such use should 
be avoided.


> What is not permissible is to dismiss someone else's Cantonese
> content tagged as 'zh' as wrong.
> 
> A corollary example might help:
> 
> It is always permissible to tag US English as 'en'. It is also
> permissible, within one's own application, to require that
> people who want something other than US English to us a
> different tag from 'en'. For example, they can be required to
> use the tag 'en-GB'.
> 
> What is not permissible is to dismiss someone else's UK English
> content tagged as 'en' as wrong.


Let me reuse your example:

  In Mac OS X I can select UK English as preferred language. 
Unless 'en_UK' localisations are available, then the 'en' tagged 
localisations with 'en-US' content will be served. However, there 
will be one important difference: UK dictioanaries will be 
preferred over US ones. And and certain other things will shift to 
its British values.

Just like the "color" of the "en" tag shifts based on whether the 
user prefers en-US, en-UK, en-Ca etc, the same way the 
Macrolanguage tag should shift according to which variety of the 
Chinese/Norwegian/Arabic language one is preferring.

Btw, since I have been critical about Apple, I think they do the 
right thing when they use 'en' for US English *while still* 
translating its meaning as "English" and not as "US English". It 
is *this* which is permissible. And if this is what you mean, 
Addision, then I agree with you. But if you mean that one can use 
"en" but put a "US English" on it as a label, then I disagree.
-- 
leif halvard silli
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru