Re: [Ltru] Extended language tags (long reply)

I would say:

1. With Extlangs.

- change to filtering: none, but you probably want to use extended 
filtering instead of basic filtering (i.e. "zh-Hant-HK" matches 
"zh-yue-Hant-HK" and "zh-cmn-Hant-HK")

- change to lookup: treat extlang as atomic with the primary language 
subtag; potentially loop-back through the subtags. That is, given the 
range "zh-yue-Hant-HK", the fallback pattern is this:

  zh-yue-Hant-HK
  zh-yue-Hant
  zh-yue
  zh-Hant-HK
  zh-Hant
  zh
  (default)

Or this:

  zh-yue-Hant-HK
  zh-yue-Hant
  zh-yue
  (default)

2. Without extlangs.

- change to filtering: none

- change to lookup: none

BUT... you want to include the macro language in your ranges in some 
cases. Alternatively, we would have to define new filtering and lookup 
options that include mapping to macrolanguages. For example, with the 
range "yue-Hant-HK", you would want the fallback to be:

  yue-Hant-HK
  yue-Hant
  yue
  zh-Hant-HK
  zh-Hant
  zh
  (default)

This can be achieved either by having the language priority list 
"yue-Hant-HK;zh-Hant-HK" or by inferring it using registry data about 
macro languages.

A similar case can be made for filtering.

Addison

Mark Davis wrote:
> I think what might help is for us to draw up in detail what the matching 
> algorithms (changes to 4747) would be like in either of the two 
> proposals, and look at what happens with different cases 'ar', 'zh', 
> 'no', and others.
> 
> Mark
> 
> On 10/7/07, *Andrew Cunningham* <lang.support@gmail.com 
> <mailto:lang.support@gmail.com>> wrote:
> 
>     On 08/10/2007, Addison Phillips <addison@yahoo-inc.com
>     <mailto:addison@yahoo-inc.com>> wrote:
> 
>      >
>      > So, for me, the main issue is whether we are going to explicitly
>     break
>      > the connection between the language and its macrolanguage (at the
>     tag
>      > level). In some cases (Norwegian) we already know this can be
>      > problematic; in others, it may actually be desirable.
>      >
> 
>     It probably comes down to philosophical differences.
> 
>     So, cutting to the chase, which way forward?
> 
>     Andrew
> 
> 
>     _______________________________________________
>     Ltru mailing list
>     Ltru@ietf.org <mailto:Ltru@ietf.org>
>     https://www1.ietf.org/mailman/listinfo/ltru
>     <https://www1.ietf.org/mailman/listinfo/ltru>
> 
> 
> 
> 
> -- 
> Mark

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