This feature would be *extremely* useful. I'm sure most translation teams have specific procedures for proofreading translations. The way we (Danish translators) do it, someone writes a translation, then submits it for proofreading. The proofreader writes comments, and the translator then implements the proofreader's suggestions. This cannot be done at all using the web interface, so our procedure right now is to work by downloading and uploading entire po-files - which is the way every other project (GNOME, TranslationProject, KDE...) is handled.
Writing an email or IM to the translator could technically work, but then it's much more effective to write comments directly to the translations and just send an email saying 'Hey, could you make corrections according to these comments?'
Even if the proofreader changes the suggested strings as necessary and then incorporates them (which might be a more realistic procedure in Launchpad's case given how easy it is to make "hit-and-run" translations), many translators would still want to know why their translations were "rejected" (which is as far as I know the only thing they'll see if we insert a single comma before accepting the string).
This feature would be *extremely* useful. I'm sure most translation teams have specific procedures for proofreading translations. The way we (Danish translators) do it, someone writes a translation, then submits it for proofreading. The proofreader writes comments, and the translator then implements the proofreader's suggestions. This cannot be done at all using the web interface, so our procedure right now is to work by downloading and uploading entire po-files - which is the way every other project (GNOME, TranslationProject, KDE...) is handled.
Writing an email or IM to the translator could technically work, but then it's much more effective to write comments directly to the translations and just send an email saying 'Hey, could you make corrections according to these comments?'
Even if the proofreader changes the suggested strings as necessary and then incorporates them (which might be a more realistic procedure in Launchpad's case given how easy it is to make "hit-and-run" translations), many translators would still want to know why their translations were "rejected" (which is as far as I know the only thing they'll see if we insert a single comma before accepting the string).