On 3 Apr 2006 at 9:15, Martin Quinson wrote: Hi,
> > > > > > The po file must be updated against the day2 pot version, even if hte po > > > file itself is more recent. Yes, you're right. However when writing my report, I was pretty sure that po4a makes use of POT-Creation-Date - the documentation says so! Let me quote the po4a man page: The default behavior (when --force is not specified) is the following: [snip] The PO files are re-generated based on the POT-Creation-Date of the POT and PO files. > > > update the po file. Unfortunately, the documentation says: > > > -U, --update > > > update def.po, do nothing if def.po already up to date > > > > > > It does not even update the POT revision date of the po file (just > > > tested). I would consider it as a bug in msgmerge. But since po4a doesn't use the field, the bug is not as important as I had thought. > Robert, what do you think of all these new elements? Do you still consider > this as a bug? Please update the docs, and close the bug. Regards, robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]