Re: [Ltru] Re: Punjabi

"Doug Ewell" <dewell@adelphia.net> Sat, 17 March 2007 17:39 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HScsW-0006Kt-AQ; Sat, 17 Mar 2007 13:39:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HScsV-0006Km-Eo for ltru@ietf.org; Sat, 17 Mar 2007 13:39:39 -0400
Received: from mta10.adelphia.net ([68.168.78.202]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HScsT-00078U-Rc for ltru@ietf.org; Sat, 17 Mar 2007 13:39:39 -0400
Received: from DGBP7M81 ([76.167.184.182]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with SMTP id <20070317173936.UPDN2272.mta10.adelphia.net@DGBP7M81>; Sat, 17 Mar 2007 17:39:36 +0000
Message-ID: <004501c768bb$3bc185e0$6401a8c0@DGBP7M81>
From: Doug Ewell <dewell@adelphia.net>
To: LTRU Working Group <ltru@ietf.org>
References: <E1HRsNL-0001ob-5h@megatron.ietf.org> <003501c76756$f2213760$6401a8c0@DGBP7M81> <30b660a20703161305h1f007acalb7ecf2c45224b4da@mail.gmail.com> <20070316210509.GF17950@mercury.ccil.org> <30b660a20703161537q77fcf86y9c6488e0eb0603b@mail.gmail.com> <45FB2259.7050202@yahoo-inc.com> <30b660a20703161617u85dbfe1r44ddc29fcfcf1a6d@mail.gmail.com> <45FB2C4E.9090303@yahoo-inc.com> <006e01c7682b$f0687b10$d1397130$@net>
Subject: Re: [Ltru] Re: Punjabi
Date: Sat, 17 Mar 2007 10:39:36 -0700
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc:
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

Don Osborn <dzo at bisharat dot net> wrote:

> I also concur with Mark's unease with "baking" in a certain approach, 
> given the potential alternative needs. I would say "flexibility" here 
> but that got me into trouble before.

If the proposal is to allow both "zh-cmn" and "cmn" as synonyms, with 
neither deprecated in favor of the other, then I will indeed object to 
that kind of "flexibility."  The current thinking seems to be that 
matching algorithms will be too dumb to perform anything but basic 
remove-from-right truncation, which would fail dismally under such a 
plan.

> In effect cmn would "map" to zh?

Yes, via the Prefix field.

> I wonder if the existence of the codes doesn't pretty much guarantee 
> that some people will, for whatever reason, use the language code 
> without attention to the macrolanguage code. One would have to 
> consider this possibility and provide for it.

"cmn" would be listed as "Type: extlang".  If people misuse the protocol 
to the point of using extended language subtags alone, without their 
prefix, there is probably nothing we can do about it.  This type of 
person will also invent their own subtags, switch the order of subtags 
from what the ABNF specifies, and so forth.

>> My surmise is that macro-languages are a one-time event: "discovery" 
>> of future macro-languages will mostly be prohibited by rule (since 
>> most of the languages will already have codes in the "primary" 
>> position when they become part of a macro-language collection). If my 
>> surmise is correct, we could ban future extlang additions and use the 
>> remainder of that namespace for (well) nefarious purposes.
>
> Don't agree here. I think there are de facto macrolanguages out there 
> without the title that may need new codes and the extlang 
> relationships with other 639-3 or even 639-1/2 coded (sub)languages 
> that those would imply (Runyakitara, Oshiwambo, and Beti are examples 
> of possibilities, from my understanding of descriptions). At the very 
> least, the door should not be closed.

I think Addison was talking about the combination of (a) ISO 639-3 
adding new macrolanguage relationships with languages that are not 
currently encoded, and (b) our group sticking to its rule about adding 
extlangs.  If we change our rules and allow extlangs to mean something 
other than what they mean in draft-4646bis-02, then anything can happen.

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://users.adelphia.net/~dewell/
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru