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
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.
Hi,
The permissions are stored in the database and don't get translated.
Refer: https://code.djangoproject.com/ticket/1688.
poniedziałek, 10 maja 2021 o 19:35:38 UTC+2 M Vv napisał(a):
> Translation of user permissions is not done.
>
> [image: gruop trans.PNG]
>
> How should it go about it?
>
Translation of user permissions is not done.
[image: gruop trans.PNG]
How should it go about it?
--
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 fr
