Comment 2 for bug 423529

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?