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

Peter Constable <petercon@microsoft.com> Tue, 10 October 2006 18:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXMcq-0007Px-5x; Tue, 10 Oct 2006 14:46:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXMco-0007Pm-MP for ltru@lists.ietf.org; Tue, 10 Oct 2006 14:46:46 -0400
Received: from mailc.microsoft.com ([131.107.115.214] helo=smtp.microsoft.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXMcl-0005qr-D5 for ltru@lists.ietf.org; Tue, 10 Oct 2006 14:46:46 -0400
Received: from mailout6.microsoft.com (157.54.69.150) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server id 8.0.647.8; Tue, 10 Oct 2006 11:46:42 -0700
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.61.148]) by mailout6.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Oct 2006 11:46:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Ltru] Is 639-3 bogus ? (was: Proposal: include new"Language-Type:" field)
Date: Tue, 10 Oct 2006 11:46:17 -0700
Message-ID: <F8ACB1B494D9734783AAB114D0CE68FE0B1B1A7F@RED-MSG-52.redmond.corp.microsoft.com>
In-Reply-To: <452BBE3E.1060100@yahoo-inc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Ltru] Is 639-3 bogus ? (was: Proposal: include new"Language-Type:" field)
thread-index: AcbsgglujEkBgPqySS6wOebWpSVI4wAGjLtA
References: <F8ACB1B494D9734783AAB114D0CE68FE0B1B1999@RED-MSG-52.redmond.corp.microsoft.com> <452BBE3E.1060100@yahoo-inc.com>
From: Peter Constable <petercon@microsoft.com>
To: Addison Phillips <addison@yahoo-inc.com>
X-OriginalArrivalTime: 10 Oct 2006 18:46:41.0455 (UTC) FILETIME=[6D022BF0:01C6EC9C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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>
Content-Type: multipart/mixed; boundary="===============0893008544=="
Errors-To: ltru-bounces@ietf.org

ISO 639-3 is very clear about which items are macrolanguages: it is clear both from the normative scope attribute and from the macrolanguage mapping table.


Peter

-----Original Message-----
From: Addison Phillips [mailto:addison@yahoo-inc.com] 
Sent: Tuesday, October 10, 2006 8:38 AM
To: Peter Constable
Cc: ltru@lists.ietf.org
Subject: Re: [Ltru] Is 639-3 bogus ? (was: Proposal: include new"Language-Type:" field)

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