Re: [Ltru] Macrolanguage usage

"Phillips, Addison" <addison@amazon.com> Fri, 16 May 2008 16:47 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 49FF23A6B56; Fri, 16 May 2008 09:47: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 9A8DA3A6B62 for <ltru@core3.amsl.com>; Fri, 16 May 2008 09:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.504
X-Spam-Level:
X-Spam-Status: No, score=-106.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 fzzq5lL2il90 for <ltru@core3.amsl.com>; Fri, 16 May 2008 09:47:37 -0700 (PDT)
Received: from smtp-fw-9101.amazon.com (smtp-fw-9101.amazon.com [207.171.184.25]) by core3.amsl.com (Postfix) with ESMTP id AB3743A6B60 for <ltru@ietf.org>; Fri, 16 May 2008 09:47:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,630,1199664000"; d="scan'208";a="32824631"
Received: from smtp-in-5102.iad5.amazon.com ([10.218.9.29]) by smtp-border-fw-out-9101.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 May 2008 16:47:32 +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 m4GGlTI9002223 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Fri, 16 May 2008 16:47:29 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; Fri, 16 May 2008 09:47:28 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: Shawn Steele <Shawn.Steele@microsoft.com>, Peter Constable <petercon@microsoft.com>, Doug Ewell <doug@ewellic.org>, LTRU Working Group <ltru@ietf.org>
Date: Fri, 16 May 2008 09:47:27 -0700
Thread-Topic: [Ltru] Macrolanguage usage
Thread-Index: Aci3JsQR79pXsZVBSjCDjtvmPhwOZgANuV+wAAEc12AAA73A1AAAa27g
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013A218331@EX-SEA5-D.ant.amazon.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>
In-Reply-To: <C9BF0238EED3634BA1866AEF14C7A9E561554BEAF9@NA-EXMSG-C116.redmond.corp.microsoft.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

Shawn wrote:
>
> > So we have a small impasse, indicative of the larger problem here: do
> we or do we not
> > recommend against the use of 'zh' to tag Mandarin Chinese? It isn't
> the tagging of
> > Cantonese that is the controversy. It is whether 'zh' is equated with
> Mandarin.
>
> I would recommend against tagging Mandarin chinese with zh.  Most
> people seem to be fairly clear that "zh" means "general unspecified
> chinese" and "cmn" means Mandarin.

Yes. I agree. I'm trying to incorporate everyone's comments into a coherent whole. Since the situation is complex, the "solution" or at least the explantation will necessarily be complex.

>
> --
> <t>With the adoption of this document, subtags for the encompassed
> languages became available for use in language tags. These subtags
> SHOULD be used instead of the macrolanguage subtag 'zh' to identify
> Chinese language content. While documents written in Standard Mandarin
> could use the 'cmn' (Mandarin) subtag, their wide accessibility can be
> indicated by using the 'zh' subtag in this case.</t>
> --
> <shawn> this makes no sense :)  The middle sentence ways "use cmn
> instead of zh". and the final sentence says "use zh instead of cmn".

No, not exactly. What is says is: you *can* label these as 'cmn', but you *can* (the 2119 keyword is MAY, maybe I should use that) indicate your *intention* of making the text (it is text) generally accessible.

Maybe rephrase as:

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

> If the last sentence is necessary, then it should mention back compat
> or other mechanisms (like as part of a list that also includes cmn).
> The way its written is like saying "tag english as 001 (world) because
> lots of people can read it".

Actually, we have a tag for that: it is "i-default" and that is, in fact, the purpose of "i-default".

> I don't think that zh should ever be
> appropriate for cmn (excluding maybe back compat concerns), unless
> people really don't know which chinese it is.  It has been made very
> clear that although most Cantonese speakers may be able to read
> Mandarin, it is not sort of general chinese readable by all when read,
> it is Mandarin.
>
It *is* Mandarin, but using the 'zh' tag might indicate that it is "general purpose" text, and not specific to a particular audience. Software resources, for example, typically use this form of Mandarin. My copy of Windows, for example, offers a number of flavors of Chinese locale--and they all appear to be Mandarin.

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