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) It's important to the Tor project that we help facilitate translation of 
14) many different parts of this ecosystem.
15) </p>
16) 

17) <a href="#GettingStartedTranslatingTor">Getting Started with Translating Tor</a>.<br>
18) <a href="#GettingStartedTranslatingVidalia">Getting Started with Translating Vidalia</a>.<br>
19) <a href="#GettingStartedTranslatingTorbutton">Getting Started with Translating Torbutton</a>.<br>
20) <a href="#GettingStartedTranslatingTorCheck">Getting Started with Translating Torcheck</a>.<br>
21) 
22) <a id="GettingStartedTranslatingTor"></a>
23) <h2><a class="anchor" href="#GettingStartedTranslatingTor">
24) Tor: Getting started with translation of our website and documentation</a></h2>
25) <hr />
26) 

27) <p>
28) If you want to help translate the Tor website and documentation into
29) other languages. We've written some basic guidelines to help you do this as

30) efficiently as possible on our <a href="<page translation>">main translation 

31) page</a>. It would be useful to read those guidelines first and to consider 
32) the advice for further translation work.
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 interests
39) you and if you need help, please ask — we're always happy to lend a hand.

40) </p>
41) 

42) <a id="GettingStartedTranslatingVidalia"></a>
43) <h3><a class="anchor" href="#GettingStartedTranslatingVidalia">Translating 
44) Vidalia: Getting started</a></h3>

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) is in need of translation.
66) Vidalia now supports using LaunchPad for easy translation. LaunchPad offers 
67) a web service to aid with translation. You can easily
68) visit the <a href="https://translations.launchpad.net/vidalia/trunk">
69) Vidalia LaunchPad translation page</a>. Just visit LaunchPad 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) For more advanced users, translation of Vidalia can be handled with 

79) subversion. You're welcome to 
80) <a href="http://svn.vidalia-project.net/svn/vidalia/trunk/src/vidalia/i18n/">check 
81) the current translation files</a>, find a locale that 
82) <a href="http://trac.vidalia-project.net/wiki/Translations#UpdateGUITranslation">
83) requires further translation</a>, or
84) <a href="http://trac.vidalia-project.net/wiki/Translations#NewGUITranslation">
85) start a translation</a> that we don't have.
86) </p>
87) 
88) <p>
89) Regardless of your choice between the two methods, you can translate with the 
90) LaunchPad service and/or with files directly from subversion.
91) The process isn't as important as the final product, you should use the method 
92) that best suits your working style.
93) </p>
94) 

95) <p>
96) The <b>Win32 installer</b> uses the NSI format and is found in the Vidalia subversion 
97) repository. The NSI format is very similar to normal gettext templates. 
98) The file format is quite simple. Essentially, it is text with the corresponding 
99) translations. This is a good place to get your feet wet with localization.
100) You'll only need a text editor and knowledge of two languages, English and 
101) whatever locale you'll be translating the original English into.
102) You can download the NSI localization files from the Vidalia subversion 
103) repository. For more information on translating the Win32 
104) installer, please see the corresponding instructional 
105) <a href="http://trac.vidalia-project.net/wiki/Translations#TranslateInstallers"> 
106) page on the Vidalia wiki</a>. It's a useful page that explains step by step 
107) information for translation, encoding and submission for inclusion in the next 
108) release. You'll also notice that the wiki page lists translators - we're 
109) especially in need of Farsi and Hebrew translators. Perhaps you're the one?
110) </p>

111) 
112) <p>
113) Last but certainly not least, Vidalia requires diligant 
114) <a href="http://trac.vidalia-project.net/wiki/Translations#AvailableHelpTranslations">

115) translation of its <b>help documents</b></a>. This is important to ensure that users 

116) fully understand the choices that they make and so they understand 
117) the choices the software makes on their behalf. We're currently looking 
118) for German and Bulgarian translators, perhaps you're the right person for the job?
119) <p>
120) </p>
121) 

122) <a id="GettingStartedTranslatingTorbutton"></a>
123) <h4>
124) <a class="anchor" href="#GettingStartedTranslatingTorbutton">
125) Translating Torbutton: Getting started</a></h4>

126) <hr />
127) 
128) <p>
129) <a href="http://torbutton.torproject.org/dev/">Torbutton</a>
130) is a very important piece of software for users that wish to use a 
131) graphical web browser. It protects users against many different threats. 
132) It's basically required for anyone using Firefox and Tor together. This is why 
133) it is very imporant to ensure that Torbutton is translated into as many 
134) languages as is possible.
135) </p>
136) 
137) <p>
138) Torbutton translation is managed in subversion like Vidalia. However, Torbutton 
139) does not use LaunchPad. The main translation website used by Torbutton is the 
140) <a href="http://www.babelzilla.org/">Babelzilla</a> project. You'll need to 
141) sign up for a Babelzilla account to use the website. It is possible to 
142) download the locale files for 
143) <a href="https://tor-svn.freehaven.net/svn/torbutton/trunk/src/chrome/locale">
144) translation from subversion</a> and edit them by hand.
145) </p>
146) 
147) <p>It's also possible to easily 
148) <a href="http://www.babelzilla.org/index.php?option=com_wts&Itemid=88&extension=3510&type=lang">
149) view the current status of all Torbutton translations</a> in Babelzilla.
150) In addition to the current status of all Torbutton translations, Babelzilla 
151) also offers <a href="http://www.babelzilla.org/forum/index.php?showtopic=2340">
152) a discussion board</a> for participating translators.
153) </p>
154) 

155) <a id="GettingStartedTranslatingTorCheck"></a>
156) <h5><a class="anchor" href="#GettingStartedTranslatingTorCheck">
157) Translating TorCheck: Getting started</a></h5>