On Tue Jan 22 07:20:22 2013, PERLOVER wrote:
Show quoted text> I don't understand your module
>
> I think you mix territories and languages.
The territory and language codes comes directly from the CLDR.
Show quoted text> For example you have the Locales::DB::Territory::cs module. The cs is
> language code of Czech in territory CZ. The CS territory misses. Other
Correct, in CLDR the language tag 'cs' is 'Czech' and the territory tag 'cs' is 'Serbia and
Montenegro'.
Show quoted text> example: Ukraine country. There the uk language code and UA country
> code. You have the Locales::DB::Territory::uk module but it means as UA
> territory.
Correct, in CLDR the language tag 'uk' is 'Ukrainian' and there is no territory tag 'uk'.
Show quoted text> I think there is territory codes which match with other
> language codes.
Sure they can be the same letters but they are two completely different categories and so
completely different things.
One combines them into a single “locale” tag to get more specific:
en (English)
en_gb (English in Great Britain)
es (Spanish)
es_mx (Spanish in Mexico)
es_es (Spanish in Spain) - notice that the language and territory parts that make up this locale
tag are the same letters as each other
Show quoted text> For example i cannot use your module because it incorrect works.
What are you trying to do? Can you send a short command that demonstrates that along with
what it is doing and what you expected it to do?
Show quoted text> Why did you do Locales::DB::Territory:* modules with language codes instead territory codes?
As I outline above the data comes from CLDR and the fact that a territory and a language tag
share the same letters is not a problem since they are not the same thing.
It sounds like you're trying to create an object from a territory tag instead of a proper locale tag
and getting unexpected results since the territory tag is also a (likely unrelated) language tag.
But I can help more if you send the example that demonstrates the trouble you're having.
thanks!
