translations.txt 3.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. ## Instructions for helping translate text for Vidalia and TorButton
  2. ## ( More translation information for Tor related apps will accumulate here )
  3. You'll need an account on launchpad[0] and you'll want to request access.
  4. Access will need to be granted by either Matt or Jacob.
  5. Uploading new translations is quite simple. First you'll need to checkout
  6. the source to Vidalia. Then you'll want to change into the i18n directory:
  7. cd vidalia/src/vidalia/i18n;
  8. Now you'll run the proper commands[1] to convert from the native QT .ts format.
  9. You'll want to convert the .ts format into gnugettext .po files. Do so like so:
  10. for file in `ls -1|grep .ts$|cut -f1 -d.`;
  11. do
  12. echo "Attempting to convert" $file.ts;
  13. ts2po --input=$file.ts --output=$file.po;
  14. done
  15. This is pretty straight forward but also error prone. You'll want to check for
  16. proper formatting of the .po files like so:
  17. for file in `ls -1|grep .po$`
  18. do
  19. msgfmt -c $file;
  20. done
  21. You have to correct all duplicate strings and all errors before uploading.
  22. Ensure that the .po files are valid, possibly by compiling them into .mo files:
  23. for file in `ls -1|grep .po$|cut -f1 -d.`
  24. do
  25. msgfmt -o $file.mo $file.po;
  26. file $file.mo;
  27. done
  28. If you're able to make proper .mo files and you have no errors, you're probably
  29. ready to upload the .po files for translation. A proper .mo file may look like:
  30. "GNU message catalog (little endian), revision 0, 11 messages"
  31. Once you have the current selection of .po files, you'll want to make a .tgz:
  32. tar -cvzf vidalia.tar.gz *.po;
  33. Now you're ready to upload 'vidalia.tar.gz' by visiting translation upload
  34. area of launchpad:
  35. https://translations.launchpad.net/vidalia/trunk/+translations-upload
  36. Once you've performed your upload, you will have to wait for admin approval.
  37. After approval, translators will be able to download the files and translate.
  38. When the files are ready to be put back into Vidalia's trunk repository, visit:
  39. https://translations.launchpad.net/vidalia/trunk/+export
  40. Download the files in the .po format by following the instructions on the above
  41. page. You should see something like:
  42. "When these translations have been exported, a message will be sent
  43. to your-launchpad-email@yourdoma.example. This message will tell you
  44. where you can download your file."
  45. Once you have the .po files, you'll want to make .ts files from them. To reverse
  46. the process and send .ts files to Matt, you'll want to do the following:
  47. for file in `ls -1|grep .po$|cut -f1 -d.`;
  48. do
  49. echo "Attempting to convert" $file.po;
  50. po2ts --input=$file.po --output=$file.ts;
  51. done
  52. If you're interested in helping to translate Torbutton, it uses Babelzilla[2].
  53. You'll need a login to Babelzilla just as you do with Launchpad. Once logged
  54. in visit the following page for progress information and downloads of templates:
  55. http://www.babelzilla.org/index.php?option=com_wts&Itemid=88&extension=3510&type=lang
  56. All information about locales can be viewed at the above url. Click on
  57. different languages to see their respective statistics. Explore.
  58. To download all locale strings with missing transations in their original
  59. form, you can visit this url:
  60. http://www.babelzilla.org/index.php?option=com_wts&Itemid=88&type=downloadtar&extension=3510
  61. To download all locale strings with missing translations as an empty string,
  62. you can visit this url:
  63. http://www.babelzilla.org/index.php?option=com_wts&Itemid=88&type=downloadempty&extension=3510
  64. If you plan to translate using Babelzilla often, you'll want to email
  65. tor-translation@torproject.org and discuss your desires. Sadly, there is a
  66. fixed number of translators allowed per project. To read more about Babelzilla
  67. please read their Q&A section:
  68. http://www.babelzilla.org/index.php?option=com_content&task=category&sectionid=3&id=7&Itemid=25
  69. [0] https://www.launchpad.net
  70. [1] These tools can be found in the Debian package 'translate-toolkit'
  71. [2] http://www.babelzilla.org/