Updated string

[gosa.git] / gosa-core / README

diff --git a/gosa-core/README b/gosa-core/README
index c24df4c24fb9df2127b4da72a5e5d80fe8e4ed2c..21f670f34b93389afec819e2605ccde0f15c01e8 100644 (file)
--- a/gosa-core/README
+++ b/gosa-core/README
@@ -20,19 +20,21 @@ GOsa infrastructure howto is work in progress and not released yet.
 * Translations
 
 GOsa is not available in your native language? Just take the message.po
 * 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
+file out of the locales/core directory and put your translations into the

 msgstr fields. 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.
 msgstr fields. 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.

-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,
+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,
 then just send the .po file to me.
 
 that the specific locale will be generated (via dpkg-reconfigure locales).
 
 You may want your translations to be included in the main GOsa repository,
 then just send the .po file to me.
 

+Run update-gosa after you've added translations in order to let GOsa
+compile and re-sync the translations.
+

 
 * NOTES
 
 
 * NOTES