django.views.i18n loads English catalog first, then loads default locale catalog, and finally loads the selected locale catalog. Only for English, it takes care a case without the locale catalog.
In my case, I write Japanese strings in my source code. I create English catalog for English locale, and no catalog for Japanese locale. When Japanese locale is selected, I expect NullTranslations is used, however django.views.i18n uses English catalog for this case. django.utils.translation works as I expected. I don't understand why django.views.i18n makes it so complicated. If the selected locale catalog exists, use it, otherwise go to NullTranslations. Why this simple way doesn't work? Shiro Ninomiya -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
