-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Question: Default fallback for country variant #26
Comments
There are no such auto-fallbacks, because those are not acceptable in 100% of use cases. Use |
Ok, thanks. Agree in general but FYI for pt-BR default is pt as defined there http://cldr.unicode.org/translation/default-content. Anyway i think i will better to add pt-PT and pt-BR instead of reinventing wheels. |
Usually people use base names only (ru) or full names only (ru-RU) for all project. It's unordinary to have both translations and such fallback is not required at all. Probably, you mean locale "autodetection", when browser sends "ru; ru-RU;". But this happens before babelfish call and usually normalize locale names length, according to your project needs. For example: https://github.com/nodeca/nodeca.core/blob/master/lib/autoload/hooks/server_chain/locale_set.js |
Yes, that is similar with what i want, will add preprocessing to set fallbacks. |
Hello.
I would like to ask question about using country variants:
Shouldn't last line fallback to 'pt' ? Or i should manually add every possible fallback with .setFallback?
Thanks.
The text was updated successfully, but these errors were encountered: