mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-03-31 19:46:42 +00:00
Code Issues 32 Releases Wiki Activity

Update contributing documentation for changed translation policy.

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15275 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jannis Leidel 2011-01-21 19:37:16 +00:00
parent 2f34d70bf2
commit 70a2a71c9b
1 changed files with 30 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
docs/internals/contributing.txt
View File

@ -411,34 +411,45 @@ translated, here's what to do:
* Make sure you read the notes about :ref:`specialties-of-django-i18n`. * Make sure you read the notes about :ref:`specialties-of-django-i18n`.
* Create translations using the methods described in the * Signup at `Transifex`_ and visit the `Django project page`_.
:doc:`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 * On the "`Translation Teams`_" page, choose the language team you want
strings marked for translation. It creates (or updates) a message file in to work with, **or** -- in case the language team doesn't exist yet --
the directory ``conf/locale`` (for example for ``pt_BR``, the file will be request a new team by clicking on the "Request a new team" button
``conf/locale/pt_BR/LC_MESSAGES/django.po``). and select the appropriate language.
* Make sure that ``django-admin.py compilemessages -l <lang>`` runs without * Then, click the "Join this Team" button to become a member of this team.
producing any warnings. Every team has at least one coordinator who is responsible to review
your membership request. You can of course also contact the team
coordinator to clarify procedual problems and handle the actual
translation process.
* Repeat the last two steps for the ``djangojs`` domain (by appending the * Once you are a member of a team choose the translation resource you
``-d djangojs`` command line option to the ``django-admin.py`` want update on the team page. For example the "core" resource refers
invocations). to the translation catalogue that contains all non-app translations.
Each of the contrib apps also have a resource -- prefixed with "contrib-".
.. note::
For more information about how to use Transifex, see the
`Transifex Help`_
* Optionally, review and update the ``conf/locale/<locale>/formats.py`` * Optionally, review and update the ``conf/locale/<locale>/formats.py``
file to describe the date, time and numbers formatting particularities of file to describe the date, time and numbers formatting particularities
your locale. See :ref:`format-localization` for details. of your locale. These files aren't covered by the use of Transifex and
require a patch against the Django source tree, just as a code change
would:
* Create a diff 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 * Open a ticket in Django's ticket system, set its ``Component`` field
``Translations``, and attach the patch to it. to ``Translations``, and attach the patch to it. See
:ref:`format-localization` for details.
.. _Django i18n mailing list: http://groups.google.com/group/django-i18n/ .. _Django i18n mailing list: http://groups.google.com/group/django-i18n/
.. _Transifex: http://www.transifex.net/
.. _Django project page: http://www.transifex.net/projects/p/django/
.. _translation teams: http://www.transifex.net/projects/p/django/teams/
.. _Transifex Help: http://help.transifex.net/
Submitting javascript patches Submitting javascript patches
============================= =============================