Validation of translations

Bug #111 reported by Karianne Fog Heen on 2005-02-01
Affects Status Importance Assigned to Milestone
Launchpad itself
Carlos Perelló Marín

Bug Description

An idea for some kind of validation for packages. I'm not sure how it would work in practice, though. If each page of a translation has to be approved by a second translator of that language, we could assure that all translations have been double checked. It will increase the amount of work, but it will also greatly decrease the amoung of misspellings and bad translations.

Mårten Woxberg (maxmc) wrote :

I suggest the translation to be subbmitted to the correct language groups mailinglist for it to be verified and commited by the one who usually do it.

Carlos Perelló Marín (carlos) wrote :

This would increase the complexity to translate, the main problem with people translating is the lack of translators so if we add that double check a translation would take too much time since it's done until it's applied.

I think the review process described at is a better solution.

We are going to implement it in the next three months.

Carlos Perelló Marín (carlos) wrote :

About the idea of sending the suggestions to the mailing list...

I don't think it would be too much user friendly... that implies that the translator needs to manually copy the string from the email and copy it into Rosetta... I think it's better if you just click to select the translation you want to use.

Changed in rosetta:
assignee: nobody → carlos
status: New → Rejected
Christian Reis (kiko) wrote :

Just for the record, the idea of sending suggestions sounds to me like "Rosetta Notifications", which are also something that is planned but not currently implemented.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers