#13861: Translate permissions
-------------------------------------+--------------------------------------
Reporter: tonnzor | Owner: nobody
Status: closed | Milestone: 1.3
Component: Authentication | Version: SVN
Resolution: duplicate | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by tonnzor):
Replying to [comment:5 russellm]:
> By the by -- passive aggressive comments like "no answer as usually" are
a grand example of how to *not* get the help you need
Thanks for pointing that. Reading your post I realized that at the time of
writing I was just disappointed in workflow of bugs accepting - dev
discussion (decision) is needed, dev sometimes don't respond as issue is
simply closed (not even marked as "to be done one day")
Please, look at the comment that resulted in closing #1688 -
http://code.djangoproject.com/ticket/1688#comment:1
> The permissions are stored in the database and don't get translated.
That's it! 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?
Another ticket you pointed to is #6460 that is much more generic issue and
has not a word about permissions or auth module - that says about
translating model fields into several languages. E.g. Article.text ->
Article.text_ru + Article.text_en
Please have no doubt that I read and understood the tickets you pointed
before making such statement as "answer is not relevant".
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 - as a volunteer - work on it.
--
Ticket URL: <http://code.djangoproject.com/ticket/13861#comment:6>
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.
