-
-
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
Notifications issue #9486
Comments
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! |
"Translated string" is indeed subset of "Changed string". It covers only changes done by translator in Weblate. It excludes changes done in the repository, automatic translation, or state changes, so it is less noisy. Similarly there is "Approved string" notifications, which is subset of "Changed string", but only triggered on strings approval with the review workflow. |
My point is that there is no notification setting for (2). |
“Translated string” is actually triggered on both “Translation changed” and “New translation”. There is indeed no separate notification for accepting suggestions. |
(2) isn't about "Suggestion accepted". What I miss is a notification for a previously untranslated string that got translated for the first time, which can happen either by a manual translation or an accepted suggestion. This is what I have labeled (2). I thought that "Translated string" meant exactly this (but I was wrong). You can close this issue if you feel that workflow steps (1), (2) and (3) do not require separate notifications. |
I think it makes sense to include suggestion accepted action in the translated string notification. I'd rather not introduce another notification choice. |
If implemented, I think a more specific name for the “Translated string” notification is needed. |
@nijel Thank you, I appreciate your efforts and can understand not introducing a new notification choice. However, I think that the current notification labels might be confusing to users. "Translated string" should rather read something like "New or changed translation of string" or so and "Changed string" should rather read something like "Any change to string" or so to express that it is some kind of superset. Otherwise it is hard to understand what the difference between "Translated" and "Changed" is supposed to be. Just my opinion, though. |
Naming is indeed not good. The intention here was to have one notification for user triggered changes and the other for all changes (including automatic translation, updates from the repository, bulk edits, ...). I've renamed first to "Edited string", hopefully it's a better name. |
Thank you for your report; the issue you have reported has just been fixed.
|
- there is no UI reason to stick with really short names here, so make them more descriptive - use pgettext to make sure these are translated differently from change events See also WeblateOrg#9486
- there is no UI reason to stick with really short names here, so make them more descriptive - use pgettext to make sure these are translated differently from change events See also WeblateOrg#9486
- there is no UI reason to stick with really short names here, so make them more descriptive - use pgettext to make sure these are translated differently from change events See also WeblateOrg#9486
- there is no UI reason to stick with really short names here, so make them more descriptive - use pgettext to make sure these are translated differently from change events See also WeblateOrg#9486 Co-authored-by: Benjamin Alan Jamie <benjamin@weblate.org>
- there is no UI reason to stick with really short names here, so make them more descriptive - use pgettext to make sure these are translated differently from change events See also WeblateOrg#9486 Co-authored-by: Benjamin Alan Jamie <benjamin@weblate.org>
- there is no UI reason to stick with really short names here, so make them more descriptive - use pgettext to make sure these are translated differently from change events See also #9486 Co-authored-by: Benjamin Alan Jamie <benjamin@weblate.org>
Describe the issue
@nijel This is a addition to #9464.
I still don't understand why the "Translated string" notification is nothing but a subset of "Changed string".
The usual translation workflow is: (1) "New strings to translate" → (2) "New translation" or "Suggestion accepted" → (possibly later) (3) "Translation changed".
There are options to be notified separately for (1) and (3), but not for (2).
I already tried
Steps to reproduce the behavior
Select "Translated string" and "Changed string" in the user settings.
Expected behavior
I would expect there to be a notification option that informs on first-time, new translations only.
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: