Re: [Ietf-languages] EWTS transliteration tag: follow-up

"Doug Ewell" <doug@ewellic.org> Tue, 19 February 2019 21:41 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 C52AA130FA6 for <ietf-languages@ietfa.amsl.com>; Tue, 19 Feb 2019 13:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 FKIpiDQ9iOL6 for <ietf-languages@ietfa.amsl.com>; Tue, 19 Feb 2019 13:41:55 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71BDD130F8B for <ietf-languages@ietf.org>; Tue, 19 Feb 2019 13:41:55 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id 748317C3FAF; Tue, 19 Feb 2019 22:41:53 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 60FBD7C3F78 for <ietf-languages@alvestrand.no>; Tue, 19 Feb 2019 22:41:53 +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 mc3-Hp6PnWrL for <ietf-languages@alvestrand.no>; Tue, 19 Feb 2019 22:41:51 +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.46.72; helo=pechora6.dc.icann.org; envelope-from=doug@ewellic.org; receiver=ietf-languages@alvestrand.no
Received: from pechora6.dc.icann.org (pechora6.icann.org [192.0.46.72]) by mork.alvestrand.no (Postfix) with ESMTPS id ACA1C7C3F33 for <ietf-languages@alvestrand.no>; Tue, 19 Feb 2019 22:41:50 +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 pechora6.dc.icann.org (Postfix) with ESMTPS id A0A371E070F for <ietf-languages@iana.org>; Tue, 19 Feb 2019 21:41:47 +0000 (UTC)
Received: from p3plgemwbe03-07.prod.phx3.secureserver.net ([72.167.218.135]) by :WBEOUT: with SMTP id wD8KgLSmPnuxVwD8Kg5rLs; Tue, 19 Feb 2019 14:40:56 -0700
X-SID: wD8KgLSmPnuxV
Received: (qmail 172397 invoked by uid 99); 19 Feb 2019 21:40:56 -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.55
Message-Id: <20190219144054.665a7a7059d7ee80bb4d670165c8327d.9cb966b7b0.wbe@email03.godaddy.com>
From: Doug Ewell <doug@ewellic.org>
To: Élie_Roux <elie.roux@telecom-bretagne.eu>, IETF Languages Discussion <ietf-languages@iana.org>
Cc: Mark Davis <mark@macchiato.com>
Date: Tue, 19 Feb 2019 14:40:54 -0700
Mime-Version: 1.0
X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.6.2 (pechora6.dc.icann.org [192.0.46.72]); Tue, 19 Feb 2019 21:41:47 +0000 (UTC)
X-CMAE-Envelope: MS4wfG6x5qwKAqeK4L5Xwt7NR72TePrndU34CrtN8rh4aJY6+EGYUcfgY3WGDY5pNnlvOcpTIPtbBqgg9g0XsNMsRHn1I4Fn5lYUrjLA1fbQVzalpLe3roGM pG/SKNPty9vg/7XqKuoLE2C9R2judXpxxtSHRQ4wL3P4nDJNv2gfv5A3fcERh7mgeZ7W+QOwl9/UQhD5G3k47ms7ZLThm8OlPKI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/StO6695GNqgB0HDAveL2Sld974U>
Subject: Re: [Ietf-languages] EWTS transliteration tag: follow-up
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, 19 Feb 2019 21:41:58 -0000

Élie_Roux wrote:
 
> About how many transliteration tag requests were filed since it was
> decided to reroute them to CLDR? How many reached CLDR?
 
I decided to reply now so you wouldn't think list members were
stonewalling or otherwise intentionally not responding. However, neither
I nor anyone else has evidently had time to research this question.
 
If you mean "filed" with this group, someone would have to go through
the list archives, which are only available one message at a time and
not in digest form, and look for discussions. I can do that, but not
right now. (You could also do that; the list archives are public.)
 
> The reason I'm asking is because after 18 months, my two tickets to
> include EWTS and IAST in CLDR ([1], [2]) are yet to see any progress
> and I don't know what to do to normalize these tags.
 
According to the CLDR ticket links you included, 10547 (EWTS) and 10548
(IAST) were targeted 4 months ago for "35-optional", which I guess means
the CLDR people left it open whether to include them in release 35. You
might want to check the alpha or beta data, but it looks like there was
no further discussion and so it might be better to ping CLDR for
information. (We aren't them.)
 
9895 has been targeted for "UNSCH", which I guess means it's on the back
burner. This ticket seems to be about collation rules and not a
transliteration identifier as such, and so I'm not sure why that link
was included here.
 
> CLDR 34 only includes 20 transliteration tags so there doesn't seem to
> be any overflow of such tags that would need to be reviewed.
 
Again, we aren't CLDR, so we can't speak for their workload or
priorities.
 
> Also, the
> processing time for a request on this mailing list seems relatively
> short (a few days/weeks), while the processing time at CLDR apparently
> takes a few dozen months (other requests seem to take a similar amount
> of time, see [3]).
 
Noted. We actually take a minimum of two weeks to approve any subtag,
since there is a compulsory review period specified in RFC 5646.
 
> My point is not to judge or annoy anyone, but I'm
> just asking for an acknowledgment of this situation that makes it
> virtually impossible to register transliteration tags, and maybe for a
> reconsideration of the process. What do you think? Could the automatic
> delegation to CLDR be reconsidered?
 
We decided, rightly IMHO, that because CLDR has established an extension
and a mechanism for registering transliteration identifiers, it would
not be a good idea for ietf-languages to register them directly as
variant subtags. This would perpetuate a situation in which, for any
given transliteration scheme, it would be unclear and inconsistent which
mechanism to use.
 
If you are concerned about CLDR's time frame and feel a sense of urgency
to get these encoded, I suggest you communicate that to CLDR. The fact
that our process is faster than theirs doesn't mean we are the right
venue. I know this isn't the expedient answer you were looking for.
 
--
Doug Ewell | Thornton, CO, US | ewellic.org