Translation status: how does project leader change status of submitted translations?

Asked by Sveinn í Felli

I'm involved in translating a bunch of projects on Launchpad; in many of them (recent ones on LP) the project managers have not found out how to make submitted translations 'Unchanged' or 'green' (which is a color very dear to us translators).
Which steps are necessary to change the status from 'New' (violet) to 'Unchanged' (green)?

Do they have to export the translations (e.g. or is there some other approval procedure?


Sveinn í Felli

Question information

English Edit question
Launchpad itself Edit question
Launchpad Translations Administrators Edit question
Last query:
Last reply:
Revision history for this message
David Planella (dpm) said :


In the ideal scenario, if a project is hosted in Launchpad and it uses automatic translation exports, this process will be automatic. That is, the translator submits the translation and then it is committed automatically to the project's bzr branch. After this has happened, the translation will become "Green". This is the recommended setup, because it requires little to no manual intervention, making the translations process nearly transparent for both translators and maintainers.

However, there are other scenarios in which there are additional steps involved, namely the project maintainer has to request an export of a tarball with the translations from Launchpad and then commit those in the project. This happens for example when a project is hosted in Launchpad, open for translations there and also open for translations in a distro, e.g. Ubuntu.

This is a very general overview, so if you'd like to know the exact steps for a specific project, I'd recommend you to provide us a couple of links to projects where you've observed this and we can try to better clarify the steps.



Revision history for this message
Sveinn í Felli (sveinki) said :

One such project is OpenShot <>.
Actually, when I asked Jonathan the project leader about this, he asked me if I could find out the mechanism for him :-)
Another project is Stellarium <>.
Both projects have mostly violet strings which have been as such for a long time. This does not indicate that the activity is low - on the contrary. The 'green' strings in those projects - I suspect them to be something imported from former development sites.

Revision history for this message
Henning Eggers (henninge) said :

The colouring scheme was created when mainly upstream projects were imported to be used in Ubuntu. In that case "100% green" means "we are using 1oo% upstream translations". For projects that use Launchpad as their primary translation plattform, this state is not that important and "100% purple" is equivalent to "100% green". It might be a good idea to change the colouring scheme in the future.

To get them all to "green" you will have to simulate an external upstream by exporting and re-importing all translations. Please be aware of bug 354372 and more importantly of its duplicate bug 353981.

But I think the real bug is the colouring scheme or the naming of "translated" and "changed in Launchpad" and you need not really do anything about your translations.

Can you help with this problem?

Provide an answer of your own, or ask Sveinn í Felli for more information if necessary.

To post a message you must log in.