Tor: Translation guidelines

If you want to help translate the Tor website and documentation into other languages, here are some basic guidelines to help you do this as efficiently as possible.
To get an idea how current our translations are, we have created a page with the current translation status.

Note that we're interested in getting the complete website translated for each language, but even a few pages will still be helpful.

1. Look in svn/website/en/ for a set of ".wml" files. The most important ones to translate are listed as "high priority", "medium priority", and "low priority" on the translation status page. You can look at svn/website/de/ for examples of the desired translation formats.
2. The first line in the translated file should be
   # Based-On-Revision: 6000
   where 6000 is the revision number of the original page translated. This lets you easily spot when a page gets out of date. The revision number is found at the top on each page -- it is created by SVN so be sure to checkout the latest version of the website.
3. The second line in the translated file should be the email address of the translator:
   # Last-Translator: abc at example.com
   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.)
4. We would also like some translations for the diagrams on the overview page. 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.
5. Translated pages should link to the other translated pages.
6. Use valid character entities. 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 CHARSET="UTF-8" to the end of the line that starts with #include "head.wmi".
7. Keep your translation valid XHTML to minimize the work needed before the page is committed to SVN. You can test your code at validator.w3.org.
8. When you have some pages ready, send them to the tor-webmaster alias on the contact page. (If you have changes to existing pages, please use the diff tool to generate patch files, if possible.) If you plan to stick around and keep maintaining them, we'll be happy to give you an SVN account to manage them directly.