Closed buhtz closed 3 months ago
Learned from other of your issues this might be because babel does stick to "CLDR" (not knowing what this is). If this is the case then you minimally should improve your error message to make it clear to the users that it is not "the fault" of babel but CLDR. This would prevent more distracting tickets in your project.
See #689, #454, #344.
As it is, Locale.parse()
only supports locales that have data in the Unicode Common Locale Data Repository (the CLDR).
It seems that "ie" is supported by CLDR (latest stable release 45). But I might be wrong or in the wrong version of CLDR?
Ah, good catch. #1077 – the PR to support CLDR 45 – has been merged but not released yet. I'm planning on getting around to releasing Babel 2.16 soon.
I can confirm ie
is supported in my local working copy, so it'll be supported in 2.16:
>>> import babel
>>> babel.Locale.parse('ie').territories["US"]
'Unit States'
Thank you very much from the bit-team/backintime project.
My apologize. It seems that "ie" is supported since your 2.15 release.
No worries, thank you for the documentation PR! Closing this for the time being.
It seems that babel do not support Occidental/Interlingue.
I am just an upstream maintainer need to deal with over 40 languages and having some helper scripts. One of that scripts now fails because of that new added language. Currently I can add some exceptional handling for that. But I would prefer to have it supported by babel.
Just for fun I also tried
"tlh"
language code for Klingon. It is also not supported.Both of them are "official" standardized languages, with scientific interest and rare use in real live. I don't want to argue about the relevance of such languages. I don't care. But my users are. IMHO if there is an ISO language code I would say babel and similar packages should support it.