Hello Transifex Community!
We’re thrilled to share some further enhancements related to Transifex Glossary and Machine Translation integration. These improvements build upon the recent introduction of Glossary support across multiple machine translation services, as highlighted in our previous post here.
1. Improved Handling of Empty Glossary Translations
When a glossary term lacks a translation or consists of whitespace characters only, our system will seamlessly step in. It will ensure that occurrences of such glossary terms within projects linked to the glossary are correctly translated by the machine translation engine, treating them as standard text.
2. Handling Ambiguity with Multiple Matching Glossary Terms
We understand that working with multiple glossary terms can sometimes lead to ambiguity, especially when a single string matches multiple glossary terms, with potential word overlap. In such complex scenarios, our platform now follows a set of conditions to determine which glossary term to prioritize, ensuring that the most relevant translation is applied.
Here are the conditions used, listed in priority order:
- 1. Term (or Variant) is Translated: If a glossary term or one of its variants already has a translation, that translation will take precedence.
- 2. Term (or Variant) Word Count: Longer terms or variants will be favored, as they provide more context for translation.
- 3. Single Terms (Without Variants): Terms without variants will be considered next.
- 4. Case-Sensitive Terms: Case-sensitive glossary terms will be given priority when determining the most appropriate translation.