Hi,

thanks so far for the opinions on the language question.

I agree that the current i18n support is a broken by design
and we should better think to apply the standard gettext
tools and methods.

On Mittwoch, 30. April 2008, Javier Fernandez-Sanguino wrote:
> 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.

That would be true with the gettext approach.

> 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 more tend to a concept where the po stuff of the NASL scripts
is handled on the server side. One the one hand it would allow a
better consistency. On  the other hand it would be easier to maintain
because the release cycle of the Client(s) are different from the Server
and especially different from the plugins. It might even be an option to
distribute po files via the feed service, but a simple solution should
be followed first to learn about the actual needs.

However, a core question is: Is it OK to work on the translation inside
a po text file (or a tool that allows for ellegant work on it) instead
of working on the translations right in the NASL code?
My personal answer is yes, but there may be good reasons whether
po files are not good?

In case we decide on going the po way, I think it would be relatively
easy to build gettext support into NASL and handle the textdomains for
the NASL scripts in openvasd.
The only problems I see is that we break compatibility (we will sooner
or later have to anyway) and that I do know whether using gettext
would lower performance of openvasd. For the latter I don't really
expect it, because the current handling will be dropped - only measurements
will really give an answer I guess. Hm, a I think about it, the gettext
way might be even faster than the NASL interpreter string handling.

Opinions?

Best

        Jan

-- 
Dr. Jan-Oliver Wagner                        Intevation GmbH, Osnabrück
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