This document describes the steps for a new language:

Translate the string which are embedded into perl:
--------------------------------------------------

1. create a new directory src/common/lib/locale/xy_XY
2. copy the Makefile from es_ES, de_DE or any other language to xy_XY and fix it
3. add the language to src/common/lib/locale/Makefile
4. copy src/common/locale/openca.pot and src/common/locale/openca-html.pot to src/common/locale/xy_XY
5. tranlate openca.po and openca-html.po
6. compile openca.po and openca-html.po with msgfmt 

Notice: strings like __FILE__ must be present in the translations too
        because they are dynamically replaced by OpenCA - yes, they
        are placeholders for variables :)

Translate the javascript-code:
------------------------------

1. create a new directory src/common/lib/javascript/xy_XY/
2. copy all files from src/common/lib/javascript/C/ to xy_XY
3. translate the files

Translate the configuration-files:
----------------------------------

1. create the new directories src/web-interfaces/*/i18n/xy_XY
2. copy the configfile *.conf.in from src/web-interfaces/*/i18n/C/ to xy_XY
3. translate the configurationfile
4. add the language to src/web-interfaces/*/i18n/Makefile

Fix configure.in
----------------

1. check for internationalized files (e.g. search for files with *fr_FR*)
2. add your language files
3. run autoconf to check the correctness of your configure.in

The modules are actually not integrated into OpenCA's internationalization
because several other users use our modules and they are not ready for
internationalization.

Any comments and translations are welcome.

Michael Bell <michael.bell@web.de>
2003-Apr-29
