Re: [Ietf-languages] Tongyong Pinyin bites the dust (was: Pinyin)

"Doug Ewell" <doug@ewellic.org> Tue, 08 January 2019 17:51 UTC

Return-Path: <doug@ewellic.org>
X-Original-To: ietf-languages@ietfa.amsl.com
Delivered-To: ietf-languages@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07DC9130F37 for <ietf-languages@ietfa.amsl.com>; Tue, 8 Jan 2019 09:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0DfY6fPueP7 for <ietf-languages@ietfa.amsl.com>; Tue, 8 Jan 2019 09:51:32 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99129130F35 for <ietf-languages@ietf.org>; Tue, 8 Jan 2019 09:51:31 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id 0AD5F7C5811; Tue, 8 Jan 2019 18:51:30 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id E2AE07C53E7 for <ietf-languages@alvestrand.no>; Tue, 8 Jan 2019 18:51:29 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPrj21HMmufQ for <ietf-languages@alvestrand.no>; Tue, 8 Jan 2019 18:51:27 +0100 (CET)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.33.72; helo=pechora2.lax.icann.org; envelope-from=doug@ewellic.org; receiver=ietf-languages@alvestrand.no
Received: from pechora2.lax.icann.org (pechora2.icann.org [192.0.33.72]) by mork.alvestrand.no (Postfix) with ESMTPS id 5902D7C061F for <ietf-languages@alvestrand.no>; Tue, 8 Jan 2019 18:51:27 +0100 (CET)
Received: from p3plwbeout03-03.prod.phx3.secureserver.net (p3plsmtp03-03-2.prod.phx3.secureserver.net [72.167.218.215]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora2.lax.icann.org (Postfix) with ESMTPS id 9795F1E0575 for <ietf-languages@iana.org>; Tue, 8 Jan 2019 17:51:24 +0000 (UTC)
Received: from p3plgemwbe03-05.prod.phx3.secureserver.net ([72.167.218.133]) by :WBEOUT: with SMTP id gvWLgRYRz7CDBgvWLgJhtm; Tue, 08 Jan 2019 10:50:33 -0700
X-SID: gvWLgRYRz7CDB
Received: (qmail 141043 invoked by uid 99); 8 Jan 2019 17:50:33 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 159.100.160.53
User-Agent: Workspace Webmail 6.9.50
Message-Id: <20190108105031.665a7a7059d7ee80bb4d670165c8327d.925fda7df5.wbe@email03.godaddy.com>
From: Doug Ewell <doug@ewellic.org>
To: ietf-languages <ietf-languages@iana.org>
Cc: Michael Everson <everson@evertype.com>
Date: Tue, 08 Jan 2019 10:50:31 -0700
Mime-Version: 1.0
X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.6.2 (pechora2.lax.icann.org [192.0.33.72]); Tue, 08 Jan 2019 17:51:24 +0000 (UTC)
X-CMAE-Envelope: MS4wfAnTA27RMmaZbwacRrn0dNwL7VCIgQ6BqJ3uCDVxmUKzjVGimsnJ1nMLRMexx04R5t/uoig5t7PIcZTsMGkjdSfxJlj1++X/Sfn/OWLAwi2EVdOuQ/s5 7JP3XTN9Q7QhjoRa0joM9RtvnysujzEYoksosT4knkW2FpBhKQOSzbG0i0ywY7W3rMLyy1UuDzkRw6UmFZPky9VA9oAEwmTlCb4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/zwbunDpoqSkPD23xGIn_Z96ZOvQ>
Subject: Re: [Ietf-languages] Tongyong Pinyin bites the dust (was: Pinyin)
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ietf-languages.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-languages/>
List-Post: <mailto:ietf-languages@ietf.org>
List-Help: <mailto:ietf-languages-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2019 17:51:34 -0000

Michael Everson wrote:

> On 1 Jan 2019, at 23:31, Doug Ewell <doug at ewellic.org> wrote:
>
>> I’m not going to fight this proposal. I just wanted to make sure the
>> discussion 10 years ago was considered.
>
> Well, did you review it and find anything of concern?

I found this, which you wrote on 2008-09-17 in approving the 'pinyin'
subtag:

https://www.alvestrand.no/pipermail/ietf-languages/2008-September/008290.html

| On 17 Sep 2008, at 06:40, Mark Davis wrote:
|
| > What I have requested is a subtag for distinguishing a particular
| > set of orthographic conventions for romanization of Mandarin
| > Chinese, not Tibetan. If John wants a subtag that includes (for
| > whatever reasons you have) both romanizations of Chinese and
| > Tibetan, that's fine. But that's not what I applied for, nor what my
| > company needs.
|
| Maybe, but the subtag you requested can apply to more than one
| language. That is the point. You may need zh-cmn-Latn-pinyin, but the
| final subtag there can be correctly applied to bo-Latn-pinyin and zh-
| Latn-TW-pinyin. This is, as I have said, analogous to the use we make
| of the "fonupa" subtag and as John has said, analogous to the
| "baku1926" subtag we had approved for Jangalif and other related
| orthographies. Pinyin (i.e. with Hanyu Pinyin-like conventions for the
| meaning of "x" and "q") is just the same.
|
| I do not agree to restrict the "pinyin" subtag to Hanyu Pinyin on
| linguistic grounds. The three languages mentioned above use Pinyin
| conventions in certain romanizations (Tibetan for instance also uses
| Wiley).
|
| I am happy to agree to add the "pinyin" subtag so long as it can be
| used for Tibetan and Tongyong (with appropriate prefixes). I don't
| agree to add it as a subtag that is restricted to Hanyu Pinyin alone,
| because I believe that this linguistically incorrect.

Again, I am not trying to arguing against this change. But it should be
understood as a change from the original decision. We do acquire
additional information over time that can cause us to reverse earlier
decisions.

> My view is that if zh is replaced by jh etc then it’s not the same system.

I don't know what 'jh' refers to here.
 
--
Doug Ewell | Thornton, CO, US | ewellic.org