how to start the upstream

Hi Joe,

Upstream translations are automaticaly imported into Ubuntu only when a new upstream package is updated in Ubuntu and the package file contains the updated upstream translations.

You should ask ghe Gdebi developers to create a new release of Gdebi, containing the updated translations. After that you should ask the Ubunu gdebi package mantainer to also update the upstream package in Ubuntu (for each release).

As you said you could also manualy update the translations in Launchpad.

I recommend you to ask Gdebi developers to create an updated release, in this way new translations will also be available in other distributions.

Kind regards,
Adi

Hi Adi, thanks a lot for your answer.

I was a little unclear in my question. The translation i have done in Main, is in Launchpad (not outside Launchpad).

https://translations.edge.launchpad.net/gdebi/main/+pots/gdebi/da/+translate?start=0&batch=10&show=all&field.alternative_language=&field.alternative_language-empty-marker=1&old_show=changed_in_launchpad

What i was looking for where an easy way to update the different versions of Ubuntu meaning a merge of the translations (only one language at a time) in Main (Launchpad) with 6.06 (Launchpad), Main (Launchpad) with 6.10 (Launchpad) et cetera.
(as i understand the procedure translations i Ubuntu are not depended on getting a new release. They can receive an updated translation anyway for the release actually already in Ubuntu)?

If it can't be done at the moment, this looks, to me, as an obvious proposal for the developers?

As the project is using Launchpad as the place to translate, i assumed it took care of the downstream til the project itself and thereafter to other distributions. (in the next updated release).

hope this help in the understanding of my question.
bye
Joe

Hi,

As far as I know there is no automatic downstream Ubuntu package updates for translations.

In Ubuntu all updates (bugfix, new features, updated translations) are made by creating a new package and copy it into the Ubuntu repo. The package should be signed by a person and this is done manualy.

You could create a blueprint for that.

To ensure quality I assume the automaticaly translations should be reviewed by Ubuntu Translators.
In order to do that you should look over each string.

Right now all upstream translations are displayed as sugestions in a template for Ubuntu , so when an Ubuntu Translator is reviewing the package it will need only one click to aprove the upstream translation.

Cheers,
Adi

This bit is not correct: "Right now all upstream translations are displayed as suggestions in a template for Ubuntu." Upstream translations automatically also become the current translation in Launchpad, *unless* the translation team has chosen to override the upstream translation for that string with a different one. Only in that case do upstream translations show up as mere suggestions.

Question answered. It is just not possible at the moment, so i have started the tedious work of uploading the same file to the 7 Ubuntu versions (6.06 - 9.04).
thanks
Joe

Jeroen, does this also apply for upstream packages hosted in Rosetta, where no updated package was created for Ubuntu ?

For example we have gdebi.0.3.2 in Ubuntu Gutsy.
Joe is translating gdebi upstream, in gdebi main (trunk/mainline). Does it mean that his translations are automaticaly reflected in Gutsy gdebi 0.3.2 ?
I know Danilo said this will be done with the implementation of shared messages. Do we have shared messages in Rosetta?

Joe, I don't know you could use the same file for all Ubuntu version.

For example in Jaunty we have gdebi with 114 strings and in hardy with 107 strings.

During a package lifecicle some strings are removed, some are modified and some are added.

Joe, I don't know you could use the same file for all Ubuntu version.

gdebi is a new program and it is expanding. I translated main, which had all the newest strings. downloaded the file and Imported it to 9.04 and 8.10. All strings where covered, for 7.10 and 8.04 only 1 string were different. (off course i had a lot of strings who where just removed, but the merge took care of this). The oldest versions only had 6 strings who differed. So only few strings has been modified or removed in gdebi.

bye
Joe

Joe, not all applications have more string is newer version.

Check Brasero for example.
From Hardy to Intrepid i think that in Brasero were removed more than 200 strings.

I don't know the exact numbers, but I know that I did the same thing with Brasero and I was not so lucky :)

Cheers,
Adi

Adi: yes, what I said also applies between "user" and "published" uploads for a project.

Now, about message sharing: apart from the package uploads, there is no automatic sharing between an upstream project registration and a corresponding Ubuntu package, even if the upstream project is translating in Launchpad.

This won't change when we implement message sharing, because it introduces too much complexity in one go, but it will bring translations of the same package in different Ubuntu releases together, as well as translations across release series of the same upstream project. But it won't act between the project and the package.