[Bf-translations-svn] SVN commit: /data/svn/bf-translations [74] trunk/po/README.txt: Updated Readme.txt.

[bf-translations at blender.org]

Revision: 74
          http://projects.blender.org/scm/viewvc.php?view=rev&root=bf-translations&revision=74
Author:   mont29
Date:     2011-10-14 20:39:17 +0000 (Fri, 14 Oct 2011)
Log Message:
-----------
Updated Readme.txt. But anyway, the whole scripts stuff needs to be refactored, to get a better, more rational set of tools! Will give it a try in the next days.

Modified Paths:
--------------
    trunk/po/README.txt

Modified: trunk/po/README.txt
===================================================================
--- trunk/po/README.txt	2011-10-14 19:24:14 UTC (rev 73)
+++ trunk/po/README.txt	2011-10-14 20:39:17 UTC (rev 74)
@@ -1,6 +1,10 @@
 Blender translation HOWTO
 =========================
 
+*** XXX All this is a bit fuzzy, since we moved to bf-translations. I’ll try to make it more
+        rational in next days (merge some scripts doing basically the same thing, make work
+        update_msg/update_pot from that new dir, etc.). --mont29 ***
+
 I'll try briefly explain how translation works and how to update translation files.
 
 1. How it works
@@ -16,7 +20,7 @@
 and so it'll be displayed on the screen as "translation for this message".
 Pretty simple.
 
-This source files are pre-compiled into ../relese/bin/.blender/locale/<language>/LC_MESSAGES/blender.mo,
+This source files are pre-compiled into ../release/bin/.blender/locale/<language>/LC_MESSAGES/blender.mo,
 so they aren't getting compiled every time Blender is compiling to same some time and prevent
 failure on systems which doesn't have needed tools for compiling .po files.
 
@@ -32,7 +36,7 @@
 msgstr "translation for this message"
 
 it means translation used to exist for this message, but message was changed, so translation
-also have to be updated (it's easier to make new translation based on previos translation).
+also have to be updated (it's easier to make new translation based on previous translation).
 When translation was updated, remove line with '#, fuzzy' and it'll work.
 
 If there's no message in .po file you want to translate, probably .po file should be updated.
@@ -42,11 +46,11 @@
   to update messages.txt file (this file contains strings collected
   automatically from RNA system and python UI scripts)
 - Run update_pot.py script which will update blender.pot file. This file contains all
-  strings which should be transated.
+  strings which should be translated.
 - Run update_po.py script to merge all .po files with blender.pot (so all .po files
   will contain all msgid-s declared in blender.pot) or update_po.py <language> to
   update only needed .po file(s) to save time when you're busy with translation.
-  But before ocmmit all .po files better be updated.
+  But before commit all .po files better be updated.
 
 When you've finished with translation, you should re-compile .po file into .mo file.
 It's also pretty simple: just run update_mo.py script to recompile all languages or
@@ -74,8 +78,18 @@
 4. Other scripts
 ----------------
 
-- check_po.py: this script checks if all messages declared in blender.pot exists in.po files
+- check_po.py: this script checks if all messages declared in blender.pot exists in .po files
                and that no extra messages are declared in .po files
 - clean_po.py: this script removes all commented messages which aren't required by .pot file anymore.
-- merge_po.py: this scripts accepts two files as arguments and copies translations from second file
+- merge_po.py: this script accepts two files as arguments and copies translations from second file
                into first file.
+- branches_update_po.py: This script updates all (or a subset given by command line args) .po
+                         files under /branches.
+- branches_check_po.py: This script checks all (or a subset given by command line args) .po files
+                        under /branches, reporting missing/unneeded messages.
+- branches_clean_po.py: This script removes all unneeded commented messages in all (or a subset
+                        given by command line args) .po under /branches.
+- branches_check_progress.py: This script makes some quick and raw stats about progress in all
+                              (or a subset given by command line args) .po under /branches.
+- import_po_from_branches.py: This script imports all .po that are advanced enough (default value
+                              is 80%, can be set by opt command arg) from /branches into /trunk/po.