IETF Logo Mail Archive

Re: [Ltru] Is 639-3 bogus ? (was: Proposal: include new"Language-Type:" field)

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXJfv-0003lS-AS; Tue, 10 Oct 2006 11:37:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXJfu-0003ki-8c for ltru@lists.ietf.org; Tue, 10 Oct 2006 11:37:46 -0400
Received: from rsmtp1.corp.yahoo.com ([207.126.228.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXJfs-0006MC-Tz for ltru@lists.ietf.org; Tue, 10 Oct 2006 11:37:46 -0400
Received: from [10.72.72.226] (snvvpn1-10-72-72-c226.corp.yahoo.com [10.72.72.226]) (authenticated bits=0) by rsmtp1.corp.yahoo.com (8.13.6/8.13.6/y.rout) with ESMTP id k9AFbXU6041930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Oct 2006 08:37:33 -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=VPFfJV7FgF9tIHgg/qyZ8FFivkj/zR8+8JhrZIlE11q4+HIAXloojoGutzHZ43kq
Message-ID: <452BBE3E.1060100@yahoo-inc.com>
Date: Tue, 10 Oct 2006 08:37:34 -0700
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Peter Constable <petercon@microsoft.com>
Subject: Re: [Ltru] Is 639-3 bogus ? (was: Proposal: include new"Language-Type:" field)
References: <F8ACB1B494D9734783AAB114D0CE68FE0B1B1999@RED-MSG-52.redmond.corp.microsoft.com>
In-Reply-To: <F8ACB1B494D9734783AAB114D0CE68FE0B1B1999@RED-MSG-52.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ltru@lists.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

Peter Constable wrote:
> 
> I'm not saying I think the type info is needed; 
 > I am inclined to think it would be good to include
 > the scope values, though. And as for the source not
 > identifying collections, actually it does: every
 > alpha-3 in 639-2 that is not in 639-3 is a collection.
> 

The LSR doesn't indicate which alpha3 codes are ISO 639-2 vs. ISO 639-3, 
so collections won't be clear in the registry unless we label them 
somehow, which this proposal does provide. On the other hand, 
"collection" codes are just language subtags that someone may choose or not.

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.

I'm against replicating information just to replicate it. It would be 
simpler and more efficient to provide a link to ISO 639-3 and point out 
that there is more information there. Oh. Wait. We already do that. ;-)

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

v2.23.0 | Report a Bug | By Email