Replies: 2 comments 4 replies
-
|
Did you do some changes to the project settings since then? The suggestion was from the translation memory, and there is no match now. One part of the problem is that the partially defined plural (missing first string for zero) was imported as non-translated from the repository. This then kicked in automatic translation, which inserted partial matches as needing editing (which itself is probably correct). translate/translate#5699 fixes the wrong state calculation. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Describe the issue
I constantly get bad translations for plurals (Localizable.stringsdict).
Even when they are placed in a separate Component, and this component is locked for translations.
I got this change immediately every time I make "Reset all changes".
The component: https://hosted.weblate.org/projects/organicmaps/ios-plurals/
Again the latest change: https://github.com/organicmaps/organicmaps/pull/11336/files
I already tried
Steps to reproduce the behavior
Make Localizable.stringsdict with
NSStringLocalizedFormatKey. For example:is always replaced with
Expected behavior
Screenshots
Exception traceback
How do you run Weblate?
No response
Weblate versions
No response
Weblate deploy checks
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions