I've spend 3 days on this. Please help.

I've created the following locale to my project below:
/home/robin/myproject/locale/id/LC_MESSAGES/django.po
/home/robin/myproject/locale/id/LC_MESSAGES/django.mo

so I have a custom language which is suppose to be Indonesian
indentified as 'id'

Done django-admin.py makemessages, compilemessages and all that.
I followed everything from http://www.djangoproject.com/documentation/i18n/
except the javascript bit at the end, and not really understanding
this 'manually configured settings' note.

The language becomes 'id' WITHOUT the localemiddleware and works, but
of course the site will always be one language with no user
preferences.

When I turn on the localemiddleware, 'id' translation will refuse to
take effect, but other default languages like 'en' and 'de' does work.

It is only until i copy ANY kind of django.mo to <DJANGO directory>/
conf/locale/id/LC_MESSAGES/django.mo then will the locale in my
PROJECT directory be recognized.

I've googled around and I hear at one place that this is the desired
effect while other sites (including the official i18n doc) teaches
django internationalization as if project locale is suppose to work
with locale middleware straight away. If it is the desired effect, why
is it so?

I've spent too long on this seemingly easy implementation, please help
clarify.

Thanks a lot,
Robin

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