On Thu, May 02, 2002 at 06:28:22PM +0200, Vincent Renardias wrote:
> 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.
We could imagine includes...
> Why are very few nessus plugins translated (except those written by Renaud
> which have a French translation) ?
^^^^^^^^^^^^^^^^^^
Not true any more. I don't even translate plugins in my
own language, there's too much overhead involved.
> - Because the current system is a real pain:
> - Translators have to edit hundreds of files.
That will still be the case. Putting all the translations in _one_ file
goes against the plugin paradigm.
> - 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...)
I agree with that.
> Spliting data in as many items as possible will not change this IMHO
> and most plugins will remain in english only.
I think it will help the use of gettext on this data. Dynamic strings
won't be dynamic any more (just preformated, as in : "the remote host is
exporting the following filesystems : %s")
> Unless the work of translators is made easier, I fear the situation will
> not improve :(
There's also a lack of motivation. While some people are interested in
translations, most of the Nessus user community focuses (I hope) on _security_
not on fancyness.
-- Renaud
