IETF Logo Mail Archive

RE: Pinyin

Peter Constable <petercon@microsoft.com> Thu, 25 September 2008 20:27 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 16A8F39E40A for <ietf-languages@alvestrand.no>; Thu, 25 Sep 2008 22:27:34 +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 wL3Psc5iYYkW for <ietf-languages@alvestrand.no>; Thu, 25 Sep 2008 22:27:31 +0200 (CEST)
X-Greylist: from auto-whitelisted by SQLgrey-1.6.8
Received: from pechora2.lax.icann.org (pechora2.icann.org [208.77.188.37]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 6234F39E3F7 for <ietf-languages@alvestrand.no>; Thu, 25 Sep 2008 22:27:31 +0200 (CEST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by pechora2.lax.icann.org (8.13.8/8.13.8) with ESMTP id m8PKRegU031050 for <ietf-languages@iana.org>; Thu, 25 Sep 2008 13:28:00 -0700
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.291.1; Thu, 25 Sep 2008 13:27:40 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by tk1-exhub-c101.redmond.corp.microsoft.com ([157.54.46.185]) with mapi; Thu, 25 Sep 2008 13:27:36 -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 13:27:35 -0700
Subject: RE: Pinyin
Thread-Topic: Pinyin
Thread-Index: AckfM3bOKVcM/WVbTw+QF5QVc5/K4QAGTkYg
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB835795633BC6C2EC@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> <DDB6DE6E9D27DD478AE6D1BBBB835795633BC6C00F@NA-EXMSG-C117.redmond.corp.microsoft.com> <003a01c91f33$722b4000$6801a8c0@oemcomputer>
In-Reply-To: <003a01c91f33$722b4000$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 version 0.93.3, clamav-milter version 0.93.3 on pechora2.lax.icann.org
X-Virus-Status: Clean
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora2.lax.icann.org [208.77.188.37]); Thu, 25 Sep 2008 13:28:00 -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 20:27:34 -0000

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

>> B. Register "pinyin" with a broader scope, and register one or more variants to
>> support differentiating the various orthographies.
>
> I can see how this could be made to work, but do not see any value to
> doing it this way.  Our job is not to provide a hierarchical taxonomy of
> orthographies.  WHAT IS THE USE CASE???

I agree.

In a sense, specifying a prefix of *-Latn might be seen as a type of taxonomic hierarchy, which is true. (Same for the various tags for Resian variants.) But we don't do that because we thing everything should be done in a hierarchical manner; we do that because it supports particular use cases.



Peter

v2.23.0 | Report a Bug | By Email