Generated projects do not support translations

Thanks for your report.
Hum, I think we can embed the translation handling in both package/share/release code instead of adding a new command.

I think this can be easy handled for 0.4 release (as we currently target 0.2.1).

I was suggesting a new command to generate the po file for an additional language - normally you would do a bunch of intltool commands to generate a .pot file, rename it, do some translation, tweak autoconf rules, update the headers, and finally commit it. You could make this friendlier.

So to, say, add a Dutch translation, "quickly translate nl" would generate or update an nl.po file in the correct location, add it to source control, and open it in gtranslator (or poedit).

I was sort of assuming that packaging and releasing would "do the right thing" once the po file exists.

Does that make the use case clearer?

We should also add the:

import gettext
_ = gettext.lgettext

in some reasonable place. Promoting this convention is a worthy goal.

Didrocks, thoughts about where to add this code for the project? Do we need to add it to each and every generated file?