Launchpad itself

How come that not all translations are exported to a branch?

Asked by Kristina Hoeppner

For our project we have set up a translation that is currently available for version 1.5, 1.6 and 1.7. The code is not kept in Launchpad, but just the translations. I figured out that in order to export a translation, I needed to upload a branch and then make that the translation branch. We just did that for 1.6 and 1.7, but not all templates are exported to the correct folders. The folders seem to be create themselves during the export once a day, but unfortunately, not all folders are created that will contain the po files. The path for the templates is set correctly.

It somehow worked for our 1.5 version, but someone else had set this up way back in the day.

Example:
https://translations.launchpad.net/mahara-manual/1.7/+templates has a bunch of templates, but the export branch http://bazaar.launchpad.net/~mahara-lang/mahara-manual/1.7_STABLE-export/files/head:/potfiles/ only contains 3 folders, i.e. a folder each for 3 templates but doesn't have all translations. German, for example, is almost fully translated, but there is no translation. Yesterday, only two folders existed and today a third one was created.

For version 1.6 http://bazaar.launchpad.net/~mahara-lang/mahara-manual/1.6_STABLE-export/files/head:/potfiles/ almost all folders got created, but a couple are missing. The translation records look better though.

Is there something that we are overlooking when creating the branch? Would it be best to start from scratch? If so, how could the existing branches be deleted on Launchpad as this is the only place we need them? I could not yet delete a branch due to "This branch cannot be deleted as it has 2 branches sharing revisions. "

Thank you for any pointers.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Kristina Hoeppner
Solved:
Last query:
Last reply:
Revision history for this message
Kristina Hoeppner (kris-hoeppner) said : 		#1

To answer my own question: The export is only made for files that have changed and not for the rest as the export seems to assume that everything else staid the same. As we needed a different folder structure than was set up initially, we could not re-use the translations.

Thus, we exported all translations, fixed the names so that we only had the language ID and not the folder name in the file name and then uploaded these changes to the branch to give us all the translations.

Then everything seemed to work. Waiting for the automatic sync this evening.

Revision history for this message
Kristina Hoeppner (kris-hoeppner) said : 		#2

To answer my own question: The export is only made for files that have changed and not for the rest as the export seems to assume that everything else staid the same. As we needed a different folder structure than was set up initially, we could not re-use the translations.

Thus, we exported all translations, fixed the names so that we only had the language ID and not the folder name in the file name and then uploaded these changes to the branch to give us all the translations.

Then everything seemed to work. Waiting for the automatic sync this evening.