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

Add comment fields for translators #209

pixolin opened this issue Jan 14, 2016 · 2 comments

Add comment fields for translators #209

pixolin opened this issue Jan 14, 2016 · 2 comments


Copy link

@pixolin pixolin commented Jan 14, 2016

Add comment fields to text strings where translator can note, why a translation differs from original text.

Sometimes text strings are difficult to translate, e.g. if it comes to trademarks being used in composites. (Example: WordPress plugin WP Smush uses the term "Smush", referring to the former web service Smush it. The term is used in composites such as "Bulk-Smush", "Super-Smush", "smush your images", "can be smushed". While it is necessary to keep the reference to the web service, some of these terms don't translate. A solution could be to replace the text string where appropriate and keep it where necessary.)

For validation and translation on future versions, such divergence should be documented:

  • Why does the translation differ?
  • Has the plugin author agreed that the translation deviates from the original?

To my understanding it would be helpful to have as well a general comment field for the entire plugin (e.g. "term 'Smush' can be replaced with 'compress' where appropriate") as also separate comments fields for each single translation term (e.g. "term 'Bulk-Smush' translated in this case as 'Mehrfach-SMUSHen' to keep meaning of trademark").

@ocean90 ocean90 changed the title [Feature request] Add comment fields for translators Add comment fields for translators Jan 14, 2016
@javorszky javorszky self-assigned this Feb 4, 2016
@ocean90 ocean90 added this to the Future milestone Feb 11, 2016
Copy link

@ocean90 ocean90 commented Mar 11, 2016

Related chat on Slack:

javorszky [15:39] 
so that... can I pick your brains on it now?

ocean90 [15:39] 

javorszky [15:39] 
2 questions: 1) I think it could live in the meta table, but I can also see it needing a new Thing

javorszky [15:39] 
2) should it be threaded?

ocean90 [15:40] 
(Everything which is at future can be moved to 1.1 if it's ready)

javorszky [15:41] 
3) UI-wise, I was thinking it can live here: (edited)

javorszky [15:41] 

gregross [15:42] 
1) those are not mutually exclusive, you could use the meta table and still have a new thing.

ocean90 [15:42] 
1) I'd do a new "Thing"
2) For v1 I'm fine with non-threaded
3) UI.. Yes and no. We definitely need a new UI :simple_smile:

javorszky [15:43] 
new thing it is :simple_smile: (edited)

gregross [15:43] 
2) non-threaded seems resonable.

gregross [15:43] 
3) Looks good given the current layout

javorszky [15:44] 
okies :simple_smile: regarding 2) non-threaded, multiple replies? would translator / validator need a back-and-forth, or would it just be a note the translator leaves on a translation and that's that?

ocean90 [15:44] 
Re UI: I'm totally in love with the interface of Pontoon. Example: The tabs below the textbox
Live web localization tool

gregross [15:45] 
I'd keep it a simple note, getting much more complex then that seems out of place of the requirement.

ocean90 [15:45] 
So it shouldn't be just comments, I'd like to call it History or similar. Does that make sense?

ocean90 [15:45] 
A place where you can add "everything"

javorszky [15:46] 
a blob thing

ocean90 [15:46] 
Codename "Blob", I like that. :simple_smile:

javorszky [15:46] 

gregross [15:46] 
History might not be the right term, that might infer the ability to see previous versions etc.

javorszky [15:46] 

ocean90 [15:47] 
Was just going to say the same

gregross [15:47] 

javorszky [15:47] 
awsm, thank you :simple_smile:
Copy link

@ocean90 ocean90 commented Apr 27, 2016

Related: #324

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

Successfully merging a pull request may close this issue.

None yet
4 participants