$Id: README,v 1.4 2005/04/26 07:58:29 jan Exp $
Copyright (C) 2004 Intevation GmbH
Author: Jan-Oliver Wagner <jan@intevation.de>


Nessus Message Translations
===========================

Updating the message catalogs currently only works on unix-like systems
and requires xgettext 0.14.
There are two so-called text domains, one is 'nessus' which is the
client and for which the processing works mostly automatic.
Ther other one is 'nessus-scripts' which are the administration
shell-script for the Nessus Server.

Nessus Client (text domain 'nessus')
------------------------------------

 - When the nessus sources were edited so that e.g. messages have been
   changed or added, run

     $ make nessus.pot-update

   to update the nessus.pot file. You also need to do this after a fresh
   CVS checkout to build nessus.pot

 - To merge the changes in the .pot file with the messages already in the
   .po files, run

     $ make update-po

   This also forces a rebuild of nessus.pot.

   Repeat this command after you changed the po file to see whether
   you treated all untranslated or fuzzy elements.

 - When the translations in the po files have been changed, run

     $ make

   to generate new .gmo files

 - For installation, run

     $ make install

   which will copy the files typically to something like
   $prefix/share/locale/de/LC_MESSAGES/  (for a german translation)


 - Note, that

     $ make dist

   does not work!
   This would require either adaption of the Makefile
   in this directory to the dist mechanism of the parent directory
   or vice versa.

Editing the .po file -- IMPORTANT
---------------------------------

    Please note that the file de.po is UTF8 encoded. Thus
    if you eg. use vim as text editor, make sure you "set encoding=utf8".
    NOTE, that the file  nessus-scripts-de.po in contrast is
    encoded in latin1!

Nessus Admin Scripts (text domain 'nessus-scripts')
---------------------------------------------------

Unfortunetly, for shell scripts the updating process does
not work automatically. Even the initial preparation was
largly handcrafted after these steps did some automatic
extraction (sample for adduser):
xgettext -d nessus-scripts -s -o nessus-scripts.pot -L Shell nessus-adduser.in
msginit -l de_DE -o nessus-scripts-de.po -i nessus-scrits.pot

To just install the german translation (this will automatically
create the gmo file):

	$ make install-nessus-scripts
