bug fix #1135, show more is usable again

[friendica.git] / util / README

diff --git a/util/README b/util/README
index cb2fd9b55b7e72a4232fadc8c4e01308465348be..aceade3e235965c670343f83e84e372b5da97f16 100644 (file)
--- a/util/README
+++ b/util/README
@@ -81,6 +81,11 @@ Xgettext and .po workflow
 1. Run util/run_xgettext.sh script (on *unix sistems, with GNU xgettext installed)
        This script runs xgettext on source tree, extracting strings from t() and tt()
        functions, and creates a util/messages.po file.
+
+       % cd util; ./run_xgettext.sh ../view/{language}/messages.po
+
+       Replace {language} with the language you are working on - e.g. 'es', 'fr', 'de', etc. 
+
 2. copy util/messages.po to view/<langauage>/messages.po
 3. open view/<langauage>/messages.po with a text editor and fill in infos in
        "Last-Translator: FULL NAME <EMAIL@ADDRESS>"
@@ -106,11 +111,11 @@ Xgettext and .po workflow
        to create the strings.php file
        
 When strings are added or modified in source, you could run
-       $ util/run_xgettext.sh view/<language>/messages.po
-       to extraxt strings from source files and join them with the existing .po file:
+       $ cd util; ./run_xgettext.sh ../view/<language>/messages.po
+       to extract strings from source files and join them with the existing .po file:
        new strings are added, the existing are not overwritten.
        
-If you already translated Friendika using strings.php, you could import your old
+If you already translated Friendica using strings.php, you could import your old
 translation to messages.po. Run:
 $ php util/php2po.php view/<language>/strings.php