Re: Updating po files on make dist

[Bruno Haible <bruno clisp org>]

Christian Rose writes:

> >   9. Check if the POT file was updated by the translators meanwhile.
> >      cvs update *.pot
> >      If this command reports "U" or "P", the POT file has changed, and
> >      you need to update your PO file accordingly:
> > 
> >      mv xy.po xy.po.tmp
> >      cvs update xy.po
> >      msgmerge -o xy.po xy.po.tmp *.pot
> 
> As Abel already pointed out, we do not keep pot files inside GNOME CVS.

OK, then you can reformulate this step in such a way that it doesn't
refer to the POT file:

   9. intltool-commit xy.po

Now it's up to you to write 'intltool-commit'. IMO it should contain
the regeneration of the POT file (since you are saying that it's
never committed into CVS) followed by msgmerge.

> > The 'msginit' program has been created to streamline this step for the
> > translators, filling in most of the header entry. So you can write
> > this step as follows:
> > 
> >   4. Create the initial xy.po:
> >      msginit -l xy
> 
> I'm reluctant to add that, at least yet. msginit seems pretty much tied
> to the Translation Project's listing of teams

msginit is indented to work with GNOME and KDE projects as well. If it
doesn't work as you expect, please file bug reports to the
bug-gnu-gettext mailing list. msginit is *not* limited to the
Translation Project @ umontreal.ca.

> Also, I'd prefer if msginit left the charset field uninitialized
> ("CHARSET") or as "UTF-8" (as we mandate the use of UTF-8 in GNOME)

I can arrange that for GNOME projects "msginit" always sets the
charset to "UTF-8". Any objections?

Bruno