Hello,
I translated a couple of pages with the translation editor on the website, and it was convenient and smooth.
Now, for some reason, the translation editor does not show paragraphs and does not auto-translate. Instead, it breaks texts word by word without auto translation (screenshot).
Can you help me fix this?
I am using WPbakery for page builder and the page structure is very simple (screenshots).
Moreover, I have already translated 2 identical pages with different texts and it was fine. The Translation editor immediately translated all the text for me and I was able to translate text block by text block.
I'd like to request temporary access (wp-admin and FTP) to the website to investigate the issue further.
You'll find the necessary fields below the comment section if you log in to leave the next reply. The information you provide will be private, meaning only you and I will be able to see and access it.
IMPORTANT
Please be sure to create a backup of the website and database before granting us access.
If you don't see the "wp-admin / FTP" fields, your login credentials for the post and website will be set to "PUBLIC." Do NOT publish the information unless you see the required wp-admin / FTP fields.
The private reply form looks like this: hidden link
When replying again, click "I still need assistance".
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any login information not specifically provided in the private reply form for this ticket.
There isnt any updates to Uncode theme plugins (screenshot)!
The problem is still there. you have the wordpress access - if you see an update please do it - I have a daily backup.
This issue has been blocking me from progressing for a week now. I expect a more efficient assistance please.
The segmentation you’re seeing in WPML’s Advanced Translation Editor (ATE) is a direct consequence of how the original content is structured in HTML.
Why WPML builds segments per word
ATE segmentation logic: ATE breaks text into segments based on inline HTML elements.
Your content: Every single word is wrapped in its own <span class="BZ_Pyq_fadeIn">…</span>.
Result: Since ATE treats each <span> as a separate unit, it generates one translation segment per word.
Why is this expected
WPML isn’t arbitrarily splitting text; it’s respecting the DOM structure.
From ATE’s perspective, each <span> is an independent inline element, so segmentation at the word level is the correct behavior.
This is not a bug in WPML, but a side effect of the animation/markup used in the original content.
Implications
Translators see dozens of micro‑segments instead of continuous sentences, which makes translation less fluid.
WPML cannot merge these automatically because doing so would risk breaking the markup or animations.
How to address it
Best practice: Apply fade‑in or animation classes to larger text blocks (e.g., entire <p> or sentence) instead of wrapping each word.
Alternative: If word‑by‑word animation is required, accept that ATE will segment accordingly.
In short: WPML is segmenting per word because each word is wrapped in its own <span>. That behavior is expected and by design. If you want smoother translation segments, the markup needs to be simplified so that sentences or paragraphs are wrapped instead of individual words.
