Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

This topic contains 13 replies, has 2 voices.

Last updated by Kor 5 months, 4 weeks ago.

Assisted by: Kor.

Author Posts
August 13, 2024 at 11:37 am #16065887

Wannes

Background of the issue:
We are translating posts with the automatic deepl translation, but it doesn't seem to keep the formatting. As you can see here almost all paragraphs are combined in one: hidden link where in the original all paragraphs are in seperate

tags hidden link

Also if there is a youtube url in the content it show the video in the front end of the original, but the actual link for the translated item. When saving the translated post again it does change to the youtube video in the front-end.

Symptoms:

Questions:
Is there a way to keep the formatting from text editors when doing the automatic translations with deepl?

August 13, 2024 at 1:28 pm #16066658

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for reaching out.

It seems you're facing an issue that has already been reported here: https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-editor/ . Please use the provided workaround until we have a permanent fix. We will keep you updated through the errata link.

August 13, 2024 at 1:50 pm #16066730

Wannes

That link goes to a 404 not found page. What is the workaround?

August 13, 2024 at 1:54 pm #16066764

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Sorry, it's this one https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/

August 14, 2024 at 7:36 am #16069041

Wannes

Is there any fix for already translated content? The workaround seems to word for new translations, but we have many posts that were already translated and have the formatting issues

August 14, 2024 at 8:24 am #16069232

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for responding. Are you indicating that your older content created with the old Advanced Translation Editor is still experiencing the same issue? It should only impact pages/posts that use the new Advanced Translation Editor.

August 14, 2024 at 8:33 am #16069302

Wannes

Yes, the content that was translated before (with automatic deepl translation) still has the no formatting issue. How do we fix that content? We had already translated a lot of content.

August 14, 2024 at 12:31 pm #16070489

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.

Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.

Your upcoming reply will be treated with confidentiality and will only be visible to you and me.

✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.

August 14, 2024 at 3:48 pm #16071687

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your response.

To address the issues, I reverted to the older version of the Advanced Translation editor and made minor adjustments to the primary language page located at hidden link . I retranslated it, and now it appears correctly in English at hidden link . Could you please verify this? Additionally, could you test this on another post and provide feedback on its performance?

August 19, 2024 at 8:32 am #16082377

Wannes

So the fix is to manually update every post in the primary language and then use more credits to retranslate the post so the pagination is fixed? Would that mean we pay double the translation fees?

August 19, 2024 at 8:43 am #16082452

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

No worries, retranslating the same content will not cost you any credits. Translations are saved in the translation memory as explained here https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/ .

What I did was resync the Advanced Translation Editor by making minor edits to the page(as shown in the screen recording I shared above). Then, after resync, the correct layout will show up on your translated page.

August 19, 2024 at 10:44 am #16083072
Wannes

Ok, thank you. We're having some other issues as well. For example this item doesn't translate the ACF fields page section in ES or FR: hidden link

But when I edit the translation I can see all the content, but it's not coming through

New threads created by Kor and linked to this one are listed below:

https://wpml.org/forums/topic/acf-fields-cannot-be-translated-2/

August 19, 2024 at 11:37 am #16083234
Wannes

it seems that url's aren't translation either. for example in this event there is a lnik to the events page but it goes to the NL version instead of the EN hidden link

this link 'here': Find out what sprouts from previous editions via the updates HERE.

New threads created by Kor and linked to this one are listed below:

https://wpml.org/forums/topic/urls-cannot-be-translated/

August 19, 2024 at 2:32 pm #16084344

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your response.

Please note that our support policy permits us to address only one issue per ticket. Handling one issue at a time allows our support team to focus better and helps other users find solutions more quickly.

I've separated your two new questions below so we can address each one appropriately.

https://wpml.org/forums/topic/acf-fields-cannot-be-translated-2/
https://wpml.org/forums/topic/urls-cannot-be-translated/

The topic ‘[Closed] automatic translation deepl formatting issues’ is closed to new replies.