Comment 9 for bug 683342

Thanks Didier, your explanations are clear.

I don't see where the problem would be to update the .pot file when doing `quickly save`. This would ensure that after each commit the .pot file is 100% synchronized with the source code. It's up to you if you want to push to Launchpad or not (additionally, why would you want to push translations that are not yet available in the source code that's on Launchpad?)

Launchpad would be able to retrieve the latest translations after a `bzr push`, if you have configured your project to automatically update the translations from your main Bazaar branch (which I always do)

Updating the .pot file on each `quickly save` does not imply any interaction with Launchpad, so you can continue developing your project on the plane ;) And doing it this way would mean that we don't need to create a new command just for that (as I understand you want to keep the number of commands low)

This is for the exporting part. Concerning the importing, I am afraid that this is not doable automatically. AFAIK you can only manually update the .po (either by merging the branch where you optionally export the translations, or by requesting an export [1] that will send you a link per email to a tarball containing all the .po/.mo files).

So my suggestion is to automatically do what can be done automatically (i.e. exporting on `quickly save`), and leave the importing to be manual. The compilation of the .po in .mo are currently done while packaging, or manually with `python setup.py build`.

Concerning `quickly sync` I don't personally see the need for it, since I always push my changes to Launchpad after a coding session, so when I use another machine I can just branch the project from Launchpad and I know it's complete. I am currently more concerned about the whole translation workflow (which potentially affect each Quickly project) than the smaller population of developers that switch machines all the time.

[1] https://translations.launchpad.net/quickly/0.x/+export