Re: [Ltru] a modest proposal...

"Phillips, Addison" <addison@amazon.com> Thu, 29 May 2008 21:22 UTC

Return-Path: <ltru-bounces@ietf.org>
X-Original-To: ltru-archive@megatron.ietf.org
Delivered-To: ietfarch-ltru-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A64B3A6BE0; Thu, 29 May 2008 14:22:17 -0700 (PDT)
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 B22D43A6BC8 for <ltru@core3.amsl.com>; Thu, 29 May 2008 14:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.382
X-Spam-Level:
X-Spam-Status: No, score=-106.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4sVxt2LADdbb for <ltru@core3.amsl.com>; Thu, 29 May 2008 14:22:14 -0700 (PDT)
Received: from smtp-fw-6101.amazon.com (smtp-fw-6101.amazon.com [72.21.208.25]) by core3.amsl.com (Postfix) with ESMTP id 0A0FC28C1B1 for <ltru@ietf.org>; Thu, 29 May 2008 14:21:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,563,1204502400"; d="scan'208";a="316622996"
Received: from smtp-in-1104.vdc.amazon.com ([10.140.10.25]) by smtp-border-fw-out-6101.iad6.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 May 2008 21:21:33 +0000
Received: from ex-hub-4101.ant.amazon.com (ex-hub-4101.ant.amazon.com [10.248.163.22]) by smtp-in-1104.vdc.amazon.com (8.12.11/8.12.11) with ESMTP id m4TLLWFx015558 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Thu, 29 May 2008 21:21:32 GMT
Received: from EX-SEA5-D.ant.amazon.com ([10.248.163.28]) by ex-hub-4101.ant.amazon.com ([10.248.163.22]) with mapi; Thu, 29 May 2008 14:21:32 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: "Broome, Karen" <Karen_Broome@spe.sony.com>, Peter Constable <petercon@microsoft.com>, LTRU Working Group <ltru@ietf.org>
Date: Thu, 29 May 2008 14:21:31 -0700
Thread-Topic: a modest proposal...
Thread-Index: AcjBw5BlRJZHduEQRBGmurf+XW+6jgAAhYBQAAEiR4AAACZLsAAAzNlA
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013A84C85F@EX-SEA5-D.ant.amazon.com>
References: <4D25F22093241741BC1D0EEBC2DBB1DA013A84C706@EX-SEA5-D.ant.amazon.com> <C9BF0238EED3634BA1866AEF14C7A9E561BF7D8385@NA-EXMSG-C116.redmond.corp.microsoft.com> <DDB6DE6E9D27DD478AE6D1BBBB835795633304EB85@NA-EXMSG-C117.redmond.corp.microsoft.com> <E19FDBD7A3A7F04788F00E90915BD36C13C251B494@USSDIXMSG20.spe.sony.com>
In-Reply-To: <E19FDBD7A3A7F04788F00E90915BD36C13C251B494@USSDIXMSG20.spe.sony.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Ltru] a modest proposal...
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

> I think this proposal may make the guidance task worse.

Are you really saying that Quechua, Cree, Zapotec, Konkani, Malay, Swahili and the rest somehow make Chinese tagging guidance *easier*? I'm totally mystified now about what you think would work.

Guidance under this plan for tagging Chinese could be very straightforward. Perhaps:

--
When selecting a tag for a Chinese language, that tag SHOULD always use the specific extended language subtag. For example, tag Mandarin Chinese content with a tag starting with "zh-cmn", adding any necessary additional subtags for script, region, or variant as appropriate. If the specific variety of Chinese is not known or is not important to the content, the primary language subtag 'zh' MAY be used without an extended language subtag to form the complete tag.
--


Addison


Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.


> -----Original Message-----
> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of
> Broome, Karen
> Sent: Thursday, May 29, 2008 1:39 PM
> To: Peter Constable; LTRU Working Group
> Subject: Re: [Ltru] a modest proposal...
>
> I think this proposal may make the guidance task worse.
>
> Karen
>
> >-----Original Message-----
> >From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf
> >Of Peter Constable
> >Sent: Thursday, May 29, 2008 1:29 PM
> >To: LTRU Working Group
> >Subject: Re: [Ltru] a modest proposal...
> >
> >It's a proposal that (whether with or without Shawn's variation)
> >might be just the right compromise. (See my comments in another mail
> >I just posted.)
> >
> >We would still need to have text giving clear guidance on how to tag
> >for Chinese.
> >
> >
> >Peter
> >
> >> -----Original Message-----
> >> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On
> >Behalf Of
> >> Shawn Steele
> >> Sent: Thursday, May 29, 2008 12:54 PM
> >> To: Phillips, Addison; LTRU Working Group
> >> Subject: Re: [Ltru] a modest proposal...
> >>
> >> I would either like that, or the same thing, except where cmn and
> >yue
> >> are allowed as aliases of zh-cmn & zh-yue
> >>
> >> - Shawn
> >>
> >> -----Original Message-----
> >> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On
> >Behalf Of
> >> Phillips, Addison
> >> Sent: Thursday, May 29, 2008 12:38 PM
> >> To: LTRU Working Group
> >> Subject: [Ltru] a modest proposal...
> >>
> >> Since:
> >>
> >> 1. We appear to be stuck.
> >> 2. We (most of us, anyway) would like to see this work completed.
> >> 3. We haven't a compelling-enough technical argument that resolves
> >the
> >> issue.
> >>
> >> I would like to submit a "modest proposal" for addressing the
> >impasse:
> >>
> >> 1. Restore a *single* extlang to the ABNF.
> >> 2. Keep the Macrolanguage field in the registry for all
> >encompassed
> >> languages, which information may be use by implementations however
> >> makes the most sense.
> >> 3. Cherry pick *only* the 'zh' (and possibly the 'ar') encompassed
> >> languages for registration as extlangs. This is done in the name
> >of
> >> compatibility alone. 4. Permit implementations to treat the
> >'language'
> >> production as atomic (that is, the sequence "zh-yue" MAY be
> >treated as
> >> if it were a single subtag but MAY be treated as separate subtags,
> >> notably by existing implementations). Note that the 'language'
> >> production is the one that includes both the primary and extended
> >> language subtags.
> >>
> >> Thoughts?
> >>
> >> Addison
> >>
> >> Addison Phillips
> >> Globalization Architect -- Lab126
> >>
> >> Internationalization is not a feature.
> >> It is an architecture.
> >>
> >>
> >> _______________________________________________
> >> 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
> >_______________________________________________
> >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
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru