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

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

18) are: Vidalia, Torbutton and TorCheck. Please read the sections that interest

19) you and if you need help, please ask — we're always happy to lend a hand.
20) </p>
21) 

22) <ul>

23) <li><a href="#TTP">The Tor Translation Portal</a></li>

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

25) <li><a href="#TranslatingVidalia">Translating Vidalia</a></li>

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

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

30) </ul>

31) 

32) <a id="TTP"></a>
33) <h2><a class="anchor" href="#TTP">The Tor Translation Portal</a></h2>
34) <hr />
35) 
36) <p>

37) The <a href="https://translation.torproject.org/">Tor Translation Portal</a> is

38) a system which lists all sentences in use in a particular project, and allows
39) interested volunteers to translate individual

40) sentences or phrases as they are able.
41) </p>
42) 
43) <p>
44) You can check the status of all translations for a given project by visiting
45) each project page.  The following statuses are updated in real time when new
46) translations are added:
47) <a href="https://translation.torproject.org/projects/torbutton/">Torbutton</a>,
48) <a href="https://translation.torproject.org/projects/torcheck/">TorCheck</a> and
49) of course <a
50) href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>.
51) </p>
52) 

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

54) <h2>
55) <a class="anchor" href="#TTPVidalia">Translating Vidalia with the Tor Translation Portal</a></h2>
56) <hr />
57) 
58) <p>

59) Vidalia uses the <a href="https://translation.torproject.org/">Tor

60) Translation Portal</a> to manage translations.

61) </p>
62) 

63) <p>

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

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

67) page</a> to get started. Be sure to enter a proper email address and a strong
68) password. After you fill in the form and use the 'Register Account' button, you
69) should see some text indicating that things worked out: 
70) <pre>
71) Account created. You will be emailed login details and an activation code.
72) Please enter your activation code on the activation page.
73) </pre>
74) </p>
75) 
76) <p>

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

78) provided. The email should look something like the following:
79) <pre>
80) A Pootle account has been created for you using this email address.
81) Your activation code is:
82) 36074ec543c1fa23ceeaf8e187dfa43e
83) This message is sent to verify that the email address is in fact correct. If
84) you did not want to register an account, you may simply ignore the message.
85) Your user name is: example_user
86) Your password is: example_user
87) Your registered email address is: username@example.com
88) </pre>
89) </p>
90) 
91) <p>
92) Once you've received the email, you'll need to activate your account by
93) visiting the <a

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

95) Enter your username and activation code into the form and then submit the form
96) by pressing the "Activate Account" button.
97) 
98) You'll see a message that says:
99) <pre>
100) Redirecting to login Page...
101) Your account has been activated! Redirecting to login...
102) </pre>
103) </p>
104) 
105) <p>

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

107) language preferences on the <a

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

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

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

111) you wish to translate. Save your changes by clicking the "Save Changes" button
112) when you're finished.
113) </p>
114) 
115) <p>
116) You're ready to translate!
117) </p>
118) 
119) <p>
120) At this point, you'll want to select a project, such as <a

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

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

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

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

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

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

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

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

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

133) Translate</a>" link. This will take you to the first untranslated string in the
134) language group for the current project.
135) </p>
136) 
137) <p>
138) If you're able, please translate the string you see and click the 'Submit'
139) button. If you're unsure, click the 'Suggest' button. Feel free to leave
140) comments for any of the translations if you feel it's important to clarify
141) anything.
142) </p>
143) 
144) <p>
145) When you're finished, you'll want to commit your changes by returning to the
146) page with the <a

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

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

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

150) link. This will commit your changes into the <a
151) href="https://tor-svn.freehaven.net/svn/translation/trunk/projects/vidalia/de/">Translation
152) subversion module</a> in the specific area as specified by your choices of
153) language and project (Vidalia and German, for this example).
154) </p>
155) 
156) <p>
157) For more advanced users who like to translate without a web browser, you can
158) also download the .po file directly. You'll find this option after clicking on
159) the "<a

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

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

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

163) this option fits your working habits, by all means, please use it! When you're
164) finished translating the .po file, you can upload it by using the "upload file"
165) form in the upper right hand corner, simply select the file and click the
166) 'Upload file' button. 
167) </p>
168) 
169) <p>
170) That's all there is to it!

171) </p>
172) 

173) <a id="TranslatingVidalia"></a>
174) <h2>
175) <a class="anchor" href="#TranslatingVidalia">Other Vidalia translation efforts</a>
176) </h2>
177) <hr />
178) 
179) <p>
180) If you're interested in more advanced translation efforts, you've found the
181) right place. It's best to start by reading the general Vidalia
182) <a href="http://trac.vidalia-project.net/wiki/Translations">translation
183) overview page on the Vidalia wiki</a>.
184) </p>
185) 
186) <p>
187) Vidalia has three key areas in need of translation. The first area is the
188) Vidalia GUI itself. This area is covered by the Tor Translation Project. The
189) second area for translation is the Win32 installer, and then third is localized
190) help documentation.
191) </p>
192) 
193) <p>
194) <b>The main Vidalia program</b> (the GUI itself) needs to be translated.
195) Please visit the <a
196) href="https://translation.torproject.org/projects/vidalia/">Tor Translation
197) Portal page for Vidalia</a>. If you're unsure how the portal works, please see
198) our <a href="<page translation-portal>#TTPVidalia">Vidalia walkthrough using
199) the Tor Translation Portal</a>.
200) </p>
201) 
202) <p>
203) For more advanced users, translation of Vidalia can be handled in subversion.
204) You're welcome to

205) <a href="http://trac.vidalia-project.net/browser/vidalia/trunk/src/vidalia/i18n">check

206) the current translation files</a>, and find a locale that
207) <a href="https://translation.torproject.org/projects/vidalia/">
208) requires further translation</a> or
209) <a href="http://trac.vidalia-project.net/wiki/Translations#NewGUITranslation">
210) start a translation</a> that we don't have. If you do use check out with
211) subversion, please upload via the Tor Translation Portal web interface.
212) </p>
213) 
214) <p>
215) Regardless of your choice between the two methods, you can translate with the

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

217) service and/or with files directly from subversion. The process isn't as
218) important as the final product, so you should use
219) the method that best suits your working style. We think that the Tor
220) Translation Portal will suit most users best.
221) </p>
222) 
223) <p>
224) The <b>Win32 installer</b> uses the NSI format and is found in the Vidalia subversion
225) repository. The NSI format is very similar to normal gettext templates.
226) The file format is quite simple. Essentially, it is text with the corresponding
227) translations. This is a good place to get your feet wet with localization and a
228) normal text editor. Currently this format is not supported by the translation
229) portal.  You'll only need a text editor and knowledge of two languages, English
230) and whatever locale you'll be translating the original English into.
231) You can download the NSI localization files from the Vidalia subversion
232) repository. For more information on translating the Win32
233) installer, please see the corresponding instructional
234) <a href="http://trac.vidalia-project.net/wiki/Translations#TranslateInstallers">
235) page on the Vidalia wiki</a>. It's a useful page that explains step by step
236) information for translation, encoding and submission for inclusion in the next
237) release. You'll also notice that the wiki page lists translators - we're
238) especially in need of Farsi and Hebrew translators. Perhaps you're the one?
239) </p>
240) 
241) <p>
242) Last but certainly not least, Vidalia requires diligent
243) <a href="http://trac.vidalia-project.net/wiki/Translations#AvailableHelpTranslations">
244) translation of its <b>help documents</b></a>. This is important to ensure that users
245) fully understand the choices that they make and so they understand
246) the choices the software makes on their behalf. We're currently looking
247) for German and Bulgarian translators; perhaps you're the right person for the job?
248) </p>
249) 

250) <a id="TranslatingTorbutton"></a>
251) <h2>
252) <a class="anchor" href="#TranslatingTorbutton">Translating Torbutton</a></h2>

253) <hr />
254) 
255) <p>

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

260) </p>
261) 
262) <p>

263) Torbutton (like Vidalia and TorCheck) translation is managed by the <a

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

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

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

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

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

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

272) </p>
273) 

274) <p>

275) If you're unsure about how to use the <a

276) href="https://translation.torproject.org/">Tor Translation Portal</a> to
277) translate Torbutton, please read <a href="<page
278) translation-portal>#TTPVidalia">our example walkthrough with Vidalia</a>.
279) Torbutton uses the same system with the same processes.
280) </p>
281) 

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

284) <hr />
285) 
286) <p>

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

294) </p>
295) 
296) <p>

297) TorCheck (like Vidalia and Torbutton) is managed by the  <a

298) href="https://translation.torproject.org/">Tor Translation Portal</a>. Simply visit the <a

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

300) translation status page</a> to see what's in need of translation. Please just
301) jump in and start translating the missing messages. (You'll have to create an account and log in.)
302) </p>
303) 

304) <p>

305) If you're unsure about how to use the <a

306) href="https://translation.torproject.org/">Tor Translation Portal</a> to

307) translate TorCheck, please read <a href="<page

308) translation-portal>#TTPVidalia">our example walkthrough with Vidalia</a>.
309) TorCheck uses the same system with the same processes.
310) </p>
311) 

312) <p>
313) If the locale
314) you wish to add support for isn't translated or doesn't exist, you can easily
315) start the translation. Simply download a copy of
316) <a
317) href="https://tor-svn.freehaven.net/svn/translation/trunk/projects/torcheck/templates/TorCheck.pot">the

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

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

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

323) </p>
324) 
325) <a id="TranslatingTor"></a>
326) <h2><a class="anchor" href="#TranslatingTor">Translating the
327) Tor website and documentation</a></h2>
328) <hr />
329) 
330) <p>
331) We've written some basic guidelines to help you translate
332) the Tor website and documentation on our <a href="<page translation>">main
333) translation page</a>. The guidelines there also provide good advice for

334) the other translation items on this page. The current status of the website
335) translations can be found on our <a

336) href="<page translation-status>">website translation status page</a>.