| 1 |
================= |
| 2 |
Localizing Django |
| 3 |
================= |
| 4 |
|
| 5 |
Various parts of Django, such as the admin site and validation error messages, |
| 6 |
are internationalized. This means they display differently depending on each |
| 7 |
user's language or country. For this, Django uses the same internationalization |
| 8 |
and localization infrastructure available to Django applications, described in |
| 9 |
the :doc:`i18n documentation </topics/i18n/index>`. |
| 10 |
|
| 11 |
Translations |
| 12 |
============ |
| 13 |
|
| 14 |
Translations are contributed by Django users worldwide. The translation work is |
| 15 |
coordinated at `Transifex`_. |
| 16 |
|
| 17 |
If you find an incorrect translation or want to discuss specific translations, |
| 18 |
go to the `Django project page`_. If you would like to help out with |
| 19 |
translating or adding a language that isn't yet translated, here's what to do: |
| 20 |
|
| 21 |
* Introduce yourself on the `Django internationalization forum`_. |
| 22 |
|
| 23 |
* Make sure you read the notes about :ref:`specialties-of-django-i18n`. |
| 24 |
|
| 25 |
* Sign up at `Transifex`_ and visit the `Django project page`_. |
| 26 |
|
| 27 |
* On the `Django project page`_, choose the language you want to work on, |
| 28 |
**or** -- in case the language doesn't exist yet -- |
| 29 |
request a new language team by clicking on the "Request language" link |
| 30 |
and selecting the appropriate language. |
| 31 |
|
| 32 |
* Then, click the "Join this Team" button to become a member of this team. |
| 33 |
Every team has at least one coordinator who is responsible to review |
| 34 |
your membership request. You can also contact the team coordinator to clarify |
| 35 |
procedural problems and handle the actual translation process. |
| 36 |
|
| 37 |
* Once you are a member of a team choose the translation resource you |
| 38 |
want to update on the team page. For example, the "core" resource refers |
| 39 |
to the translation catalog that contains all non-contrib translations. |
| 40 |
Each of the contrib apps also has a resource (prefixed with "contrib"). |
| 41 |
|
| 42 |
.. note:: |
| 43 |
For more information about how to use Transifex, read the |
| 44 |
`Transifex User Guide`_. |
| 45 |
|
| 46 |
Translations from Transifex are only integrated into the Django repository at |
| 47 |
the time of a new :term:`feature release <Feature release>`. We try to update |
| 48 |
them a second time during one of the following :term:`patch release |
| 49 |
<Patch release>`\s, but that depends on the translation manager's availability. |
| 50 |
So don't miss the string freeze period (between the release candidate and the |
| 51 |
feature release) to take the opportunity to complete and fix the translations |
| 52 |
for your language! |
| 53 |
|
| 54 |
Formats |
| 55 |
======= |
| 56 |
|
| 57 |
You can also review ``conf/locale/<locale>/formats.py``. This file describes |
| 58 |
the date, time and numbers formatting particularities of your locale. See |
| 59 |
:doc:`/topics/i18n/formatting` for details. |
| 60 |
|
| 61 |
The format files aren't managed by the use of Transifex. To change them, you |
| 62 |
must: |
| 63 |
|
| 64 |
* :doc:`Create a pull request<writing-code/submitting-patches>` against the |
| 65 |
Django Git ``main`` branch, as for any code change. |
| 66 |
|
| 67 |
* Open a ticket in Django's ticket system, set its ``Component`` field to |
| 68 |
``Translations``, set the "has patch" flag, and include the link to the pull |
| 69 |
request. |
| 70 |
|
| 71 |
.. _Transifex: https://www.transifex.com/ |
| 72 |
.. _Django project page: https://app.transifex.com/django/django/ |
| 73 |
.. _Django internationalization forum: https://forum.djangoproject.com/c/internals/i18n/14 |
| 74 |
.. _Transifex User Guide: https://help.transifex.com/ |
| 75 |
|
| 76 |
.. _translating-documentation: |
| 77 |
|
| 78 |
Documentation |
| 79 |
============= |
| 80 |
|
| 81 |
There is also an opportunity to translate the documentation, though this is a |
| 82 |
huge undertaking to complete entirely (you have been warned!). We use the same |
| 83 |
`Transifex tool <https://app.transifex.com/django/django-docs/>`_. The |
| 84 |
translations will appear at ``https://docs.djangoproject.com/<language_code>/`` |
| 85 |
when at least the ``docs/intro/*`` files are fully translated in your language. |
| 86 |
|
| 87 |
Once translations are published, updated versions from Transifex will be |
| 88 |
irregularly ported to the `django/django-docs-translations |
| 89 |
<https://github.com/django/django-docs-translations>`_ repository and to the |
| 90 |
documentation website. Only translations for the latest stable Django release |
| 91 |
are updated. |