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) The Tor bundles include several different programs, all of which need
13) translation help. In order of importance they are: Vidalia, Torbutton
14) and TorCheck. Please read the sections below and help out. If
15) you need help, please ask — we're always happy to lend a hand.
16) </p>
17) 
18) # The below three paragraphs should get merged into the project
19) # descriptors inside Pootle, and then removed from here. -RD
20) <p>
21) <a href="http://vidalia-project.net/">Vidalia</a> is a program that
22) provides a graphical interface for Tor. While Tor is just a proxy that
23) runs in the background, Vidalia lets you start and stop the Tor software,
24) configure it, view its status at a glance, and monitor bandwidth usage.
25) </p>
26) 
27) <p>
28) <a href="https://torbutton.torproject.org/dev/">Torbutton</a>
29) is a Firefox extension that protects Firefox users from many different
30) threats. Since Torbutton is necessary to help protect users, we need
31) Torbutton to be translated into as many languages as possible.
32) </p>
33) 
34) <p>
35) <a href="https://check.torproject.org/">TorCheck</a> is a website that
36) allows Tor users to check if they are using Tor properly. Since TorCheck
37) is the first website that some Tor users see, and its goal is to let
38) them know if their browser is set up correctly, it is useful to have
39) this page available in many languages.

40) </p>
41) 

42) <ul>

43) <li><a href="#TTP">Using The Tor Translation Portal</a></li>
44) <li><a href="#TranslatingVidalia">Other Vidalia components</a></li>

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

47) </ul>

48) 

49) <a id="TTP"></a>

50) <a id="TTPVidalia"></a>
51) <h2><a class="anchor" href="#TTP">Using The Tor Translation Portal</a></h2>

52) <hr />
53) 
54) <p>

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

56) is a website that lets users contribute translations online using their
57) web browser. It lists all sentences or phrases (called "strings") used

58) by a particular project, and allows interested volunteers to translate

59) individual sentences or phrases as they are able.

60) </p>
61) 
62) <p>
63) You can check the status of all translations for a given project by visiting
64) each project page.  The following statuses are updated in real time when new
65) translations are added:

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

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

68) and
69) <a href="https://translation.torproject.org/projects/torcheck/">TorCheck</a>.

70) </p>
71) 

72) <p>

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

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

76) page</a> to get started. Be sure to enter a proper email address and a strong
77) password. After you fill in the form and use the 'Register Account' button, you
78) should see some text indicating that things worked out: 
79) <pre>
80) Account created. You will be emailed login details and an activation code.
81) Please enter your activation code on the activation page.
82) </pre>
83) </p>
84) 
85) <p>

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

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

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

104) Enter your username and activation code into the form and then submit the form
105) by pressing the "Activate Account" button.
106) 
107) You'll see a message that says:
108) <pre>
109) Redirecting to login Page...
110) Your account has been activated! Redirecting to login...
111) </pre>
112) </p>
113) 
114) <p>

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

116) language preferences on the <a

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

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

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

120) you wish to translate. Save your changes by clicking the "Save Changes" button
121) when you're finished.
122) </p>
123) 
124) <p>
125) You're ready to translate!
126) </p>
127) 
128) <p>

129) At this point, you can select a project, such as <a

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

131) see a nice list of all of the currently supported languages along with the

132) current translation progress. Select a language — in our example,
133) you'll click

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

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

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

137) This is the file with all of the currently translated German strings for

138) Vidalia. You should click on the "<a

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

140) Editing Functions</a>" link above the 'vidalia_de.po' row. Next you should

141) click the "<a

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

143) Translate</a>" link. This will take you to the first untranslated string in the
144) language group for the current project.
145) </p>
146) 
147) <p>
148) If you're able, please translate the string you see and click the 'Submit'
149) button. If you're unsure, click the 'Suggest' button. Feel free to leave
150) comments for any of the translations if you feel it's important to clarify
151) anything.
152) </p>
153) 
154) <p>

155) When you're finished, you need to commit your changes. Return to the

156) page with the <a

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

158) Functions</a>, and click on the "<a

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

160) link. This will commit your changes into the <a
161) href="https://tor-svn.freehaven.net/svn/translation/trunk/projects/vidalia/de/">Translation
162) subversion module</a> in the specific area as specified by your choices of
163) language and project (Vidalia and German, for this example).
164) </p>
165) 

166) <p>

167) That's all there is to it! Be sure to go through the steps again and
168) contribute to Torbutton and Torcheck too.

169) </p>
170) 

171) <p>
172) For more advanced users who like to translate without a web browser, you can
173) also download the .po file directly. You'll find this option after clicking on
174) the "<a

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

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

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

178) this option fits your working habits, by all means, please use it!
179) You may find a program called <a href="http://www.poedit.net/">Poedit</a>
180) to make the job easier, especially for right-to-left languages that don't
181) work as well in text editors. If you're using Poedit, you should disable
182) compiling .mo files in Poedit's preferences (File -&gt; Preferences -&gt;
183) Editor -&gt; Behavior, uncheck "Automatically compile .mo file on save").
184) When you're finished translating the .po file, you can upload it by
185) using the "upload file" form in the upper right hand corner: simply
186) select the file and click the 'Upload file' button.

187) </p>
188) 

189) <a id="TranslatingVidalia"></a>
190) <h2>
191) <a class="anchor" href="#TranslatingVidalia">Other Vidalia translation efforts</a>
192) </h2>
193) <hr />
194) 
195) <p>

196) In addition to the main Vidalia interface, which is covered by the above <a

197) href="#TTPVidalia">Vidalia walkthrough</a>, we also need translations
198) for the Win32 installer and the help documentation.

199) </p>
200) 
201) <p>
202) The <b>Win32 installer</b> uses the NSI format and is found in the Vidalia subversion
203) repository. The NSI format is very similar to normal gettext templates.
204) The file format is quite simple. Essentially, it is text with the corresponding
205) translations. This is a good place to get your feet wet with localization and a
206) normal text editor. Currently this format is not supported by the translation
207) portal.  You'll only need a text editor and knowledge of two languages, English
208) and whatever locale you'll be translating the original English into.
209) You can download the NSI localization files from the Vidalia subversion
210) repository. For more information on translating the Win32
211) installer, please see the corresponding instructional
212) <a href="http://trac.vidalia-project.net/wiki/Translations#TranslateInstallers">
213) page on the Vidalia wiki</a>. It's a useful page that explains step by step
214) information for translation, encoding and submission for inclusion in the next
215) release. You'll also notice that the wiki page lists translators - we're
216) especially in need of Farsi and Hebrew translators. Perhaps you're the one?
217) </p>
218) 
219) <p>
220) Last but certainly not least, Vidalia requires diligent
221) <a href="http://trac.vidalia-project.net/wiki/Translations#AvailableHelpTranslations">
222) translation of its <b>help documents</b></a>. This is important to ensure that users
223) fully understand the choices that they make and so they understand
224) the choices the software makes on their behalf. We're currently looking
225) for German and Bulgarian translators; perhaps you're the right person for the job?
226) </p>
227) 

228) <p>

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

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

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

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

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

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

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

238) </p>
239) 

240) <p>

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

242) href="https://translation.torproject.org/">Tor Translation Portal</a> to
243) translate Torbutton, please read <a href="<page
244) translation-portal>#TTPVidalia">our example walkthrough with Vidalia</a>.
245) Torbutton uses the same system with the same processes.
246) </p>
247) 

248) <a id="TranslatingTor"></a>
249) <h2><a class="anchor" href="#TranslatingTor">Translating the
250) Tor website and documentation</a></h2>
251) <hr />
252) 
253) <p>
254) We've written some basic guidelines to help you translate
255) the Tor website and documentation on our <a href="<page translation>">main
256) translation page</a>. The guidelines there also provide good advice for

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

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