aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorredmatrix <git@macgirvin.com>2016-01-08 06:44:29 +1100
committerredmatrix <git@macgirvin.com>2016-01-08 06:44:29 +1100
commit00b98730f7c05804fe0f4ce3e0dff08af16dfc00 (patch)
tree5eb5b244c0ff7423696255866d75ba67b2a0198a
parent761afd029d97703f2f7609d546b7b5f3d257c601 (diff)
parent242da95eed745d274d03887d50793f7bfa593409 (diff)
downloadvolse-hubzilla-00b98730f7c05804fe0f4ce3e0dff08af16dfc00.tar.gz
volse-hubzilla-00b98730f7c05804fe0f4ce3e0dff08af16dfc00.tar.bz2
volse-hubzilla-00b98730f7c05804fe0f4ce3e0dff08af16dfc00.zip
Merge pull request #250 from wave72/master
In Hubzilla messages.po is hmessages.po
-rw-r--r--doc/Translations.md40
1 files changed, 20 insertions, 20 deletions
diff --git a/doc/Translations.md b/doc/Translations.md
index d0fe489f3..226fa2e1a 100644
--- a/doc/Translations.md
+++ b/doc/Translations.md
@@ -4,13 +4,13 @@ Translating the $Projectname
Translation Process
-------------------
-The strings used in the UI of Red is translated at [Transifex][1] and then
+The strings used in the UI of Hubzilla is translated at [Transifex][1] and then
included in the git repository at github. If you want to help with translation
-for any language, be it correcting terms or translating Red to a
+for any language, be it correcting terms or translating Hubzilla to a
currently not supported language, please register an account at transifex.com
-and contact the Red translation team there.
+and contact the Redmatrix translation team there.
-Translating Red is simple. Just use the online tool at transifex. If you
+Translating Hubzilla is simple. Just use the online tool at transifex. If you
don't want to deal with git & co. that is fine, we check the status of the
translations regularly and import them into the source tree at github so that
others can use them.
@@ -26,32 +26,32 @@ tree.
If you want to get your work into the source tree yourself, feel free to do so
and contact us with and question that arises. The process is simple and
-Red ships with all the tools necessary.
+Hubzilla ships with all the tools necessary.
The location of the translated files in the source tree is
/view/LNG-CODE/
where LNG-CODE is the language code used, e.g. de for German or fr for French.
For the email templates (the *.tpl files) just place them into the directory
-and you are done. The translated strings come as a "messages.po" file from
-transifex which needs to be translated into the PHP file Red uses. To do
+and you are done. The translated strings come as a "hmessages.po" file from
+transifex which needs to be translated into the PHP file Hubzilla uses. To do
so, place the file in the directory mentioned above and use the "po2php"
-utility from the util directory of your Red installation.
+utility from the util directory of your Hubzilla installation.
Assuming you want to convert the German localization which is placed in
-view/de/messages.po you would do the following.
+view/de/hmessages.po you would do the following.
1. Navigate at the command prompt to the base directory of your
- Red installation
+ Hubzilla installation
2. Execute the po2php script, which will place the translation
- in the strings.php file that is used by Red.
+ in the hstrings.php file that is used by Hubzilla.
- $> php util/po2php.php view/de/messages.po
+ $> php util/po2php.php view/de/hmessages.po
- The output of the script will be placed at view/de/strings.php where
+ The output of the script will be placed at view/de/hstrings.php where
froemdoca os expecting it, so you can test your translation mmediately.
-3. Visit your Red page to check if it still works in the language you
+3. Visit your Hubzilla page to check if it still works in the language you
just translated. If not try to find the error, most likely PHP will give
you a hint in the log/warnings.about the error.
@@ -59,19 +59,19 @@ view/de/messages.po you would do the following.
not give any output if the file is ok but might give a hint for
searching the bug in the file.
- $> php view/de/strings.php
+ $> php view/de/hstrings.php
4. commit the two files with a meaningful commit message to your git
- repository, push it to your fork of the Red repository at github and
+ repository, push it to your fork of the Hubzilla repository at github and
issue a pull request for that commit.
Utilities
---------
Additional to the po2php script there are some more utilities for translation
-in the "util" directory of the Red source tree. If you only want to
-translate Red into another language you wont need any of these tools most
-likely but it gives you an idea how the translation process of Red
+in the "util" directory of the Hubzilla source tree. If you only want to
+translate Hubzilla into another language you wont need any of these tools most
+likely but it gives you an idea how the translation process of Hubzilla
works.
For further information see the utils/README file.
@@ -79,7 +79,7 @@ For further information see the utils/README file.
Known Problems
--------------
-* Red uses the language setting of the visitors browser to determain the
+* Hubzilla uses the language setting of the visitors browser to determain the
language for the UI. Most of the time this works, but there are some known
quirks.
* the early translations are based on the friendica translations, if you