Localizing Django

Translations are contributed by Django users worldwide. The translation work is coordinated at .

If you find an incorrect translation or want to discuss specific translations, go to the Django project page. If you would like to help out with translating or add a language that isn’t yet translated, here’s what to do:

Make sure you read the notes about .
On the Django project page, choose the language you want to work on, or – in case the language doesn’t exist yet – request a new language team by clicking on the “Request language” link and selecting the appropriate language.
Once you are a member of a team choose the translation resource you want to update on the team page. For example the “core” resource refers to the translation catalog that contains all non-contrib translations. Each of the contrib apps also have a resource (prefixed with “contrib”).

Note

Translations from Transifex are only integrated into the Django repository at the time of a new . We try to update them a second time during one of the following patch releases, but that depends on the translation manager’s availability. So don’t miss the string freeze period (between the release candidate and the feature release) to take the opportunity to complete and fix the translations for your language!

You can also review . This file describes the date, time and numbers formatting particularities of your locale. See for details.

The format files aren’t managed by the use of Transifex. To change them, you must create a patch against the Django source tree, as for any code change:

Create a diff against the current Git master branch.
Open a ticket in Django’s ticket system, set its field to , and attach the patch to it.

There is also an opportunity to translate the documentation, though this is a huge undertaking to complete entirely (you have been warned!). We use the same . The translations will appear at when at least the files are fully translated in your language.