consistency between .po and .pot files

Dwayne Bailey dwayne at
Thu Feb 17 07:18:05 UTC 2005

On Thu, 2005-02-17 at 16:28 +1000, Sarah Wang wrote:
> > > d. Each translator to perform "msgmerge" prior translation
> > 
> > e. Download current po file from the webpage.
> > 
> > Options d and e together should be sufficient. Translators
> > already knows tools like intltool-update or msgmerge.
> > If that is not a case then they could download current
> > (and updated) po file from the web.
> Here is another option extending option d:
> have auto pre-commit check, compare .po file with .pot file, if .po is
> not most up to date, commit will fail (perhaps allow it during grace
> period but give warnings). If the translator doesn't know how to do
> msgmerge, he/she can get help from the coordinator.
> Would this option be better?

I think that is a good option.  But that only catches out of date files
when you commit.

Perhaps doing a blanket update at various points during the dev process
would be good.  Such as weekly after a message freeze.

It would be nice to have some script or something on the stats page that
specifies which PO files are out of date.

Dwayne Bailey
083 443 7114

>From a mesh network in White River, Mpumalanga, South Africa

More information about the trans mailing list