Re: [Ltru] Extended language tags

I think this is a mis-reading of Mark's example. His presupposition goes 
something like: "suppose Breton had a macrolanguage of Celtic..."

It would be a more effective example, I think, if we used an actual 
enclosed language. I've been writing a long email in response to Shawn's 
(and various responses thereto) that I haven't quite been able to make 
myself send. Part of it includes this rephrasing of the example:

--
Let me rephrase Mark's Breton case: when you want Chippewa, any old 
Ojibwa (its macrolanguage) -- which might be a language such as Ottawa 
-- will not do. It could be unintelligible (I don't actually know). If 
it is unintelligible, you're probably better off *not* mapping Chippewa 
to Ojibwa. You're better off serving some useful default (for Chippewa, 
this is probably English, but the default is up to the application, not 
something RFC 4647 or the registry do). Or the app could fail to find 
content.
--

When considered like this, the Breton vs. French example is more useful. 
Otherwise it is pointless.

Addison

Peter Constable wrote:
> But I think Shawn's point is that the Breton/French example doesn't really tell us much of anything of interest wrt extlangs -- neither language has any macrolanguage / extlang issues involved. For Lookup, the best fallback for Dyirbal is probably English; the best fallback for Ainu is Japanese. So?
> 
> 
> Peter
> 
> -----Original Message-----
> From: John Cowan [mailto:cowan@ccil.org]
> Sent: Thursday, October 04, 2007 8:22 PM
> To: Shawn Steele
> Cc: ltru@ietf.org
> Subject: Re: [Ltru] Extended language tags
> 
> Shawn Steele scripsit:
> 
>> * I don't think the Breton example applies.  http-accept-lang allows for
>> "br-FR;fr-FR" type fallback, so that is a solution.  If an application
>> independently wanted to make this assumption that's fine by me, but
>> this seems orthogonal to the problem we're trying to solve here.
> 
> That works for filtering (which is what Accept-Lang does), but not so
> well in practice for lookup.  Normally people don't specify multiple match patterns
> in lookup situations, they just say "I speak Breton, what's the best
> match you have?"
> 
> --
> You're a brave man! Go and break through the            John Cowan
> lines, and remember while you're out there              cowan@ccil.org
> risking life and limb through shot and shell,           http://ccil.org/~cowan
> we'll be in here thinking what a sucker you are!
>         --Rufus T. Firefly
> 
> 
> _______________________________________________
> 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

-- 
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