IETF Logo Mail Archive

Re: [Ltru] Consensus call: extlang

"Phillips, Addison" <addison@amazon.com> Tue, 03 June 2008 18:32 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 6A18A3A691C; Tue, 3 Jun 2008 11:32:15 -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 CFECF3A691C for <ltru@core3.amsl.com>; Tue, 3 Jun 2008 11:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.684
X-Spam-Level:
X-Spam-Status: No, score=-106.684 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 WLdNxujJDrGK for <ltru@core3.amsl.com>; Tue, 3 Jun 2008 11:32:13 -0700 (PDT)
Received: from smtp-fw-6101.amazon.com (smtp-fw-6101.amazon.com [72.21.208.25]) by core3.amsl.com (Postfix) with ESMTP id 3AEC93A6930 for <ltru@ietf.org>; Tue, 3 Jun 2008 11:32:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,585,1204502400"; d="scan'208";a="318533616"
Received: from smtp-in-5102.iad5.amazon.com ([10.218.9.29]) by smtp-border-fw-out-6101.iad6.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Jun 2008 18:32:11 +0000
Received: from ex-hub-4104.ant.amazon.com (ex-hub-4104.sea5.amazon.com [10.248.163.25]) by smtp-in-5102.iad5.amazon.com (8.12.11/8.12.11) with ESMTP id m53IWAA7029834 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Tue, 3 Jun 2008 18:32:11 GMT
Received: from EX-SEA5-D.ant.amazon.com ([10.248.163.28]) by ex-hub-4104.ant.amazon.com ([10.248.163.25]) with mapi; Tue, 3 Jun 2008 11:32:10 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, LTRU Working Group <ltru@ietf.org>
Date: Tue, 03 Jun 2008 11:32:08 -0700
Thread-Topic: [Ltru] Consensus call: extlang
Thread-Index: AcjFpwp4wSpHbMhdQra1AHSLp+0CBAAADMxw
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013AABBD22@EX-SEA5-D.ant.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>
In-Reply-To: <008e01c8c5a7$1ba88b60$6801a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

>
> 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 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).

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.

Addison
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru

v2.23.0 | Report a Bug | By Email