Difference between revisions of "Developer Area/Language Packs/Launchpad Migration"

From Mahara Wiki

< Developer Area‎ | Language Packs
Line 1: Line 1:
=How to migrate a gitorious language pack to launchpad=
Steps required to do a one-off language pack migration from gitorious to launchpad
===Convert the existing language pack to a .po file===
===Convert the existing language pack to a .po file===

Revision as of 16:00, 23 August 2011

Steps required to do a one-off language pack migration from gitorious to launchpad

Convert the existing language pack to a .po file

This should be done on a language-by-language basis for all branches (1.2, 1.3, 1.4, and master) because it's not possible to have some branches using gitorious and others using launchpad. Use the script mahara-langpacks/ in the mahara-scripts repository. You probably want to change the directory locations near the top, and you definitely want to change the list of languages.

Update the Last-Translator line in each .po file

"Last-Translator: Gregor Anželj <[email protected]>\n"

If you don't do this, you (as the uploader) will be credited as the translator after it's uploaded to Launchpad.

Get the most up to date .pot templates from launchpad

You need one mahara.pot for each branch. You can find them on these bzr branches:


Create a tarball for each branch

Put all the files in a mahara directory, and rename the .po files to just sl.po, etc., so you now have four tarballs, named something like master.tar.gz, 14stable.tar.gz, etc., each containing:


You can upload individual .po files rather than tarballs, but don't. It seems to take forever for them to be imported, possibly because it requires human approval.

Upload the tarballs

Each branch has its own upload page:

All the files should now be visible on the import queue:

After 24 hours the translations should have been imported into launchpad and should be visible at

Create a translation team

Go to the Translation group at

If there's only one translator, just add their launchpad user as the Team on that page. If there are likely to be multiple translators, create a team with a name like mahara-lang-es, change the team's owner to mahara-reviewers, remove yourself from the list of active members, and add each translator's launchpad user as a member of the team. Then go back to the Translation group and add the team as the maintainer.

Update the master language pack location

In mahara-scripts/mahara-langpacks/language-repos.txt, change the location for each language you imported to launchpad from gitorious to lp:mahara-lang. The langpack list at will start pulling from launchpad instead of gitorious.