This thread is resolved. Here is a description of the problem and solution.
Problem: You are trying to automatically translate content with glossary terms, but encountering issues with words that include a copyright symbol since the last WPML update. Solution: We have acknowledged this issue and published an errata page that addresses it. If you're experiencing this problem, we recommend visiting the errata page for detailed information and potential fixes. You can find the errata here: ATE Glossary Issues with Automatic Translation of Trademark Symbols using DeepL in ATE.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
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.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
My apologies, but I believe that there is a kind of confusion here when it comes to the usage of automatic translation engines and the glossary which are in general two separate things, with one exception case.
Once you translate content automatically you will use a translation engine from Google, Microsoft, or DeepL.
The automatic translation will only be able to be applied from the Glossary if the translation engine from DeepL is used:
I do understand right, that only DeepL is activated on your site?
If you were using Google or Microsoft or our Test Engine on the Sandbox, then the glossary will only remain a recommendation and will not auto-complete the automatic translation.
When reviewing the automatic translation the ATE suggests a Glossary entry for each segment that is affected, so when you revise the translation for this section, you should simply apply the correct translation from the glossary.
This will then be saved inside the translation memory of the ATE and will auto-complete for any similar segment in future translations.
Also, we need to verify if the wrong translation may maybe coming from translation memory.
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Hello!
I just created a draft blog post for you. The same problem happens. hidden link
Actually, I figured out that when the Card Name/Glossary Term is alone in a string, it works. But whenever there is some text around, it causes an issue.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Thank you for your comments.
Please take note again, that such an issue can not be replicated on the sandbox, as the sandbox uses a fake translation engine - further your last example is not an automatic translation.
If you use automatic translation with DeepL, then the reported issues are actually expected - see attached screenshots from the DeepL translation engine.
Only when using DeepL (not when using Google's or Microsoft's engine) we should be able to add Glossary items before applying automatic translations for specific terms, which seems not to work as expected in this case.
As I am not able to use DeepL on the sandbox, I can not confirm the issue.
This is would I would like you to allow me to keep access to your site active so that I can escalate this issue to a second-tier support member, who will revise this issue and then reach out to our ATE development team.
Once I have feedback from the responsible second-tier support member I will be in contact with you again.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Thank you for your message.
Yes, in my last message I actually only wanted to make sure that you left the site access to your website active so that the second-tier support can have a look at the issue.
We are currently reaching out to the ATE development team which will revise this problem shortly.
As soon I have further information from our team I will be in contact.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello TM,
Thank you very much for the confirmation.
The issue has already escalated to our ATE development team and the changes should take place soon. Until now I can not tell when this will be the case, but as ATe runs on our server, the changes will take place immediately without the need for any plugin update.
