Re: [Ltru] Macrolanguage usage

"Mark Davis" <mark.davis@icu-project.org> Fri, 16 May 2008 20:09 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 496E728C282; Fri, 16 May 2008 13:09:40 -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 A8E0928C292 for <ltru@core3.amsl.com>; Fri, 16 May 2008 13:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.981
X-Spam-Level:
X-Spam-Status: No, score=-1.981 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 v84HD030C8nG for <ltru@core3.amsl.com>; Fri, 16 May 2008 13:09:37 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by core3.amsl.com (Postfix) with ESMTP id 2E12228C282 for <ltru@ietf.org>; Fri, 16 May 2008 13:09:36 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so609568ywj.49 for <ltru@ietf.org>; Fri, 16 May 2008 13:09:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=qr0BG+z0rVKRN43nUawvNyHXeEGvg1kKFBgJISOMow0=; b=CKbZ04kKrIGpddfwGPtHbmi1qvxUY3/mqkn5VyTjF7aQMF/hSO4niJRFfTG8/ap/ubrCDJRxoODg/fQ2QG7V3ghPZ9dO4Y8GKAg0uvFpBbWM98Tt7NQZMtDf7tvUBfIy3NPonM106vAKhR7JrczG7v3KrK3oaDrAEIEP071upRE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=V67Z9ljyQxeTl+KIQuyeKTeAw2jROyewfirs/osdGhdwDtqMQgX4ftxIPWJErerfIjoeNjsAALkM7/Qwk1fRhyUKcfAV+x80WGVhQl/BLP8lIiGs1kZDon5nRmrJ/8h/YoMLRKmWgVpfaX9vDa8MtL6ESBDUIUQ6a0hZ9rHuS9E=
Received: by 10.150.68.41 with SMTP id q41mr4019691yba.107.1210968555084; Fri, 16 May 2008 13:09:15 -0700 (PDT)
Received: by 10.150.206.3 with HTTP; Fri, 16 May 2008 13:09:14 -0700 (PDT)
Message-ID: <30b660a20805161309u67158b6arcb3b2df1c46db6a7@mail.gmail.com>
Date: Fri, 16 May 2008 13:09:14 -0700
From: Mark Davis <mark.davis@icu-project.org>
To: Randy Presuhn <randy_presuhn@mindspring.com>
In-Reply-To: <005901c8b787$930f98c0$6801a8c0@oemcomputer>
MIME-Version: 1.0
References: <mailman.494.1210865385.5128.ltru@ietf.org> <00a901c8b6f5$c04529a0$e6f5e547@DGBP7M81> <30b660a20805161108w578b6cf9g11933ca34996a596@mail.gmail.com> <005901c8b787$930f98c0$6801a8c0@oemcomputer>
X-Google-Sender-Auth: 968b7424c13aac7f
Cc: LTRU Working Group <ltru@ietf.org>
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: multipart/mixed; boundary="===============0751123974=="
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

I think that would be fine.

On Fri, May 16, 2008 at 12:03 PM, Randy Presuhn <
randy_presuhn@mindspring.com> wrote:

> 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
>



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