Re: [Ltru] Is 639-3 bogus ?

Addison Phillips <addison@yahoo-inc.com> Tue, 10 October 2006 19:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXNOV-0004bo-Hr; Tue, 10 Oct 2006 15:36:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXNOU-0004aS-Dh for ltru@ietf.org; Tue, 10 Oct 2006 15:36:02 -0400
Received: from rsmtp1.corp.yahoo.com ([207.126.228.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXNOT-0005nV-1v for ltru@ietf.org; Tue, 10 Oct 2006 15:36:02 -0400
Received: from [172.21.148.255] (wlanvpn-mc2e-246-255.corp.yahoo.com [172.21.148.255]) (authenticated bits=0) by rsmtp1.corp.yahoo.com (8.13.6/8.13.6/y.rout) with ESMTP id k9AJZgCV054127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Oct 2006 12:35: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=x60zTJo5y/SzPfx/8h44zfIS+oIVT93Pvv0aziyo6wQQE7igL5jxiXQcAJvJDx0l
Message-ID: <452BF610.7040800@yahoo-inc.com>
Date: Tue, 10 Oct 2006 12:35:44 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: John Cowan <cowan@ccil.org>
Subject: Re: [Ltru] Is 639-3 bogus ?
References: <F8ACB1B494D9734783AAB114D0CE68FE0B1B1999@RED-MSG-52.redmond.corp.microsoft.com> <452BBE3E.1060100@yahoo-inc.com> <20061010182238.GF31563@ccil.org>
In-Reply-To: <20061010182238.GF31563@ccil.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ltru@ietf.org
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


John Cowan wrote:
> Addison Phillips scripsit:
> 
>> I was hoping that 639-3 would provide the information on what is 
>> or is not considered a macro-language. But this information isn't 
>> it.
> 
> "Scope" means "individual language or macrolanguage".  You can
> deduce from the registry which are which; a macrolanguage is one
> that appears as the Prefix of some extlangs.

What I was looking for was:

   http://www.sil.org/iso639%2D3/macrolanguages.asp

And:

   http://www.sil.org/iso639%2D3/scope.asp#M

Ideally, extended language subtags would be restricted to the list in 
the first link above and 4646bis would reflect that fact. I don't want 
to construct that list from the registry: I would prefer something much 
more cut-and-dried, i.e. getting it from ISO 639-3.

I can see at least one problem with the macro languages list: there are 
at least some languages (the "Serbo-Croatian" family) that will be 
grandfathered into language subtags rather than extlangs.

Now, all that said, I think it would be useful to include a "type" field 
for "collective" languages (with the warnings about their suitability 
proposed by John) and for "macro" languages (defining what can be used 
as a prefix value in an extlang).

However, I can also see that this information does not necessarily need 
to occur in the registry.

Addison

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.

Internationalization is an architecture.
It is not a feature.

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