Re: [Ltru] Consensus call: extlang

["Phillips, Addison" <[e-mail]>]

Peter wrote:

> Rather than filtering, it's *lookup* for which a request for zh-cmn
> would match existing zh content. But I think it's fair to say that
> lookup is most typically used for UI resource matching or similar
> scenarios in which the options for available content are likely to be
> fairly limited and controlled, with users being presented with the set
> of specific options available. In that kind of controlled environment,
> fallback from (zh-)cmn to zh is less likely to be needed.
>

In fact, in my experiments at least, lookup requires some modification in order to produce the best results when working with extlang. For my applications, at least, it seems that treating the primary-extlang pair as "atomic" for at least the first pass makes the most sense. That is, the fallback pattern works better when it goes like this:

zh-cmn-Hans-HK
zh-cmn-Hans
zh-cmn
zh-Hans-HK
zh-Hans
zh
(default)

... then when it goes according to the current rules:

zh-cmn-Hans-HK
zh-cmn-Hans
zh-cmn
zh
(default)

This is especially true when one has mixed content regimes (mixed scripts, regions, dialects, languages, etc.) in which 'zh' can represent only one variety (and frequently the wrong value).

Extlangistas will note that you have to make the same modification if you omit extlang to obtain the *exact* same results:

cmn-Hans-HK
cmn-Hans
cmn
zh-Hans-HK (presumably from Macrolanguage field??)
zh-Hans
zh
(default)

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.


_______________________________________________
Ltru mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ltru