I’d like to tweak the Weblate (glossary) Gramps component to include all the terms from the wiki Gramps Glossary and tag them as terminology. Then use the component’s CSV export as (easily updatable) data files for a gramplet. But don’t want to mess up any current functionality.
Can you explain the purpose of that component?
There seems to be a bit of accidental corruption with other languages being used in the English. For example, the “active person” has an ‘english’ “Source string explanation” set to Finnish: “Valittu henkilö, johon toiminto kohdistetaan” (meaning “Selected person to whom the action is applied”)
The Weblate Glossary looks to be automatically created by Weblate
An empty glossary for a given project is automatically created with the project. Glossaries are shared among all components of the same project, and optionally with other projects using Share in projects from the respective glossary component.
The Program component contains the translations for the core code.
The Addons component contains the translations for the third-party addons in our addons repository. We run a script to exclude any strings that are already in the Program component.
The Web component contains the translations for Gramps Web. These are in addition to the Program component which is also needed. I’m not sure if the Web component contains any duplicates - I haven’t checked.
The Glossary is a special component created by Weblate. It helps translators standardise the translations of certain terminology and words and phrases that may be difficult to translate or have multiple options.