[tor-commits] r24818: {translation} updated info about bridgedb and wrote about how to validate (translation/trunk/documentation)

[Runa Sandvik <runa.sandvik@xxxxxxxxx>]

Author: runa
Date: 2011-06-10 09:52:32 +0000 (Fri, 10 Jun 2011)
New Revision: 24818

Modified:
   translation/trunk/documentation/howto.txt
Log:
updated info about bridgedb and wrote about how to validate translations

Modified: translation/trunk/documentation/howto.txt
===================================================================
--- translation/trunk/documentation/howto.txt	2011-06-09 18:12:20 UTC (rev 24817)
+++ translation/trunk/documentation/howto.txt	2011-06-10 09:52:32 UTC (rev 24818)
@@ -148,7 +148,8 @@
 
        By default, this command will check if the modification time of
        your local files is more recent than that on the Transifex server
-       and will not overwrite newer files. Use --help for more
+       and will not overwrite newer files. You can also use '-f -a' to
+       force the fetching of all translations. Use --help for more
        information.
        
 All projects:
@@ -161,15 +162,35 @@
 
        To pull new translations from the server, cd to the 'po'
        directory and run 'tx pull'. Remember to commit the changes to
-       SVN.
+       SVN or Git.
 
-    2. Adding New Translation Resources to Transifex
+    2. Validating the input
 
+       Transifex does not validate (that is, look for malicious
+       characters in translated strings) the translations. It is
+       important that you do this for your project before you include
+       new/updated translations.
+
+       The script validate.py in translation/trunk/tools compares the
+       English strings against the translated strings, and emit a
+       warning whenever a translated string is using more symbols than
+       the English string. And then it's up to whoever is running this script
+       to review the warnings and figure out if there is anything to be
+       concerned about.
+
+       Below is an example on how you can run the script (the line
+       assumes you are inside the po directory of whatever project you
+       wish to validate translations for):
+
+       $  for i in */*.po ; do python /path/to/validate.py -i $i -l validate.py ; done       
+
+    3. Adding New Translation Resources to Transifex
+
        To add new translation resources to Transifex, open up
        'po/.tx/config' and create entries for the new resources. Use an
        existing entry as a template. Remember to commit the file.
 
-    3. Pushing Files to the Transifex Server
+    4. Pushing Files to the Transifex Server
 
        To push new/updated source files or translations to the Transifex
        server, cd to the 'po' directory and run 'tx push' with either
@@ -192,6 +213,13 @@
 
 BridgeDB:
 
+    The translation template (and some translations) can be found here:
+    https://gitweb.torproject.org/bridgedb.git
+
+    NOTE: We do not yet have a Transifex config file for BridgeDB, which
+    means that we cannot pull new and updated translations from the
+    server. See #2891 for more information.
+
     1. Updating the Translations
 
        After pulling new translations from Transifex and checking them into

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits