On Mon, 2009-03-02 at 11:24 -0800, Scott wrote: > Hi Malcolm, > > Thanks for your response, I suspected that it was something similar. > I'm actually using the Django helper for App Engine (http:// > code.google.com/p/google-app-engine-django/), so there is no django > installation to configure. Further to this, all of the strings are > being provided by our client and are application-based - there is no > generation of Django content, I'm only working with templates.
Regardless. The general rule is that if you're using Django's i18n framework, it will only work if Django already has support for that locale. The logic is built into django/utils/translation/*. Maybe it works in some miracle case, but that would be an accident and not at all guaranteed. > > The odd thing is that I can reach the Korean and Thai languages by > setting my browser's language (User agent string) to the respective > languages, but can not navigate there via cookie, unlike the others > listed. The Chinese language variations are totally unreachable. Then start putting debugging prints into the code and checking what is being processed in django/utils/translation/trans_real.py. Yes, you've said you were on GAE, so you'll probably need to install your own version of Django or test it locally. Life's like that sometimes. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
