On Sat, 2012-06-02 at 02:58 -0700, Houmie wrote: > The good news is the problem is solved. A friendly chap in > stackoverflow > actually bothered to look into it. > > The problem is as simple as the translation files couldn't be found. > For > some odd reason the important information about how Django locates > them is > at the very last section of the documentation. It is really easy to > miss. > > All you have to do is to move the locale directory with the > translation > files into your Application directory. Thats it !!!
it may have solved your problem. But actually nowadays django looks into settings.LOCALE_PATHS - could you check whether the svn revision number you are using is less than 17860 or greater. -- regards Kenneth Gonsalves -- 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.
