mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 18:38:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Edited docs changes from [9010] and [9011]

Browse source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9014 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2008-09-11 03:32:28 +00:00
parent 8c6f5c6f05
commit 1b58b77f0d
2 changed files with 30 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/internals/contributing.txt
View file

@ -399,7 +399,7 @@ incorrect translation, or if you'd like to add a language that isn't yet
translated, here's what to do:
* Join the `Django i18n mailing list`_ and introduce yourself.
* 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
@ -409,16 +409,16 @@ translated, here's what to do:
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``).
* Make sure that ``django-admin.py compilemessages -l <lang>`` runs without
producing any warnings.
* Repeat the last two steps for the ``djangojs`` domain (by appending the
``-d djangojs`` command line option to the ``django-admin.py``
invocations.)
invocations).
* Create a diff of the ``.po`` file(s) 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.