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

"Don Osborn" <dzo@bisharat.net> Thu, 29 November 2007 17:10 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 1Ixmtv-0007Qp-Dp; Thu, 29 Nov 2007 12:10:11 -0500
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1Ixmtu-0007PM-IF for ltru-confirm+ok@megatron.ietf.org; Thu, 29 Nov 2007 12:10:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ixmtt-0007P9-Pz for ltru@ietf.org; Thu, 29 Nov 2007 12:10:09 -0500
Received: from 113166.kabissa.org ([72.32.199.201] helo=kabissa.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ixmtr-0000pD-TY for ltru@ietf.org; Thu, 29 Nov 2007 12:10:09 -0500
Received: (qmail 19184 invoked from network); 29 Nov 2007 11:10:05 -0600
Received: from pool-72-75-10-67.washdc.east.verizon.net (HELO IBM92AA25595C4) (72.75.10.67) by 72.32.229.137 with SMTP; 29 Nov 2007 11:10:02 -0600
From: "Don Osborn" <dzo@bisharat.net>
To: "'Addison Phillips'" <addison@yahoo-inc.com>, "'John Cowan'" <cowan@ccil.org>
References: <20071129143920.GC32134@mercury.ccil.org> <474EE92A.30209@yahoo-inc.com>
In-Reply-To: <474EE92A.30209@yahoo-inc.com>
Subject: RE: [Ltru] Fallback vs. Macrolanguage? (was: John Cowan throws in...)
Date: Thu, 29 Nov 2007 12:09:58 -0500
Message-ID: <004801c832aa$ac53a090$04fae1b0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcgypTkoZB4mksGgRX+ZrwsBmanRAgABMWNw
Content-Language: en-us
X-Spam-Score: -0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: ltru@ietf.org
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

Some macrolanguage headings might be used also for locales and for describing orthographies (which in Africa often are defined by country and not by categories in ISO 639). How would the draft affect such cases? So in the case of Fula, one would probably be talking about ff-SN, ff-NE, etc., for at least some purposes, without resort to the alpha-3 codes introduced in part 3.

(Sorry I have not been tracking this as closely as I would like to have.)

Don

> -----Original Message-----
> From: Addison Phillips [mailto:addison@yahoo-inc.com]
> Sent: Thursday, November 29, 2007 11:31 AM
> To: John Cowan
> Cc: ltru@ietf.org
> Subject: [Ltru] Fallback vs. Macrolanguage? (was: John Cowan throws
> in...)
> 
> 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




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