Jorge G. Mare wrote:
It may be wise to limit users to the specific languages that they can actually translate to, so that one does not accidentally translate the wrong target. Perhaps users can define what languages they can handle in the user profiles?
A good idea in general. OTOH, there may very well be situations while proof reading, that there's a small error you'd quickly want to correct in every translation. And "proof-reading" isn't suited for a role itself, because everybody does it to some extent when doing translating work.
Your argument with accidentally translating the wrong target is a good one, however. What can we do to avoid it? I suggest a nice big flag and language above the translation panel. Plus, maybe renaming the "OK" button to "Submit {LANGUAGE} translation".
On a separate suggestion, it looks like it may be helpful if the popup translation window had a Previous/Next navigation buttons, so that the translator can go from one block to the next w/o having to close and then re-opening the translation window for every block. Just a thought.
Maybe convenient, but it takes away the gravity of having to press a big button to "Submit {LANGUAGE} translation". Always think twice before hitting a button, never clickedy-click back and forth, all the while submitting any (accidental) changes. :)
Regards, Humdinger -- --=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=- Deutsche Haiku News @ http://www.haiku-gazette.de
