RE: [Ltru] RE: duel(ing) tags

"Debbie Garside" <debbie@ictmarketing.co.uk> Wed, 10 October 2007 20:39 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 1IfiL6-00053G-AF; Wed, 10 Oct 2007 16:39:32 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IfiL5-000534-6x for ltru-confirm+ok@megatron.ietf.org; Wed, 10 Oct 2007 16:39:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfiL4-00052v-SM for ltru@ietf.org; Wed, 10 Oct 2007 16:39:30 -0400
Received: from 132.nexbyte.net ([62.197.41.132] helo=mx1.nexbyte.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IfiL4-0001Zn-Ff for ltru@ietf.org; Wed, 10 Oct 2007 16:39:30 -0400
Received: from 145.nexbyte.net ([62.197.41.145]) by mx1.nexbyte.net (mx1.nexbyte.net [62.197.41.132]) (MDaemon PRO v9.6.2) with ESMTP id md50007325460.msg for <ltru@ietf.org>; Wed, 10 Oct 2007 21:42:58 +0100
Received: from CPQ86763045110 ([83.67.121.192]) by 145.nexbyte.net with MailEnable ESMTP; Wed, 10 Oct 2007 21:39:33 +0100
From: Debbie Garside <debbie@ictmarketing.co.uk>
To: Shawn.Steele@microsoft.com, addison@yahoo-inc.com
References: <E1Ifdys-0005rn-RG@megatron.ietf.org><C9BF0238EED3634BA1866AEF14C7A9E55A5988038C@NA-EXMSG-C116.redmond.corp.microsoft.com> <470D2F66.2010202@yahoo-inc.com> <060201c80b79$9a7079f0$0d00a8c0@CPQ86763045110> <C9BF0238EED3634BA1866AEF14C7A9E55A59880490@NA-EXMSG-C116.redmond.corp.microsoft.com>
Subject: RE: [Ltru] RE: duel(ing) tags
Date: Wed, 10 Oct 2007 21:38:15 +0100
Message-ID: <060801c80b7d$7e0d7d90$0d00a8c0@CPQ86763045110>
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <C9BF0238EED3634BA1866AEF14C7A9E55A59880490@NA-EXMSG-C116.redmond.corp.microsoft.com>
Thread-Index: AcgLeKwEnoA0O6lJSC+xA/wWE7++agAAIQiAAAC3ncAAACfKUA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Processed: mx1.nexbyte.net, Wed, 10 Oct 2007 21:42:58 +0100 (not processed: message from valid local sender)
X-MDRemoteIP: 62.197.41.145
X-Return-Path: prvs=18038546a2=debbie@ictmarketing.co.uk
X-Envelope-From: debbie@ictmarketing.co.uk
X-MDaemon-Deliver-To: ltru@ietf.org
X-MDAV-Processed: mx1.nexbyte.net, Wed, 10 Oct 2007 21:43:00 +0100
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ltru@ietf.org
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: debbie@ictmarketing.co.uk
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

Shawn wrote:

Its just my experience
> that people don't really always pay that much attention, so
> they might use both.  I was merely suggesting that robust
> applications might want to recognize both forms, even if one
> was "illegal".

But if we already know that is what people will do (which is the case) and
if we are to use extended language subtags with the inclusion of 639-3
within the registry why not include a way to catch the "illegal" tags that
is easy for applications to implement?   I see more use than harm in using
extended language subtags and deprecating the individual 639-3 codes to
facilitate matching.  This can be documented within 4646bis.

Best regards

Debbie


> -----Original Message-----
> From: Shawn Steele [mailto:Shawn.Steele@microsoft.com]
> Sent: 10 October 2007 21:30
> To: debbie@ictmarketing.co.uk; addison@yahoo-inc.com
> Cc: ltru@ietf.org
> Subject: RE: [Ltru] RE: duel(ing) tags
>
> > > I definitely am against providing both tagging options.
>
> > But where is the harm in including cmn in the registry and then
> > deprecating in favour of zh-cmn?  As stated previously, this would
> > catch those who unwittingly tag with any 639-3 code and are
> unaware of
> > macrolanguages and 4646bis.
>
> I wasn't suggesting registering both.  Its just my experience
> that people don't really always pay that much attention, so
> they might use both.  I was merely suggesting that robust
> applications might want to recognize both forms, even if one
> was "illegal".
>
> - Shawn
>
>
>






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