SUMMARY Even within the same "project", such as KDE, there may be subprojects that need their own glossaries. For instance, "asset" in KMyMoney has a very different meaning in Kdenlive. In Weblate projects, each component also gets its own glossary. It would be very useful if there is a way for Lokalize to load component-specific glossaries. I imagine this could be done by either: - Trying to load a folder-specific glossary first before falling back onto the "project"-wide glossary. This would work when the translator has full control over the local folder setup, but it doesn't work so well when working with checkouts directly like with KDE SVN. - Or perhaps some way to define a map between component / folder names and glossaries in project settings, then use the defined map to decide which glossary to use. STEPS TO REPRODUCE 1. Open Lokalize on a large project with multiple folders representing components or subprojects 2. Try to translate things in different components, which may have different definitions for different terms 3. Observe the same glossary has to be shared across all files OBSERVED RESULT There is no way to make subproject-specific glossaries, and all files in a Lokalize project have to share the same glossary EXPECTED RESULT There is a way to make subproject-specific glossaries SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.1 Kernel Version: 6.6.68-1-lts (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION