tg-Cyrl-TJ and tk-TM

[Rafael Xavier]

Thank you Philippe for all your detailed explanation about default content.
But, my question was a little more basic. Sorry not being explicit about it
and by causing any confusion. But, I cannot find either tg or tk as a main
bundle.

Can someone point me to its LDML file?

Thanks

On Tuesday, February 3, 2015, Mark Davis ☕️ <mark at macchiato.com> wrote:

> ​Nice explanation, Philippe.​
>
> One quick note: CLDR does define 'en' to have the content for
> 'en-Latn-US'. However, it also supplies 'en-001' — English (World) — which
> can be used for an international form of English.
>
> Mark <https://google.com/+MarkDavis>
>
> *— Il meglio è l’inimico del bene —*
>
> On Tue, Feb 3, 2015 at 4:35 AM, Philippe Verdy <verdy_p at wanadoo.fr
> <javascript:_e(%7B%7D,'cvml','verdy_p at wanadoo.fr');>> wrote:
>
>> Note that this is the same case for the likely value of "en", which is
>> "en-Latn-US" (but you could argue that "en" represents just the
>> international form of English, without the US specific jargon) : you don't
>> need data for "en-Latn" and "en-Latn-US" or "en-US".
>>
>> Similar case for "zh", but with more branches :
>>
>> (1) Its likely value is "zh-Hani-CN", but more precisely "cmn-Hans-CN"
>> (Mandarin being the predomnant language in the Chinese macrolanguage, and
>> predominently written with the the simplified sinographic script variant).
>> So with "zh" data you don't need additional data for "zh-Hani",
>> "zh-Hani-CN", "zh-Hans", "zh-Hans-CN", "zh-CN", "cmn", "cmn-Hani",
>> "cmn-Hani-CN", "cmn-Hans", "cmn-Hans-CN" or "cmn-CN".
>>
>> (2) But you can have specific data for "zh-Hant", futher specialized with
>> additional data:
>>
>> * for either "zh-Hani-TW" or "zh-Hant-TW", or just "zh-TW" (given that
>> the likely script variant in Taiwan is traditional)
>> * for either "zh-Hani-MO" or "zh-Hant-MO", or just "zh-MO" (given that
>> the likely script variant in Taiwan is traditional)
>> * for either "zh-Hani-SG" or "zh-Hans-SG", or just "zh-SG" (given that
>> the likely script variant in Taiwan is simplified)
>> ​
>> A lot of combinations of BCP47 subtags can be used in localization data,
>> but CLDR data concentrates on the default for the root of all branches, and
>> provides specialized data only for specific branches needing them (it
>> assumes that you'll use them with the standard fallback resolution
>> mechanism of BCP47. So you should understand how the fallback mechanism
>> works: as soon as "likely" subtags are registered in the IANA database for
>> BCP47 it removes the need to make many specializations for various
>> combinations (and this is the best role of these "likely" declarations).
>>
>>
>> _______________________________________________
>> CLDR-Users mailing list
>> CLDR-Users at unicode.org
>> <javascript:_e(%7B%7D,'cvml','CLDR-Users at unicode.org');>
>> http://unicode.org/mailman/listinfo/cldr-users
>>
>>
>

-- 
+55 (16) 98138-1582, +1 (415) 568-5854, skype: rxaviers
http://rafael.xavier.blog.br
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20150203/c809cde6/attachment.html>