Glossary not named as such in component admin menu

[comradekingu]

Papercut

This situation is a bit quirky. In my wisdom a lot of projects have the same project and component name, so there is a Glossary derived from the former(?) making it hard to tell what is a glossary and what is a component.

One solution would be to put a "Glossary" label in gray there. (Like elsewhere).

I suppose the project glossary naming scheme makes sense in the bigger instance glossary?

Options considered (but not thought through): Calling all project level glossaries "Glossary".

[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.