X-Git-Url: https://main.carlh.net/gitweb/?a=blobdiff_plain;f=TRANSLATORS;h=b8c4c4004ecf91caf9e1a008893345cafe8537d7;hb=refs%2Ftags%2F5.4;hp=684b632af5a8b3f1adf162abd998f85bb269cb4a;hpb=9a4948b087345756857e68e9a717445e4b515f18;p=ardour.git

diff --git a/TRANSLATORS b/TRANSLATORS
index 684b632af5..b8c4c4004e 100644
--- a/TRANSLATORS
+++ b/TRANSLATORS
@@ -19,10 +19,10 @@ libs/ardour/po/ru.po
 There are few supplementation translations that can be found here (again,
 showing the case for Russian):
 
-libs/gtk2mmext/po/ru.po
+libs/gtkmm2ext/po/ru.po
 
 Every PO file's name is a two-character code, e.g. 'de' for German, 'es' for
-Spanish and so on. However it's fairly common to have localizations for local
+Spanish, and so on. However it's fairly common to have localizations for local
 versions of a language, e.g. 'pt_BR' would stand for Brazilian Portuguese, and
 'es_MX' would stand for Mexican Spanish. Please refer to ISO language code
 table for details.
@@ -30,22 +30,47 @@ table for details.
 Here is the best workflow for existing translations.
 
 1. Build Ardour  using './waf' command (this step is actually optional).
+
 2a. If there is no existing translation for your language, run './waf i18n_pot'
 which will generate a POT (.pot) file for each of the directories shown
-above. For each directory you plan to translate, rename the POT file to end in .po and then
-continue with step 3.
+above. For each directory you plan to translate, rename the POT file to end in 
+.po and then continue with step 3.
+
 2b. If there is an existing translation for your language, run './waf
-i18n_pot' which will bring it up to date (along with all other PO files)
+i18n_po' which will bring it up to date (along with all other PO files)
+
 3. Open the relevant PO file in you PO editor of choice (see below).
-4. Open Ardour, find something untranslated, locate this phrase in PO file, translate.
+
+4. Open Ardour, find something untranslated, locate this phrase in PO file, 
+translate.
+
 5. Repeat previous step several times, save the PO file.
-6. Run './waf i18n_mo' to regenerate binary MO files and 'sudo ./waf install' to install them.
-7. Restart Ardour to see what your translation looks like and whether it needs fixes, e.g. has to be shorter.
 
-Note that as of Ardour 3 beta 1 the translations are only installed when you
-run './waf i18n' after './waf' and before 'sudo ./waf install'.
+6. Run './waf i18n_mo' to regenerate binary MO files and 'sudo ./waf install' 
+to install them.
+
+7. Restart Ardour to see what your translation looks like and whether it needs 
+fixes, e.g. has to be shorter.
+
+Note that as of Ardour 4 the translations are only installed when you run 
+'./waf i18n' after './waf' and before 'sudo ./waf install'.
+
+When you are done translating, it's best to get credited for your contribution. 
+Here is how you can do it:
+
+1. Run 'git commit -a' (assuming you only modified translation files) and 
+describe the changes you made. Typically the commit message looks like 
+'Update German translation'. That should be sufficient.
+
+2. Run 'git format-patch origin/master' (assuming you worked on a clone of the 
+master branch. That should generate a file called something like 
+'0001-Update-German-translation.patch'.
+
+3. Run 'bzip2 0001-Update-German-translation.patch' to compress the file.
 
-When you are done, save the file and submit it to the tracker.
+4. File a new bug report at http://tracker.ardour.org and attach the resulted 
+compressed file and tell either rgareus (Robin Gareus) or las (Paul Davis) on 
+the project's IRC channel (#ardour at irc.freenode.net) about your patch.
 
 There are some more things you need to know.