Re: i18n - local translation does not show up - bug
On Mon, 2012-05-07 at 11:44 +0530, kenneth gonsalves wrote: > > It'd be strange, but certainly possible, it is broken. We have > > a test case checking that such feature works: > > > > > https://github.com/django/django/blob/master/tests/regressiontests/views/tests/i18n.py#L140 > > > > Could you reduce your failing case to the simplest form > > and share it so we can do more research?. > > I was away - will do that now weird - I made a simple app with one model that has one field. Trunk picks up the local translation - if LOCALE_PATHS is commented out, it fails as expected. But in none of my older apps (one running for over 5 years) is this happening. Settings are identical in all the apps. -- 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.
Re: i18n - local translation does not show up - bug
On Thu, 2012-05-03 at 10:29 -0300, Ramiro Morales wrote: > > > > I had gone through the docs and added the LOCALE_PATHS setting - but > it > > just does not work - have tried on fedora, debian, ubuntu ... > > Good to know that, I couldn't infer that from your initial email. > > It'd be strange, but certainly possible, it is broken. We have > a test case checking that such feature works: > > https://github.com/django/django/blob/master/tests/regressiontests/views/tests/i18n.py#L140 > > Could you reduce your failing case to the simplest form > and share it so we can do more research?. I was away - will do that now -- 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.
Re: i18n - local translation does not show up - bug
On Thu, May 3, 2012 at 9:17 AM, kenneth gonsalves wrote: > > I had gone through the docs and added the LOCALE_PATHS setting - but it > just does not work - have tried on fedora, debian, ubuntu ... Good to know that, I couldn't infer that from your initial email. It'd be strange, but certainly possible, it is broken. We have a test case checking that such feature works: https://github.com/django/django/blob/master/tests/regressiontests/views/tests/i18n.py#L140 Could you reduce your failing case to the simplest form and share it so we can do more research?. -- 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.
Re: i18n - local translation does not show up - bug
On Wed, 2012-05-02 at 10:53 -0300, Ramiro Morales wrote: > > 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. > > I had gone through the docs and added the LOCALE_PATHS setting - but it just does not work - have tried on fedora, debian, ubuntu ... -- 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.
Re: i18n - local translation does not show up - bug
On Wed, May 2, 2012 at 4:13 AM, kenneth gonsalves 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.
i18n - local translation does not show up - bug
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 -- regards Kenneth Gonsalves -- 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.