On Thu, 1 Jul 2004 09:47:36 +0200
Fabien Vantard <fzz@...> wrote:
> > Great news! I think you probably know the procedure from
> > reading this list, right? I mean the cvs freeze, po update,
> > release procedure.
> To update the po file from cvs source :
> <after getting CVS sources>
> $ cd sylpheed-claws/po
> $ ../tools/update-po LANG.po
> <now edit LANG.po to completion>
> To apply po file modifications and testing it :
> $ make LANG.gmo
> $ make install (as root)
> reload sylpheed and test the po file.
> I'm right ?
Well, that looks good on how to update the translation,
but it is not quite what I was talking about.
I meant this procedure:
I announce here that a CVS freeze and release is
imminent. I give the date for the CVS freeze. This
is a 24 hour period, (a whole day, in fact, GMT TZ),
when none of the developers make any new changes
in CVS, (apart from any critical last-minute bug
fixes), and the translators should update their
CVS trees, and create the po to be included in the
release. Updated translations should then be sent
to me at <translations@...> as soon
The freeze normally happens the day before the release,
so this gives a 'reasonable' amount of time to the
translators without holding up the flow too much.
> I've just only a little question about po syntax file : is it possible to
> include some comments explaining choices of translations like the comments at
> the beginning of the po file but where we want in the file ?
afaik, a comment line should start with a '#' symbol.
"Thanks to his green candle, the 'Pataphysician can
lighten our darkness."