RE: [Ltru] Re: Extended language tags

"Debbie Garside" <debbie@ictmarketing.co.uk> Wed, 10 October 2007 09:47 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 1IfYA6-0001Py-0h; Wed, 10 Oct 2007 05:47:30 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IfYA4-0001Pj-V3 for ltru-confirm+ok@megatron.ietf.org; Wed, 10 Oct 2007 05:47:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfYA4-0001PV-Go for ltru@ietf.org; Wed, 10 Oct 2007 05:47:28 -0400
Received: from 132.nexbyte.net ([62.197.41.132] helo=mx1.nexbyte.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IfYA4-0005su-0n for ltru@ietf.org; Wed, 10 Oct 2007 05:47:28 -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 md50007322197.msg for <ltru@ietf.org>; Wed, 10 Oct 2007 10:50:55 +0100
Received: from CPQ86763045110 ([83.67.121.192]) by 145.nexbyte.net with MailEnable ESMTP; Wed, 10 Oct 2007 10:47:29 +0100
From: Debbie Garside <debbie@ictmarketing.co.uk>
To: Shawn.Steele@microsoft.com, 'Doug Ewell' <dewell@roadrunner.com>, 'LTRU Working Group' <ltru@ietf.org>
References: <E1IdcAd-0008M3-Cl@megatron.ietf.org><009301c80a0e$8a4b9c10$6401a8c0@DGBP7M81> <C9BF0238EED3634BA1866AEF14C7A9E55A5987FFBE@NA-EXMSG-C116.redmond.corp.microsoft.com>
Subject: RE: [Ltru] Re: Extended language tags
Date: Wed, 10 Oct 2007 10:46:18 +0100
Message-ID: <04f501c80b22$68debac0$0d00a8c0@CPQ86763045110>
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <C9BF0238EED3634BA1866AEF14C7A9E55A5987FFBE@NA-EXMSG-C116.redmond.corp.microsoft.com>
Thread-Index: AcgKDtABtbHoCNogTkKlXKsVXK54mwAmoFJQAB2EeJA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Processed: mx1.nexbyte.net, Wed, 10 Oct 2007 10:50:55 +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 10:50:56 +0100
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc:
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

Hi

I may have missed the answer to this question, apologies if I have, but why
not include cwm within the registry and then deprecate in favour of zh-cwm?
This way both are in the registry and the fallback, as described by Mark, is
facilitated. The same could be done for zh-yue and yue and no-nb etc.  Thus
if people tag "incorrectly", with, for example, cwm or yue, applications
would come up with the correct match anyway.

I cannot pretend that I understand the entirety of the current conversations
wrt extended language tags but I do think their inclusion would be useful
for matching purposes.

Best regards

Debbie Garside


> -----Original Message-----
> From: Shawn Steele [mailto:Shawn.Steele@microsoft.com]
> Sent: 09 October 2007 20:25
> To: Doug Ewell; LTRU Working Group
> Subject: RE: [Ltru] Re: Extended language tags
>
>
> > > * Even for the current tags, many of the people in the
> > > teleconference seem to extend RFC 4647 in ways that are best for
> > > them.  Strict use of
> > > 4647 behavior seems rare.  It seems reasonable to me to
> expect that
> > > in the future people may continue to do so and that RFC
> 4647 and the
> > > registry can only provide guidelines.
>
> > I agree with the part about RFC 4647, but not the Registry,
> at least
> > not in blanket terms.
>
> > The Registry contains some fields that are normative and
> some that are
> > informative.
>
> Tagging and lookup however are different.  Many of the uses
> I'm involved with presume that tags are correctly defined:
> ie: only installed locales are allowed to be used for
> resource names, or for marking documents.  Presumably the
> locales were created correctly when they were installed, so I
> don't have to worry about "eng" being valid.
>
> Making a matching dependency on the registry would require a
> new data source, which could be problematic, which is why I
> prefer the information be in the tags.  If the tags are
> invalid I won't match correctly, but I won't have to look up
> an on-line dependency.  Obviously this is less of a problem
> for some applications, but I don't see there being any
> downside and it does help to have the ext lang tag in this case.
>
> - Shawn
>
>






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