Background of the issue:
I created 916 lines of glossary for product names, expecting the translation system to use it. The issue can be seen at hidden link.
Symptoms:
The translation system translated the glossary terms anyway, instead of using the glossary.
here are some examples:
- the word SHIELD should not change. It was actually translated into the French version in the collections image. But not in German.
- To all the lotions the translation has been applied, while in the glossary it remains the same
- From the home page if I click on the Solargel colors, it gives me 404 error
- On the home page SHIELD has been translated SHILD
Questions:
Why is the glossary not being used by the translation system?
How can I ensure the glossary is applied correctly?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hi, Could you please send me the CSV you have and tell me what type were you using before vs what you want right now?
From your current issue, i understand that you used "terms" as the types instead of "names" and that's why it's being translated, right?
See, you're using DeepL which is the only one that accepts the "terms" type and it has this "feature" where it basically ignores the glossary because it sees the translations is better without it (Yeah, it defeats the purpose of the glossary feature!).
We're trying to find a solution for this since, unfortunately DeepL mentioned that for them that wasn't a bug but a feature.
If you use the other type, "name", this won't happen because those are willfully ignored by any translation Engine.
Send the CSV via any sharing platform and I'll try to see why it doesn't update and how we can have that fixed and in the meantime fix it on your end.
Regards,
The topic ‘[Closed] Created the glossary but translates the same’ is closed to new replies.
