Skip to content

List seed locales too #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yvanzo opened this issue Aug 11, 2022 · 3 comments
Open

List seed locales too #31

yvanzo opened this issue Aug 11, 2022 · 3 comments
Labels

Comments

@yvanzo
Copy link

yvanzo commented Aug 11, 2022

For example “Church Slavic (cu), Volapük (vo), Prussian (prg)” “have been moved in the folder structures” in CLDR 38. It led to the removal of these locales in DateTime::Locale 1.29/1.30.

From the ticket CLDR-14080, it seems that these locales have been moved from “common” to “seed” locales depending on the coverage level.

The opposite move has been made for Sanskrit (sa), making these available in DateTime::Locale 1.29/1.30.

It would be useful to list the seed locales in DateTime::Locale, even though their level of coverage isn’t as high, rather than having locales to disappear when the coverage requirements change. Seed locales could be listed separately from common locales if the coverage level is important to DateTime::Locale.

@autarch
Copy link
Member

autarch commented Aug 14, 2022

Thanks for the report. I agree that it'd make sense to include these "seed" locales. Any interest in working on a PR to fix this?

@yvanzo
Copy link
Author

yvanzo commented Aug 15, 2022

Not at the moment but I still had a quick look at the code:

  • There are currently 826 “common” locales for 176 “seed” locales.
  • DateTime-Locale uses cldr-json which doesn’t include “seed” locales from cldr.
    So it is not a small change I hoped it would be.

@autarch
Copy link
Member

autarch commented Aug 20, 2022

Yeah, I took a look and AFAICT there's no mention of the seed locales in cldr-json. Without that I don't think there's any good way to include them. Dealing with the LDML files is an absolute nightmare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants