![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
diff --git a/gosa-core/README b/gosa-core/README
index 8508057a08d07db5a2b456c012501e61db3353ee..3d1b0cf193865b9fcaf6049b5a88521b8dfafe29 100644 (file)
--- a/gosa-core/README
+++ b/gosa-core/README
-GOsa2.1 README
-==============
+GOsa 2.6 README
+===============
* Information
* Information
* Translations
* Translations
-GOsa is not available in your native language? Just take the message.po
-file out of the locales directory and put your translations into the
-msgstr fields. You may look at the de/LC_MESSAGES for the way how it
+GOsa is not available in your native language? Just read on...
+
+Translations (or I18N) in GOsa is done by the gettext library. As a
+result, every set of translations is stored inside of one directory
+per language as a text file called "messages.po".
+
+For GOsa you've to differenciate between gosa-core and single
+gosa-plugins. The core as a translation and every plugin has a seperate
+translation, too.
+
+GOsa core can be translated by taking a look at the locales/core
+directory. Just take the messages.po file and copy it to some other
+location and put your translations into the msgstr fields of this
+file. For more comfort, use programs like i.e. kbabel or poedit to
+achieve this. You may look at the de/LC_MESSAGES for the way how it
works.
If you're ready with that, create a directory for your language using
the ISO shortcuts (i.e. es for spain) with a subdirectory LC_MESSAGES.
works.
If you're ready with that, create a directory for your language using
the ISO shortcuts (i.e. es for spain) with a subdirectory LC_MESSAGES.
-Put your messages.po in there and run "msgfmt messages.po" from that
-directory. Make sure your apache has locale support or, in case of debian,
-that the specific locale will be generated (via dpkg-reconfigure locales).
+In case of spain this will be
+
+ gosa-core/locales/core/es/LC_MESSAGES
+
+and put the freshly translated messages.po in this directory.
+
+To test this, you've deploy the messages.po file in your running copy
+of GOsa and run the "update-gosa" command, to let GOsa merge the
+translations. Then, Make sure your apache has locale support or, in case
+of debian, that the specific locale will be generated (via dpkg-reconfigure
+locales).
You may want your translations to be included in the main GOsa repository,
You may want your translations to be included in the main GOsa repository,
-then just send the .po file to me.
+then just send the .po file to me or ask for SVN access.
+For gosa-plugins, every plugin has a locales directory. Translation works
+like described for gosa-core.
-* NOTES
+Always run update-gosa after you've added translations in order to let GOsa
+compile and re-sync the translations.
-You'll need php-cups (http://www.cups.org) and php-krb5 (pear) in order
-to get full functionality. To make shared folders work in a proper way,
-you either need a recent PHP or a patched one for the get_acl functions
-(see contrib/patches). Basically GOsa will run without these.
+
+* NOTES
Be sure that 'gosaUserTemplates' are not able to log into your server,
since they may have no password set. Example configs can be found in
Be sure that 'gosaUserTemplates' are not able to log into your server,
since they may have no password set. Example configs can be found in