From 1b58b77f0d4b23d2be7c96af34636677ddb45a85 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Thu, 11 Sep 2008 03:32:28 +0000 Subject: Edited docs changes from [9010] and [9011] git-svn-id: http://code.djangoproject.com/svn/django/trunk@9014 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/internals/contributing.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/internals') diff --git a/docs/internals/contributing.txt b/docs/internals/contributing.txt index 0f94f5b380..a9cfdb94bc 100644 --- a/docs/internals/contributing.txt +++ b/docs/internals/contributing.txt @@ -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 `. 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 `` 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. -- cgit v1.3