1 ## Instructions for helping translate text for Vidalia, TorButton
3 ## ( More translation information for Tor related apps will accumulate here )
5 Our translations are handled in one of two places. The Tor Translation Portal
6 handles all of the translations for Vidalia, Torbutton and TorCheck. The Tor
7 website itself is currently handled by hand translations using subversion.
9 -------------------------------------------------------------------------
11 For the Tor website, you'll need a Tor SVN account.
12 If you do not have one and you need one, please run this command with your
13 desired username in place of 'USERNAME':
14 htdigest -c passwd.tmp "Tor subversion repository" USERNAME
15 and send us the contents of passwd.tmp.
17 -------------------------------------------------------------------------
19 For the Portal-based projects, all three check in their respective .po
20 files into the following subversion urls:
22 https://tor-svn.freehaven.net/svn/translation/trunk/projects/torbutton
23 https://tor-svn.freehaven.net/svn/translation/trunk/projects/torcheck
24 https://svn.vidalia-project.net/svn/vidalia/trunk/src/vidalia/i18n/
26 The current pootle configuration is checked into subversion as well:
28 https://tor-svn.freehaven.net/svn/translation/trunk/pootle
30 TorCheck uses our translation portal to accept translations. Users use
31 the portal to check in their changes. To make use of the translations
32 that users have commited to the translations/ subversion module, you'll
33 need to ensure that you have a current checked out copy of TorCheck:
36 check/trunk/i18n$ svn up
38 You should see something like the following:
40 Fetching external item into 'pootle'
41 External at revision 15300.
45 Now if you had changes, you'd simply want to move the newly updated .po files
46 into the current stable directory. Moving the .po files from
47 'check/trunk/i18n/pootle/' into 'check/trunk/i18n' properly naming the files
48 for their respective locale.
50 Here's an example of how to move all of the current pootle translations into
51 the svn trunk area of TorCheck:
54 for locale in `ls -1 pootle/|grep -v template`;
56 mv -v pootle/$locale/TorCheck_$locale.po TorCheck_$locale.po;
59 Now check the differences (ensure the output looks reasonable):
63 Ensure that msgfmt has no errors:
67 And finally check in the changes:
71 Torbutton uses our translation portal to accept translations. Users use
72 the portal to check in their changes.
73 To make use of the translations that users have commited to the translations/
74 subversion module, you'll need to ensure that you have a current checked out
77 cd torbutton/trans_tools
78 torbutton/trans_tools$ svn up
80 You should see something like the following:
82 Fetching external item into 'pootle'
83 External at revision 15300.
87 Now if you had changes, you need to convert from .po and move
88 the newly updated mozilla files into the current stable locale
89 directory. First convert them with the 'mkmoz.sh' script and then
90 moving the proper mozilla files from 'torbutton/trans_tools/moz/' into
91 'torbutton/src/chrome/locale/' directory while properly naming the files
92 for their respective locale.
94 Here's an example of how to move all of the current pootle translations into
95 the svn trunk area of Torbutton:
97 cd torbutton/trans_tools
99 for locale in `ls -1 moz/`;
101 mv -v moz/$locale/*.{rdf,dtd,properties} ../src/chrome/locale/$locale/;
104 Now check the differences (ensure the output looks reasonable):
108 And finally check in the changes:
112 Vidalia uses our translation portal to accept translations. Users use the
113 portal to check in their changes. No conversion or moving is required other
114 than normal pootle usage.