Format choice in export-to-branch

Bug #407581 reported by Jeroen T. Vermeulen
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Mike Rooney notes that it'd be great if export-to-branch could produce MO files for him. See comment at:

http://blog.launchpad.net/general/exporting-translations-to-a-bazaar-branch

Revision history for this message
Michael Rooney (mrooney) wrote :

Thanks for filing this Jeroen! I think either a choice of formats could work, or it might be more flexible to have two checkboxes, "Export PO files to branch: ", and "Export MO files to branch: ". This requires another attribute to be stored but could be pretty cool, as I think both can have value. Though I'd certainly rather see a choice of one of them than nothing at all :)

Changed in rosetta:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Steven Sproat (sproaty) wrote :

I too would love this functionality, seems trivial to get it working if LP can already email you the .po/.mo files

Changed in rosetta:
importance: Medium → Low
Revision history for this message
Christophe Simonis (OpenERP) (kangol) wrote :

This feature would be very interesting for Python projects as the built-in gettext module (in the standard library) can only use MO files, having Rosetta only export POs thus requires an additional build step to MO before being able to use the tool

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.