On Mon, Sep 8, 2008 at 12:53 PM, timc3 <[EMAIL PROTECTED]> wrote:
>
>> 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/

Shouldn't you run it from the mysite/ directory? Even further, now that I think
about it, you should can simplify things by simply manually
creating the mysite/locale directory  and then doing

mysite $ python manage.py makemesages -l se

(just tested it and it works)

(manage.py is functionally equivalent to django-admin.py but
it knows it should use the settings.py file located in the
same directory).

>
> And the django.po file has longer paths to everything.

The paths in the PO file comments have no effect.

HTH,

-- 
 Ramiro Morales

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to