[1.6.x] Fixed #20690 -- Mentioned LOCALE_PATHS earlier in translation docs.
Thanks rene@ for the suggestion.
Backport of 231e31c690
from master.
This commit is contained in:
parent
2de0d4c452
commit
25b9939fed
|
@ -1242,9 +1242,11 @@ The script should be run from one of two places:
|
||||||
* The root directory of your Django app.
|
* The root directory of your Django app.
|
||||||
|
|
||||||
The script runs over your project source tree or your application source tree
|
The script runs over your project source tree or your application source tree
|
||||||
and pulls out all strings marked for translation. It creates (or updates) a
|
and pulls out all strings marked for translation (see
|
||||||
message file in the directory ``locale/LANG/LC_MESSAGES``. In the ``de``
|
:ref:`how-django-discovers-translations` and be sure :setting:`LOCALE_PATHS`
|
||||||
example, the file will be ``locale/de/LC_MESSAGES/django.po``.
|
is configured correctly). It creates (or updates) a message file in the
|
||||||
|
directory ``locale/LANG/LC_MESSAGES``. In the ``de`` example, the file will be
|
||||||
|
``locale/de/LC_MESSAGES/django.po``.
|
||||||
|
|
||||||
By default :djadmin:`django-admin.py makemessages <makemessages>` examines every
|
By default :djadmin:`django-admin.py makemessages <makemessages>` examines every
|
||||||
file that has the ``.html`` or ``.txt`` file extension. In case you want to
|
file that has the ``.html`` or ``.txt`` file extension. In case you want to
|
||||||
|
|
Loading…
Reference in New Issue