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 adding a language that isn’t yet translated, here’s what to do:
\nIntroduce yourself on the Django internationalization forum.
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 also contact the team coordinator to clarify\nprocedural problems and handle the actual translation 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 has 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\nthem a second time during one of the following patch releases, but that depends on the translation manager’s availability.\nSo don’t miss the string freeze period (between the release candidate and the\nfeature release) to take the opportunity to complete and fix the translations\nfor 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:
\nCreate a pull request against the Django Git\nmain branch, as for any code change.
Open a ticket in Django’s ticket system, set its Component field to\nTranslations, set the «has patch» flag, and include the link to the pull\nrequest.
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.
Once translations are published, updated versions from Transifex will be\nirregularly ported to the django/django-docs-translations repository and to the\ndocumentation website. Only translations for the latest stable Django release\nare updated.
\n