Translation of group permissions

[M Vv]

Translation of user permissions is not done.

How should it go about it?

[macie...@gmail.com]

Hi,

The permissions are stored in the database and don't get translated.

Refer: https://code.djangoproject.com/ticket/1688.

[Fran Hrženjak]

I ran into this same issue last week. That ticket raises a valid question IMHO: why even save permission descriptions in the DB? 

Anyone seeing any downsides of the proposed approach to fetch the descriptions from code (and apply translation on the fly)?

Fran

On 22.05.2021., at 02:08, macie...@gmail.com <macie...@gmail.com> wrote:

Hi,

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/da4f96c9-d780-4dde-8ae8-d6c7f0ef59b7n%40googlegroups.com.

[Ramez Ashraf]

This is an old decision not to store translated strings in the db... and it's makes sense what if your site is multi lingual ?
Solution: The widget should be replaced with a another widget that display the permissions in a dynamically translated fashion.

There is this app to address that and to address the fact that it's is not very user friendly especially when we have an increased number of models 
https://github.com/RamezIssac/django-tabular-permissions
Disclaimer: i'm the author of this library.