On Wed, May 2, 2012 at 4:13 AM, kenneth gonsalves <law...@thenilgiris.com> wrote: > hi, > > I want two languages in my project - en and ta. I have set this up in > many projects over the years and this is the first time I am seeing > failure. The problem is that on switching to tamil, the django strings > are getting translated, but not the local strings. Django is obviously > not finding my local .mo file. Makemessages and compilemessages work > fine. My locale directory is at the same level as manage.py. Even if I > put it at the same level as settings.py, it still does not work. > > django version - latest trunk > > later: on checking, this works upto revision 17860 and breaks from 17861
Well if you are using the development version it is assumed you are closely following the development activity (so this kind of changes don't take you by surprise) and/or can read the Fine Manual where the decprecation and the steps you need to take are (and have been since Django 1.3 Apr 2011) documented. Two hints: The Django 1.3 release notes and the LOCALE_PATHS setting. -- Ramiro Morales -- 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.
