Add documentation on the supported layout on the tarball upload form

Bug #651900 reported by David Planella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

When checking on the status of some manual KDE uploads today I noticed that they were not imported because they did not follow the gettext layout (i.e. POT and PO files flat in the same directory, PO files named $LANG.po), and the uploader did not know about the expected format.

Here's the upload form in one of the templates where it happened:

  https://translations.launchpad.net/ubuntu/maverick/+source/plasma-mobile/+pots/plasma-mobile/+upload

It would be useful to either add an additional paragraph with an explanation, a link to the existing documentation [1] or a popup with this information. This way the uploader would have known the expected layout in the tarball.

[1] https://help.launchpad.net/Translations/YourProject/ImportPolicy#Sample%20directory%20layout

Revision history for this message
Данило Шеган (danilo) wrote :

TBH, we should probably aim to support layouts like that instead. See bug #444706 for one particular case that is quite common, and this bug seems to describe the other:

  .../<lang1>/template1.po
  .../<lang1>/template2.po
  ...
  .../<lang2>/template1.po
  ...

Changed in rosetta:
status: New → Triaged
importance: Undecided → Low
tags: added: import-queue
Revision history for this message
Henning Eggers (henninge) wrote :

Sorry for the status toggle but I just saw that this is already implemented for project uploads. Should be easy to transfer to the other upload form. Maybe I'll do that this afternoon. ;-)

Changed in rosetta:
status: Triaged → Fix Released
status: Fix Released → Triaged
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.