localizing.txt 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677
  1. =================
  2. Localizing Django
  3. =================
  4. Various parts of Django, such as the admin site and validation error messages,
  5. are internationalized. This means they display differently depending on each
  6. user's language or country. For this, Django uses the same internationalization
  7. and localization infrastructure available to Django applications, described in
  8. the :doc:`i18n documentation </topics/i18n/index>`.
  9. Translations
  10. ------------
  11. Translations are contributed by Django users worldwide. The translation work is
  12. coordinated at `Transifex`_.
  13. If you find an incorrect translation or want to discuss specific translations,
  14. go to the `Django project page`_. If you would like to help out with
  15. translating or add a language that isn't yet translated, here's what to do:
  16. * Join the :ref:`Django i18n mailing list <django-i18n-mailing-list>` and
  17. introduce yourself.
  18. * Make sure you read the notes about :ref:`specialties-of-django-i18n`.
  19. * Sign up at `Transifex`_ and visit the `Django project page`_.
  20. * On the `Django project page`_, choose the language you want to work on,
  21. **or** -- in case the language doesn't exist yet --
  22. request a new language team by clicking on the "Request language" link
  23. and selecting the appropriate language.
  24. * Then, click the "Join this Team" button to become a member of this team.
  25. Every team has at least one coordinator who is responsible to review
  26. your membership request. You can of course also contact the team
  27. coordinator to clarify procedural problems and handle the actual
  28. translation process.
  29. * Once you are a member of a team choose the translation resource you
  30. want to update on the team page. For example the "core" resource refers
  31. to the translation catalog that contains all non-contrib translations.
  32. Each of the contrib apps also have a resource (prefixed with "contrib").
  33. .. note::
  34. For more information about how to use Transifex, read the
  35. `Transifex User Guide`_.
  36. Formats
  37. -------
  38. You can also review ``conf/locale/<locale>/formats.py``. This file describes
  39. the date, time and numbers formatting particularities of your locale. See
  40. :ref:`format-localization` for details.
  41. The format files aren't managed by the use of Transifex. To change them, you
  42. must :doc:`create a patch<writing-code/submitting-patches>` against the
  43. Django source tree, as for any code change:
  44. * Create a diff against the current Git master branch.
  45. * Open a ticket in Django's ticket system, set its ``Component`` field to
  46. ``Translations``, and attach the patch to it.
  47. .. _Transifex: https://www.transifex.com/
  48. .. _Django project page: https://www.transifex.com/projects/p/django/
  49. .. _Transifex User Guide: http://support.transifex.com/
  50. .. _translating-documentation:
  51. Documentation
  52. -------------
  53. There is also an opportunity to translate the documentation, though this is a
  54. huge undertaking to complete entirely (you have been warned!). We use the same
  55. `Transifex tool <https://www.transifex.com/projects/p/django-docs/>`_. The
  56. translations will appear at ``https://docs.djangoproject.com/<language_code>/``
  57. when at least the ``docs/intro/*`` files are fully translated in your language.