-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
Bug: Pluralization and Fallbacks modules do not play well together #124
Comments
/cc @josevalim |
Please, fix this bug. |
We still have this issue in 0.6.5. |
check this, please! |
I would accept a PR to fix this issue. |
Did this ever get fixed..? |
@Matt-Yorkley The card's still open, so I am guessing not. |
We have many open cards for the same issue. I've already proposed a fix which has been closed without any explanation. It's a pity. |
Related (RU, may want to use Google Translate): yaroslav/russian#29 (comment)
Summary:
pluralize method of Backend::Pluralization relies on resolving pluralize rule this way:
Unfortunately, if you have a locale with non-english transliteration rule as I18n default (say, :ru that may return any of [:one, :few, :many, :other]), then enable I18n fallback and use :en locale as current, Pluralization module will look up for pluralize lambda in current locale, fallback to :ru, use russian pluralization rule and fail miserably with simple :en translations (such as the ones shipped with Rails).
Now, regarding the fix.. It seems that we can't really tell if we are receiving a translation that was fallback'd, so, basically two options that come to mind (probably there is a perfect solution, but I'm not there yet):
Can implement both fixes but we probably gotta talk about this first. /cc @svenfuchs, @clemens?
The text was updated successfully, but these errors were encountered: