#35181: behaviour of makemessage dont follow documentation
-------------------------------------+-------------------------------------
     Reporter:  Pierre               |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Documentation        |                  Version:  4.2
     Severity:  Normal               |               Resolution:  needsinfo
     Keywords:  translation,         |             Triage Stage:
  makemessage                        |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Pierre):

 As I understand it, LOCALE_PATHS  is only used to find the .mo files but
 not to tell were are going the .po files, which go in the locale folder of
 the app if it exists, or in the locale folder of the project if it exists.
 On [this
 page](https://docs.djangoproject.com/fr/4.2/topics/i18n/translation/) it
 is written
 "The script runs over your project source tree or your application source
 tree and pulls out all strings marked for translation (see How Django
 discovers translations and be sure LOCALE_PATHS is configured correctly)"
 Actually at this stage (creation of the .po files), the LOCALE_PATHS
 didn't work for me, but maybe it is related to my OS (windows 10).

 It is also written:
 "A string extracted from a file of an app without any locale directory
 will either go in a message file under the directory listed first in
 LOCALE_PATHS or will generate an error if LOCALE_PATHS is empty."
 If I have a locale folder in my project folder, the .po files can go
 there, even without LOCALE_PATHS defined.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35181#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018dbb9e22a2-873b6d63-9dc8-487a-8886-d501409a626a-000000%40eu-central-1.amazonses.com.

Reply via email to