Ferenc Engard <[EMAIL PROTECTED]> Forwarded From:
> Alan Knowles wrote:
> >
> > We have had a few discussions here about similar issues - mainly concerning how to
>make the interface 'translation' friendly
> >
> > At present the nadmin translator module will
> > read styles and create translated styles based on parsing an original style called
>..._eng
>
> Sorry but I don't understand what you mean. Could you describe it more?
> Maybe with a diagram...? Basically it means that I have one master
> style, nadmin parses the style's elements, offer an interface to write
> in the translations, stores its own database, and each time I change the
> original style I have to 'recompile' the other styles?
Pretty much spot on..
At present it doesnt work out what has been changed and only update those - it does a
full 'remake' of all the elements when prompted.
stage 1 the parser
- reads all the 'text' from the original html pages
- stores it in the database using md5sums of the strings.
stage 2 the input system
the interface does a look up on similar words already translations and uses these for
suggestions
Attempts to summarize the number of missing words..
stage 3 reparse and update
re reads the original translations and creates or updates the translated template
based on the results of the first one.
stage 4 import/export
saves each database entry in a serialize format (not 100% reliable but not too bad)
>
> I have looked into the translation module, but I cannot see how to
> include a new language.
Thats one of those leftover todos-
you have to create a snippetdir in the hklc_adminsite_tools/data directory with the
name of the language you want to add..
>
> Bye:
> Ferenc
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
