Add comment field to translation (suggestion)

Hm, good idea. But this definitely needs to be hidden by default. Most of the time, you will not need this field, right?

I wonder whether relating nodes as discussion pages (ala wikis) to source text when desired is any good idea. Unfortunately the discussion page lacks display of the translation and suggestions (as in the wiki), and vice versa. However, it would let translators use a well known system (either wiki page or node with comments) in their language group (thinking of you using organic groups module). Thoughts?

I've been redirected from here: #1062210: "Comments for translations" feature

please elaborate there on UI ideas for both entering and displaying comments.

As I wrote there, there is already example of this feature well-implemented, Notabenoid. Unfortunately that site is completely in russian, so I'll try to describe how it's done there:

• Translation pages looks very similar to ones at l.d.o.
• But the last column indicates existence of comments. If some string has comments related to it then there's an icon in that column in front of this string. See screenshot 1
• If you click on that icon, a small javascript "window" (a layer, actually) appears containing a thread-like list of comments and simple form for adding a new one. See screenshot 2
  It has a source string instead of "Title" and comments doesn't have "Subject" since there's no need in it. It's important to mention, that "threads" are created one per source string, not one per translation/suggestion.
• If there is no comments yet for some string, there's nothing in that column. But if you hover your mouse above it, a small icon appears allowing to create new thread. It looks like "string has comments" icon, but has different color. See screenshot 3

This is just a description of something already existing in the web. And here are some my suggestions for making this feature even better:

• Comments in "thread" can have "common" fields just like issues at d.o. So if the value of this field is changed in the comment, it's changed for entire "thread". This way some fields can be added, like "Status" at d.o, which will allow moderators to easily track updates in translations.
• Also, each comment can be "bound" to specific suggestion(s)/translation(s). So that if the translation this comment is bound to is declined, than it's also greyed out ("dimmed") at "thread window".
• If this "binding" to translations is implemented, than a side panel can be added to the "window". This panel lists all translations added to the current string (even declined ones). It does double job:
  1. it actually lists all added translations (as we know, declined strings are still at the base, but are not displayed at translation page), which can be useful for later re-approving;
  2. if you select some translation, only comments related to it will be displayed/highlighted (if multiple translations are selected, than comments can be highlighted with different colors), which will allow to separate different discussions about one string while keeping everything in one place.

I'm not familiar with Drupal API and don't know if what I describe is possible at all. So this is nothing more than just an end-user's suggestion. But I hope it helps.

to haas:
Sorry, can't understand what you mean. Is your question addressed to me?
I don't know if Notabenoid is build on Drupal or not. Most likely, it's not.
I just posted a suggestion of what the UI for this feature can look like.

related issues #1375838: [META] feature requests born from cyrillic l.d.o