2008/6/18 Danilo Šegan <[EMAIL PROTECTED]>: > Hi Kenneth, > > On Saturday at 16:04, Kenneth Nielsen wrote: > > >> > Furthermore it is also very time consuming to review and approve > >> > suggestions. I don't see a real speedup compared to writing them on my > >> > own. Especially since there is no way to provide feedback to the > >> > translators in Rosetta. If there is no contact outside of Rosetta I > have > >> > to correct the same errors again and again. > >> > >> I believe the lack of documentation is to blame here. Reviewing > >> suggestions would not speed you up short-term, but once you have > >> reviewed enough of someone's translations and start considering him a > >> good translator, you'd make him a reviewer as well, and then it would > >> be two of you translating, and two of you reviewing. > > > > > > I disagree. I believe it is the process currently involved that is the > > principal source of the time used reviewing, reviewing _can_ be done in a > > manner that takes less time per string than you would use translating it > > your self, so getting more people to review would simply mean more people > > wasting time. > > I think you are missing one important point. A "reviewer" can also > submit translations without waiting for them to be reviewed.
No I.e. by reviewing someone's translations, you are aiming for a new > 'trusted' translator as well. Not if we can't provide feedback and make them make the corrections themselves. > So, now it'll be two guys who can > translate directly, and if that doesn't speed you up long-term, I > don't know what will. I think you are missing an important point here. There are _many_ upstream translators/translation teams that consider reviewing translations, even those done by seasoned translators, as a integral part of the translation process, that is absolutely necessary to reach a high quality output. E.g. _all_ translations submitted to the GNOME SVN for the Danish language has been reviewed, indenpendently of the translator. We don't want to comprimise our standards for quality in Ubuntu, hence what we need is a way to quickly review, _not_ "correct", a translation, because if we correct them ourselves then translator will not learn anything and the reviewers will have to keep correcting the same things. What we do when we review is to read through the translations, commenting only on the one that needs commenting, and only in as much detail as is required for the individual string. This can sometimes only be a single word or sentence "Typo", "Reformulate to avoid english sentence structure", "misgid has plural" or sometimes it can be a long explanation of some preferred terminology or policy. This all means that I can review and provide feedback for translations, as fast as I can read, write and delete text in a text editor and send an email, and _that_ is what I am looking for. My suggested "point-diff" approach will allow for that, in parallel with anything else you guys might think up as the main approach in the web-interface. Regards Kenneth Nielsen
-- ubuntu-translators mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
