Andrei Zmievski wrote:
>
> On Thu, 10 May 2001, Hartmut Holzgraefe wrote:
> > do you have a better idea on how to solve the 'missing functions'
> > problem in translation?
>
> Write a little tool in PHP that uses XML parser to gather all documented
> functions in en/functions/imap.xml and de/functions/imap.xml, compares
> them, and gives you the result.
that's exactly what i have done for generating the function tables,
but here the goal is different (although i used a slightly different
approach with customized dsssl stylesheets for jade instead of a PHP
XML parser, comes in after this first step)
for the function tables i just wanted to know which functions were
translated and which not
for the manual we need something that generates input for jade with
the missing pieces in translations filled with the original stuff
from the 'en'-tree
right now configure takes care of this by creating chapters.ent
which contains all the entities used by manual.xml to include
files
each file not found in the translation tree is replaced by
its original form the english tree
this is superior to the old scheme where we had untranslated files
in the translatin subdirs as this lead to tranlsations of already
outdated files if translators didn't check the copies of the
englisch files for being up-to-date before starting translations
(and it saves some diskspace, too)
the big problem right now is that functions added to the english
version of an extension documentation will not show up in the
translations if added after translation
that's why i want to get the replacement mechanism down to the
function level, because these new functions do not show up in
anywhere in the translated manuals
sure, we could create some build system clever enough to compare
the translated and original XML, find missing pieces in the translation,
create a temporary file that puts in all these parts from the original
and uses this temporary files as input for jade,
but IHMO this would lead to *very* bad performance (and building the
manual is already a time-consuming task) while i hope that having
more, but smaller, input files wouldn't hurt jade performance to
much while making configure burn some more cycles, but the current
configure is almost as fast as light compared to how long a make
takes so making it a little slower wouldn't harm as much
--
Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77
