On Fri, Jun 21, 2002 at 03:12:20PM +0200, Josip Rodin wrote:
> On Fri, Jun 21, 2002 at 12:36:50AM +0200, Denis Barbier wrote:
> > > Will gettext do all of its fuzzy stuff with the templates, BTW?
> >
> > Hmm, can't see what you are thinking about, but webwml/po/README may
> > answer some of your questions. Of course, feel free to ask again if
> > explanations are needed.
>
> I don't think it explains this... will there ever be "fuzzy" translations
> with this? I'm guessing no, but just to be sure, please answer.
How message catalogs are handled is not clearly defined, but here are
my present thoughts (may slightly differ from what I wrote in the
README file).
There are IMO 2 strong requirements:
* The PO files are committed into CVS. They are managed by
translators.
* The MO files are not under CVS control, because they must be
automatically updated before builds.
As Makefiles will tell that HTML files must be regenerated when MO files
of the current language have changed, some extra care must be taken.
Here is a solution:
* templates.xx.po are managed by translators and committed into CVS
* templates.pot is automatically generated by scripts/wmlxgettext.pl
during builds
* updated PO files (e.g. with a .pou suffix) are never committed
(to avoid CVS conflicts):
msgmerge templates.xx.po templates.pot -o templates.xx.pou
* MO files are generated:
msgfmt -o templates.xx.gmo templates.xx.pou
This is where the "fuzzy" stuff takes place. As written above,
fuzzy translations are removed. If you want to keep them, add
the -f flag.
* MO files are installed if they differ from the current ones.
Denis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
