Vincent Renardias wrote:
> I see the following pros:
> - only 1 translation file per language for all the plugins. Thus making
> the translators' work much easier: only one file to edit instead of ~900
> nasl files.
This really depends in a big way on how the translation will be
done. If you're going to have one translator, fine - this makes
sense. If, on the other hand, you are going to have a community
of 20 or 30 translators/script writers, then this becomes a major
headache. Not to mention - having one file introduces at least
one other major problem: script writers that decide to re-use
"string"s across NASL scripts - that would be a disaster from a
long term perspective.
IMHO, I don't think this would be the right way to go given the
distributed nature of the NASL script contributions.
Thomas
