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
I'm evaluating Worldwide, and I noticed something unexpected happening after running configure_i18n.
We have Haitian Creole ht as one of our supported locales. Our available_locales list before running configure_i18n looks something like:
config.i18n.available_locales=[:en,:es,:ht, ...]
After calling configure_i18n, I noticed that ht is no longer in the available_locales.
I believe this is because configure_i18n calls Worldwide::Cldr.fallbacks.descendants for each locale, but descendants(:ht) returns nothing []. And that seems to be because ht is not a known locale, according to Worldwide::Locales.known. I was a little surprised by this, but checking CLDR, it seems true that ht is not covered.
However, I would expect that Worldwide would ignore locales that it does not know about, rather than removing them from the list. We have been using ht via Google Translate, which does support ht as a possible locale, so I would still like to be able to use Worldwide for our other locales, even if all of its features wouldn't be available in some of our locales.
The text was updated successfully, but these errors were encountered:
I'm evaluating Worldwide, and I noticed something unexpected happening after running
configure_i18n
.We have Haitian Creole
ht
as one of our supported locales. Ouravailable_locales
list before runningconfigure_i18n
looks something like:After calling
configure_i18n
, I noticed thatht
is no longer in theavailable_locales
.I believe this is because
configure_i18n
callsWorldwide::Cldr.fallbacks.descendants
for each locale, butdescendants(:ht)
returns nothing[]
. And that seems to be becauseht
is not a known locale, according toWorldwide::Locales.known
. I was a little surprised by this, but checking CLDR, it seems true thatht
is not covered.However, I would expect that Worldwide would ignore locales that it does not know about, rather than removing them from the list. We have been using
ht
via Google Translate, which does supportht
as a possible locale, so I would still like to be able to use Worldwide for our other locales, even if all of its features wouldn't be available in some of our locales.The text was updated successfully, but these errors were encountered: