[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] a .gmo file is not regenerated when its .po file chang

From: Benno Schulenberg
Subject: Re: [bug-gettext] a .gmo file is not regenerated when its .po file changed
Date: Sun, 31 May 2015 23:00:58 +0200

On Sat, May 30, 2015, at 12:26, Daiki Ueno wrote:
> Benno Schulenberg <address@hidden> writes:
> > It has been designed so, yes.  But it was designed wrong, in my opinion;
> > the content of the file does not need to be changed, and should therefore
> > not be changed, but the timestamp should be touched/updated so that make
> > (and humans) can see that things are up to date.
> If you think so, could you consider providing a patch and maintaining it
> in gettext?

Yes I would.  But it will take me a long time to make it as I
understand very little of Makefiles.  So give me half a year.

>  To be honest, I am not confident that I could do that by
> myself, without breaking something else.

No need to be afraid.  Mistakes may be made.  I see you
already have introduced the ability to decouple 'make dist'
from 'make update-po', and 'make update-po' from 'make
tralala.pot'.  I can understand why a maintainer would want
the first one, but I fail to grasp the use of the second one?

If necessary, we can make the same conditional decoupling
between GMO and PO files, or whatever it's going to be.

>  Also, I don't see any strong
> reason why "make update-gmo" is not sufficient.  It even runs on "make
> dist" (by default).

Because I'm not a maintainer, I'm a user, I never run 'make dist',
just 'make' and 'make install'.  That should cover everything, no
matter what file I change.  The only thing that should be a separate
and independent target is 'make POT', because PO files don't acquire
new translations automatically, there is no point in updating the POT
file if you can't acquire new PO files -- you have to be a maintainer:
you run 'make POT', send it out to translators, go to sleep, wake up a
week later, pull in the updated PO files, and then run 'make dist'.

> > (By the way, what are $(CATALOGS) exactly?  How are they different from
> > $(POFILES) or $(GMOFILES)?)
> It basically same as $(GMOFILES), but $(CATALOGS) depends on the LINGUAS
> envvar specified at configure time.  See m4/po.m4.

But... shouldn't then all "CATALOGS" be replaced with "POFILES" in that
stamp-po comment?  Otherwise it doesn't make sense to me.


http://www.fastmail.com - IMAP accessible web-mail

reply via email to

[Prev in Thread] Current Thread [Next in Thread]