IETF Logo Mail Archive

RE: Subtag registration: Russian transliteration of Chinese

"Doug Ewell" <doug@ewellic.org> Tue, 13 October 2015 16:47 UTC

Return-Path: <doug@ewellic.org>
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 37D657C025E for <ietf-languages@alvestrand.no>; Tue, 13 Oct 2015 18:47:51 +0200 (CEST)
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 SApC0SlCJxaG for <ietf-languages@alvestrand.no>; Tue, 13 Oct 2015 18:47:50 +0200 (CEST)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from pechora3.lax.icann.org (pechora3.icann.org [IPv6:2620:0:2d0:201::1:73]) by mork.alvestrand.no (Postfix) with ESMTPS id 5986F7C0257 for <ietf-languages@alvestrand.no>; Tue, 13 Oct 2015 18:47:49 +0200 (CEST)
Received: from p3plwbeout03-03.prod.phx3.secureserver.net (p3plsmtp03-03-2.prod.phx3.secureserver.net [72.167.218.215]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id t9DGlQYk023942 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ietf-languages@iana.org>; Tue, 13 Oct 2015 16:47:47 GMT
Received: from localhost ([72.167.218.243]) by p3plwbeout03-03.prod.phx3.secureserver.net with bizsmtp id UgnS1r0015FgiYg01gnS6u; Tue, 13 Oct 2015 09:47:26 -0700
X-SID: UgnS1r0015FgiYg01
Received: (qmail 18990 invoked by uid 99); 13 Oct 2015 16:47:26 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.189
User-Agent: Workspace Webmail 5.15.9
Message-Id: <20151013094724.665a7a7059d7ee80bb4d670165c8327d.14960e68d0.wbe@email03.secureserver.net>
From: Doug Ewell <doug@ewellic.org>
To: Yegor Grebnev <yegor.grebnev@wolfson.ox.ac.uk>, Markus Scherer <markus.icu@gmail.com>
Subject: RE: Subtag registration: Russian transliteration of Chinese
Date: Tue, 13 Oct 2015 09:47:24 -0700
Mime-Version: 1.0
X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Tue, 13 Oct 2015 16:47:47 +0000 (UTC)
Cc: ietf-languages <ietf-languages@iana.org>
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: Tue, 13 Oct 2015 16:47:51 -0000

Yegor Grebnev wrote:

> Sorry, it seems that I have misunderstood Doug's original
> recommendation. Yes, "Chinese transcribed as Russian" seems to be an
> appropriate option. Thank you!

So it sounds like Yegor does expect the transformed content to continue
to be identified primarily as Chinese, not as Russian, where "ru-t-zh"
or "ru-anything" might imply the latter.

So, I know RFC 6497 has been around for three and a half years, but I
guess I'm still a little puzzled by the idea that content in language A,
transliterated according to the orthographic conventions of language B,
should result in that content being labeled "language B" according to
the primary language subtag.

Consider:

(English)
This is a sample sentence.

(Russian)
Это образец приговор.

(Russian, transliterated according to some English-specific convention)
Eto obrazets prigovor.

These snippets would be tagged, respectively, as "en", "ru", and
(according to 6497) "en-t-ru". Is this right?

--
Doug Ewell | http://ewellic.org | Thornton, CO 🇺🇸

v2.23.0 | Report a Bug | By Email