[or-cvs] r15609: linewrap/whitespace fixes (tor/trunk/doc)

[arma at seul.org]

Author: arma
Date: 2008-07-02 17:10:13 -0400 (Wed, 02 Jul 2008)
New Revision: 15609

Modified:
   tor/trunk/doc/translations.txt
Log:
linewrap/whitespace fixes


Modified: tor/trunk/doc/translations.txt
===================================================================
--- tor/trunk/doc/translations.txt	2008-07-02 21:06:18 UTC (rev 15608)
+++ tor/trunk/doc/translations.txt	2008-07-02 21:10:13 UTC (rev 15609)
@@ -1,4 +1,5 @@
-##      Instructions for helping translate text for Vidalia, TorButton and TorCheck
+##      Instructions for helping translate text for Vidalia, TorButton
+##      and TorCheck
 ##  ( More translation information for Tor related apps will accumulate here )
 
 Our translations are handled in one of two places. The Tor Translation Portal
@@ -12,7 +13,8 @@
     htdigest -c passwd.tmp "Tor subversion repository" USERNAME
 
 
-All three of the above projects check in their respective .po files into the following subversion urls:
+All three of the above projects check in their respective .po files into
+the following subversion urls:
 
     https://tor-svn.freehaven.net/svn/translation/trunk/projects/torbutton
     https://tor-svn.freehaven.net/svn/translation/trunk/projects/torcheck
@@ -21,12 +23,12 @@
 The current pootle configuration is checked into subversion as well:
 
     https://tor-svn.freehaven.net/svn/translation/trunk/pootle
-    
-TorCheck uses our translation portal to accept translations. Users use the portal to check in their changes.
-To make use of the translations that users have commited to the translations/
-subversion module, you'll need to ensure that you have a current checked out
-copy of TorCheck:
-    
+
+TorCheck uses our translation portal to accept translations. Users use
+the portal to check in their changes.  To make use of the translations
+that users have commited to the translations/ subversion module, you'll
+need to ensure that you have a current checked out copy of TorCheck:
+
     cd check/trunk/i18n/
     check/trunk/i18n$ svn up
 
@@ -36,7 +38,7 @@
     External at revision 15300.
 
     At revision 15300.
- 
+
 Now if you had changes, you'd simply want to move the newly updated .po files
 into the current stable directory.  Moving the .po files from
 'check/trunk/i18n/pootle/' into 'check/trunk/i18n' properly naming the files
@@ -47,12 +49,12 @@
 
     cd check/trunk/i18n/
     for locale in `ls -1 pootle/|grep -v template`;
-    do 
+    do
     mv -v pootle/$locale/TorCheck_$locale.po TorCheck_$locale.po;
     done
 
 Now check the differences (ensure the output looks reasonable):
-    
+
     svn diff
 
 Ensure that msgfmt has no errors:
@@ -63,12 +65,13 @@
 
     svn commit
 
-Torbutton uses our translation portal to accept translations. Users use the portal to check in their changes.
+Torbutton uses our translation portal to accept translations. Users use
+the portal to check in their changes.
 To make use of the translations that users have commited to the translations/
 subversion module, you'll need to ensure that you have a current checked out
 copy of Torbutton:
-    
-    cd torbutton/trans_tools 
+
+    cd torbutton/trans_tools
     torbutton/trans_tools$ svn up
 
 You should see something like the following:
@@ -77,25 +80,26 @@
     External at revision 15300.
 
     At revision 15300.
- 
-Now if you had changes, you need to convert from .po and move the newly updated mozilla files
-into the current stable locale directory. First convert them with the
-'mkmoz.sh' script and then moving the proper mozilla files from
-'torbutton/trans_tools/moz/' into 'torbutton/src/chrome/locale/' directory
-while properly naming the files for their respective locale.
 
+Now if you had changes, you need to convert from .po and move
+the newly updated mozilla files into the current stable locale
+directory. First convert them with the 'mkmoz.sh' script and then
+moving the proper mozilla files from 'torbutton/trans_tools/moz/' into
+'torbutton/src/chrome/locale/' directory while properly naming the files
+for their respective locale.
+
 Here's an example of how to move all of the current pootle translations into
 the svn trunk area of Torbutton:
 
-    cd torbutton/trans_tools 
+    cd torbutton/trans_tools
     ./mkmoz.sh
     for locale in `ls -1 moz/`;
-    do 
+    do
     mv -v moz/$locale/*.{rdf,dtd,properties} ../src/chrome/locale/$locale/;
     done
 
 Now check the differences (ensure the output looks reasonable):
-    
+
     svn diff
 
 And finally check in the changes: