igit.exe added

[TortoiseGit.git] / Languages / translations.txt

Translations\r
------------\r
\r
TortoiseSVN is still in development so translations of all resources is\r
also a work 'in progress'.\r
\r
General\r
-------\r
The TortoiseSVN project uses gettext PO (portable object) files for its\r
translation. PO files are plain text, so you can even translate using a\r
normal text editor. The only thing you have to take care of is that the\r
editor can handle the UTF-8 charset. There is a wide range of tools out\r
there that can handle and manipulate PO files.\r
We recommend that you use poEdit (http://poedit.sourceforge.net) on Windows\r
or kbabel (http://i18n.kde.org/tools/kbabel/) on Linux.\r
\r
This description assumes that you use poEdit.\r
\r
Getting started\r
---------------\r
If you want to implement a new language for TortoiseSVN do the following.\r
\r
1) Use TortoiseSVN (or any other SubVersion client) to check out:\r
   http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Languages/\r
   (You will get more than one file)\r
   or point your browser to:\r
   http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/Languages/\r
   right-click on Tortoise.pot and save this file to your local harddisk.\r
   Tortoise.pot is the portable object template (hence .pot) for the\r
   translation.\r
\r
2) Rename Tortoise.pot to Tortoise_xx.po, where xx is your two letter\r
   ISO-639-1 language code. Look up your language code here:\r
   http://www.loc.gov/standards/iso639-2/langcodes.html\r
   If you want to translate into a language that has two different locales\r
   and you *really* need the second locale, add the two letter ISO-3166\r
   locale code. If you're not sure about your country code, look here:\r
   http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html.\r
   Please keep in mind that we would like to have as few translations as\r
   possible that cover as many languages as possible. We would not be\r
   very happy at having to maintain a (de_CH) Swiss German, (de_AT)\r
   Austrian German and (de_DE) German German translation. :-)\r
   But if it's necessary like in Chinese, sure go ahead. We are happy with\r
   simplified (zh_CN) and traditional (zh_TW) Chinese.\r
\r
3) Now translate what you can using poEdit. If you are not sure with one\r
   or the other translation, mark it as "fuzzy". You can enter a comment\r
   in poEdit to give some information about your thoughts to other trans-\r
   lators.\r
   If you are not sure about the meaning of the original sentence ask on\r
   the list.\r
\r
4) Add a header with '#' comments to the PO file using a normal text edi-\r
   tor that explains which language you translated and the terminology\r
   you used, like:\r
   #\r
   # German translations for TortoiseSVN\r
   # This file is distributed under the same license as the subversion package.\r
   #\r
   # Translation dictionary:\r
   #\r
   # argument     parameter\r
   # bogus        ungültig\r
   # checkout     auschecken (denglisch, ich weiß, aber akzeptabel)\r
   # client       Client, des Client\r
   # commit       übertragen\r
   # item         Objekt\r
   # label        Marke / Markierung\r
\r
5) Make sure your file is saved in UTF-8 encoding and that it does *not*\r
   begin with UTF-8 BOMs (Byte Order Marks)\r
\r
6) Send your Tortoise_xx.po to the mailing list (tortoisegit-dev@googlegroups.com\r
).\r
\r
Adding to an existing translation\r
---------------------------------\r
1) Get hold of Tortoise.pot and the Tortoise_xx.po you want to improve\r
\r
2) Start poEdit with Tortoise_xx.po and select "Update from .pot file"\r
   from the "Catalog" Menu\r
\r
3) Select Tortoise.pot and wait until poEdit has finished merging the\r
   template and the current translation.\r
\r
4) The untranslated strings (and fuzzy translations) are always at the\r
   top of the list.\r
\r
5) Translate what you can and send the resulting PO file back to the\r
   mailing list (patches@tortoisesvn.tigris.org).\r
\r
Format your translation\r
--------------------------\r
Please format your translation before send Tortoise_xx.po to the\r
mailing list, or commit to the TortoiseSVN repository. You can do it\r
like this:\r
    $ msgmerge --no-wrap -o Tortoise_xx.po.new Tortoise_xx.po Tortoise.pot\r
    $ mv -f Tortoise_xx.po.new Tortoise_xx.po\r
\r
This can minimize the svn diff output, review your translation is easy.\r
\r
What now?\r
---------\r
That's all you have to do. We'll take care of creating the resource dlls\r
and installers for the different language packs.\r
\r
Building your own dlls\r
----------------------\r
If you want to test the translations you made yourself, before you release\r
them, you need four things:\r
\r
#The Below is tortoiseSVN document. \r
\r
- The "raw" resource dlls for your version of TortoiseSVN. Other dlls\r
  won't work. Take a look at:\r
  http://tortoisesvn.tigris.org/servlets/ProjectDocumentList?folderID=1847\r
  and pick your language dlls e.g. Languages_1.0.8.zip for TortoiseSVN 1.0.8.\r
- The pot file for your version of TortoiseSVN e.g:\r
  http://tortoisesvn.tigris.org/svn/tortoisesvn/tags/version_1.0.8/...\r
- Any po file for your language. Either pick one from tags or the latest\r
  po file from trunk\r
- The ResText utility that is used to insert the data from the po file\r
  into your resource dlls:\r
  http://tortoisesvn.tigris.org/files/documents/406/14560/ResText.zip\r
\r
Once you finished your installation, you run:\r
\r
restext apply TortoiseProcLang.dll ..\bin\TortoiseProcNNNN.dll Tortoise_CC.po\r
restext apply TortoiseMergeLang.dll ..\bin\TortoiseMergeNNNN.dll Tortoise_CC.po\r
\r
where NNNN is your four digit country code (1031 for germany)\r
and CC is your 2 letter country code (de for germany)\r
\r
You can find the four digit country code at\r
http://www.microsoft.com/globaldev/reference/lcid-all.mspx\r
under the column LCID dec.\r
\r
After successfully creating your dlls, copy them into:\r
C:\Program Files\TortoiseSVN\Languages\r
Now you should be able to select your language from the combobox on the\r
TortoiseSVN main setting page.\r