Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with automatic translations when translating posts from Dutch to German using the DeepL translation engine. Specifically, the URL field is getting translated into English instead of German, despite the settings being configured for Dutch to German translation. The client is also concerned about whether the translation memory will recognize and apply corrections to similar future translations of slugs.

Solution:
1. We advised the client to correct the translation in the Advanced Translation Editor to ensure it is saved to the translation memory. This way, when translating the same slug in the future, the issue should not reoccur.

2. We confirmed that the translation memory requires an exact match to remember a full sentence or string. Therefore, any variations in the sentence will not be recognized by the translation memory.

3. We suggested that the client review and correct translations in the Advanced Translation Editor if they notice any incorrect translations. This process involves the server retrieving results from the translation engine, and corrections can be made directly within the editor.

For more information, the client can refer to the following documentation:

If the provided solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum 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.

Tagged: 

This topic contains 7 replies, has 2 voices.

Last updated by Long Nguyen 1 year, 2 months ago.

Assisted by: Long Nguyen.

Author Posts
February 21, 2024 at 10:07 am #15326750

erikM-19

When translating posts automatically I am sometimes getting the wrong language in translations, but only for the URL field 🤔

It clearly says Dutch to German, but I am getting a English translation instead.

I have enabled the option to translate Pager URLs and enabled slug translations because I want my post slugs to be translated.

Is this a bug?

2024-02-21_10-54-02.jpg
February 22, 2024 at 4:14 am #15330996

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Hi Erik,

Thank you for contacting WPML support, I'd be happy to help you with this issue.

I see you are using the DeepL translation engine to translate content from Dutch to German language. It could be a specific issue on your site, I try to replicate it on my demo site and DeepL translation homepage (hidden link) but don't see the problem. Please check two attached screenshots.

Please correct the translation in the Advanced Translation Editor to save it to the translation memory. When you translate the same slug, you won't see this issue again.
Refer documentation https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/

Looking forward to your reply.
Thanks

DeepL Translate: The world's most accurate translator 2024-02-22 11-09-36.png
Screenshot 2024-02-22 at 11.04.14.png
February 22, 2024 at 11:35 am #15333198

erikM-19

Hi Long,

I understand the translation memory will be updated when I correct these incorrect translations.

But from my understanding the translation memory only remembers complete/full strings or paragraphs. Will it work for similar (but not identical) future translations of such URLs?

E.g.:

I'll correct the slug "vietnam-with-children" to "vietnam-mit-kindern"

I would expect the translation memory will remember this exact full string translation. And thus future, similar translations containing *only* the same postfix "-mit-kindern" would *not* be applied and this problem can resurface, such as with "peru-with-children" or "australia-with-children" ?

Please advice. Thank you.

February 23, 2024 at 7:37 am #15336185

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Hi,

I would expect the translation memory will remember this exact full string translation.

Yes, the translation memory remembers the full sentence and requires a perfect match. Any changes to the sentence will not be recognized. Please read more about this in the documentation https://wpml.org/faq/why-arent-my-translations-showing/#why-does-my-translation-disappear-from-the-advanced-translation-editor-when-i-update-my-default-content

I hope I was helpful. Don't hesitate to ask if you find any problem along the way, I'll gladly help you.

February 23, 2024 at 7:42 am #15336189

erikM-19

Hi,

Ok but that leaves the question: how do I prevent this from happening again?

Please advice. Thank you.

February 23, 2024 at 9:28 am #15336752

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Hi,

Actually, the automatic translation content in Advanced Translation Editor is the result that our server gets from the translation engine. I'm not sure why it happens on your site but I cannot replicate it on my demo site.
Next time, you can review the translation and correct it if you see the translation isn't correct.

Refer documentation https://wpml.org/documentation/automatic-translation/how-to-review-automatic-translations-on-your-site/

Thanks.

February 23, 2024 at 9:50 am #15336813

erikM-19

My guess is that the translation engine can't handle slug string constructs too well (like-this-word-which-does-not-have-spaces), so I have disabled slug translations for now and just auto-generate a post slug based on its (translated) title.

February 26, 2024 at 1:23 am #15342054

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Ok, feel free to contact us again if you have any questions.

Thanks and have a good day.