Some more small documentation stuff

[friendica.git] / util / README

diff --git a/util/README b/util/README
index b8fd7c9ee7bfdeb461f0c13918a9d5ba8549f316..fad1270d473275f1fdb0abcd4776a98fb50244e7 100644 (file)
--- a/util/README
+++ b/util/README
@@ -10,7 +10,7 @@ Internationalisation
 
 extract.php - extracts translatable strings from our project files. It 
 currently doesn't pick up strings in other libraries we might be using such as 
-tinymce, simplepie, and the HTML parsers.
+tinymce and the HTML parsers.
 
 In order for extract to do its job, every use of the t() translation function 
 must be preceded by one space. The string also can not contain parentheses. If
@@ -82,11 +82,11 @@ Xgettext and .po workflow
        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. 
+       $ cd util; ./run_xgettext.sh 
 
 2. copy util/messages.po to view/<langauage>/messages.po
+       Replace <language> with the language you are working on - e.g. 'es', 'fr', 'de', etc. 
+
 3. open view/<langauage>/messages.po with a text editor and fill in infos in
        "Last-Translator: FULL NAME <EMAIL@ADDRESS>"
        "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -115,7 +115,7 @@ When strings are added or modified in source, you could run
        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