Sorting Glossary Entries - give prio to glossaries from "own" project

[ilocit]

Describe the problem

When using multiple (shared, from other projects) glossaries in a project, it would be nice if those matches from the "original Glossary component belonging to the current project were shown at the top rather than the bottom of somewhere in the middle.

Glossary entries within the project are always better matches and more important than those from other (reference) projects.

Describe the solution you'd like

Move glossary entry matches retrieved from current project Glossary component to top.
I.e section (1) above section (2) on the screenshot below

Describe alternatives you've considered

No response

Screenshots

Additional context

No response

[nijel]

I'm not really convinced that this would be better in all cases – alphabetic sorting has advantages as well…

[github-actions]

This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate.

Please try to clarify the use case or consider proposing something more generic to make it useful to more users.

[ilocit]

The alphabetic sorting should be kept, within each Glossary component.
With glossaries with many entries, this gets really messy and there needs to be a way to prioritize. And the "core glossary component within the project should always prevail above shared ones.
All other matches can be sorted in whatever way (mixed, alphabetically), but the matches from the "core" glossary need to be shown at the top. Really.

[KadAnna]

We use a "common" glossary that tries to unify terms across projects and that one I want to give a priority over the project's glossary... so cannot agree with the original suggestion.

[ilocit]

Well, @KadAnna, normally Terms on a project level are more specific to the project than any general shared glossaries.
You only add terms to a project glossary when you want to set a different translation for that particular project compared to "general" (for good reason).
Anyhow, what we see here, the use cases are very different, so maybe a general "switch" or "setting" is needed for (shared) Glossaries to prioritize them.

[nijel]

But we do have existing solution to order components – https://docs.weblate.org/en/latest/admin/projects.html#priority. It just should be applied to the glossary terms as well.

[ilocit]

But we do have existing solution to order components – https://docs.weblate.org/en/latest/admin/projects.html#priority. It just should be applied to the glossary terms as well.

Sorry, @nijel the suggested solution does not work.
I added two Glossaries to a project, one as Medium one as Very High.
This has no effect on the order in which the entries are being displayed in the Glossary section.

[nijel]

It will work in 4.15...

[ilocit]

It will work in 4.15...

Thanks!