Skip to content
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

Merged
merged 4 commits into from
Sep 19, 2017
Merged

Improve handling of complex plurals #701

merged 4 commits into from
Sep 19, 2017

Conversation

Changaco
Copy link
Member

@Changaco
Copy link
Member Author

I've opened an issue upstream: python-babel/babel#530.

@Changaco
Copy link
Member Author

Sneaked in a commit to take care of #696.

@Changaco Changaco merged commit 3289eb0 into master Sep 19, 2017
@Changaco Changaco deleted the plurals-2 branch September 19, 2017 10:05
@trebmuh
Copy link
Member

trebmuh commented Sep 19, 2017

👍

@Changaco
Copy link
Member Author

@pskosinski finds this confusing.

@AllDragonsAreDead
Copy link
Contributor

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 <unused singular (hash=… as source strings I thought something in the Liberapay's or Weblate's source code got broken. It was not intuitive to me. Now it seems like a good solution though, I guess.

@AllDragonsAreDead
Copy link
Contributor

Seems like the strings whose msgid's got converted, e.g.:

-msgid "Your donations will be funded for {n} weeks ({0})"
+msgid "<unused singular (hash=578803aaecf90d69fa606ab0f5a693e9)>"

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.

@Changaco
Copy link
Member Author

/o\

Working on a fix…

@Changaco Changaco mentioned this pull request Sep 28, 2017
@Skybladev2
Copy link
Contributor

@Changaco Can you please clarify when this fix will be reflected to Weblate?
I see this at the moment:

default

@Changaco
Copy link
Member Author

Changaco commented Oct 1, 2017

@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.

@Skybladev2
Copy link
Contributor

@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?

@Changaco
Copy link
Member Author

Changaco commented Oct 1, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants