2008/5/6 Jan-Oliver Wagner <[EMAIL PROTECTED]>: > Opinions? Even though client and server releases are different I don't suggest bundling the PO files with the openvasd release and have the server handle gettext translations. For several reasons:
- the NASL code is actually in the openvas-plugins package, not in the server - it adds complexity to the server for a task unrelated to vulnerability scanning - you (probably?) have to modify the Nessus client-server protocol so that the client can provide the server its language settings (the client knows the settings based on the user's environment). I suggest taking this approach instead: - adding PO support for NASL scripts through a wrapper that takes the message text calls and generates POT files for them in the openvasl-plugins's po/ (or intln/) directory that translators can work with. - Separately, have the PO files be distributed by a separate openvas-plugins-XX package (with XX the language code). That package installs the proper /usr/share/openvas just like you provide openvas-plugins packages that installs the appropiate MO files for a given gettext domain (say 'openvas-plugins') at its proper location under /usr/share/locale/XX/LC_MESSAGES/OpenVAS-plugins.mo (with XX the language code) - Since the gettext domain would be different (different MO files) have the client change its gettext domain when parsing NASL input, so that it gets translated (you can see a way to do this in Squirrel's Mail plugins at http://www.squirrelmail.org/wiki/HelpTranslating, basically the OpenvAS client would have to swith to the 'OpenVAS-plugins' gettext domain when generating its output associated with the NASL info and then switch back to its own gettext domain after it. It might sound complicated, but to me it looks easier to do than the other approach (server side) which involves introducing gettext in the server and change the Nessus protocol so that client can provide it's language environment to the server. Regards Javier _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
