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) Our <a href="https://translation.torproject.org/">Translation Portal</a> will suit most translators best.

15) In addition to the main Tor website and Tor documentation, there are currently
16) other projects in need of translation help. In order of importance they
17) are: Vidalia, TorButton and TorCheck. Please read the sections that interest
18) you and if you need help, please ask — we're always happy to lend a hand.
19) </p>
20) 

21) </p>

22) <ul>
23) <li><a href="#TranslatingVidalia">Translating Vidalia</a></li>

24) <li><a href="#TTPVidalia">Tor Translation Portal walkthrough with Vidalia</a></li>

25) <li><a href="#TranslatingTorbutton">Translating Torbutton</a></li>
26) <li><a href="#TranslatingTorCheck">Translating Torcheck</a></li>

27) <li><a href="#TranslatingTor">Translating the Tor website and
28) documentation</a></li>

29) </ul>

30) 
31) <a id="TranslatingVidalia"></a>
32) <h2><a class="anchor" href="#TranslatingVidalia">Translating
33) Vidalia</a></h2>

34) <hr />
35) 

36) # XXX We should get rid of this section, or at least move it under
37) # the Pootle walk-through and remove all the redundant pieces. -RD
38) 

39) <p>

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

42) </p>
43) 
44) <p>
45) It's best to start by reading the general Vidalia

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

47) overview page on the Vidalia wiki</a>.
48) </p>
49) 
50) <p>

51) Vidalia has three key areas in need of translation. The first area is the

52) Vidalia GUI itself, the second is the Win32 installer, and then third is

53) localized help documentation.
54) </p>
55) 
56) <p>

57) <b>The main Vidalia program</b> (the GUI itself) needs to be translated.

58) Please visit the <a

59) href="https://translation.torproject.org/projects/vidalia/">Tor Translation

60) Portal page for Vidalia</a>.

61) </p>
62) 
63) <p>

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

66) <a href="https://svn.torproject.org/svn/translation/trunk/projects/vidalia/">check

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

68) <a href="https://translation.torproject.org/projects/vidalia/">

69) requires further translation</a> or

70) <a href="http://trac.vidalia-project.net/wiki/Translations#NewGUITranslation">
71) start a translation</a> that we don't have.
72) </p>
73) 
74) <p>

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

76) Tor Translation Portal service and/or with files directly from subversion.

77) The process isn't as important as the final product, so you should use

78) the method that best suits your working style. We think that the Tor

79) Translation Portal will suit most users best.

80) </p>
81) 

82) <p>

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

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

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

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

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

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

98) 
99) <p>

100) Last but certainly not least, Vidalia requires diligent

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

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

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

106) </p>
107) 

108) <a id="TTPVidalia"></a>

109) <h2>
110) <a class="anchor" href="#TTPVidalia">Translating Vidalia with the Tor Translation Portal</a></h2>
111) <hr />
112) 
113) <p>

114) The Tor Translation Portal is a system which lists all sentences in use in a

115) particular project, and allows interested volunteers to translate individual
116) strings as they are able.
117) </p>
118) 
119) <p>
120) You can check the status of all translations for a given project by visiting
121) each project page.  The following statuses are updated in real time when new
122) translations are added:

123) <a href="https://translation.torproject.org/projects/torbutton/">Torbutton</a>,
124) <a href="https://translation.torproject.org/projects/torcheck/">TorCheck</a> and

125) of course <a

126) href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>. The

127) current status of the website translations can be found on our <a
128) href="https://www.torproject.org/translation-status.html">website translation
129) status page</a>.

130) # XXX the above sentence is out of place here. shouldn't it be in the
131) # 'tor page translator' section? -RD

132) </p>
133) 

134) <p>

135) To get started using our translation website, you need to sign up for an
136) account. Visit the <a

137) href="https://translation.torproject.org/register.html">account registration

138) page</a> to get started. Be sure to enter a proper email address and a strong
139) password. After you fill in the form and use the 'Register Account' button, you
140) should see some text indicating that things worked out: 
141) <pre>
142) Account created. You will be emailed login details and an activation code.
143) Please enter your activation code on the activation page.
144) </pre>
145) </p>
146) 
147) <p>

148) Shortly after you see this text an email will be sent to the email address you

149) provided. The email should look something like the following:
150) <pre>
151) A Pootle account has been created for you using this email address.
152) Your activation code is:
153) 36074ec543c1fa23ceeaf8e187dfa43e
154) This message is sent to verify that the email address is in fact correct. If
155) you did not want to register an account, you may simply ignore the message.
156) Your user name is: example_user
157) Your password is: example_user
158) Your registered email address is: username@example.com
159) </pre>
160) </p>
161) 
162) <p>
163) Once you've received the email, you'll need to activate your account by
164) visiting the <a

165) href="https://translation.torproject.org/activate.html">activation page</a>.

166) Enter your username and activation code into the form and then submit the form
167) by pressing the "Activate Account" button.
168) 
169) You'll see a message that says:
170) <pre>
171) Redirecting to login Page...
172) Your account has been activated! Redirecting to login...
173) </pre>
174) </p>
175) 
176) <p>

177) When you login to your new account, you'll be prompted to configure your basic

178) language preferences on the <a

179) href="https://translation.torproject.org/home/options.html">options page</a>. At

180) the very least, you'll want to select the user interface language, select any

181) of the projects you're interested in translating, and additionally the languages

182) you wish to translate. Save your changes by clicking the "Save Changes" button
183) when you're finished.
184) </p>
185) 
186) <p>
187) You're ready to translate!
188) </p>
189) 
190) <p>
191) At this point, you'll want to select a project, such as <a

192) href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>. You'll

193) see a nice list of all of the currently supported languages along with the
194) current translation progress. Select a language, in our example, you'll click

195) <a href="https://translation.torproject.org/de/vidalia/">German</a>. The next

196) page should show you a single row of data for the file "<a

197) href='https://translation.torproject.org/de/vidalia/vidalia.po?translate=1&view=1'>vidalia.po</a>".

198) This is the file with all of the currently translated German strings for
199) Vidalia. You'll want to click on the "<a

200) href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show

201) Editing Functions</a>" link above the 'vidalia.po' row. Next you'll want to
202) click the "<a

203) href='https://translation.torproject.org/de/vidalia/translate.html?fuzzy=1&editing=1&blank=1'>Quick

204) Translate</a>" link. This will take you to the first untranslated string in the
205) language group for the current project.
206) </p>
207) 
208) <p>
209) If you're able, please translate the string you see and click the 'Submit'
210) button. If you're unsure, click the 'Suggest' button. Feel free to leave
211) comments for any of the translations if you feel it's important to clarify
212) anything.
213) </p>
214) 
215) <p>
216) When you're finished, you'll want to commit your changes by returning to the
217) page with the <a

218) href="https://translation.torproject.org/de/vidalia/index.html?editing=1">Editing

219) Functions</a>. You'll want to click on the "<a

220) href='https://translation.torproject.org/de/vidalia/index.html?editing=1&docommit=1&commitfile=vidalia.po'>Commit</a>"

221) link. This will commit your changes into the <a
222) href="https://tor-svn.freehaven.net/svn/translation/trunk/projects/vidalia/de/">Translation
223) subversion module</a> in the specific area as specified by your choices of
224) language and project (Vidalia and German, for this example).
225) </p>
226) 
227) <p>
228) For more advanced users who like to translate without a web browser, you can
229) also download the .po file directly. You'll find this option after clicking on
230) the "<a

231) href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show

232) Editing Functions</a>" link. You should see a link to download the <a

233) href="https://translation.torproject.org/de/vidalia/vidalia.po">PO file</a>. If

234) this option fits your working habits, by all means, please use it! When you're
235) finished translating the .po file, you can upload it by using the "upload file"
236) form in the upper right hand corner, simply select the file and click the
237) 'Upload file' button. 
238) </p>
239) 
240) <p>
241) That's all there is to it!

242) </p>
243) 

244) <a id="TranslatingTorbutton"></a>
245) <h2>
246) <a class="anchor" href="#TranslatingTorbutton">Translating Torbutton</a></h2>

247) <hr />
248) 
249) <p>

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

254) </p>
255) 
256) <p>

257) Torbutton translation is managed by the <a

258) href="https://translation.torproject.org/">Tor Translation Portal</a>. You can

259) easily view the status of all translations on the <a

260) href="https://translation.torproject.org/projects/torbutton/">Portal status page

261) for Torbutton</a>. Torbutton is also <a
262) href="https://tor-svn.freehaven.net/svn/translation/trunk/projects/torbutton/">in
263) subversion</a> like Vidalia and TorCheck.  Please visit the Portal page for <a

264) href="https://translation.torproject.org/projects/torbutton/">Torbutton</a> and

265) pick a locale to translate.  (You'll have to create an account and log in.)

266) </p>
267) 

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

270) <hr />
271) 
272) <p>

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

280) </p>
281) 
282) <p>

283) TorCheck uses the Tor Translation Portal. Simply visit the <a

284) href="https://translation.torproject.org/projects/torcheck/">TorCheck

285) translation status page</a> to see what's in need of translation. Please just
286) jump in and start translating the missing messages. (You'll have to create an account and log in.)
287) </p>
288) 
289) <p>
290) If the locale
291) you wish to add support for isn't translated or doesn't exist, you can easily
292) start the translation. Simply download a copy of
293) <a
294) href="https://tor-svn.freehaven.net/svn/translation/trunk/projects/torcheck/templates/TorCheck.pot">the

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

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

299) <a href="<page contact>">contact page</a>. Files should be encoded as UTF-8.

300) </p>
301) 
302) <a id="TranslatingTor"></a>
303) <h2><a class="anchor" href="#TranslatingTor">Translating the
304) Tor website and documentation</a></h2>
305) <hr />
306) 
307) <p>
308) We've written some basic guidelines to help you translate
309) the Tor website and documentation on our <a href="<page translation>">main
310) translation page</a>. The guidelines there also provide good advice for
311) the other translation items on this page.