Home › Translations

Instructions

TortoiseSVN is still in development so the translation of all resources is also a work 'in progress'.

General

The TortoiseSVN project uses gettext PO (portable object) files for its translation. PO files are plain text, so you can even translate using a normal text editor. The only thing you have to take care of is that the editor can handle the UTF-8 charset. There is a wide range of tools out there that can handle and manipulate PO files.

We recommend that you use poEdit on Windows or KBabel on Linux.

This description assumes that you use poEdit.

Getting started

If you want to implement a new language for TortoiseSVN do the following.

  1. Use TortoiseSVN (or any other SubVersion client) to check out:
    http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Languages/ (You will get more than one file).

    Or point your browser to:
    http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Languages/, right-click on Tortoise.pot and save this file to your local harddisk. Tortoise.pot is the portable object template (hence .pot) for the translation.

  2. Rename Tortoise.pot to Tortoise_xx.po, where xx is your two letter ISO-639-1 language code. Look up your language code here: http://www.loc.gov/standards/iso639-2/langcodes.html.

    If you want to translate into a language that has two different locales and you really need the second locale, add the two letter ISO-3166 locale code. If you're not sure about your country code, look here: http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html.

    Please keep in mind that we would like to have as few translations as possible that cover as many languages as possible. We would not be very happy at having to maintain a (de_CH) Swiss German, (de_AT) Austrian German and (de_DE) German German translation. :-)
    But if it's necessary like in Chinese, sure go ahead. We are happy with simplified (zh_CN) and traditional (zh_TW) Chinese.

  3. It would also be nice, if you sent us your four digit locale ID along with the file. The list of locale IDs as defined by Microsoft can be found here: http://www.microsoft.com/globaldev/reference/lcid-all.mspx
  4. Now translate what you can using poEdit. If you are not sure with one or the other translation, mark it as fuzzy. You can enter a comment in poEdit to give some information about your thoughts to other translators.
    If you are not sure about the meaning of the original sentence ask on the list.
  5. Add a header with '#' comments to the PO file using a normal text editor that explains which language you translated and the terminology you used, like:

    #
    # German translations for TortoiseSVN
    # This file is distributed under the same license as the subversion package.
    #
    # Translation dictionary:
    #
    # argument parameter
    # bogus ungültig
    # checkout auschecken (denglisch, ich weiss, aber akzeptabel)
    # client Client, des Client
    # commit Übertragen
    # item Objekt
    # label Marke / Markierung
  6. Make sure your file is saved in UTF-8 encoding and that it does not begin with UTF-8 BOMs (Byte Order Marks)
  7. Send your Tortoise_xx.po to the mailing list (dev@tortoisesvn.tigris.org) or, if you have a Tigris ID and request a role in the project and is granted the role by the project admins, you may commit your translations directory to the TortoiseSVN repository.

Adding to an existing translation

  1. Get hold of Tortoise.pot and the Tortoise_xx.po you want to improve
  2. Start poEdit with Tortoise_xx.po and select Update from .pot file from the "Catalog" Menu
  3. Select Tortoise.pot and wait until poEdit has finished merging the template and the current translation.
  4. The untranslated strings (and fuzzy translations) are always at the top of the list.
  5. Translate what you can and send the resulting PO file back to the mailing list (dev@tortoisesvn.tigris.org).

What now?

That's all you have to do. We'll take care of creating the resource dlls and installers for the different language packs.

Testing your translation

If you want to test the translations you made yourself, just wait for the next nightly build.
The nightly build is done every night at 0:00 GMT+1. The whole build takes about an hour. After the build is done, the installers (including the language packs) are uploaded for you to use.

‹ Documentationup