Re: [Ltru] Macrolanguage usage

Shawn Steele <Shawn.Steele@microsoft.com> Fri, 16 May 2008 19:39 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 0907A3A6B6A; Fri, 16 May 2008 12:39:40 -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 1BDFC3A6B6A for <ltru@core3.amsl.com>; Fri, 16 May 2008 12:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.544
X-Spam-Level:
X-Spam-Status: No, score=-10.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 jX-ZFZ39hqYz for <ltru@core3.amsl.com>; Fri, 16 May 2008 12:39:37 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 5CE523A6977 for <ltru@ietf.org>; Fri, 16 May 2008 12:39:37 -0700 (PDT)
Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.54.46.185) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.1.240.5; Fri, 16 May 2008 12:39:32 -0700
Received: from NA-EXMSG-C116.redmond.corp.microsoft.com ([157.54.62.39]) by tk1-exhub-c101.redmond.corp.microsoft.com ([157.54.46.185]) with mapi; Fri, 16 May 2008 12:39:32 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: "Phillips, Addison" <addison@amazon.com>, Peter Constable <petercon@microsoft.com>, Doug Ewell <doug@ewellic.org>, LTRU Working Group <ltru@ietf.org>
Date: Fri, 16 May 2008 12:39:31 -0700
Thread-Topic: [Ltru] Macrolanguage usage
Thread-Index: Aci3JsQR79pXsZVBSjCDjtvmPhwOZgANuV+wAAEc12AAA73A1AAAa27gAAYuUBI=
Message-ID: <C9BF0238EED3634BA1866AEF14C7A9E561554BEB05@NA-EXMSG-C116.redmond.corp.microsoft.com>
References: <mailman.494.1210865385.5128.ltru@ietf.org> <00a901c8b6f5$c04529a0$e6f5e547@DGBP7M81> <DDB6DE6E9D27DD478AE6D1BBBB83579562E143D665@NA-EXMSG-C117.redmond.corp.microsoft.com>, <4D25F22093241741BC1D0EEBC2DBB1DA013A118FF0@EX-SEA5-D.ant.amazon.com> <C9BF0238EED3634BA1866AEF14C7A9E561554BEAF9@NA-EXMSG-C116.redmond.corp.microsoft.com>, <4D25F22093241741BC1D0EEBC2DBB1DA013A218331@EX-SEA5-D.ant.amazon.com>
In-Reply-To: <4D25F22093241741BC1D0EEBC2DBB1DA013A218331@EX-SEA5-D.ant.amazon.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] Macrolanguage usage
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

---
While documents written in Standard Mandarin SHOULD use the 'cmn' (Mandarin) language subtag to form the larger language tag, for some applications where it is necessary to indicate that the text is intended for wide accessibility MAY be indicated by using the 'zh' subtag.
--

What I'm looking for is a subtle distinction.  What this sounds like is "use the cmn subtag for Mandarin, but if you want 'wide accessibility' they you're going to want zh instead".  I don't want developers to think "gee, do I want to support only Mandarin, or all of China?  Well, China's got more users, so I'll tag it zh".

Apps should be able to make the correlation between zh and cmn and yue if appropriate for them, so the zh tag only sounds that helpful in the "legacy" context, or when you don't know if its truely Mandarin.  I do not want Mandarin to be commonly tagged as zh when it can be avoided.

So I'm thinking something more like this (draft, I don't really like how well I said it)

---
While documents written in Standard Mandarin SHOULD use the 'cmn' (Mandarin) language subtag to form the larger language tag, the 'zh' (General Chinese) subtag MAY be used if the actual variation is not known or for compatibility with older applications.
---


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