Yep. And now it works perfectly. Reading the documentation again and
again I see it is actually in the documentation! You have to very
carefully read the documentation.
What confused me was the following part in the documentation. It is the
paragraph called "How to create language files". It contains the
following part:
"The script [make-messages.py] should be run from one of three places:
* The root django directory (not a Subversion checkout, but the
one that is linked-to via $PYTHONPATH or is located somewhere on that
path).
* The root directory of your Django project.
* The root directory of your Django app.
The script runs over the entire Django source tree and pulls out all
strings marked for translation. It creates (or updates) a message file
in the directory conf/locale. In the de example, the file will be
conf/locale/de/LC_MESSAGES/django.po."
Reading this part (and also the error message from make-messages.py)
made me think I had to create a conf/locale directory in my project.
However, further down in the documentation in the paragraph "Using
translations in your own projects" it clearly states where the code
will look for language files:
" * First, it looks for a locale [so NOT conf/locale!] directory
in the application directory of the view that's being called. If it
finds a translation for the selected language, the translation will be
installed.
* Next, it looks for a locale [so NOT conf/locale!] directory
in the project directory. If it finds a translation, the translation
will be installed.
* Finally, it checks the base translation in
django/conf/locale."
Perhaps the paragraph "How to create language files" could be more
clear about the difference of running make-messages.py in the django
source or in your own project.
Thanks very much for your help.
Berry.
