Translating Vidalia

  1. Translating Vidalia's GUI
  2. Translating Vidalia's help content
  3. Available help translations
  4. Translating Vidalia Win32 Installers
  5. Available Win32 Installer Translations

Translating Vidalia's GUI

Vidalia uses Tor's translation portal to manage GUI translations. Tor's website has instructions on creating an account and committing new translations.

Translating Vidalia's help content

Using Vidalia is perhaps initially difficult for some people if English is not their native language. We need people to help translate our documentation to languages other then English. Here are instructions on how to do it:

  1. Download all the files from here and put them in a folder.
  2. Open one of the HTML files in a text editor or a webpage editor and translate all the text from headers and normal text. Do not the link addresses or anchors, such as <a href="server.html"> and <a name="general"/> .
  3. Open another HTML file and translate it like in Step 2 until you have done them all, or as many as you feel like translating.
  4. When all the HTML files are translated, then the table of contents file (contents.xml) should be translated. For this I suggest using a text editor, because many webpage editors don't understand XML properly. You will have to just open it and translate the name="xxxxxxxx" part of each <topic .... />.
  5. When you are finished, you can send them all separately or packed in a .tar or .zip file to translations@….

Available help translations

This is a list of translations we currently have and the people who have contributed to them:

Feel free to help keep these translations up-to-date.

Translating Vidalia Win32 Installers

Vidalia and Vidalia/Tor/Privoxy bundle Windows installers also support translations. Here's how to translate Vidalia's installer to your language:

  1. Download vidalia_en.nsh.
  2. Rename vidalia_en.nsh to vidalia_<country-code>.nsh for whatever language you're translating to. For example, a French translation would be named vidalia_fr.nsh. See this page for a list of ISO 639-1 (two letter) language codes.
  3. Replace all ${LANG_ENGLISH} tags with whatever language you are translating this file into. For example, if you are creating a French translation, all ${LANG_ENGLISH} tags would become ${LANG_FRENCH}.
  4. Translate the quoted strings. You can move string replacement tags (e.g., ${BUNDLE_NAME}) to the appropriate place within the quoted strings, but you should not alter the tags themselves.
  5. Send us your translated .nsh file at translations@…. Unlike translated .ts files, please make sure your translated documents do not use a Unicode character encoding, since NSIS does not support Unicode. Examples of acceptable character encodings are ISO-8859-1, Windows-1251, or other related encodings.

Available Win32 Installer Translations

This is a list of translations we currently have and the people who have contributed to them:

Feel free to help keep these translations up-to-date.