Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)

Peter Constable <petercon@microsoft.com> Wed, 15 July 2009 15:26 UTC

Return-Path: <petercon@microsoft.com>
X-Original-To: ltru@core3.amsl.com
Delivered-To: ltru@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7244028C13C for <ltru@core3.amsl.com>; Wed, 15 Jul 2009 08:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.523
X-Spam-Level:
X-Spam-Status: No, score=-10.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jKLfE+ZcZqDF for <ltru@core3.amsl.com>; Wed, 15 Jul 2009 08:26:33 -0700 (PDT)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 0EAF03A6CED for <ltru@ietf.org>; Wed, 15 Jul 2009 08:26:33 -0700 (PDT)
Received: from tk5-exhub-c104.redmond.corp.microsoft.com (157.54.88.97) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.99.4; Wed, 15 Jul 2009 08:25:14 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by tk5-exhub-c104.redmond.corp.microsoft.com ([157.54.88.97]) with mapi; Wed, 15 Jul 2009 08:25:14 -0700
From: Peter Constable <petercon@microsoft.com>
To: "debbie@ictmarketing.co.uk" <debbie@ictmarketing.co.uk>, 'Randy Presuhn' <randy_presuhn@mindspring.com>, 'LTRU Working Group' <ltru@ietf.org>
Date: Wed, 15 Jul 2009 08:25:10 -0700
Thread-Topic: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)
Thread-Index: AcoExZndZwd0A4NlQZKsK0un4iE/ggAUx4RwABHdjjA=
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB8357956B0B299C05@NA-EXMSG-C117.redmond.corp.microsoft.com>
References: <548832E2D1D1486EBAC82789E800224A@DGBP7M81><1d5f01ca04a2$c495dfd0$0c00a8c0@CPQ86763045110> <036201ca04a9$c6500ec0$6801a8c0@oemcomputer> <1dcc01ca0519$f2bbb6b0$0c00a8c0@CPQ86763045110>
In-Reply-To: <1dcc01ca0519$f2bbb6b0$0c00a8c0@CPQ86763045110>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 15:26:35 -0000

SIL certainly has projects involving way more than 2-300. For them, 2000 is not unrealistic.

Peter

-----Original Message-----
From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of Debbie Garside
Sent: Wednesday, July 15, 2009 12:01 AM
To: 'Randy Presuhn'; 'LTRU Working Group'
Subject: Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)

Well for starters, there are separate codes for Catalan and Valencian :-)

And, I rather like the way ISO 639-6 deals with variants of Chinese.

Perhaps you would like to tell me how many of the 7000+ codes of ISO 639-3
will be used.  My guess is approximately 2-300 at present but over time more
and more.  The answer is the same for ISO 639-6.

Essentially, all the reasons for including ISO 639-6 are the same as for
including ISO 639-3.  Unless of course, you think that ISO 639-3 is perfect
and defines all languages distinctly and that anything else cannot, is not,
and definitely is not a language.  Then of course you have to decide that
BCP 47 will only deal with languages and not dialects.  Then, and only then,
may you exclude ISO 639-6.


Debbie

> -----Original Message-----
> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On
> Behalf Of Randy Presuhn
> Sent: 14 July 2009 18:38
> To: LTRU Working Group
> Subject: Re: [Ltru] rechartering to handle 639-6 (was FW:
> Anomalyinupcomingregistry)
>
> Hi -
>
> > From: "Debbie Garside" <debbie@ictmarketing.co.uk>
> > To: "'Doug Ewell'" <doug@ewellic.org>; "'LTRU Working Group'"
> > <ltru@ietf.org>
> > Cc: <L.Gillam@surrey.ac.uk>
> > Sent: Tuesday, July 14, 2009 9:47 AM
> > Subject: Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly
> > inupcomingregistry)
> ...
> > I think we pretty much worked this out a few years ago... See
> > http://www.ietf.org/mail-archive/web/ltru/current/msg06482.html
> > But as I said in my previous message, I am not quite ready
> yet as it
> > will involve some flagging of the data.
> ...
>
> As a technical contributor...
>
> How much content (as a percentage of internet traffic, or as
> a percentage of on-line library holdings, for example) would
> be covered by 639-6 (when it's done) that would not (or could
> not) be covered by the registry updates recently approved and
> the normal operation of ietf-languages@iana.org?
> What languages does it cover that cannot be addressed under
> the current regime?
>
> I'd really like to know the what language tagging problem
> would be fixed by digging into 639-6, what the payoff (in
> terms of users served or content tagged) would be, and why a
> working group would be necessary to cope with it.
>
> Randy
>
> _______________________________________________
> Ltru mailing list
> Ltru@ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
>
>
>




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