Re: [Ltru] Macrolanguage usage

Peter Constable <petercon@microsoft.com> Mon, 26 May 2008 16:30 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 CD9AF3A69A0; Mon, 26 May 2008 09:30:25 -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 133E93A69A0 for <ltru@core3.amsl.com>; Mon, 26 May 2008 09:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.585
X-Spam-Level:
X-Spam-Status: No, score=-10.585 tagged_above=-999 required=5 tests=[AWL=0.014, 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 5Xunt8UwMMex for <ltru@core3.amsl.com>; Mon, 26 May 2008 09:30:24 -0700 (PDT)
Received: from smtp.microsoft.com (maila.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id 437BE3A68F2 for <ltru@ietf.org>; Mon, 26 May 2008 09:30:24 -0700 (PDT)
Received: from tk5-exhub-c103.redmond.corp.microsoft.com (157.54.88.96) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.1.240.5; Mon, 26 May 2008 09:30:27 -0700
Received: from NA-EXMSG-C117.redmond.corp.microsoft.com ([157.54.62.44]) by tk5-exhub-c103.redmond.corp.microsoft.com ([157.54.88.96]) with mapi; Mon, 26 May 2008 09:30:24 -0700
From: Peter Constable <petercon@microsoft.com>
To: 'LTRU Working Group' <ltru@ietf.org>
Date: Mon, 26 May 2008 09:30:21 -0700
Thread-Topic: [Ltru] Macrolanguage usage
Thread-Index: Aci+2yxGnFrjqMpsQoOAnXRpCT7kJwAKm4CAABFndlA=
Message-ID: <DDB6DE6E9D27DD478AE6D1BBBB83579562E2A41027@NA-EXMSG-C117.redmond.corp.microsoft.com>
References: <mailman.494.1210865385.5128.ltru@ietf.org><00a901c8b6f5$c04529a0$e6f5e547@DGBP7M81><30b660a20805161108w578b6cf9g11933ca34996a596@mail.gmail.com><005901c8b787$930f98c0$6801a8c0@oemcomputer><30b660a20805161309u67158b6arcb3b2df1c46db6a7@mail.gmail.com><C9BF0238EED3634BA1866AEF14C7A9E561554BEB09@NA-EXMSG-C116.redmond.corp.microsoft.com><30b660a20805161415kb1172f0xa6c4dea251344bb6@mail.gmail.com><4832C21A.4050800@malform.no><30b660a20805201344m22f0f40cmdfba059b0123e477@mail.gmail.com><4834D693.10505@malform.no><30b660a20805212357h1cb04c00k86a64ba6621151ab@mail.gmail.com><48380784.7000001@malform.no> <DDB6DE6E9D27DD478AE6D1BBBB83579562E2A40FC3@NA-EXMSG-C117.redmond.corp.microsoft.com><014d01c8be91$7a61bc20$0201a8c0@streamserve.com> <483A2542.3070209@malform.no> <017b01c8bf0a$cad935b0$0201a8c0@streamserve.com>
In-Reply-To: <017b01c8bf0a$cad935b0$0201a8c0@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] 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

> From: ltru-bounces@ietf.org [mailto:ltru-bounces@ietf.org] On Behalf Of
> Kent Karlsson


> 2) Even when fallback to language tag prefix does apply, it is more
>    often than not inappropriate to fall back to a macrolanguage...

I'd suggest that, in just those cases, it's probably not helpful, in general, to tag content/resources with the macrolanguage ID. Of course, that is just what librarians have sometimes done, though their situation may be exceptional: I suspect they do this when dealing with smaller volumes of content and/or in languages of lower demand such that it is not cost effective to tag the content more specifically.


> > > So a no-extlang model is simpler to explain and apply, and
> >
> > For whom?
>
> Everyone. Users, software developers, you and me, this WG, IETF,
> IANA, ...
> A language code can then always be in the first position, not sometimes
> mostly arbitrarily forced to be in the second position (as an extlang).
> It will not introduce new false fallback to prefix, not introduce new
> politically sensitive fallbacks/prefixes, leave users with more easily
> managed language preference lists, etc.

This covers concerns expressed to me about complexity of extlang.


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