Re: [Po4a-dev] version 0.15.4-2

[Denis Barbier]

On Mon, Dec 01, 2003 at 08:30:55AM +0100, Martin Quinson wrote:
[...]
> > > Moreover, I tell in the translated document header that those files should
> > > not be considered as source (and thus not stored under cvs).
> > 
> > Some people argue that generated files must not be stored in CVS, but
> > I do not share this point of view, this is sometimes useful.
> > E.g. note that po/pod/po4a-pod.pot is stored in CVS.
> 
> Ok, I'm convinced (wasn't hard ;). Feel free to add the translations to the
> CVS.
> 
> Do you feel that we should change the header of generated translation to
> remove this incitation to not store those files under CVS? I'm afraid that
> some people will store only the translation and not the po source file...

I have no definitive statement; for instance with po-debconf, developers
are not encouraged to store translated templates files in CVS.  There
are several reasons:
  * Translated templates files are generated in a temporary directory
  * They contain a mix of encodings; people using stateful encodings
    may be unable to display it.
  * Po-debconf is robust, so there is no reason to search for regression
    bugs ;)

OTOH with po-debiandoc I found very useful to store translated
documents, because I could then easily check that text was not lost
or corrupted.  When each translation goes to its own file, this is
certainly my preferred choice.

So having a header is very fine, but it could be rephrased, e.g.
something like
  Warning: This is an automatically generated file. DO NOT EDIT!
with a longer explanation.
I also wonder whether putting $VERSION in this header is a good idea.

Denis