> I'd say that for being able to scan you project's locale/ subdir > (althouth this isnĀ“t obvious from the docs) and the dirs listed in > LOCALE_PATHS you need specify the Python module path of > your settings file with the --settings command line switch > as explained in: > > http://docs.djangoproject.com/en/dev/topics/i18n/#using-translations-... > > You might also want to take a look at > > http://docs.djangoproject.com/en/dev/topics/i18n/#message-files > > (Yes, we need to refactor and enhance that document.) >
When I run it from the directory above and putting in -- settings=mysite/settings I get the django.po file created, but two problems (perhaps). The locale directory is on the same level as the template and site directory: code/ -mysite/ --mysiteapp1/ --mysiteapp2/ --settings.py --manage.py -mysitetemplates/ -mysitestaticmedia/ -locale/ And the django.po file has longer paths to everything. Is this intended and correct behaviour? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---