Hello,

Sorry Marc, you already mentionned this issue, but I forgot about it.

On Wed, Nov 16, 2005 at 02:35:56PM +0100, Marc Haber wrote:
> 
> introducing po4a translated manpage support to adduser has been a
> nightmare. Together with the manpage translators, it took multiple
> weeks to get things right. Right now, doc/po4a/adduser.pot is
> generated anew after each and every build which is a severe annoyance
> for the svn-buildpackage based development process.

The plan to fix this is to only re-generate the POT if an English document
has a more recent modification time.
If the POT is generated anyway, we can also check that this update is
relevant with something like:
diff -q -I'#:' -I'POT-Creation-Date:' -I'PO-Revision-Date:'

We can also avoid to re-generate the PO by checking the POT-Creation-Date
of the POT and PO files. diff may also be used in this case.

I've already added a --no-translations to avoid re-generating the
translated documents (this may be useful in a 'make clean' rule).

I will implement it soon in po4a.
Doing it in po4a can be easier than in a makefile because I have the name
of all the documents in the configuration file. This will become the
default behavior (with a --force option to force the re-generation of the
POT and PO files), so a versionned dependency won't be necessary.

> Please, take a look at adduser 3.78 (which has just been uploaded) and
> tell me what is wrong with the po4a usage in adduser, and how to get
> rid of the repeated generation of doc/po4a/adduser.pot.

I will have a look at it, but there is probably no way to fix this issue
at the moment.

> While we're at it, some contents for /usr/share/doc/po4a such as a
> HOWTO for package manpage translation for Debian packages would be
> great.

This HOWTO is contained in the po4a.7 man page (you may not find you
answer though).
Martin Quinson plan to write a README (which will mostly point to the
po4a.7 man page).

Kind Regards,
-- 
Nekral


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to