[Ltru] Re: Frank's comments

"Frank Ellermann" <nobody@xyzzy.claranet.de> Tue, 04 December 2007 08:13 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzSuP-0000nK-3p; Tue, 04 Dec 2007 03:13:37 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IzSuO-0000lF-Jk for ltru-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 03:13:36 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzSuO-0000kU-9p for ltru@lists.ietf.org; Tue, 04 Dec 2007 03:13:36 -0500
Received: from main.gmane.org ([] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzSuL-0005Q0-VC for ltru@lists.ietf.org; Tue, 04 Dec 2007 03:13:36 -0500
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IzSo0-0003FY-2l for ltru@lists.ietf.org; Tue, 04 Dec 2007 08:07:00 +0000
Received: from mail.st-michaelis.de ([]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Tue, 04 Dec 2007 08:07:00 +0000
Received: from nobody by mail.st-michaelis.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ltru@lists.ietf.org>; Tue, 04 Dec 2007 08:07:00 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ltru@lists.ietf.org
From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
Date: Tue, 4 Dec 2007 08:54:18 +0100
Lines: 112
Message-ID: <fj31a4$ejn$1@ger.gmane.org>
References: <E1IzNhV-0004B6-6Y@megatron.ietf.org> <002201c8363a$7e17ef40$6601a8c0@DGBP7M81>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: mail.st-michaelis.de
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Subject: [Ltru] Re: Frank's comments
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

Doug Ewell wrote:

> I'd really like the chairs to declare consensus on a number of topics, 
> because otherwise this happens: old decisions and non-decisions are 
> revisited over and over again.


Of course it also helps to look into the draft from time to time, I now saw
that  there are no biannual expert reappointments, good riddance.  I had
already visions of bothering NomCom with this business, or  copying
the recall procedure into 4646bis. 

>> It still contains "Latin transliterations of descriptions", without saying 
>> what Latin is,
> Do we need to provide a definition of the Latin script?

My definition is simple:  MES-1, optionally plus a few glyphs used on a
"popular" platform.  What's your definition, Latin-1 ?

>> why the subtag review list should create "transliterations" when the
>> source standard didn't bother for whatever reasons.
> The source (ISO) standards will always provide Latin-script 
> descriptions

Okay.  So what does the new MUSTard in the draft ?  Is it about the
variants or "registered languages", and why would anybody want say 
some fonipa transliteration in addition to the description(s) offered by
the requester ?  What's special with "Latn" in a broad Unicode sense,
why no Kore, Jpan, or Brai ?  For RFC 4646 we made sure that we 
have _no_ prejudice for Latn, and permit (in theory) all code points.

> We simply need to make sure we don't register 
> "Description: Тарашкевіца"

You hit an example that I can read, therefore I recall that the review
list managed this registration without a new MUST.

> Hopefully the advent of the UTF-8 Registry will put that to an end.

Apart from causing havoc for some users UTF-8 is still Unicode, and
we had that already in RFC 4646.  BTW, some weeks ago you said
that XML is not all.  With the advent of "ooXML" (valid or otherwise)
I'm confident that hex. NCRs will soon work everywhere.

>> It still contains the unused 5*8ALPHA "registered languages"
>> instead of reviving the good tradition of i-whatever tags
>> for this in the times of 639-3 likely unnecessary loophole.
> I don't believe there is any popular sympathy, let alone consensus, to 
> change this.  I wonder why you would call out Addison for not changing 
> it.

My list contained only one point wrt consensus, the disputed territories.
It was a summary of my objections + rationale.

> You guys can beat the maximum-theoretical-tag-length issue into the 
> ground if you wish.

Will do.  Actually not 31, it's 35 for  5*8( ALPHA ) registered languages.
>> Allegedly it's unclear that a subtag can be "undrepecated" if say (in 
>> theory) ISO 3166-1 revives FX.  Or rather Doug said that it's clearly
>> not allowed, IMO that would be a bug.
> I think it's extremely clear in 4646.  Whether that's a bug is another 
> question, one I think deserves serious discussion.  But we should be 
> careful about breaking our own stability promises, and refusing to 
> un-deprecate a subtag was a stability promise.

IIRC we discussed cases of splits later re-uniting again for RFC 4646,
e.g. a new incarnation of YU, or CS.  And I thought that we made sure 
that this will work as everybody would expect it.

>> It still allows "generic" variants without prefix, they're known to be 
>> cumbersome (fonipa + fonupa).
> I don't see how they're "cumbersome." 

The "most perverse tag" has two variants.  With fonipa or fonupa it's
in theory three, or even four if a pervert manages to use fonipa and
fonupa simultaneously.

Just an example, for 4646 we discussed generic north south westx
eastx and similar cases arriving at SHOULD NOT, after fonipa and
company I'm ready for MUST NOT.
> You're probably more likely to see a 5- to 8-letter registered 
> language subtag before you see an extension.  The barriers to
> creating an extension are just too high.

With a MUST NOT for generic variants folks might manage it.   If
more cases like fonipa + fonupa are identified maybe it will result
in the first extension.   Arguably better than more generic variants,
each extension can have its own rules.  It's hard to decide if 1996
and fonupa in the same tag could make sense or not, and what 
the best order should be.


Ltru mailing list