Terminology for a project

[nijel]

There should be possible to define terminology for a project, which would be then used in all of it's dictionaries. This should not prevent translators from adding own words for just given language, but project maintainer should be able to define list of words, which should be included in all glossaries (and see how much of them is actually translated).

[ChrisOelmueller]

How feasible is tracking "terminology" as own subproject, or at least allowing to do that? With pootle the workflow was not so bad in that regard (adding strings per language was still supported). Maybe even adding strings to the subproject (through web interface) could be possible.

[nijel]

That's an option as well, though I'm not really big fan of adding
special purpose subprojects like this...

[algazarra]

+1
I was going to open a new issue called "unified glossary". If I add a glossary word in any language, that item should be added to every other language glossary.

Maybe auto start with glossary when creating a new translation.

[nijel]

Scope of this feature:

• Add new category to glossary view to define terminology, allowing adding of new words and see words status
• The per language view should list missing words
• When adding new term to glossary, it should be possible to mark it as terminology

Terminology model:

• Term.terminology references Terminology, on delete set NULL
• Term.terminology is automatically set when source string matches
• Terminology object is not editable to avoid need to adjust the foreign keys

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