2008/4/30 Jan-Oliver Wagner <[EMAIL PROTECTED]>:
> Hi,
>
> I once again stumbled across problems caused by the mutlilingual
> features of OpenVAS server (as inherited by Nessus).
>
> I wonder whether it makes sense at all to have the NASL scripts allow
> for other languages than english. IMHO this adds only unnecessary source 
> codes,
> user confusion, extra-time writing NASL scripts and potentials for 
> inconsistencies.
> Not to forget the maintenance problem!

Ok. My opinion: everything should be translated as much as possible,
with mechanisms to guarantee that:

a- translations are consistent with the text being tranlsated (this is
easy to do the first time, but more difficult to do when
the original text changes)
b- when translations are not consistent they are not used (i.e. not
presented to the user)

I can assure you that if OpenVAS provided a way to properly i18nize
the NASL scripts there would be people eager to use it. Some technical
people use vulnerability scans to generate reports that they later
have to translate to their mother language (hopefully after including
additional info) to upper management. Actually, I think I saw once a
Nessus translated into Spanish that a company intented to (illegally)
sell it without contributing the translations to the community (even
if the NASL scripts where GPLd).

The problem with the current i18n features with the NASL scripts is
that they cannot guarantee a) or b) like you can currently do with,
for example, gettext (PO files). The translations are included in the
script and there's no way to know that a translation has to be updated
because the original (english) description changed.

I think that the NASL scripts information in english should be
converted into PO content that the GUI or server would read to present
to the user (if translated) information in the reports (be it the GUI
or printed reports) in their native language. It wouldn't be difficult
to provide a conversion from NASL descriptions and informative texts
to gettext, to make translations easy. It would be slightly more
difficult to change the GUI (not the server) to use those translations
if available.

I do agree that the common technical language will always be (and will
still be) english. But there are many countries in which english is,
and will still be, a barrier which hinders use of certain
technologies.

Just my 2 c


Regards

Javier
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to