directory structure of po file exports for new translations does not match that for translations which existed in the uploaded package

Bug #354372 reported by Matthew East on 2009-04-03
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

In the gnome-user-docs package in Ubuntu, the package is uploaded with upstream translations in this directory structure:

documentname/LANG/LANG.po

e.g. gnome2-user-guide/it/it.po

This is respected when exporting the template from Rosetta.

However, when new translations are added in Rosetta, these appear in the root directory of the document, and not nested under a sub-directory:

documentname/LANG.po

e.g. gnome2-user-guide/zh_TW.po instead of gnome2-user-guide/zh_TW/zh_TW.po

I have to create the relevant subfolder manually and move the files. It would be very helpful if Rosetta would respect the directory structure.

I've ignored for the purposes of the above examples the fact that Rosetta's po files are not in fact named LANG.po, but are instead named template-LANG.po (bug 353981)

I think this is important: we should try to detect structure of uploaded files (the slightly complicated bit is that we only know paths for each of the individual files we imported, so we'd have to join them together and construct a new path using that, with added complication that existing paths in our DB are a mess).

Changed in rosetta:
importance: Undecided → High
status: New → Triaged
Robert Collins (lifeless) wrote :

This is relatively minor, as new languages are infrequent. Patches would be wonderful, but for now its not in our roadmap for LP.

Changed in launchpad:
importance: High → Low
Henning Eggers (henninge) wrote :

This is not about "new languages" but about "translations in a new language". A project transitioning translations to Launchpad may bring along translations for x languages in a tarball as described above. Now translators can add translations for further languages through the LP web interface (but the languages do already exist). Exports for these additional "LP-only" translations will not follow the directory structure of the originally imported tarball.

I have no time for a patch, tough, sorry.

On Sun, Jan 1, 2012 at 8:20 PM, Henning Eggers <email address hidden> wrote:
> This is not about "new languages" but about "translations in a new
> language". A project transitioning translations to Launchpad may bring
> along translations for x languages in a tarball as described above. Now
> translators can add translations for further languages through the LP
> web interface (but the languages do already exist). Exports for these
> additional "LP-only" translations will not follow the directory
> structure of the originally imported tarball.

Yes, I got that - I meant new languages in the context of a project.
Yes, new projects on LP will get a bunch of languages rapidly, but it
will stabilise fairly quickly.

> I have no time for a patch, tough, sorry.

No problem! I was trying to be encouraging to anyone that wants to
hack on this :)

-Rob

Henning Eggers (henninge) wrote :

Hm, then I am surprised that "new languages are infrequent". I would have thought that this happens quite regularly.

Matthew East (mdke) wrote :

Yes, this happens quite frequently and continues to be an annoyance.

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

Duplicates of this bug

Other bug subscribers