On Wed, 2009-05-13 at 13:14 -0700, hcarvalhoalves wrote: > I tried both reopening [1] and filling a new ticket [2], but looks > like I'm doing it the wrong way as they kept being closed. So here I > come asking for help on the list.
The reason in both cases was explained in the tickets (and in the contributing.txt document). If you want to address a ticket that has been resolved unsatisfactorily for your purposes, then a discussion on this list is the appropriate way. Otherwise we'd never get any peace with people opening tickets on already resolved issues. > > On syncdb, contrib.auth will create default permissions for each model > you have (add, change, delete). But the permission names aren't > translated, You aren't describing the problem correctly, as far as I can see. Translating at *syncdb* time doesn't make sense. Translate into which locale? Your viewers could be using any locale at all when they get around to viewing things. This really falls into the area of translating db content, which Django consistently does not do at the moment (and solving it piece-meal, just for permissions, isn't going to happen). When translating of db content is possible, we'll be wanting to translate the user-readable name (the "name", not the "codename" field) at template rendering time, into the appropriate locale. But certainly at syncdb time. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
