PO: modifying po-replace before integrating it to the release process

PO: modifying po-replace before integrating it to the release process

Until now, updating the translation template file is disconnected from
the releasing process, which means that a dev or translator must

1- run 'po-replace',
2- embed lilypond.pot headers,
3- eliminate all po files that have been moved upwards from po/out to
po/
4- commit the new lilypond.pot
5- run 'make dist' to have a tarball,
6- notify the Free Translation Project where to pick up that tarbal.

The first three steps may already be reduced to one single step by
embedding lilypond.pot directly (with specific options and some 'sed'
when creating) and moving it only in po/, what does this patch.

A second step would be to have a call to po-replace when the Release
Meister enters the dance, which would "group" steps 4 and 5.

We then will have the same unique tarball to refer to, directly from
linuxaudio.

[Jean-Charles, 2012-05-07 18:05:52]

Before integrating po-replace in the release process,
let build a well-formed lilypond.pot in one run.

[Graham Percival, 2012-05-10 13:23:17]

I can't see anything wrong, but it would be nice if somebody other than lilyfan
could test this.  I'm on vacation so I can't really test it until May 30.