Fixed #10260 - Refactored internationalization documentation. Thanks, Ramiro Morales.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12440 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jannis Leidel 2010-02-16 12:12:53 +00:00
parent 9b630a0857
commit f93f056c32
12 changed files with 1293 additions and 1160 deletions

View file

@ -402,15 +402,18 @@ translated, here's what to do:
* Join the `Django i18n mailing list`_ and introduce yourself.
* Make sure you read the notes about :ref:`specialties-of-django-i18n`.
* Create translations using the methods described in the
:ref:`i18n documentation <topics-i18n>`. For this you will use the
``django-admin.py makemessages`` tool. In this particular case it should
be run from the top-level ``django`` directory of the Django source tree.
:ref:`localization documentation <topics-i18n-localization>`. For this
you will use the ``django-admin.py makemessages`` tool. In this
particular case it should be run from the top-level ``django`` directory
of the Django source tree.
The script runs over the entire Django source tree and pulls out all
strings marked for translation. It creates (or updates) a message file in
the directory ``conf/locale`` (for example for ``pt-BR``, the file will be
``conf/locale/pt-br/LC_MESSAGES/django.po``).
the directory ``conf/locale`` (for example for ``pt_BR``, the file will be
``conf/locale/pt_BR/LC_MESSAGES/django.po``).
* Make sure that ``django-admin.py compilemessages -l <lang>`` runs without
producing any warnings.
@ -419,7 +422,11 @@ translated, here's what to do:
``-d djangojs`` command line option to the ``django-admin.py``
invocations).
* Create a diff of the ``.po`` file(s) against the current Subversion trunk.
* Optionally, review and update the ``conf/locale/<locale>/formats.py``
file to describe the date, time and numbers formatting particularities of
your locale. See :ref:`format-localization` for details.
* Create a diff against the current Subversion trunk.
* Open a ticket in Django's ticket system, set its ``Component`` field to
``Translations``, and attach the patch to it.