On Thu, 2 May 2002, Renaud Deraison wrote:
> On Tue, Apr 30, 2002 at 10:49:14PM +0200, Hugo van der Kooij wrote:
>
> > I would like to know if full internationalization is part of the plans for
> > v1.3 (Renaud?)
>
> Plans for 1.3 are the re-design of NASL plugins (as discussed on the
> -devel list). Mostly it means that plugins will all be coded in XML
> (or XML-like), and data will be split in as many items as possible.
I fully support the idea to have a new format easier to parse, but having
the translations in the same file as the code has always been a pain in
the ass in my experience. I sincerely hope Nessus won't use this solution.
Ever wondered why most free softwares (GNOME, KDE, GNU utils, etc) are
translated in several dozains of languages ?
- Because it's very easy to do so, even for a unique translator, who DOES
NOT have to understand the code, since the string translations are in a
dedicated file.
Why are very few nessus plugins translated (except those written by Renaud
which have a French translation) ?
- Because the current system is a real pain:
- Translators have to edit hundreds of files.
- They have to hunt for string updates when the plugins are updated.
- They need to understand nasl syntax to integrate their work (ok, it's
easy to understand, but still many translators are not coders...)
Spliting data in as many items as possible will not change this IMHO
and most plugins will remain in english only.
Unless the work of translators is made easier, I fear the situation will
not improve :(
On the other hand, GNU gettext can work on data extracted from an XML
file, so both solutions could be used.
> So international support will be easier. For now, plans for translation
> are frozen.
--
Vincent RENARDIAS
Directeur Technique
StrongHoldNET / http://www.strongholdnet.com
