On Tuesday 06 May 2008 16:18, Javier Fernandez-Sanguino wrote:
> 2008/5/6 Jan-Oliver Wagner <[EMAIL PROTECTED]>:
> > Opinions?
>
> Even though client and server releases are different I don't suggest
> bundling the PO files with the openvasd release and have the server
> handle gettext translations. For several reasons:
>
> - the NASL code is actually in the openvas-plugins package, not in the
> server

yes, I indeed hat the this module in mind, not "openvas-server".

> - it adds complexity to the server for a task unrelated to
> vulnerability scanning

yes, my intention is to get the code base of openvasd further
reduced.

> - you (probably?) have to modify the Nessus client-server protocol so
> that the client can provide the server its language settings (the
> client knows the settings based on the user's environment).

I thought that this could be neglected for a first step.
The server is simply configured with a default language and
will deliver corresponding strings if available.
It is my understanding that most users of OpenVAS-Client
have also installed and configured OpenVAS Server.
 
> I suggest taking this approach instead:
>
> - adding PO support for NASL scripts through a wrapper that takes the
> message text calls and generates POT files for them in the
> openvasl-plugins's po/ (or intln/) directory that translators can work
> with.

yes, this is a working option. However, I thought I would be
nice to add a _("") integrated function to NASL and call gettext from it
with the textdomain set to whatever is configured.
Thus, openvasd would automatically deliver the translated strings
to the client (or to log files) without more complexity than 5-10 lines of
code calling gettext in a proper way.

> - Separately, have the PO files be distributed by a separate
> openvas-plugins-XX package (with XX the language code). That package
> installs the proper /usr/share/openvas just like you provide
> openvas-plugins packages that installs the appropiate MO files for a
> given gettext domain (say 'openvas-plugins') at its proper location
> under  /usr/share/locale/XX/LC_MESSAGES/OpenVAS-plugins.mo (with XX
> the language code)

or it comes with the feed.
And we need some concept to have trusted (signed) translations
like we currently have for the NASL scripts.

> - Since the gettext domain would be different (different MO files)
> have the client change its gettext domain when parsing NASL input, so
> that it gets translated (you can see a way to do this in Squirrel's
> Mail plugins at http://www.squirrelmail.org/wiki/HelpTranslating,
> basically the OpenvAS client would have to swith to the
> 'OpenVAS-plugins' gettext domain when generating its output associated
> with the NASL info and then switch back to its own gettext domain
> after it.

I fear that it will get a update/maintenance problem when trying to
have the po files at the client. Shouldn't the translations be where the
original text is?

> It might sound complicated, but to me it looks easier to do than the
> other approach (server side) which involves introducing gettext in the
> server and change the Nessus protocol so that client can provide it's
> language environment to the server.

hm, without having really tried it, I think it should be only few lines
of code on the server side to apply a specific text domain.
Maybe I should simply try to see whether I can proove myself
wrong ;-)

Best

        Jan
-- 
Dr. Jan-Oliver Wagner                                   Intevation GmbH
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to