RE: Pinyin

Peter Constable <petercon@microsoft.com> Thu, 25 September 2008 15:35 UTC

Return-Path: <petercon@microsoft.com>
X-Original-To: ietf-languages@alvestrand.no
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9F3E639E47A for <ietf-languages@alvestrand.no>; Thu, 25 Sep 2008 17:35:46 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYiS-gVKwKuW for <ietf-languages@alvestrand.no>; Thu, 25 Sep 2008 17:35:44 +0200 (CEST)
X-Greylist: from auto-whitelisted by SQLgrey-1.6.8
Received: from pechora3.lax.icann.org (pechora3.icann.org [208.77.188.38]) by eikenes.alvestrand.no (Postfix) with ESMTPS id E324539E40A for <ietf-languages@alvestrand.no>; Thu, 25 Sep 2008 17:35:43 +0200 (CEST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id m8PFZrVo031067 for <ietf-languages@iana.org>; Thu, 25 Sep 2008 08:36:13 -0700
Received: from tk5-exhub-c104.redmond.corp.microsoft.com (157.54.88.97) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.1.291.1; Thu, 25 Sep 2008 08:35:52 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by tk5-exhub-c104.redmond.corp.microsoft.com ([157.54.88.97]) with mapi; Thu, 25 Sep 2008 08:35:52 -0700
From: Peter Constable <petercon@microsoft.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, "ietf-languages@iana.org" <ietf-languages@iana.org>
Date: Thu, 25 Sep 2008 08:35:49 -0700
Subject: RE: Pinyin
Thread-Topic: Pinyin
Thread-Index: AckeyD703n5/3hfhSJK8j8Vkx+M5OwAWr9Qw
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB835795633BC6C00F@NA-EXMSG-C117.redmond.corp.microsoft.com>
References: <mailman.5976.1222283002.6324.ietf-languages@alvestrand.no><7B1C8ACAE1994C49B8A417F457B32083@DGBP7M81><000601c91eb6$274cde40$6801a8c0@oemcomputer> <20080925030358.GD30848@mercury.ccil.org> <001c01c91ec8$3e3dcda0$6801a8c0@oemcomputer>
In-Reply-To: <001c01c91ec8$3e3dcda0$6801a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.93.3/8333/Thu Sep 25 06:06:09 2008 on pechora3.lax.icann.org
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [208.77.188.38]); Thu, 25 Sep 2008 08:36:13 -0700 (PDT)
X-BeenThere: ietf-languages@alvestrand.no
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Language tag discussions <ietf-languages.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@alvestrand.no?subject=unsubscribe>
List-Archive: <http://www.alvestrand.no/pipermail/ietf-languages>
List-Post: <mailto:ietf-languages@alvestrand.no>
List-Help: <mailto:ietf-languages-request@alvestrand.no?subject=help>
List-Subscribe: <http://www.alvestrand.no/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@alvestrand.no?subject=subscribe>
X-List-Received-Date: Thu, 25 Sep 2008 15:35:46 -0000

From: ietf-languages-bounces@alvestrand.no [mailto:ietf-languages-bounces@alvestrand.no] On Behalf Of Randy Presuhn

>> I'm happy to exclude Tongyong now, and just leave the 'pinyin'
>> subtag to cover the various PRC romanizations based on Hanyu
>> Pinyin principles.

> And the use case for lumping these together as a single variant
> is.... ???

Here's my take from what I've heard: There *isn't* a use case to lump these together, but rather that the motivation is (a) that, if we have a subtag "pinyin", then there will be users that use that for various PRC romanizations whether we define it as being for that or not; and (b) that people are thinking there are probably needs to tag content in those other romanizations, so we may as well kill two (or three...) birds with one stone.


Our options:

A. Register "pinyin" with a broader scope, and everything gets tagged the same undifferentiated way wrt written variation.

B. Register "pinyin" with a broader scope, and register one or more variants to support differentiating the various orthographies.

C. Register "pinyin" with a narrow scope -- Hanyu Pinyin only -- and expect implementers to actually read and observe what the registry has to say about the subtag.

D. Register "hpinyin" (or some other subtag) to mean specifically Hanyu Pinyin; others may register subtags for other Romanizations if they wish.

>From what I can tell, only C or D fits the original request; B may satisfy the requester's needs, though I'm guessing Mark might be less satisfied with that.



Peter