Localizing Django

Translations are contributed by Django users worldwide. The translation work iscoordinated at Transifex.

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

Make sure you read the notes about Specialties of Django translation.
On the , 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” linkand selecting the appropriate language.
Once you are a member of a team choose the translation resource youwant to update on the team page. For example the “core” resource refersto 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 atthe time of a new feature release. We try to update them a second timeduring one of the following s, but that depends on thetranslation manager’s availability. So don’t miss the string freeze period(between the release candidate and the feature release) to take the opportunityto complete and fix the translations for your language!

You can also review . This file describesthe date, time and numbers formatting particularities of your locale. SeeFormat localization for details.

The format files aren’t managed by the use of Transifex. To change them, youmust against theDjango 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 ahuge undertaking to complete entirely (you have been warned!). We use the sameTransifex tool. Thetranslations will appear at when at least the files are fully translated in your language.