Re: [Ietf-languages] Language variant subtag "tongyong" addition request (for Mandarin Chinese romanization) (Resubmission)

Sascha Brawer <sascha@brawer.ch> Wed, 20 May 2020 13:47 UTC

Return-Path: <sascha.brawer@gmail.com>
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 4A1E73A09D4 for <ietf-languages@ietfa.amsl.com>; Wed, 20 May 2020 06:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.966
X-Spam-Level: *
X-Spam-Status: No, score=1.966 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 jJOdDBV_6vos for <ietf-languages@ietfa.amsl.com>; Wed, 20 May 2020 06:47:13 -0700 (PDT)
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 7F9383A09D3 for <ietf-languages@ietf.org>; Wed, 20 May 2020 06:47:12 -0700 (PDT)
Received: by mork.alvestrand.no (Postfix) id 13EFB7C3626; Wed, 20 May 2020 15:47:10 +0200 (CEST)
Delivered-To: ietf-languages@alvestrand.no
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.33.71; helo=pechora1.lax.icann.org; envelope-from=sascha.brawer@gmail.com; receiver=ietf-languages@alvestrand.no
Received: from pechora1.lax.icann.org (pechora1.icann.org [192.0.33.71]) by mork.alvestrand.no (Postfix) with ESMTPS id 9AFEE7C3503 for <ietf-languages@alvestrand.no>; Wed, 20 May 2020 15:47:09 +0200 (CEST)
Received: from mail-il1-f194.google.com (mail-il1-f194.google.com [209.85.166.194]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id 807C170063D6 for <ietf-languages@iana.org>; Wed, 20 May 2020 13:47:06 +0000 (UTC)
Received: by mail-il1-f194.google.com with SMTP id 17so3149758ilj.3 for <ietf-languages@iana.org>; Wed, 20 May 2020 06:47:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=et5TzSADDCsZ9nCG12nJrjrq5vifeIM8QKuKpLk5QFU=; b=N8LGBzPaIq+cmUY0MHoO6zrQLipfqrJ0NfWifuZQcnV5IT3faXMGQ7q5rJlHBwbIya h7kWmY6eGkprfu5TNxjyXG0dGgvSJqP6aplAxfoD0Ikads1U2eEB3CuZAS3aEVEtlIc/ Syeo7HrhSrsm9iwEET0ZkmspAk0NmZkoe/npokDSoqcJXDRXqVweYg2NDPFe0udKuTE9 f4WWjMEg+3ii7aDoxCHLXfaNjoHdk1MwRkZrOgChNGfMmdRC0tDXsN5IF1nmguAjphpI mASgPetXpA4t1pelwRKrjb+lvOQ0v3+qUPhoN9gJ57NzUfV5cv8KYzJW2GT5HXxldnsv J0cA==
X-Gm-Message-State: AOAM5323Rm3zE/9gWFFoBVTsifuhjdh9iDOFeHDnA4M8yF25gzkbiwo6 uA98MwnpaHb5rPBDgXpcy/QXhlMB/NI8rZWEwcc=
X-Google-Smtp-Source: ABdhPJx04A1T2jDXcMym3+Oqvk3Sz89CVN2jr0P4c0yLLil0lkWfJJvdDvH0CznCn8QDMkT6nZDZPxUjTvj+ztCY2/Q=
X-Received: by 2002:a92:9e43:: with SMTP id q64mr3820973ili.136.1589982406028; Wed, 20 May 2020 06:46:46 -0700 (PDT)
MIME-Version: 1.0
References: <20190114115125.665a7a7059d7ee80bb4d670165c8327d.4243fb0563.wbe@email03.godaddy.com> <CAGHjPPKq-+3CapO51ZTE3xVRv0rnE00JJrvU-n4WpJQU-teUMA@mail.gmail.com>
In-Reply-To: <CAGHjPPKq-+3CapO51ZTE3xVRv0rnE00JJrvU-n4WpJQU-teUMA@mail.gmail.com>
From: Sascha Brawer <sascha@brawer.ch>
Date: Wed, 20 May 2020 15:46:35 +0200
Message-ID: <CABKQ4ESyG2zkceeVuRAj-tRVBYTNmvQcuJq2v=Ucdg_2LBX7rw@mail.gmail.com>
To: Phake Nick <c933103@gmail.com>
Cc: ietflang IETF Languages Discussion <ietf-languages@iana.org>, Michael Everson <everson@evertype.com>, Doug Ewell <doug@ewellic.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (pechora1.lax.icann.org [0.0.0.0]); Wed, 20 May 2020 13:47:06 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/8OBhck-A7saDuSlWmymtr5AjYXw>
Subject: Re: [Ietf-languages] Language variant subtag "tongyong" addition request (for Mandarin Chinese romanization) (Resubmission)
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: Wed, 20 May 2020 13:47:15 -0000

Instead of a BCP47 variant tag, would it be an option to register a
BCP 47 extension T
transform tag at Unicode CLDFR? This would be similar to the existing
registered tags for
other transliteration schemes such as alaloc, bgn, buckwalt, ungegn, etc.
Your full BCP47 language tag would then look like “zh-Latn-t-zh-m0-tongyong”.

For background about BCP47 extension T, see https://tools.ietf.org/html/rfc6497.
To go this route, file a CLDR ticket:
http://cldr.unicode.org/index/bug-reports#TOC-File-a-Ticket
asking to add a tag for Tongyong to this file:
https://github.com/unicode-org/cldr/blob/master/common/bcp47/transform.xml

— Sascha

Am Mi., 20. Mai 2020 um 15:21 Uhr schrieb Phake Nick <c933103@gmail.com>:
>
> This request is a resubmission of a similar request from January 2019, with a few changes including additional reference links (Thanks to Doug Ewell's help) and also removed hak/nan prefix from the request (While Tongyong romanization system for the two languages have been created published, the amount of people using them seems minimal and thus it's probably betternot to conflate the subtag with the version of system for those languages)
>
> 1. Name of requester: Phake Nick
>
> 2. E-mail address of requester: c933103 at gmail.com
>
> 3. Record Requested:
>
> Type: variant
> Subtag: tongyong
> Description: Tongyong Pinyin romanization
> Prefix: zh-Latn
> Comments: Former official transcription standard for Mandarin Chinese in Taiwan.
>
> 4. Intended meaning of the subtag: Indicate Romanized content that use
> Tongyong pinyin romanization
>
> 5. Reference to published description of the language (book or
> article):
>
> a. "Guidelines of Using Chinese Phonetic Spelling", published by the
> government of Taiwan in 2002.
> http://www.rootlaw.com.tw/LawContent.aspx?LawID=A040030001010900-1000310
>
> b. "Hanyu Pinyin to be standard system in 2009". Shih Hsiu-Chuan. In
> Taipei Times, 2008-09-18.
> http://www.taipeitimes.com/News/taiwan/archives/2008/09/18/2003423528
>
> c. "Lost in Romanisation". In The Economist, 2014-06-07.
> https://www.economist.com/asia/2014/06/07/lost-in-romanisation
>
> 6. Any other relevant information: The Tongyong Pinyin transcription standard was official in Taiwan in the mid-2000s. It has now been displaced by Pinyin romanization as the official transcription rule for Chinese languages in Taiwan, however it is still continually being used to a certain extent within Taiwan and thus it would be helpful to have a variant subtag to separate it from Pinyin Romanization.
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-languages