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
Fallback Locale #19
Comments
I think that's why you can merge in objects to the dictionary. So en_AU can merge in en_US and you can override with the differences. |
Just looks like that is for adding another dictionary. |
you can merge two objects before you set the au one.
|
You could always use JS to write less code and merge dictionary objects. It would still result in duplicate code and a little bit of unnecessary handling of the dictionary objects. |
Hhahahahha we would never say Toss or shrimp! |
Not according to Crocodile Dundee. |
I completely agree that also looking for the message in the more generic locale should be the default behaviour. Duly noted for |
@kaisermann awesome! |
Fixed on |
My main use case for i18n, is supporting multiple versions of English. For example US and AU.
Many words have different spelling, but they are both English so mainly the same.
Instead of having duplicate dictionaries with some minor differences, It would be useful to have a fallback dictionary, so that only the differences would need to be in the 'other' english dictionaries.
Thoughts on this?
The text was updated successfully, but these errors were encountered: