-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Improve handling of complex plurals #701
Conversation
I've opened an issue upstream: python-babel/babel#530. |
Sneaked in a commit to take care of #696. |
👍 |
@pskosinski finds this confusing. |
Now, after reading discussion starting here liberapay/salon#125 (comment) I do understand what's going on. Although, when I visited Weblate to check if anything needs translating, noticed all the failed tests and |
Seems like the strings whose msgid's got converted, e.g.:
stay untranslated on the website, even that they are translated on the Weblate. It's easiest to notice if you switch language to a fully translated language (e.g. French, German) and scroll down to "Recent activity" section. All the strings there are in English, even that they were getting replaced with their translations some time ago. |
/o\ Working on a fix… |
@Changaco Can you please clarify when this fix will be reflected to Weblate? |
@Skybladev2 I'm not sure what you were asking, but your comment made me realize that the source string in your screenshot was wrong because we do use the singular. I've fixed it in b29b73b. |
@Changaco I see several errors in source strings, you can see it by following this link: https://hosted.weblate.org/translate/liberapay/core/ru/?type=check%3Apython_brace_format&offset=0 Is it Weblate issue or Liberapay issue? |
The source strings are exactly what they're supposed to be. Weblate's warnings and errors are about the differences between the singular source string and its translation, they can be dismissed. |
See liberapay/salon#125 (comment).