Skip to content
Browse files

[1.6.x] Fixed #20690 -- Mentioned LOCALE_PATHS earlier in translation…

… docs.

Thanks rene@ for the suggestion.

Backport of 231e31c from master.
  • Loading branch information...
1 parent 2de0d4c commit 25b9939fed397c0764fea22b72e7e94baf9505b9 @timgraham timgraham committed
Showing with 5 additions and 3 deletions.
  1. +5 −3 docs/topics/i18n/translation.txt
8 docs/topics/i18n/translation.txt
@@ -1242,9 +1242,11 @@ The script should be run from one of two places:
* The root directory of your Django app.
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
-message file in the directory ``locale/LANG/LC_MESSAGES``. In the ``de``
-example, the file will be ``locale/de/LC_MESSAGES/django.po``.
+and pulls out all strings marked for translation (see
+:ref:`how-django-discovers-translations` and be sure :setting:`LOCALE_PATHS`
+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
By default :djadmin:` makemessages <makemessages>` examines every
file that has the ``.html`` or ``.txt`` file extension. In case you want to

0 comments on commit 25b9939

Please sign in to comment.
Something went wrong with that request. Please try again.