I want to be helpful, but I am not sure it's worth the effort, Peter.
We've been using the Roles across multiple language sites for 18 years and never found it an issue, to my knowledge nobody has asked.
Also changing role names across languages will make support more difficult.
If you start getting people to change there role name to whatever they want, it even starts to get crazier for support. I know there is the language pride and people shouting it can't be understood if the roles are not in their language, but truth be said, that is not true.

Waste you time on doing an Editor provider for Quill. :-) Unless you're getting paid for the role change.... if so jump in and do it. :-)

AFAIR the system rolenames are currently localizable via static localization (sharedResources.resx: AllUsers.text, UnauthenticatedUsers.Text and Superuser.text). However, this does noit cover portal roles, which can only be edited in the Database - and some code may rely on the name instead of ID in database table "Portals". some other roles had been added (like unverified users and new contentManager roles), without option to localize and IMO it would be helpful to provide a mechanism for localizing all of them.

Posted By Peter Donker on 10/2/2024 12:18 PM

I am working on making the (System/Core) role names localizable. That is: Administrators/Registered Users/etc can be shown in the lnaguage of the logged in user. This could include the description as well. My question is this: shall we make the system rolename description non-editable AND put in a little bit more effort in providing a proper description/explanation of what the role does? Currently the description is not very helpful for system roles (the description of Registered Users is "Registered Users", duh). So I think a bit of love in this part is overdue.

Yes,  System Role Desription for a Resource file right?
It shows on hover as a Title (PB > Pages > Security)

BTW, the importance of this depends very much on how you use DNN.
Some of us don't allow users to create pages for instance.
If you do, I can assure you that for instance "All Users" (which is what Peter already worked on) is a serious issue (Admins think it's "All DNN Users")

See: https://dnncommunity.org/forums/aft/5254