Resolved
Reported for: WPML Multilingual CMS 4.6.12
Resolved in: Advanced Translation Editor Oct 14th, 2024 Deployment
Overview of the issue
When the “prefer bigger segments” feature is enabled, line breaks (“\n”) are not included in the translated content. This results in the content displaying incorrectly on the front-end.
Workaround
There are two ways to temporarily resolve this issue:
Workaround 1:
- Go to WPML->Settings->XLIFF file options->New lines character
- Enable ” Do nothing – all new line characters will stay untouched”
- Resend the page to translation from WPML > Translation Management.
Workaround 2:
- Go to the top right corner of the translation editor
- Click the gear icon
- Disable the option “I prefer bigger segments”
- Close the editor and send the page to translate again via WPML > Translation Management.
Hi, we are having exactly the same issue. We translated 2000 pages and now the text is in just on paragraph instead of the line breaks. Is there any way to workaround the whole website without breaking it?
Hello Salvador,
I’m afraid that at the moment we don’t have another workaround available. Have you tried the one published here?
Hello, I have the same problem. But even when I turn off the option “I prefer bigger segments” the line breaks are not included in the translations. I need a quick workaround!
Hello there,
If the workaround here provided is not working, please start a chat in our assistance channel.
We will investigate your case.
In case someone else is having the same issue, follow the workaround above, but with no results, I tried the following and it worked:
**Before re-translating the page**
In the original language, find the text that ignores the line breaks and add random text or keywords, so that you can force the text to reappear on the translator. Then translate the page and see if it now respects the line breaks.
It worked on my end so I hope it helps someone else also. At least it is fixed from WPML.
Thank you very much for sharing your workaround. 🙂
The workaround is also working for me. Thank you for it. I hope the dev team can solve this issue.
I’m glad it worked. We will keep this page updated once a definitive fix has been deployed.
Regards
How can I open the ATE to do this?
“Go to the top right corner of the translation editor”
Previously, the ATE always opened when translating, now the posts are automatically translated without me seeing the ATE. So how can I call it up?
Hello there,
You can try something like the following:
– Go to your Dashboard > Pages.
– Open any of your pages.
– Click on the (+) icon: your translation should be open in ATE.
– Follow the instructions of this erratum.
If you have any issue with this procedure, please start a chat in our support channel. We will provide you the require assistance in order to continue translating your website.
Hi,
is this problem solved with the new 4.6.13?
Hello there,
I’m afraid that this fix hasn’t been released yet.
We will keep this erratum updated.
Is there still no update for this bis issue?
And since I had to translate the already translated posts again (now with unchecking the option “I prefer bigger segments”), I lost about 15,000 credits. I would like to have them back, as it is a bug in WPML.
For your credits please start a chat in our assistance channel, one of our specialists will take care of your case.
This issue has been partially fixed so far. We will update this page once a final deploy has been released.
Would like to follow this topic but don’t see a subscription button so just leave a comment. PS inserting also works.
Hello there,
Thanks for sharing your workaround. Now, for subscribing, please click on the “Subscribe to comments” link available just above the Reply box.
Let me know if it helps.
Hello Andrés,
I dont see a “Subscribe to comments” link, do you have a screenshot?
With search I don’t find “Subscribe” either (accept from your text).
Hello Tim,
I know that we are creating a new Subscribing button for erratas, however the link in the comments box should be available. Do you have your WPML session open?
Maybe a screenshot of what you see in the comments box will be helpful.
See: https://tinyurl.com/24a5mk4j
Gr Tim
Thanks for the screenshot, Tim. After talking with our systems team, the subscribe link was removed recently in order to pass to the button I mentioned before, However it is not ready yet.
I’ll keep this page updated.
Hello,
It’s 13 September and there’s still no patch?
Thanks
Loïc
This fix hasn’t been released yet. We will keep this erratum updated.
Thank you for your understanding.
Another workaround is to use the old Advanced Translations Manager for now. It worked for us.
I’m glad it worked for you. Thanks for sharing it.
For the people that still encounter the issue, please follow these steps:
– Go to WPML > Translation Management
– Send the job to translate again, either by setting it to retranslate again automatically (from scratch, not just the untranslated segments) or manually
– If you chose the manual route, locate the segment and click the automatic translation button on the segment.
You’re welcome to open a support ticket so we can help you solve this problem.