translation files in exported tarballs are non-standard

Bug #445332 reported by Henning Eggers
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

I am reporting this bug although I am quite sure it has been reported before. If anyone know the original, please mark this one as a duplicate.

When all the translations for a template or series are exported, they are put in a tarball. The directory within the tarball is taken from the template the the translations belong to. The filename is created as "translationdomain-langcode.po" to avoid problems when multiple templates have the same directory.

A naming scheme like this is not useful for for re-uploading the files to Launchpad, which needs just "langcode.po" names for translation files.

The fix it easy but the change in behaviour would have to be well communicated to translators.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

The fix is easy apart from one issue: multiple templates in the same directory. In that case, a de.po for one template would overwrite a de.po for another template in the same directory. In bzr exports we made a deliberate choice for "well don't do that then," which was easier there because it's a new feature.

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

Other bug subscribers

Related questions

Remote bug watches

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