Support Identical Glossary Names Across Languages
under review
V
Vijay Sakthivel
Currently, glossary entries with the same Name and Term cannot be imported across different languages, as the glossary Name must be unique across the project.
The customer uses an external translation service and imports glossary entries separately for each language. In some cases, the Term remains the same across languages (for example, "Widget"), while only the definition changes.
The customer would like the ability to import the same glossary Name and Term across different languages and have them treated as language-specific entries. The glossary import should also provide an option to specify the target language and name of the glossary in the csv.
Log In
Mohamed Shakheen
updated the status to
under review
Mohamed Shakheen
Hi Institutional Magpie
Thank you for sharing your use case and the detailed context.
We're currently working on a Terminology Management capability, which is intended to address scenarios like this by supporting language-specific terminology more effectively.
We'll share more details and an update as the feature progresses. We appreciate your patience and feedback!
I
Institutional Magpie
This must be balanced against the best practice for multilingual terminology, preferably maintaining only 1 unique concept (=backend UID) for all languages offered (1 binding term per language below the concept, optionally synonyms marked with “allowed/obsolved/prohibited”).
Concept (unique) /UID
1. Name main language + definition main language + qualified synonyms main language
2. Name 1st foreign language + definition 1st foreign language + qualified synonyms 1st foreign language
3rd name 2nd foreign language + definition 2nd foreign language + qualified synonyms 2nd foreign language
4th, etc.
The export and import for all languages is then always unique based on the concept UID.
V
Vijay Sakthivel
Raised on behalf of Zucchini green Bear