Re: extlang (was Re: Suggested language for "mis" (Re: [Ltru] RE: ISO 639-2 decision: "mis"))

Addison Phillips <addison@yahoo-inc.com> Tue, 19 June 2007 21:15 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 1I0l2Z-000716-Ey; Tue, 19 Jun 2007 17:15:07 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1I0l2Y-000711-9S for ltru-confirm+ok@megatron.ietf.org; Tue, 19 Jun 2007 17:15:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I0l2Y-00070t-04 for ltru@ietf.org; Tue, 19 Jun 2007 17:15:06 -0400
Received: from rsmtp2.corp.yahoo.com ([207.126.228.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0l2W-0004vU-LQ for ltru@ietf.org; Tue, 19 Jun 2007 17:15:05 -0400
Received: from [172.21.37.80] (duringperson-lx.corp.yahoo.com [172.21.37.80]) (authenticated bits=0) by rsmtp2.corp.yahoo.com (8.13.8/8.13.6/y.rout) with ESMTP id l5JLEgba015947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jun 2007 14:14:43 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=QNQpg9VvxtPPs+Wp54WV/F5vbTS03cFhpz5bGfRWOqq/uEBf9IUEd+IH/wh2gOw8
Message-ID: <46784742.9080009@yahoo-inc.com>
Date: Tue, 19 Jun 2007 14:14:42 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: extlang (was Re: Suggested language for "mis" (Re: [Ltru] RE: ISO 639-2 decision: "mis"))
References: <30b660a20706171252l3c61d451p464b96e864d1a515@mail.gmail.com> <007f01c7b166$8ef7bf10$6401a8c0@DGBP7M81> <30b660a20706181006x3efbf772t9a0751feb070a6cb@mail.gmail.com> <20070619013433.GA15048@mercury.ccil.org> <003701c7b238$16124fc0$6401a8c0@DGBP7M81> <20070619140547.GB30227@mercury.ccil.org> <4677F589.3090003@yahoo-inc.com> <20070619205855.GA19853@sources.org>
In-Reply-To: <20070619205855.GA19853@sources.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: LTRU Working Group <ltru@ietf.org>, Doug Ewell <dewell@roadrunner.com>
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

Stephane Bortzmeyer wrote:
> On Tue, Jun 19, 2007 at 08:26:01AM -0700,
>  Addison Phillips <addison@yahoo-inc.com> wrote 
>  a message of 47 lines which said:
> 
>> I guess I agree about adding "Macrolanguage" to the registry, except
>> that extlang, if preserved, already indicates this with "Prefix".
> 
> Let me check that I understand. The only way, currently, to see if a
> language is a macrolanguage is to check if there exists at least one
> extlang which references it in its Prefix field? Correct?
> 
> So, in SQL:
> 
> SELECT Languages.code AS macrolanguage, count(Extlangs.code) AS Extlangs 
>       FROM Languages,Extlangs WHERE Extlangs.prefix = Languages.code 
>       GROUP BY Languages.code ORDER BY Languages.code; 
> 
> Which yields 54 macrolanguages in 4645bis, zap (Zapotec) being the one
> with the most extlangs, 58 (if we do not count the sign languages).
> 
> Am I correct? (Sorry for using the IETF for my e-learning but I prefer
> to check before commenting.)

Essentially correct.

Note that the proposals I've seen weren't to add pointers in the 
macrolanguage's record to the extlangs, but rather an additional pointer 
in the extlang to the macrolanguage. That strikes me as pointless except 
for the grandfathered ISO 639-2 codes enclosed by macrolanguages that 
can't be extlang.

I take it you're suggesting (or interpreted the proposal) to mean that 
the macrolanguage would contain a pointer or pointers to its 
sublanguages. Hence something like:

%%
Type: language
Subtag: zh
Description: Chinese
...
Encloses: yue,cmn,.....
%%

Is that what you had in mind? Note that this type of field could apply 
even when various grandfathering rules (hello "sh", etc.) don't permit 
the use of extlangs.

Addison


-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.


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