Launchpad itself

How to deal with templates from branch & old manually imported?

Asked by Viktors Petrovs

Hello!

We decided to host sources of our project on launchpad.
https://translations.launchpad.net/austrumi

At this time there are manually created translation templates in our project. How to deal with automatic translation templates import? As i understand launcpad will import templates from sources using full file name in the source tree like:
   domain/po/domain.pot
but currently we have structure like:
   domain/domain.pot
Which is better way to solve this situation? Import templates & delete old obsolete?

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
Данило Шеган (danilo) said : 		#1

Launchpad should be completely happy with a layout like:

 domain/domain.pot
 domain/it.po
 domain/bg.po
 domain/ru.po
 ...

It should also commit translation files to where it has seen the template first. I've looked at your branch and it seems to commit it to a different location, because we have the potemplate paths stored incorrectly.

I.e. we have paths like systemtools/systemtools.pot instead of systemtools/po/systemtools.pot (where I see it in your branch). Did you upload an earlier version which had these paths?

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

If I understand the question right, it's what to do about the path changes from the old paths used in the manual uploads to the new ones as found in the bzr branch.

This shouldn't be a problem, _but_: if you've also got translation exports to the same branch enabled, disable them first. Then wait until all the files have been imported from the bzr branch, and once you're happy with the result, you can start the automatic bzr exports again.

In fact, before you start exporting translations to your source branch again, I'd recommend exporting to a test branch first to see that everything is in the right place.

Revision history for this message
Viktors Petrovs (viks77) said : 		#3

Thanks Jeroen T. Vermeulen, that solved my question.