-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Add notification or section for updated text #8442
Comments
The strings will be marked as “Needs editing” by Weblate, the change will be visible both in the history and as source string change. You can filter for such changes in the history. You can see the example here: https://hosted.weblate.org/translate/f-droid/f-droid-metadata/eo/?checksum=502bfece59e1216b#history (this is first thing I've found, and make be hard to read as there are whitespace changes only). |
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
@nijel Appreciate your help and clarification. Indeed, starting from the newer version (I don't know from which), the status is "Needs editing" for strings with updated text. |
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
|
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the problem
There might be situations in which the initial string will be updated. Then if the primary state was translated, the translation would be outdated after modification. Due to that, the translations might need to be clarified.
Describe the solution you'd like
As I see it can be done in one of two options:
Describe alternatives you've considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: