Launchpad itself

multiple pot files for translation

Asked by Michael Nagel

Simple Scan is the default scanning application for Ubuntu.
The upstream project is hosted on launchpad (https://launchpad.net/simple-scan).

There are two pot files that should be enabled for translation in launchpad:
/po/simple-scan.pot
/help/simple-scan-help.pot
(see: http://bazaar.launchpad.net/~simple-scan-team/simple-scan/trunk/files )

However, we cannot get launchpad to pick up both of them, even though we tried really hard for a long time.

Could someone look into this and help us out?

best Regards
Michael

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Jeroen T. Vermeulen
Solved:
Last query:
Last reply:
Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#1

It looks like the two templates got mixed up somehow. The template you currently have is called simple-scan, but it looks as if it was actually taken from help/simple-scan-help.pot (and its domain is simple-scan-help). The contents however look more like they're from the program. I wonder if this led to a situation where somehow two files are getting imported as the same template. Maybe something got renamed injudiciously.

Could you check whether the template that's currently translatable in the UI is the help template or the main template? I can then set the path, name, and domain to be consistent for that one template, and we'll see if that gets the imports going.

Revision history for this message
Gabor Kelemen (kelemeng) said : 		#2

The current template is the main one from po/. And some time ago the help was indeed imported under this template, but that seems to be fixed now. I have also translated some new strings about a week ago, so I think import into that template works as expected.

What is really needed: setting up/importing the help template, so that we can finally start translating that too.

Revision history for this message
Michael Nagel (nailor) said : 		#3

> What is really needed: setting up/importing the help template, so that we can finally start translating that too.
it should be added IN ADDITION TO the main template and not overwrite it.

we are here to figure out how to achieve this.

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

Yup, it looks like the whole problem was caused by one template being imported into another. With that disambiguated, the templates have been imported. I would expect the translation files you see on the queue now to be approved automatically, except help/de/de.po which should be just help/de.po.

Hope this helps!

Jeroen

Revision history for this message
Michael Nagel (nailor) said : 		#5

Thank you Jeroen! I looks quite good now. Help strings show up as untranslated now, and already translated application strings are still there :)

I created a merge request to rename help/de/de.po to help/de.po -- when this is applied and imported successfully, I will mark this question as solved/answered.

> With that disambiguated, the templates have been imported.
Does this mean you actively changed something or is this a passive thing?

Best Regards
Michael

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

The change I made was to set the name, domain, and path of the existing template to all refer to the “po” template. After that, there was no more confusion between the two templates. Then I requested a one-time import from the branch (because there might not be any new changes to trigger one automatically) and that did the trick.

Revision history for this message
Michael Nagel (nailor) said : 		#7

Thanks Jeroen T. Vermeulen, that solved my question.