When using glossaries in Elovate translations, you might encounter situations where the output does not match your expected terminology. This could be due to a mismatch between the glossary rules and the content being translated, or conflicts between multiple glossaries.
1. Understanding how glossaries work
Glossaries define specific terms that must be translated in a particular way.
When a glossary is applied to a translation job, it overrides the translation provider’s default output for matching words or phrases.
If multiple glossaries are selected, Elovate processes them in the order they appear, with later glossaries overriding earlier ones.
2. Common causes of mismatches
Overlapping glossary entries – Two glossaries define the same term differently.
Case sensitivity – Glossary rules may be case-sensitive depending on provider settings.
Plural and gender variations – The glossary term might not match the exact word form in the source text.
Provider limitations – Some providers (e.g., DeepL) may not fully enforce glossary terms in certain contexts.
3. Checking for conflicts
Go to Apps → Translations → Glossaries.
Review the selected glossary or glossaries for your translation job.
Look for duplicate or similar terms that could override each other.
If you have multiple glossaries, check their order and merge where possible to reduce conflicts.
4. Fixing a mismatch
Option 1 – Update the glossary
Edit the term in the glossary to match your intended translation.
Make sure to account for plural forms or different cases.
Save and re-run the affected translations.Option 2 – Override during translation
When reviewing a translation in the item view, manually correct the term.
Approve the corrected term so it is sent to Magento.Option 3 – Use a dedicated glossary
For projects with unique terminology, create a separate glossary and apply it only to that translation job.
5. Preventing future conflicts
Keep glossary names and purposes clear (e.g., "Fashion Terms EN–DE" vs. "Technical Parts EN–DE").
Limit the number of glossaries applied to a single job.
Regularly audit glossaries for outdated or conflicting entries.
Train your team to check glossary rules before running large translation jobs.
6. Using the synchronisation log for troubleshooting
Go to Apps → Synchronisation Logs.
If a term mismatch causes an error or unexpected output, it will often be logged here.
Clicking on the affected entity lets you inspect exactly which glossary was applied.