tor-webwml.git

@@ -19,13 +19,6 @@ Please read the sections below and help out. If you need help, please

 ask; we're always happy to lend a hand.

 </p>

-<ul>

-<li><a href="#TTP">Using The Tor Translation Portal</a></li>

-<li><a href="#TranslatingVidalia">Other Vidalia components</a></li>

-<li><a href="#TranslatingTor">Translating the Tor website and

-documentation</a></li>

-</ul>

-

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

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

 <h2><a class="anchor" href="#TTP">Using The Tor Translation Portal</a></h2>

@@ -147,9 +140,8 @@ contribute to Torbutton and Torcheck too.

 </p>

 <p>

-If your language isn't in the list of options yet, send mail to <a

-href="<page contact>">the tor-translations team</a> and we'll add it

-for you.

+If your language isn't in the list of options yet, send mail to

+<tt>tor-translation AT torproject.org</tt> and we'll add it for you.

 </p>

 <p>

@@ -168,79 +160,6 @@ Editor -> Behavior, uncheck "Automatically compile .mo file on save").

 When you're finished translating the .po file, you can upload it by

 using the "upload file" form in the upper right hand corner: simply

 select the file and click the 'Upload file' button.

-</p>

-

-<a id="TranslatingVidalia"></a>

-<h2>

-<a class="anchor" href="#TranslatingVidalia">Other Vidalia translation efforts</a>

-</h2>

-<hr />

-

-<p>

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

-href="#TTPVidalia">Vidalia walkthrough</a>, we also need translations

-for the Win32 installer and the help documentation.

-</p>

-

-<p>

-The <b>Win32 installer</b> uses the NSI format and is found in the Vidalia subversion

-repository. The NSI format is very similar to normal gettext templates.

-The file format is quite simple. Essentially, it is text with the corresponding

-translations. This is a good place to get your feet wet with localization and a

-normal text editor. Currently this format is not supported by the translation

-portal.  You'll only need a text editor and knowledge of two languages, English

-and whatever locale you'll be translating the original English into.

-You can download the NSI localization files from the Vidalia subversion

-repository. For more information on translating the Win32

-installer, please see the corresponding instructional

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

-page on the Vidalia wiki</a>. It's a useful page that explains step by step

-information for translation, encoding and submission for inclusion in the next

-release. You'll also notice that the wiki page lists translators - we're

-especially in need of Farsi and Hebrew translators. Perhaps you're the one?

-</p>

-

-<p>

-Last but certainly not least, Vidalia requires diligent

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

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

-fully understand the choices that they make and so they understand

-the choices the software makes on their behalf. We're currently looking

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

-</p>

-

-<p>

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

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

-easily view the status of all translations on the <a

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

-for Torbutton</a>. Torbutton is also <a

-href="https://svn.torproject.org/svn/translation/trunk/projects/torbutton/">in

-subversion</a> like Vidalia and TorCheck.  Please visit the Portal page for <a

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

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

-</p>

-

-<p>

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

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

-translate Torbutton, please read <a href="#TTPVidalia">our example

-walkthrough with Vidalia</a>. Torbutton uses the same system with the

-same processes.

-</p>

-

-<a id="TranslatingTor"></a>

-<h2><a class="anchor" href="#TranslatingTor">Translating the

-Tor website and documentation</a></h2>

-<hr />

-

-<p>

-We've written some basic guidelines to help you translate

-the Tor website and documentation on our <a href="<page translation>">main

-website translation page</a>. The guidelines there also provide good advice for

-the other translation items on this page. The current status of the website

-translations can be found on our <a

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

 </p>

   </div><!-- #main -->

@@ -34,55 +34,11 @@ Also, rather than just translating each page word

 by word, please try to translate the ideas so they make the most sense

 in your language.</p>

-<ol>

-<li>Look in <a

-href="<svnwebsite>en/"><svnwebsite>en/</a>

-for a set of ".wml" files. The most important ones to

-translate are listed as "high priority", "medium priority",

-and "low priority" on the

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

-You can look at <a

-href="<svnwebsite>de/"><svnwebsite>de/</a>

-for examples of the desired translation formats.</li>

-

-<li>The first line in the translated file should be<br />

-\# Based-On-Revision: 13000<br />

-where 13000 is the revision number of the original English page. This

-lets you easily spot when a page gets out of date. The revision number

-is found at the top on each page -- you can either look at the files in the

-<a href="<svnwebsite>en/"><svnwebsite>en/</a> directory, or manually

-<a href="<page documentation>#Developers">checkout</a> the latest version

-of the website.</li>

-

-<li>The second line in the translated file should be the email address of

-the translator:<br />

-\# Last-Translator: abc at example.com<br />

-so we can get ahold of you if the pages needs to be corrected or updated.

-(Since the pages will be posted on the web and spammers will find them,

-you may want to obfuscate your email address or use a separate one.)</li>

-

 <li>We would also like some translations for the diagrams on

 <a href="<page overview>">the overview page</a>. You can just send us

 the text that should go in the diagrams, and we'll take care of making

 new versions of the pictures.</li>

-<li>Translated pages should link to the other translated pages. In general

-this is automatic: writing <code>&lt;page download&gt;</code>

-will automatically link to the translated version of that page if

-there is one, and the English version otherwise.</li>

-

-<li>Use valid <a href="http://roselli.org/adrian/articles/character_charts.asp">character entities</a>.

-Even though most browsers display the characters correctly these days, we want

-to be on the safe side, so we don't get bug reports from people who can't

-read the text. If you need to use a character set other than ISO-8859-1,

-add something like <code>CHARSET="UTF-8"</code> to the end of the line

-that starts with <code>#include "head.wmi"</code>.

-</li>

-

-<li>Keep your translation valid XHTML. Once it's in place, you can test

-your page at <a

-href="http://validator.w3.org/">validator.w3.org</a>.</li>

-

 <li>When you have some pages ready, send them to the

 <tt>tor-translation</tt> alias on the <a href="<page contact>">contact

 page</a>.  (If you have changes to existing pages, please use the diff