Re: [Ltru] Consensus call: extlang

Peter Constable <petercon@microsoft.com> Tue, 03 June 2008 06: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 8B2663A6BE3; Mon, 2 Jun 2008 23:26:51 -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 40A5C3A6BAE for <ltru@core3.amsl.com>; Mon, 2 Jun 2008 23:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.545
X-Spam-Level:
X-Spam-Status: No, score=-10.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 fv2xjRAotlsR for <ltru@core3.amsl.com>; Mon, 2 Jun 2008 23:26:48 -0700 (PDT)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 2C7CC28C157 for <ltru@ietf.org>; Mon, 2 Jun 2008 23:26:42 -0700 (PDT)
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.18.53) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.1.240.5; Mon, 2 Jun 2008 23:26:44 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.46]) by TK5-EXHUB-C102.redmond.corp.microsoft.com ([157.54.18.53]) with mapi; Mon, 2 Jun 2008 23:26:43 -0700
From: Peter Constable <petercon@microsoft.com>
To: LTRU Working Group <ltru@ietf.org>
Date: Mon, 02 Jun 2008 23:26:41 -0700
Thread-Topic: [Ltru] Consensus call: extlang
Thread-Index: AcjCb86l6vRsciwpQgupBs8Mw6qTXwChM1JQABLhy+A=
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB83579563335449CE@NA-EXMSG-C117.redmond.corp.microsoft.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>
In-Reply-To: <1EEB09866D70AA48A93C0D9EB7237F0B014C231039@USSDIXMSG20.spe.sony.com>
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

> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of
> Broome, Karen


> The historic registrations of other tags (such as zh-yue and
> zh-min-nan) clearly shows that "zh" has always included Cantonese and
> other Asian languages...
> It seems like you are indicating that "zh" is the shortest
> tag for Mandarin, but not Cantonese...

Do all keep in mind comments I made a week or two ago about historical development leading up to macrolanguage:

- the macrolanguage concept means that some treat it as one language while some treat it as many

- the alpha-2 code in ISO 639-1 was initially created by terminologists, for whom developed language varieties would have been of interest, which for "Chinese" would have been Mandarin

- the alpha-3 code in ISO 639-2 was created (in part) by librarians, for whom "Chinese" was explicitly meant to cover both Mandarin and Cantonese


The different points of view expressed by Karen and by Mark are, I think, not surprising or coincidental: the need to be clear that "zh" includes Cantonese as well as Mandarin is appropriate and is consistent with existing use exemplified by library practice; and the utility, in practice, of recognizing a particular association between "zh" and Mandarin in some applications (though not necessarily all) is also appropriate and stems from the same factors that were involved in the practice of Terminologists: for a lot of business application to date, the only Chinese language with particular relevance for text scenarios has been Mandarin.

There are two realities; both need to be recognized. I see that happening by saying something to the effect of, "'zh' _means_ "Chinese"; in some applications, especially text scenarios, it may be appropriate to treat use of 'zh' in existing implementations as being particularly associated with Mandarin".


Peter


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