On Wed, Apr 1, 2009 at 6:06 PM, Killarny <killa...@gmail.com> wrote: > > I am also running across this issue. I had simply assumed that > permission names would require ugettext_lazy to be localized, but it > isn't working. In trying to understand this, I am left wondering why > the permission name field is not stored in the database in such a > fashion to allow lookup from the .po files? Isn't that how Django > accomplishes i18n for other strings? > > On Feb 20, 6:27 pm, Malcolm Tredinnick <malc...@pointy-stick.com> > wrote: > > On Fri, 2009-02-20 at 11:04 -0800, eleom wrote: > > > Hello, does somebody know if there's a way tolocalizeadmin > > > permission names, so that, for example, in the user change form, > > > instead of 'Can add <model>' a localized version of it is showed? > > > > There isn't any way at the moment. Django itself does not provide any > > localisation of database content. Maybe one day, but not today. > > > > Regards, > > Malcolm > > > Nope, django doesn't handle i18n for any string stored in the DB, there are a couple of external projects that do it though.
Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
