Update "TRANSLATING" with gettext and Transifex instructions.

Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>

TRANSLATING

 AUR Translation
 ================
 
-This document describes how to create and maintain AUR translations.
-It was derived from http://wiki.archlinux.org/index.php/AUR_Translation
+This document describes how to create and maintain AUR translations. It was
+originally derived from http://wiki.archlinux.org/index.php/AUR_Translation
 
-Creating an AUR translation requires python and git to be installed.
-
-Translation files should be gzipped to protect from possible encoding
-errors when submitting. Tarring is not necessary.
-
-You will need to register on the mailing list before submitting:
-http://mailman.archlinux.org/mailman/listinfo/aur-dev
-
-Patches should be sent to the aur-dev mailing list at:
-aur-dev@archlinux.org
+Creating an AUR translation requires a Transifex (http://www.transifex.net/)
+account. You will need to register with a translation team on the AUR project
+page (http://www.transifex.net/projects/p/aur/).
 
 
 Creating a New Translation
 ---------------------------
 
-Before beginning, please make sure that git and python are installed.
-Also, please do not translate if you are unwilling to maintain or find
-someone to maintain the translation. This is due to the fact that the
-AUR is a rapidly evolving project and there are constantly new strings
-to be translated. If the translations get too out of sync with the
-released versions, there will be too many untranslated strings for the
-translation to be usable, and it may have to be disabled.
+Before beginning, please sign up for an Transifex account and request the
+addition of a new translation team for the AUR project. Also, please do not
+translate if you are unwilling to maintain or find someone to maintain the
+translation. This is due to the fact that the AUR is a rapidly evolving project
+and there are constantly new strings to be translated. If the translations get
+too out of sync with the released versions, there will be too many untranslated
+strings for the translation to be usable, and it may have to be disabled.
 
-1. Check out the AUR source using git.
+1. Check out the AUR source using git:
 
 $ git clone git://projects.archlinux.org/aur.git aur-git
 
-2. Go into the AUR source and run translation_tool.
-   translation_tool will interactively guide you through the translation
-   process, simply answer its questions and prompts. If you wish to stop
-   at some point during the translation, you may kill translation_tool
-   using Ctrl+C. If you later wish to continue the translation, simply
-   run translation_tool again, and it will continue from where you left off.
+2. Go into the "po/" directory in the AUR source and run msginit(1) to create a
+   initial translation file from our translation catalog:
 
 $ cd aur-git
 $ git checkout master
 $ git pull
-$ cd web/lang
-$ ./translation_tool
-
-3. Add a line for the new translation in web/lib/config.inc.proto
-4. Add an entry in the AUTHORS file.
-
-5. To commit your patch to your branch:
-
-$ git add <all edited files>
-$ git commit -s
+$ cd po
+$ msginit -l <locale> -o <locale>.po -i aur.pot
 
-Write your commit message above the sign off and separate them by a
-blank line.
+3. Use some editor or a translation helper like poedit to add translations:
 
-6. Create a git formatted patch.
+$ poedit <locale>.po
 
-$ git format-patch origin/master
+5. If you have a working AUR setup, add a line for the new translation in
+   "web/lib/config.inc.proto" and test if everything looks right.
 
-7. Send the gzipped patch to the aur-dev mailing list.
+6. Upload the newly created ".po" file to Transifex. If you don't like the web
+   interface, you can also use transifex-client to do that (see below).
 
 
 Updating an Existing Translation
 ---------------------------------
 
-1. Update your copy of the AUR code.
-
-$ cd aur-git
-$ git pull
-
-2. Run translation_tool, which will only prompts for strings that have
-   changed or been added since the last translation.
-
-$ cd web/lang
-$ ./translation_tool
-
-3. To commit your patch to your branch:
+1. Download current translation files from Transifex. You can also do this
+   using transifex-client which is available through the AUR:
 
-$ git add <all edited files>
-$ git commit -s
+$ tx init --host=http://www.transifex.net
+$ tx set --auto-remote http://www.transifex.net/projects/p/aur
+$ tx pull -r aur.aurpot -a
 
-4. Create a git formatted patch.
+2. Update the existing translation file using an editor or a tool like poedit:
 
-$ git format-patch origin/master
+$ poedit <locale>.po
 
-5. Send the gzipped patch to the aur-dev mailing list.
+3. Push the updated translation file back to Transifex. Using transifex-client,
+   this works as follows:
 
+$ tx push -r aur.aurpot -t -l <locale>