Find a way to use Launchpad's automatic translations export

Bug #748446 reported by Sense Egbert Hofstede on 2011-04-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LoCo Team Portal
Wishlist
Unassigned

Bug Description

Launchpad Translations can automatically import templates and translations from a branch, but it can also automatically export translations from Launchpad to a branch. Possible outdated information about this functionality can be found at <https://help.launchpad.net/Translations/YourProject/Exports>.

At the moment the translations of the LoCo Directory are manually exported from Launchpad and then imported into the LoCo Directory. It would be a lot easier if Launchpad would automatically export all translations to the branch.

Unfortunately, it does not work with the way Django structures its locale directory. In order for automatic imports and exports to work, Launchpad needs to have the translations in the same directory as the templates, but Django puts them in "locale/XX/LC_MESSAGES/". This breaks Launchpad.

A possible solution could be to create custom makemessages and compilemessages commands that store the PO files in same directory as the POT file, but keep the MO files in the default location, so Django can find them.

Changed in loco-directory:
importance: Undecided → Wishlist
status: New → Confirmed
Adnane Belmadiaf (daker) wrote :

I think we can write a plugin for tarmac to do that.

tags: added: tarmac
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers