miro translation needs review -- help

The main thing to do when you upload an update to a template is to make sure that Launchpad can see that it's an update, not a new template. You can do this in several ways:

1. Always upload the file with the exact same file name and path. In this case the existing template is launchpad/messages.pot but the one you uploaded was just messages.pot. Unfortunately if you upload a file, your browser tells Launchpad the name but not the path. The way around that is to upload a tarball (Launchpad can of course see the directory structure inside a tarball) but that's not ideal for this situation.

2. Uploads are context-sensitive. If you want to upload an update to a template, go to the page for that template and upload from there. This tells Launchpad that the file is meant for that template, not some other (which might or might not exist yet) in the same release series of your project.

3. Set up bzr imports. This is by far the easiest way. Go to the page for your release series, and into the Translations tab. There you can instruct Launchpad to import the latest templates straight from your bzr branch. Updates will be imported automatically.

Hope this helps! I've also approved your upload manually.

Thank you for approving the import, but your answer is curious.

1. I've been uploading a .pot file called "messages.pot" to Launchpad for translations for the last two years into the trunk series. Henning set up our Miro-2.5 series a few months ago after I tried to copy the templates over from trunk. I was never told how he/she set it up, so I'm not aware of what was done. Your information is new to me. I have no idea why Henning set it up the way he/she did.

2. I go to the series page and upload the .pot file for that template. So this isn't a context-sensitive issue.

3. Launchpad hasn't successfully imported our svn repository in over two years. We recently switched to git but Launchpad doesn't support the repository url we use. Until those things are fixed on the Launchpad side, we can't use bzr imports.

Regardless, it sounds like you need me to put the messages.pot file into a launchpad directory, tar that up, and then upload it. It'd be easier if you could fix the data in the Miro-2.5 series so that the file was "messages.pot" and not "launchpad/messages.pot" just like the trunk series we have. Again, I have no idea why Henning set it up that way.

Any idea if this affects people uploading translated templates to the Miro-2.5 series, too? The second-to-most-recent Launchpad change removed the "last updated" column from the translations page, so I can't tell if translations are getting updated.

Henning is a "he." :-) The path we've got recorded for that template is launchpad/messages.pot. I'll change it to just messages.pot then. The change will only affect uploaders of translations if they were uploading files in tarballs, inside a launchpad/ directory. And again, if they were uploading from the actual translations pages, they will be giving Launchpad enough context to see what they want so it will still work.

Thank you so much, Jeroen! That helps a ton. :)