Re: Subtag registration: Russian transliteration of Chinese

Avram Lyon <ajlyon@gmail.com> Wed, 14 October 2015 18:16 UTC

Return-Path: <ajlyon@gmail.com>
X-Original-To: ietf-languages@alvestrand.no
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 0EAAC7C036E for <ietf-languages@alvestrand.no>; Wed, 14 Oct 2015 20:16:22 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Authentication-Results: mork.alvestrand.no (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 yTW7VGh67fGt for <ietf-languages@alvestrand.no>; Wed, 14 Oct 2015 20:16:21 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from pechora7.dc.icann.org (pechora7.icann.org [IPv6:2620:0:2830:201::1:73]) by mork.alvestrand.no (Postfix) with ESMTPS id EB9547C0366 for <ietf-languages@alvestrand.no>; Wed, 14 Oct 2015 20:16:20 +0200 (CEST)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) by pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id t9EIFw3Z007288 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ietf-languages@iana.org>; Wed, 14 Oct 2015 18:16:18 GMT
Received: by qkap81 with SMTP id p81so26392249qka.2 for <ietf-languages@iana.org>; Wed, 14 Oct 2015 11:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=AbLXuycyTNCZ+EHmZlc+qzIbCum7g0q2N/K2JFcRqqo=; b=E2jqTr3whVYRXz2qEpjfQQ1ZtVEKwhMtHKACmlgiP9ElR2TMP9ilWoZ0ujWgn0N7sT pefEEqSDZo9Xu/1qN2+dDBC5WEuNCPIKkepn3rGz0Bm0+Sg8DT+AcHaOSR3vNTI2Js3/ oNYYF9Ci1Ise2MAQHITUWu+PmxYReIQuLq3XKrlCSY3JZEHXYtgCRlqEaR1dQejrk/Hl nVYJslV1P+lIUe2xE/u9uSQe6yYT08i1kVEs3xQQJjFRqtHCRBKvT2td5rvwVO4Kmk3C 7+cEmB9fcRjRdOU5KMe38BlLkcrLcd+AoMcyBTz69Xh+B1+rC3WYQaYhpsKs0rvcKBnL QaFA==
X-Received: by 10.55.203.4 with SMTP id d4mr5811684qkj.47.1444846557998; Wed, 14 Oct 2015 11:15:57 -0700 (PDT)
MIME-Version: 1.0
References: <20151014100641.665a7a7059d7ee80bb4d670165c8327d.95c961055d.wbe@email03.secureserver.net>
In-Reply-To: <20151014100641.665a7a7059d7ee80bb4d670165c8327d.95c961055d.wbe@email03.secureserver.net>
From: Avram Lyon <ajlyon@gmail.com>
Date: Wed, 14 Oct 2015 18:15:48 +0000
Message-ID: <CAO2oXAChC5AeuBf8gfpGwSWuTTWrRp6dcDHfdTZ4StyTEdEPNA@mail.gmail.com>
Subject: Re: Subtag registration: Russian transliteration of Chinese
To: Doug Ewell <doug@ewellic.org>, Yury Tarasievich <yury.tarasievich@gmail.com>, ietf-languages <ietf-languages@iana.org>
Content-Type: multipart/alternative; boundary="001a113ac610d835f20522148d16"
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora7.dc.icann.org [IPv6:2620:0:2830:201::1:73]); Wed, 14 Oct 2015 18:16:18 +0000 (UTC)
X-BeenThere: ietf-languages@alvestrand.no
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF Language tag discussions <ietf-languages.alvestrand.no>
List-Unsubscribe: <http://www.alvestrand.no/mailman/options/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: Wed, 14 Oct 2015 18:16:22 -0000

So Extension T can arguably be applied for transformations that have a
target language -- but does it apply when there is solely a target script,
such as ISO 9 (https://en.wikipedia.org/wiki/ISO_9), which certainly should
not be en-t-ru when used with Russian-- because the target is a script, not
a language. Indeed, the exact same ISO 9 romanization could be classed
de-t-ru or en-t-ru or fr-t-ru, even though nothing about the content
changed.

Other cases in the same vein arise with even ALA-LC romanization (alalc97),
which is frequently used even when there is no English or other
Latin-language context, such as a fully romanized set of entries in a card
catalog.

Am I missing something about the way that Extension T interacts with the
existing variant subtags?

Avram