#1688: Permissions don't get translated in admin interface -------------------------------------------+-------------------------------- Reporter: Rudolph | Owner: hugo Status: closed | Milestone: Component: Internationalization | Version: 1.2 Resolution: wontfix | Keywords: Stage: Unreviewed | Has_patch: 1 Needs_docs: 0 | Needs_tests: 0 Needs_better_patch: 0 | -------------------------------------------+-------------------------------- Changes (by tonnzor):
* version: 1.1-beta-1 => 1.2 Comment: Unfortunately, all tickets that covers the functionality are closed because of being dupe of this ticket so I have to say here. Please, look at the comment that resulted in closing this issue: > The permissions are stored in the database and don't get translated. That says not it is implemented *now*. That covers the implementation point of view (implementation idea is not perfect), not the rationale of the issue (that is very useful for not-english). There are a lot of ways to get needed functionality: * We may get rid of auth_permissions.name column and generate translated names on fly using auth_permissions.codename value. * We may store *translated* text in auth_permissions.name (I know that name is not translated *now*) Is there any reason not to store non-english text there? If the rationale of this ticket makes sense (having translated permissions shown in admin) please keep this ticket open or point me to the ticket that has this rationale covered so I can work on it. -- Ticket URL: <http://code.djangoproject.com/ticket/1688#comment:7> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-upda...@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.