Various parts of Django, such as the admin site and validation error messages,\nare internationalized. This means they display differently depending on each\nuser’s language or country. For this, Django uses the same internationalization\nand localization infrastructure available to Django applications, described in\nthe i18n documentation.
\nTranslations are contributed by Django users worldwide. The translation work is\ncoordinated at Transifex.
\nIf you find an incorrect translation or want to discuss specific translations,\ngo to the Django project page. If you would like to help out with\ntranslating or add a language that isn’t yet translated, here’s what to do:
\nJoin the Django i18n mailing list and\nintroduce yourself.
Make sure you read the notes about Specialties of Django translation.
Sign up at Transifex and visit the Django project page.
On the Django project page, choose the language you want to work on,\nor – in case the language doesn’t exist yet –\nrequest a new language team by clicking on the “Request language” link\nand selecting the appropriate language.
Then, click the “Join this Team” button to become a member of this team.\nEvery team has at least one coordinator who is responsible to review\nyour membership request. You can of course also contact the team\ncoordinator to clarify procedural problems and handle the actual\ntranslation process.
Once you are a member of a team choose the translation resource you\nwant to update on the team page. For example the “core” resource refers\nto the translation catalog that contains all non-contrib translations.\nEach of the contrib apps also have a resource (prefixed with “contrib”).
\n\nTranslations from Transifex are only integrated into the Django repository at\nthe time of a new feature release. We try to update them a second time\nduring one of the following patch releases, but that depends on the\ntranslation manager’s availability. So don’t miss the string freeze period\n(between the release candidate and the feature release) to take the opportunity\nto complete and fix the translations for your language!
\nYou can also review conf/locale/<locale>/formats.py. This file describes\nthe date, time and numbers formatting particularities of your locale. See\nFormat localization for details.
The format files aren’t managed by the use of Transifex. To change them, you\nmust create a patch against the\nDjango source tree, as for any code change:
\nCreate a diff against the current Git master branch.
Open a ticket in Django’s ticket system, set its Component field to\nTranslations, and attach the patch to it.
There is also an opportunity to translate the documentation, though this is a\nhuge undertaking to complete entirely (you have been warned!). We use the same\nTransifex tool. The\ntranslations will appear at https://docs.djangoproject.com/<language_code>/\nwhen at least the docs/intro/* files are fully translated in your language.