You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 toDateTime::Locale
.The text was updated successfully, but these errors were encountered: