How to Send Translations

The best way to send in translations - after registering oneself as translator above - is to create a ticket and to attach the new .po file to that ticket (please don't attach .po files to this page, use the ticket system!). Use "Translations" as the component when you file the ticket, so that it shows up in {13}.

How to Update Translations

Ensure that you are running the latest subversion checkout of the code - run "svn update" in your local django subversion copy.

Run bin/make-messages.py -l <locale> and you get updated .po files

Update any untranslated and fuzzy messages with your favorite translation tool. Anything that looks like "%s" or "%(something)s" has to be copied precisely and the 's' may be a 'd' or 'x' or 'i', possibly.

Run bin/compile-messages.py -l <locale> and ensure there are no errors.

Upload the complete new .po files to Trac.

It is best practice to just check every few weeks (once a month or so if you're really enthusiastic; less often if you're
not) to see if there's been any big changes.

Prior to any release, Django maintainers will make an announcement. Prior to 1.0, we'll have a couple of weeks of string freeze in order to give people time to be 100% translated.

Tools

This should be a list of useful (and needed) software for translators to work on .po files.

Linux and other Unix Systems

required for make-messages.py and compile-messages.py: the gettext utilities. These should be available with your distribution. With Debian based distributions it is the gettext package.

Mac OS X

Translations of the Django documentation

If for some reason you are not interested to translate Django interface, but instead you feel the desire to point your translation weapons against Django documentation (the content of '/docs'), you are invited to use the TranslateDocumentation wiki page to better organize your translation works together with other translators.