summaryrefslogtreecommitdiff
path: root/docs/internals
diff options
context:
space:
mode:
authorJannis Leidel <jannis@leidel.info>2010-02-16 12:50:47 +0000
committerJannis Leidel <jannis@leidel.info>2010-02-16 12:50:47 +0000
commita23edb643bdbfde6be1e0a63d1a8bd2a1be13710 (patch)
tree7b0e171424472c241fc5865d159cbdac3b50dc69 /docs/internals
parent4384b164ccdd2d45e38cc3116f9e49c50c4268fa (diff)
[1.1.X] Fixed #10260 - Refactored internationalization documentation. Thanks, Ramiro Morales.
Partial backport of r12440. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12449 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/internals')
-rw-r--r--docs/internals/contributing.txt15
1 files changed, 9 insertions, 6 deletions
diff --git a/docs/internals/contributing.txt b/docs/internals/contributing.txt
index dd66ecfe92..007de8bdf8 100644
--- a/docs/internals/contributing.txt
+++ b/docs/internals/contributing.txt
@@ -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,7 @@ 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.
+ * 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.