[Ltru] Fallback vs. Macrolanguage? (was: John Cowan throws in...)

Addison Phillips <addison@yahoo-inc.com> Thu, 29 November 2007 16:30 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxmHy-0000RS-DR; Thu, 29 Nov 2007 11:30:58 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IxmHx-0000RJ-3Q for ltru-confirm+ok@megatron.ietf.org; Thu, 29 Nov 2007 11:30:57 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxmHw-0000R9-PH for ltru@ietf.org; Thu, 29 Nov 2007 11:30:56 -0500
Received: from rsmtp2.corp.yahoo.com ([207.126.228.150]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IxmHw-0001hn-Ae for ltru@ietf.org; Thu, 29 Nov 2007 11:30:56 -0500
Received: from [10.72.73.112] (snvvpn1-10-72-73-c112.corp.yahoo.com [10.72.73.112]) by rsmtp2.corp.yahoo.com (8.13.8/8.13.8/y.rout) with ESMTP id lATGUZpH007409; Thu, 29 Nov 2007 08:30:36 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=0+m9nBCX7S80468NEK6uN/gKpDKCsefJZ2DCDFsNANU12981+ccQG7ZlekRGh0eN
Message-ID: <474EE92A.30209@yahoo-inc.com>
Date: Thu, 29 Nov 2007 08:30:34 -0800
From: Addison Phillips <addison@yahoo-inc.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: John Cowan <cowan@ccil.org>
References: <20071129143920.GC32134@mercury.ccil.org>
In-Reply-To: <20071129143920.GC32134@mercury.ccil.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ltru@ietf.org
Subject: [Ltru] Fallback vs. Macrolanguage? (was: John Cowan throws in...)
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Errors-To: ltru-bounces@ietf.org

John Cowan wrote:
> 
> IMO we should strongly consider adding a new informative (and mutable)
> "Fallback" header in the registry which will inform people about
> problematic cases like "cmn" and "arb" (Standard Arabic), instructing
> them which language subtag to fall back to in cases of match failure.
> These will have to be cherry-picked, like Suppress-Script, but Peter
> Constable has estimated that there are no more than 15 such cases
> actually in wide use.  For some macrolanguages, there is no dominant
> variety, and no special consideration is as yet required; if new dominant
> varieties come to exist in future, new Fallback headers can be added.
> RFC 4647bis can then be revised to explain how this header MAY be used
> to enhance matching.
> 

Wouldn't it be easier, more consistent, cleaner, and cherry-free to keep 
what we've already proposed in draft-09, that is, to include the 
Macrolanguage field in the registry as informative information (and then 
note in either 4646bis or 4647bis about possible courses of action in 
cases of match failure)?

Addison

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.
Chair -- W3C Internationalization Core WG

Internationalization is an architecture.
It is not a feature.


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