Home›Support›English Support›[Escalated to 2nd Tier] Word in wrong order with automatic Deepl translations
[Escalated to 2nd Tier] Word in wrong order with automatic Deepl translations
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Elementor users - please update WPML to the latest version to maintain compatibility. More details here - https://wpml.org/changelog/2024/12/wpml-4-6-15-critical-update-for-elementor-sites/
I don't know the exact flow of the conversation between our team and the DeepL team, but I asked for an update, and our team told me that they don't have one from DeepL yet.
Thanks for your patience. DeepL didn't answer, but our Dev team checked the issue again, and they think your issue might be a separate variation from the ones we knew about.
Would you please share your site's access details and the page that contains this glossary term so that our team can investigate the issue further?
Your answer will be private, meaning only you and I can access it.
Our ATE team has checked the issue and found the following: The main issue here is that you seem to have a lot of glossary entries that are basically forcing a specific translation on DeepL.
When DeepL knows you're forcing a glossary entry translation, it tries to position it somewhere, which could result in the entry being positioned differently.
To fix this issue, please check the glossary, delete any unneeded entries, and leave only the important ones.
We can help you delete the entries, but we need your help knowing which ones.
Thanks for checking. That's a weird behaviour. These specific entries are names of locations and rental properties that should stay as is, without translation. It doesn't make sense that a glossary term also puts that word in a wrong position in the sentence, causing a completely wrong translation. The glossary is there to make sure that certain words are translated correctly, it shouldn't result in a different and grammatically incorrect sentence structure.
I know there are a lot of glossary entries*, but it's not that the examples I gave contain all of them. Most of them only contain one or two glossary terms. Which is exactly what the glossary is meant for, right? If a sentence only contains one term, then why would that term be positioned in the wrong place?
Based on the examples I gave, can your ATE team be a bit more specific on which glossary terms causes the issue? I mean, if the sentence contains the name of a city like in the third sentence, and that name is the only word in the sentence that's also a glossary term, then why is that word placed as the first word in the sentence? Which other terms play a role in this? Or, how would I know what terms should be removed?
Note that I have never had this issue before. It started after the ATE update that added bigger segments, dark mode etc.
* As for the number of glossary entries, I agree it's a lot and I don't like it either. The problem here is that the glossary (and TM) is shared across all connected sites. The reason these sites are all connected is because I have a single pay-as-you go account. Primarily to ensure that I get a single monthly invoice instead of a separate one (10+) for each site. The ideal way for me would be to have a shared pay as you go account for invoicing with a separate glossary (and TM) for each site. Is that possible?
