Re: [Ltru] Consensus call: extlang

Peter Constable <petercon@microsoft.com> Tue, 27 May 2008 08:54 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 45F863A67A5; Tue, 27 May 2008 01:54:16 -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 2315A3A67DD for <ltru@core3.amsl.com>; Tue, 27 May 2008 01:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.626
X-Spam-Level:
X-Spam-Status: No, score=-10.626 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 8aq9j3wz6fGQ for <ltru@core3.amsl.com>; Tue, 27 May 2008 01:54:14 -0700 (PDT)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 4BBF13A6784 for <ltru@ietf.org>; Tue, 27 May 2008 01:54:14 -0700 (PDT)
Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.54.46.185) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.1.240.5; Tue, 27 May 2008 01:54:19 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by tk1-exhub-c101.redmond.corp.microsoft.com ([157.54.46.185]) with mapi; Tue, 27 May 2008 01:54:18 -0700
From: Peter Constable <petercon@microsoft.com>
To: LTRU Working Group <ltru@ietf.org>
Date: Tue, 27 May 2008 01:54:13 -0700
Thread-Topic: [Ltru] Consensus call: extlang
Thread-Index: Aci/pjihkdCzquBDTwqbPL/M1pWqvwAGLvlbAASgXUA=
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB83579562E2A410C8@NA-EXMSG-C117.redmond.corp.microsoft.com>
References: <01c301c8bbe5$8c2810c0$6801a8c0@oemcomputer> <008a01c8bedc$72b97b20$6801a8c0@oemcomputer> <30b660a20805252132g28ff50b0kd5b04d6f47ca35d2@mail.gmail.com> <002001c8bef3$e0497520$6801a8c0@oemcomputer>, <30b660a20805262003j21fff6c4tf20d59be11f28633@mail.gmail.com> <C9BF0238EED3634BA1866AEF14C7A9E561573585C0@NA-EXMSG-C116.redmond.corp.microsoft.com>
In-Reply-To: <C9BF0238EED3634BA1866AEF14C7A9E561573585C0@NA-EXMSG-C116.redmond.corp.microsoft.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of Shawn Steele

>> ... that the Accept-Language value meaning 'Mandarin then French' would be
>> * under RFC 4646: "zh, fr"
>> * under this proposal: "zh-cmn, zh, fr, zh-cjy;q=0, zh-cpx;q=0, zh-czh;q=0,
>> zh-czo;q=0, zh-gan;q=0, zh-hak;q=0, zh-hsn;q=0, zh-mnp;q=0, zh-nan;q=0,
>> zh-wuu;q=0, zh-yue;q=0".
>
> Under RFC 4646 "zh, fr" doesn't mean "Mandarin, then French" it means
> "Chinese, then french".

Mark: Shawn has a valid point here: you present the two from unequal sets of premises without clarifying that difference, thus (unintentionally, I'm sure) giving a subtly deceiving argument.

All of the zh-??? tags have be valid for 4646 as they would be for a 4646bis with extlang. Thus, all other things being equal, the Accept-Language value "zh, fr" should have just the same meaning and effect in the latter as for the former, as should the value "zh-cmn, zh, ...".

I think that perhaps the contrast you present here is best described not as that between 4646 and a 4646bis *specifically with extlang*, but rather between a situation in which "zh" is predominantly used and a situation in which it is recommended that content be tagged for the specific, encompassed Chinese language rather than being tagged generically as "zh" -- a situation that could obtain under 4646 as well as under 4646bis. And if that situation obtained in a 4646-without-extlang world, then the corresponding Accept-Language value would be "cmn, zh, fr, cjy;q=0, cpx;q=0, ..."


While I was the proto-proponent for extlang, I've come to lean toward no-extlang since, to the extent that I've been able to think through scenarios,

- it seems to me that the benefits are far more limited than what I initially was supposing, and

- because one of the benefits is to slip fallback relationships into a small set of tags whereas in general good fallback needs a lot more -- true for cases related to macrolanguages let alone for the very many more cases not related to any macrolanguages.

I'm concerned, though, about such not-quite-careful-enough cases being made for (or against): someone is likely to sense something not quite right and come back, perhaps with an equally slightly-flawed case, in which event we end up not making any progress. So, to your comment,

> we should consider each of the applications of language tags:
> identification, lookup, filtering, and Accept-Language, and be
> able to have a reasoned judgment on the technical merits

I would only add: we need to do this with *carefully* reasoned judgment, pausing to make sure the arguments presented really do stand up.



Peter


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