Re: [Ltru] Consensus call: extlang

"Phillips, Addison" <addison@amazon.com> Tue, 03 June 2008 19:57 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 E599A3A69D1; Tue, 3 Jun 2008 12:57:06 -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 13BE03A6941 for <ltru@core3.amsl.com>; Tue, 3 Jun 2008 12:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.676
X-Spam-Level:
X-Spam-Status: No, score=-106.676 tagged_above=-999 required=5 tests=[AWL=-0.077, 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 MNTVycHgiQSk for <ltru@core3.amsl.com>; Tue, 3 Jun 2008 12:57:04 -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 4FA403A6BB5 for <ltru@ietf.org>; Tue, 3 Jun 2008 12:55:20 -0700 (PDT)
Received: from smtp-in-0201.sea3.amazon.com ([172.20.19.24]) by smtp-border-fw-out-2101.iad2.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Jun 2008 19:55:22 +0000
Received: from ex-hub-4104.ant.amazon.com (ex-hub-4104.sea5.amazon.com [10.248.163.25]) by smtp-in-0201.sea3.amazon.com (8.12.11/8.12.11) with ESMTP id m53JtJN9014842 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Tue, 3 Jun 2008 19:55:19 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; Tue, 3 Jun 2008 12:55:19 -0700
From: "Phillips, Addison" <addison@amazon.com>
To: Kent Karlsson <kent.karlsson14@comhem.se>, 'LTRU Working Group' <ltru@ietf.org>
Date: Tue, 03 Jun 2008 12:55:18 -0700
Thread-Topic: [Ltru] Consensus call: extlang
Thread-Index: AcjFpwp4wSpHbMhdQra1AHSLp+0CBAAADMxwAAGIwbAAATGl8A==
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013AABBE64@EX-SEA5-D.ant.amazon.com>
References: <01c301c8bbe5$8c2810c0$6801a8c0@oemcomputer><6.0.0.20.2.20080527170755.05bd89c0@localhost><002f01c8c024$0dcdb5c0$6801a8c0@oemcomputer><6.0.0.20.2.20080528163346.074fac80@localhost><001f01c8c122$0cbcae80$6801a8c0@oemcomputer><4D25F22093241741BC1D0EEBC2DBB1DA013A84C314@EX-SEA5-D.ant.amazon.com><007601c8c1bc$84d93920$6801a8c0@oemcomputer><104f01c8c1d8$94ad6f30$0a00a8c0@CPQ86763045110><30b660a20805291559x4f6243a8pecc7ee92c2a36d9c@mail.gmail.com><E19FDBD7A3A7F04788F00E90915BD36C13C251B4FC@USSDIXMSG20.spe.sony.com><30b660a20805300911j1713bff0xa7e8e468e039d42@mail.gmail.com><1EEB09866D70AA48A93C0D9EB7237F0B014C231039@USSDIXMSG20.spe.sony.com><008e01c8c5a7$1ba88b60$6801a8c0@oemcomputer> <4D25F22093241741BC1D0EEBC2DBB1DA013AABBD22@EX-SEA5-D.ant.amazon.com> <AC7A28FFDCDC419F8DFE122581AAF459@streamserve.com>
In-Reply-To: <AC7A28FFDCDC419F8DFE122581AAF459@streamserve.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] Consensus call: extlang
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

> >
> > It is always permissible to tag US English as 'en'. It is
> > also permissible, within one's own application, to require
> > that people who want something other than US English to us a
> > different tag from 'en'. For example, they can be required to
> > use the tag 'en-GB'.
> >
> > What is not permissible is to dismiss someone else's UK
> > English content tagged as 'en' as wrong.
>
>
> You're comparing an apple/pear situation with a peach/nectarine
> situation, if you allow me the analogy. There are differences
> between ("standard") en-US and ("standard") en-GB, sure. But
> it is (most often) VERY small compared to differences between
> languages covered by a macrolanguage code.

Yes. Actually, see my just-posted message. I know this is the case, but I was attempting to draw an illustrative analogy without getting carried away.

> The latter varies
> in degree of difference, but for zh, someone (who I think knows
> this) compared cmn/yue differences as en par with fr/es
> differences, in addition pointing out that the difference was
> greater than between Scandinavian languages.

There are many flavors of difference. How well-received those differences are depends on the specific case. In the 'en' case, one might be satisfied pretty well with the US English information, regardless of which flavo(u)r one prefers. In the 'zh' case, perhaps this is less the case. It doesn't invalidate the problem.

(laughing) For example, when I typed the above paragraph, my spell checker "fixed" 'flavour' to 'flavor' automagically. I had to fix it to make it stick (before deciding to include the parens). If I had requested UK English, I might have been peeved at that.

>
> I'm sure you would not want a macrolanguage code for fr/es,
> even if there was a way to get that (like way back when...),
> nor recommend using a collection code for Gallo-Iberian
> for language tagging.
>

No, but, again, that's not my point. My point is that one can use less-specific tags consciously and deliberately to create a specific effect.

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