On Tue, 30 Apr 2002, Hugo van der Kooij wrote:
> On 30 Apr 2002, Ari Supperi wrote:
>
> > Has anybody translated in to Spanish the description-messages of the
> > plug-ins ?
> >
> > Anyone interested ?
>
> Translations have been discussed about but the present architecture is not
> very well suited for this.
>
> I would like to know if full internationalization is part of the plans for
> v1.3 (Renaud?)
I'm interested in contributing to the i18n effort of the future
releases. I have some experience with gettext (I helped to i18n Gimp and
some parts of Gnome), and hope this solution (GNU gettext) is acceptable
by Renaud.
I see the following pros:
- only 1 translation file per language for all the plugins. Thus making
the translators' work much easier: only one file to edit instead of ~900
nasl files.
- many tools (Gnome, KDE, Emacs modes) exists to handle .po files and make
it easy to spot which strings need to be updated.
- very easy to add another language.
- light impact on the code.
- doesn't need to change the plugin syntax, so it doesn't prevent, for
example to use XML in the future for plugins...
- the same system could be used to localise the nessus GTK client.
As far as I know the nessus/nasl code (that is not so much), the better
place would be in the nasl interpreter.
For the plugins themselves, they'll have to be edited so that each string
returned is first send to gettext for translation before to be returned
to nessusd. ie: instead of having
security_hole(port:80, data:"string")
we'd need to use
security_hole(port:80, data:gettext("string"))
Opinions?
Cordialement,
--
Vincent RENARDIAS
Directeur Technique
StrongHoldNET / http://www.strongholdnet.com
