Re: [Ltru] Macrolanguage usage

"Phillips, Addison" <addison@amazon.com> Fri, 16 May 2008 19:36 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 59EAF3A6BA0; Fri, 16 May 2008 12:36:14 -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 3A2233A6BA0 for <ltru@core3.amsl.com>; Fri, 16 May 2008 12:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.661
X-Spam-Level:
X-Spam-Status: No, score=-106.661 tagged_above=-999 required=5 tests=[AWL=-0.062, 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 5tQqDSJw-Slk for <ltru@core3.amsl.com>; Fri, 16 May 2008 12:36:12 -0700 (PDT)
Received: from smtp-fw-2101.amazon.com (smtp-fw-2101.amazon.com [72.21.196.25]) by core3.amsl.com (Postfix) with ESMTP id 067653A68A0 for <ltru@ietf.org>; Fri, 16 May 2008 12:36:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,459,1199664000"; d="scan'208";a="45851834"
Received: from smtp-in-5102.iad5.amazon.com ([10.218.9.29]) by smtp-border-fw-out-2101.iad2.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 May 2008 19:36:06 +0000
Received: from ex-hub-4104.ant.amazon.com (ex-hub-4104.sea5.amazon.com [10.248.163.25]) by smtp-in-5102.iad5.amazon.com (8.12.11/8.12.11) with ESMTP id m4GJa4n9003433 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Fri, 16 May 2008 19:36:04 GMT
Received: from EX-SEA5-D.ant.amazon.com ([10.248.163.28]) by ex-hub-4104.ant.amazon.com ([10.248.163.25]) with mapi; Fri, 16 May 2008 12:36:04 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, LTRU Working Group <ltru@ietf.org>
Date: Fri, 16 May 2008 12:36:03 -0700
Thread-Topic: [Ltru] Macrolanguage usage
Thread-Index: Aci3h51800DWKSbORNG/6E4BWVL9lAAA8PjQ
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013A2185E3@EX-SEA5-D.ant.amazon.com>
References: <mailman.494.1210865385.5128.ltru@ietf.org><00a901c8b6f5$c04529a0$e6f5e547@DGBP7M81> <30b660a20805161108w578b6cf9g11933ca34996a596@mail.gmail.com> <005901c8b787$930f98c0$6801a8c0@oemcomputer>
In-Reply-To: <005901c8b787$930f98c0$6801a8c0@oemcomputer>
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] Macrolanguage usage
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

Hmm... that's a good bit of text.

I incorporated it and did some more editing to cut down the extraneous text, incorporate some of Mark/Peter's text, etc. and posted the result as editor copy "b" here:

  http://www.inter-locale.com/ID/editor/draft-ietf-ltru-4646bis-14b.html#macrolanguages
  http://www.inter-locale.com/ID/editor/draft-ietf-ltru-4646bis-14b.txt

Comments?

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
> Randy Presuhn
> Sent: Friday, May 16, 2008 12:04 PM
> To: LTRU Working Group
> Subject: Re: [Ltru] Macrolanguage usage
>
> Hi -
>
> As a technical contributor...
>
> > From: "Mark Davis" <mark.davis@icu-project.org>
> > To: "Doug Ewell" <doug@ewellic.org>
> > Cc: "LTRU Working Group" <ltru@ietf.org>
> > Sent: Friday, May 16, 2008 11:08 AM
> > Subject: Re: [Ltru] Macrolanguage usage
> ...
> > The only thing that the text is saying is that when there is a
> predominant
> > language, for backwards compatibility -- AND with some careful
> caveats --
> > the above is broadened. This is *not* with respect to permissibility,
> but
> > with respect to recommended practice.
> >
> >    - It is *permissible* to tag Mandarin text with "und" or "zh" or
> "cmn".
> >       - It is a *good idea* to tag/lookup with "cmn"*, except that
> for
> >       backwards compatibility, "zh" may be better for many
> implementations.*
> >    - It is *permissible* to tag Standard Arabic text with "und" or
> "ar" or
> >    "arb".
> >       - It is a *good idea* to tag/lookup with "arb"*, except that
> for
> >       backwards compatibility, "ar" may be better for many
> implementations.*
> >
> > That lets people like Google, which has a very serious and important
> issue
> > with backwards compatibility, support the vast amount of
> Mandarin/Arabic/...
> > that is tagged with "zh", and continue to tag Mandarin content with
> "zh". It
> > also lets people like Shawn's group at Microsoft, having no backwards
> > compatibility issues with "cmn" and "zh", to shift over immediately.
> >
> > It is also orthogonal to the recommendation for non-predominant
> encompassed
> > languages, where we would tag with the more specific tags: "yue",
> > "yue-Hant-HK", "yue-Hant-US", "abh-AF", and so on, once they are
> available.
> ...
>
> I'd re-frame it in slightly different terms, as an example of the "tag
> wisely"
> principle, rather than as anything that might be understood as a
> recommendation.
> "For some applications, it is possible that there will be cases where
> it could
> be advantageous to deliberately use a tag which is imprecise.  For
> example,
> due to the peculiar situation of written Chinese, an application with
> large
> quantities of legacy textual data already tagged with 'zh' might
> countinue
> to use this over-broad tag even for new data which would more precisely
> be
> tagged with 'cmn'."
>
> 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