Re: [Ltru] my technical position on extlang

Leif Halvard Silli <lhs@malform.no> Tue, 20 May 2008 11:41 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 06D863A68B3; Tue, 20 May 2008 04:41:35 -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 5A06728C0F7 for <ltru@core3.amsl.com>; Tue, 20 May 2008 04:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650, 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 iPbKr+KueijU for <ltru@core3.amsl.com>; Tue, 20 May 2008 04:41:29 -0700 (PDT)
Received: from lakepoint.domeneshop.no (lakepoint.domeneshop.no [194.63.248.54]) by core3.amsl.com (Postfix) with ESMTP id 89F663A6808 for <ltru@ietf.org>; Tue, 20 May 2008 04:41:29 -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 m4KBfHSv016416; Tue, 20 May 2008 13:41:18 +0200
Message-ID: <4832B8DD.802@malform.no>
Date: Tue, 20 May 2008 13:41:17 +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: John Cowan <cowan@ccil.org>
References: <6.0.0.20.2.20080518102122.04b49530@localhost> <20080518015749.GA7651@mercury.ccil.org>
In-Reply-To: <20080518015749.GA7651@mercury.ccil.org>
Cc: LTRU Working Group <ltru@ietf.org>
Subject: Re: [Ltru] my technical position on 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

John Cowan 2008-05-18 03.57:
> Martin Duerst scripsit:
>
> > In my understanding, one of the main points against extlangs was
> > that the "remove from the right" fallback hierarchy may not be
> > right. 
>
> The problem is, AFAIU, that too much information is thrown away:
> zh-yue-Hant does not fall back to zh-Hant, but first to zh-yue and
> then to zh.
>   

If we say the tag must EITHER be formed as 'zh-yue-Hant' OR as 
'yue-(region)-Hant', then we can have different fallback rules for 
either. For 'zh-yue-Hant', then "take away the second subtag" could be 
the rule.

I.e. the use of 'macroLang-encompLang' could defined as the preferred 
construction when a fallback to the macrolanguage is recommended (by the 
author and/or the spec) as a good choice and/or when the 
"macroLang-encompLang" construct is considered more important/relevant 
than "encompLang-Region".

Thus this way we would permit the tagger to state whether fallback to 
the macrolanguage tag SHOULD happen or not.

In case the tagger uses 'encompLang-(whaterver)' then the same rules as 
currently proposed counts: Then implementations MAY use the 
macrolanguage information for fallback decisions.

> > I'm opposed to allowing both extlang and independent tags
> > (i.e. both zh-yue and yue), but if that's what we as a WG
> > decide, I can live with it.
>
> I don't think anyone has ever suggested that: it's either/or.
>   

See Phillips, Addison 2008-05-13 01.11, under the subject "Re: [Ltru] 
extlang or not extlang", and Karen's reply. Above, and in my previous 
post, I have hopefully given the "better spelled out usage rules" that 
Karen asked for.
-- 
leif halvard silli
_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www.ietf.org/mailman/listinfo/ltru