Launchpad itself

Choose translation languages for projects

Asked by Nicolas Ganivet

How is it possible to choose/restrict the languages a particular project will be translated to? I would hate that somebody spends time translating my project in an obscure language that is never going to be used and/or updated over time. I have not found any settings that would make this possible, except maybe by restricting who can contribute translations, which goes against the essence of Launchpad.

In concise form, how can I enable anyone to contribute Spanish/French/Italian/Chinese/Arabic/... translations, but not in any other languages?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
Данило Шеган Edit question
Last query:
Last reply:
Revision history for this message
Tim Penhey (thumper) said : 		#1

I don't think you can, but I'll assign to someone on the translations team as they may know more.

Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#2

Very thoughtful to think of that—in fact it's our biggest worry when existing projects are opened for translation in Launchpad!

The best approximation of this that we have is the Restricted permissions model (in combination with a custom translation group). In this model, the languages that are not covered by the translation group are closed for translation. For the other languages, anyone can contribute; but the contributions have to be reviewed by members of the translation team for that language.

This works fine if you have enough active members in the translation teams who review the suggestions made by other users. We did it this way to allow project owners to control the quality and consistency of translations. If you want everyone to be able to edit the translations directly, without separate review, you can make the translation team(s) in the translation group open so that anyone can join and basically become reviewers themselves.

It's even possible to do this on a per-language basis: if you have enough translators to Spanish to get very good quality, but not enough to Albanian to get a full translation even before you start worrying about quality, then you can have a closed Spanish translation team with only "proven" reviewers, but leave the Albanian team open so anyone can join.

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

On the other hand, why not publish your application in that obscure language if the translation is complete?

Even if you don't *ship* your application with all the languages it has been translated into, you could still point people to Launchpad where they can download the mo file or files for their language. I am sure that translators and speakers of obscure languages are willing to jump through extra hoops to get an application in their own language.

I don't think such a restriction is necessary and I guess that is why it's not directly implemented in Launchpad. But this is just my opinion ... ;-)

Henning

Can you help with this problem?

Provide an answer of your own, or ask Nicolas Ganivet for more information if necessary.

To post a message you must log in.