So you've installed IPCop and love it, but it doesn't speak your language. How can you help?
IPCop needs folks that speak something other than English to do translations. Getting the installation and the run time code to produce data in another language is relatively easy.
Check the How to Help the IPCOP Translation Effort page.
Contact the Documentation/Translation coordinator and let them know the language you are prepared to tackle. This way you can find out if someone is already working to on the translation. If someone is, you may be able to contact them and help.
Obtain the two language dependent files from the IPCop CVS repository, see the CVS section below. The files are in the ipcop project. The English versions of the files are lang_en.c and en.pl. Remember to select the current 0.1 source branch. The files don't exist under the 0.2 branch, yet.
Translate the files to your desired language. You may want to reference Eric Oberlander's excellent IPCop Translations web site for a comparison table of phrases in all currently available languages.
Return the files to the documentaton coordinator for check in to CVS.
Translating the rest of the documentation is a bigger task. Historically, teams of translators have been formed to handle this task. If desired, the language team leaders will be designated as developers with the ability to check files into CVS.
To attack the document translation, you may want to become familiar with DocBook. Please skim the material on it, below.
You might be able to translate successfully just by translating the text between the pairs of <title> and </title>, and <para> and </para> elements. Please check out the files under the IPCopDoc CVS project to do your translations.