Re: [Ltru] Consensus call: extlang

Leif Halvard Silli <lhs@malform.no> Wed, 28 May 2008 00:37 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 D1EB13A6817; Tue, 27 May 2008 17:37:48 -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 77A763A67E1 for <ltru@core3.amsl.com>; Tue, 27 May 2008 17:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.74
X-Spam-Level:
X-Spam-Status: No, score=-2.74 tagged_above=-999 required=5 tests=[AWL=-0.141, BAYES_00=-2.599]
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 VCHaVH0-v8eF for <ltru@core3.amsl.com>; Tue, 27 May 2008 17:37:46 -0700 (PDT)
Received: from lakepoint.domeneshop.no (lakepoint.domeneshop.no [194.63.248.54]) by core3.amsl.com (Postfix) with ESMTP id 90E0B3A6C44 for <ltru@ietf.org>; Tue, 27 May 2008 17:36:47 -0700 (PDT)
Received: from 10013.local (cm-84.208.108.246.getinternet.no [84.208.108.246]) (authenticated bits=0) by lakepoint.domeneshop.no (8.13.8/8.13.8) with ESMTP id m4S0acWD011995; Wed, 28 May 2008 02:36:38 +0200
Message-ID: <483CA918.9090304@malform.no>
Date: Wed, 28 May 2008 02:36:40 +0200
From: Leif Halvard Silli <lhs@malform.no>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b1) Gecko/20060724 Thunderbird/2.0a1 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: "Broome, Karen" <Karen_Broome@spe.sony.com>
References: <01c301c8bbe5$8c2810c0$6801a8c0@oemcomputer> <008a01c8bedc$72b97b20$6801a8c0@oemcomputer> <30b660a20805252132g28ff50b0kd5b04d6f47ca35d2@mail.gmail.com> <002001c8bef3$e0497520$6801a8c0@oemcomputer> <30b660a20805262003j21fff6c4tf20d59be11f28633@mail.gmail.com> <E19FDBD7A3A7F04788F00E90915BD36C13C251B2E2@USSDIXMSG20.spe.sony.com>
In-Reply-To: <E19FDBD7A3A7F04788F00E90915BD36C13C251B2E2@USSDIXMSG20.spe.sony.com>
Cc: LTRU Working Group <ltru@ietf.org>
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="utf-8"
Content-Transfer-Encoding: base64
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

Broome, Karen 2008-05-28 00.09:

> Mark writes: [...]

> • 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".
> 
> Karen responds: [...]

> But you didn't ask for Mandarin, you asked for Chinese. [...]
> This is where I think we are prioritizing generalized fallback
> over precision in identification -- even if what we are
> precisely identifying is intentionally vague. I lose the
> ability to identify "some kind of Chinese, I don't know what
> kind" if zh is thought to be synonymous with Mandarin. (A real
> need given the history of these tags.) I also will not know
> what the user intended if they use the tag "zh". 


So, keeping 'zh' general, we will know what it meant until now.

> When it becomes possible to tag more specifically, we won't be
> able to know whether the decision to use the more general tag
> ("zh") was a conscious choice or not.


True. We won't know.

> zh is a bad tag; its semantics have always been muddy. We are
> going to rather great lengths to avoid deprecating it.

Then I want to ask: Do you think that we should/could deprecate 
'zh' but still have extlang? And, do you think that all 
macrolanguage tags for which there exist extlang tags -  in 
principle should be deprecated? (Or would you even prefer to 
deprecate the other macrolangauge tags?)

[ Browsers would then need to use the 'zh' in order to match old 
resources, only. (We could perhaps expect e.g server software to 
perform the extra hoop that Apache allready does for browsers 
which asks for 'en-GB' when they should be asking for 'en'. In 
fact Apache would do the same trick if the browser asks for 
'zh-cmn'.) ]

Thus is it so that the fallback that you want is only fallback 
from current tagging to deprecated tagging?
-- 
leif halvard silli
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru