Written by OgMacielq the 22 Sep 08 at 23:44.
Category: Usability.
Related project:
Nothing/Others.
Status: New
Rationale
Every day (literally) hundreds of translation suggestions and/or modifications are generated in Rosetta. Due to some current limitations in Rosetta, it is fairly hard for translation teams members to keep up with the flood of information or even know about contributions awaiting for review/approval. My intent is to describe a mechanism by which translation teams can better administrate the contributions sent by Rosetta users, provide useful feedback and take a first step toward a better relationship with upstream projects.
Been discussing this with Og, and he has really good grasp of what translators need since he's been involved in translations for over a century or so. What, you dare to say I'm wrong?!
Sometimes we need to do an extra work in roseta to merge some upstream translations, maybe a better method of administration would make translation's lives more easy.
"Feedback" part in the blueprint is really important. Translators should be able to explain some of their decisions, namely uncommon translations and abbreviations.
While such global approving mechanism would improve quality, it would also slow down translation progress. I think the proposed process of committing changes should be simplified a bit.
I really appreciate your attempt to improve the translation process. Although your idea looks quite smart at the first sight your idea is much too complicated.
It's too complicated to get implemented in Rosetta and I also think it's too complicated to handle, because if you lock something you must always consider the scenario that a translator doesn't unlock the translation correctly. This would require additional admin use cases. All this together would be more complex than everything that's implemented today in Rosetta.
IMHO Rosetta suffers from the lack of much simpler features. Thinks I would like to see in Rosetta are:
(1) an automatic import of upstream translations from GNOME, KDE etc. on a regular basis (daily or weekly)
(2) a web service API to download and upload po files so translation teams can implement own synchronization scripts
(3) an option for translation teams to lock translations from being edited in Rosetta
(4) a subscribing mechanism for translations that sends me a mail each time a new contributor joins in to make suggestions. So I can contact her or him to inform her or him about our team structure, processes an priorities.
Hi joskulj, thanks for your comment. The issue about locks and what not can be simplified when you add more use cases (as you had mentioned). The scenario I envision for this would be that the official members of a translation team are the ones who can unlock a translation that is taking too long (maybe the user is away?). In order to provide good quality translations, I am willing to give up "speed" for quality translations.This type of process, locking and unlocking plus marking things for review has worked extremely well for the Brazilian team, albeit we're using a different tool called Vertimus.
Let me just clarify that I am totally with you: translations need reviews - there is no question about this. Your workflow addresses this very well and IMHO your workflow describes quite exactly the process we practise in our team without tool support but by having todo lists in the wiki and communicating via mailing list. Therefore I would love to see this workflow supported by Rosetta; I am just a little pessimistic if this will be implemented in Rosetta since much simpler requirements aren't implemented yet.
Furthermmore I think that we may need more than a single workflow. The workflow you set up is a good solution for Ubuntu-specific packages and documentation but besides this we need a way to keep the translations in sync with the upstream translations which should be provided automatically.
You have to implement a mechanism that recognizes when a suggested translation has been suggested more than once[URL="http://www.onthegophotobooth.com"].[/URL]