tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision: 13774 $
3) 
4) #include "head.wmi" TITLE="Tor: Translation Portal"
5) 
6) <div class="main-column">
7) 

8) <h1>Tor: Translation Portal</h1>

9) <hr />
10) 
11) <p>

12) Effective use of Tor is made possible by an ecosystem of software.

13) Many different parts of this ecosystem need translation help:

14) </p>

15) <ul>
16) <li><a href="#TranslatingTor">Translating the Tor website and
17) documentation</a></li>
18) <li><a href="#TranslatingVidalia">Translating Vidalia</a></li>
19) <li><a href="#TranslatingTorbutton">Translating Torbutton</a></li>
20) <li><a href="#TranslatingTorCheck">Translating Torcheck</a></li>
21) </ul>

22) 
23) <a id="TranslatingTor"></a>
24) <h2><a class="anchor" href="#TranslatingTor">Translating the
25) Tor website and documentation</a></h2>

26) <hr />
27) 

28) <p>

29) We've written some basic guidelines to help you translate
30) the Tor website and documentation on our <a href="<page translation>">main
31) translation page</a>. The guidelines there also provide good advice for
32) the other translation items on this page.

33) </p>
34) 
35) <p>

36) In addition to the main Tor website and Tor documentation, there are currently
37) other projects in need of translation help. In order of importance they

38) are: Vidalia, TorButton and TorCheck. Please read the sections that interest

39) you and if you need help, please ask — we're always happy to lend a hand.

40) </p>
41) 

42) <a id="TranslatingVidalia"></a>
43) <h2><a class="anchor" href="#TranslatingVidalia">Translating
44) Vidalia</a></h2>

45) <hr />
46) 
47) <p>

48) Getting started with <a href="http://www.vidalia-project.net/">Vidalia</a>
49) translations is easy. We're working on making it easier daily.

50) </p>
51) 
52) <p>
53) It's best to start by reading the general Vidalia

54) <a href="http://trac.vidalia-project.net/wiki/Translations">translation

55) overview page on the Vidalia wiki</a>.
56) </p>
57) 
58) <p>

59) Vidalia has three key areas in need of translation. The first area is the
60) Vidalia GUI itself, the second is the Win32 installer and then third is

61) localized help documentation.
62) </p>
63) 
64) <p>

65) <b>The main Vidalia program</b> (the GUI itself) needs to be translated.
66) Vidalia now supports using LaunchPad, which is a
67) web service to aid with translation. You can

68) visit the <a href="https://translations.launchpad.net/vidalia/trunk">

69) Vidalia LaunchPad translation page</a> to get started.

70) You'll need an account on LaunchPad to use this service to the full extent
71) possible. The step by step instructions are currently listed in the

72) translations section of the
73) <a href="https://tor-svn.freehaven.net/svn/tor/trunk/doc/translations.txt">

74) translations.txt Tor documentation</a>.

75) </p>
76) 

77) <p>

78) In addition to LaunchPad, we suggest using the Qt Linguist program. The fine
79) folks that write Qt (the GUI toolkit that Vidalia uses) have good guide for
80) using Qt Linguist. Check out the <a

81) href="http://doc.trolltech.com/4.3/linguist-translators.html">Qt Linguist

82) Manual for Translators</a> on the Qt site. To use Qt Linguist, you'll need 

83) to download the Vidalia .ts files either from the Vidalia Trac <a
84) href="http://trac.vidalia-project.net/browser/vidalia/trunk/src/vidalia/i18n">website</a>
85) or from subversion repository as documented below.  </p>
86) 

87) <!-- XXX We should avoid pointing end-users to the translations.txt file.
88) Which instructions from it do the translators need? -RD -->
89) 
90) <!-- To add: The intermediate option is to download the Qt translator and use
91) that. Assuming that actually works, I guess. -RD -->
92) 

93) <p>

94) For more advanced users, translation of Vidalia can be handled in subversion.
95) You're welcome to

96) <a href="http://svn.vidalia-project.net/svn/vidalia/trunk/src/vidalia/i18n/">check

97) the current translation files</a>, and either find a locale that

98) <a href="http://trac.vidalia-project.net/wiki/Translations#UpdateGUITranslation">

99) requires further translation</a> or

100) <a href="http://trac.vidalia-project.net/wiki/Translations#NewGUITranslation">
101) start a translation</a> that we don't have.
102) </p>
103) 
104) <p>

105) Regardless of your choice between the two methods, you can translate with the

106) LaunchPad service and/or with files directly from subversion.

107) The process isn't as important as the final product, so you should use
108) the method that best suits your working style.

109) </p>
110) 

111) <p>

112) The <b>Win32 installer</b> uses the NSI format and is found in the Vidalia subversion
113) repository. The NSI format is very similar to normal gettext templates.
114) The file format is quite simple. Essentially, it is text with the corresponding

115) translations. This is a good place to get your feet wet with localization.

116) You'll only need a text editor and knowledge of two languages, English and

117) whatever locale you'll be translating the original English into.

118) You can download the NSI localization files from the Vidalia subversion
119) repository. For more information on translating the Win32
120) installer, please see the corresponding instructional
121) <a href="http://trac.vidalia-project.net/wiki/Translations#TranslateInstallers">
122) page on the Vidalia wiki</a>. It's a useful page that explains step by step
123) information for translation, encoding and submission for inclusion in the next
124) release. You'll also notice that the wiki page lists translators - we're

125) especially in need of Farsi and Hebrew translators. Perhaps you're the one?
126) </p>

127) 
128) <p>

129) Last but certainly not least, Vidalia requires diligent

130) <a href="http://trac.vidalia-project.net/wiki/Translations#AvailableHelpTranslations">

131) translation of its <b>help documents</b></a>. This is important to ensure that users
132) fully understand the choices that they make and so they understand
133) the choices the software makes on their behalf. We're currently looking

134) for German and Bulgarian translators; perhaps you're the right person for the job?

135) <p>
136) </p>
137) 

138) <a id="TranslatingTorbutton"></a>
139) <h2>
140) <a class="anchor" href="#TranslatingTorbutton">Translating Torbutton</a></h2>

141) <hr />
142) 
143) <p>

144) <a href="https://torbutton.torproject.org/dev/">Torbutton</a>
145) is a Firefox extension that protects Firefox users from many different
146) threats. Since Torbutton is necessary to help protect users, we need
147) Torbutton to be translated into as many languages as possible.

148) </p>
149) 
150) <p>

151) Torbutton translation is managed in subversion like Vidalia. However, Torbutton
152) does not use LaunchPad. The main translation website used by Torbutton is the
153) <a href="http://www.babelzilla.org/">Babelzilla</a> project. You'll need to
154) sign up for a Babelzilla account to use the website. It is possible to
155) download the locale files for

156) <a href="https://tor-svn.freehaven.net/svn/torbutton/trunk/src/chrome/locale">
157) translation from subversion</a> and edit them by hand.
158) </p>
159) 

160) <p>It's also possible to easily

161) <a href="http://www.babelzilla.org/index.php?option=com_wts&Itemid=88&extension=3510&type=lang">
162) view the current status of all Torbutton translations</a> in Babelzilla.

163) (You'll have to create an account and log in.)

164) In addition to the current status of all Torbutton translations, Babelzilla

165) also offers <a href="http://www.babelzilla.org/forum/index.php?showtopic=2340">
166) a discussion board</a> for participating translators.
167) </p>
168) 

169) <p>
170) Babelzilla has some limitations on the number of translators per project.
171) It may be that if you'd like to use Babelzilla directly for all of your
172) translation, you'll need to request specific permissions. Please do not
173) hesitate to contact us if you'd like to become a translator with Babelzilla. 
174) </p>
175) 

176) <a id="TranslatingTorCheck"></a>
177) <h2><a class="anchor" href="#TranslatingTorCheck">Translating TorCheck</a></h2>

178) <hr />
179) 
180) <p>

181) TorCheck is the simplest and smallest of the bunch. TorCheck is a
182) website run by a simple python program. It allows Tor users to check if
183) they are using Tor properly. Since TorCheck is the first website that
184) some Tor users see, and its goal is to let them know if their browser
185) is set up correctly, it is useful to have this page available in many
186) languages. TorCheck is also the easiest to translate as it's a single
187) very small file with only a few strings.

188) </p>
189) 
190) <p>

191) TorCheck uses subversion. It's best to check

192) <a href="https://tor-svn.freehaven.net/svn/check/trunk/i18n/">the repository</a>

193) to see if the locale you wish to translate is already started. If the locale
194) you wish to add support for isn't translated, you can easily start the
195) translation. Simply download a copy of
196) <a href="https://tor-svn.freehaven.net/svn/check/trunk/i18n/TorCheck.pot">the

197) gettext template from the subversion repository</a>, open it in your text
198) editor, and start translating.

199) When you're finished translating, you'll want to submit a patch via email
200) to the <tt>tor-translation</tt> team as listed on the