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

Tracking changes in the translation text field #2062

Closed
bugzilla-to-github opened this issue Apr 19, 2017 · 3 comments
Closed

Tracking changes in the translation text field #2062

bugzilla-to-github opened this issue Apr 19, 2017 · 3 comments
Labels
enhancement P3 Default, possibly shipping in the following two quarters

Comments

@bugzilla-to-github
Copy link
Collaborator

This issue was created automatically by a script.

Bug 1357834

Bug Reporter: @gueroJeff
CC: @flodolo, @Pike, @Delphine, @mathjazz, @peiying2
See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1203265

Rather than contact fellow localizers about changes they need to make to a translation, reviewers often make changes themselves and don't notify the translator. To support that inclination + the need to provide translators with feedback, changes should be tracked and compiled into a report delivered to translators on a regular basis (e.g., all changes made by reviewers per day as a report accessed through notifications or viewed in email). If changes are tracked, they can then be attributed to an alternate user through an alternate action that is enabled when Pontoon detects that a translation has been changed (e.g., 'Suggest/Submit' button changes to 'Submit edits' or something like that when Pontoon detects that a text field with translated content is activated and changed (maybe through edit distance metric?)).

@bugzilla-to-github
Copy link
Collaborator Author

Comment Author: @Pike

Can we split out the UX flow of "review this string with edits" from the reporting UX?

I think that "review this string" is likely at least "take suggestion" and "set the reviewed state to true". We'll need to hash the details out, that conversation is scheduled for mid-May, right?

@bugzilla-to-github
Copy link
Collaborator Author

Comment Author: @mathjazz

Yes, let's use the May conversations as an opportunity to figure out the details of this.

@mathjazz
Copy link
Collaborator

mathjazz commented Nov 8, 2021

This issue has been split into the following two:

@mathjazz mathjazz closed this as completed Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement P3 Default, possibly shipping in the following two quarters
Projects
None yet
Development

No branches or pull requests

2 participants