It could be quite easy to extract the description of the permissions (tables userflags and permissions) into the templates.
They could be translatable like any other strings in templates.
alter table permissions drop column description;
alter table userflags drop column flagdesc;
And in the templates:
[% IF flag == superlibrarian %]
Access to all librarian functions
[% IF code == 'circulate_remaining_permissions' %]
Remaining circulation permissions
And delete / move sql files:
mv installer/data/mysql/en/mandatory/userpermissions.sql installer/data/mysql/userpermissions.sq
# same for userflags.sql
Someone against the idea?
I think it would make sense to move those descriptions out of the database as they don't change often and it's always a lot of work to add a new permission to all files.
I think the installer bit needs a bit more thought, but is solvable:
Currently if you don't have a mandatory file in the directory, there is no fallback to the en file. So we'd have to have a mechanism like for the sysprefs.sql file that is outside and always loaded, no matter that language you run the installer in.
Bernardo, any thoughts? Something you already have developed somewhere else?
*** This bug has been marked as a duplicate of bug 13632 ***