Several issues with new glossary implementation

[Fat-Zer]

I've noticed several relatively small issues in recent glossary reimplementation and its documentation. I don't feel like each of those deserves it's own bug report. Although I don't want them to get lost.

Describe the issues

• Marking terms as forbidden are available for users now, but it shows an «insufficient privileges» error (despite actually adds the flag).
• IMHO marking terms as "Not translatable" should be available for users as it should be managed by translators and the set of such words may differ from one language to another.
• Adding explanations should be available for users and bond to translation.
• It would be nice to have explanations available from the glossary panel (probably in form of a tooltip)/source string tooltip text.
• Glossary documentation messages that you can share a glossary with an another project quite badly: it can be misread as "If you have a shared component, you will share the glossary"
• It would be nice to have a shortcut to browse the glossary on the side panel e.g, an eye-shaped icon besides the pen one.
• It would be nice to have a more clear designation for forbidden translations: may be an icon with an exclamation mark as for the configuration errors between the term and the translation.

[nijel]

The explanation should be already available in the glossary panel. I will check rest later...

[Fat-Zer]

I'm felling like I'm pushing some keep-feedback-useful limit, adding more and more to the list... Feel free to tell me to stop or if you want it in some other format...

[tjhietala]

There's also the small issue that there's nothing to indicate that the user is editing the glossary. It looks just like any other component. Even the glossary pane on the right hand side is displayed! (example)

[tjhietala]

Correction: Actually it says "Glossary term", but that might be easily missed as evidenced above...

[nijel]

It is more visible since 353ff0e.

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.