Skip Navigation

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

Problem:
The client is experiencing issues with WPML where making corrections in the original language during the translation process causes the translations of the corrected lines to be deleted.
Solution:
We explained that the current behavior is expected because the Advanced Editor's translation memory only recognizes 100% identical segments. When the original text is edited, the translation memory no longer matches, resulting in the deletion of the translations for those segments. We acknowledged the need for fuzzy matches to address this issue but also noted that implementing such a feature is technically complex and not currently planned.
We recommended that the client should finalize the content in the default language before starting the translation process to avoid frequent changes that could disrupt the workflow and lead to the need for retranslation. This approach aligns with the original design of WPML, where content is translated only when it is complete and ready.
We also mentioned that we have received similar requests from other clients and that we will consider the issue for future improvements.

Please note that this solution might be irrelevant if it's outdated or not applicable to your specific case. If you're still facing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.

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 5 replies, has 2 voices.

Last updated by Laura 1 year, 3 months ago.

Assisted by: Laura.

Author Posts
February 9, 2024 at 2:42 am #15283822

michaelW-144

Hy WPML Team,

I use WPML since some years, and always struggle with the fact, that if I make small changes in the first language (for example corrections of mistakes), it kills the translations of this line too.

When I translate into another language, I often find some mistakes in the first language (left side). As I am not able, to correct them directly (left side), I have to switch to the original page, to make the correction, and than go back to proceed in translating. This is a break in the workflow.
But it makes no sense, to collect all mistakes and correct them after translation is finished, because when I correct the lines afterwards in the first laguage, the system deletes all translations of this line, even the translations are correct itself.

What is the best way to go, when I find mistakes in the first language, while translating without interrupting the workflow and without deleting the translations after correcting the mistakes in the first language?

Thanks for your ideas!

Best regards
Michael

February 9, 2024 at 11:42 am #15285749

Laura
WPML Supporter since 05/2018

Languages: English (English ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Hi Micheal,

thanks for contacting us.

Unfortunately at the moment what you're experiencing is expected and there is no solution to it.

The Advanced editor relies on a translation memory, which can only match 100% identical segments. The moment you do small edits to the original the Translation memory doesn't match anymore and that's why you see your translation "erased".

We should implement fuzzy matches but it's not an easy task so at the moment we don't have a plan for adding them.

February 9, 2024 at 12:44 pm #15286156

michaelW-144

Hi Laura, thank you for your reply. So just one question. Wouldn't it be possible, to create a switch/button that enables something like a "disconnection" of the translation from the first language? Let's say, you are ready with the translation, than you "disconnect" this translation from the first language, so that you can make changes there, without harming the translation.
If the editor wants to connect it again, he could "switch" it back, knowing, that the changes will affect the translation in the way we kno it.
I know, this sounds simple when thinking about it, don't know how ambitious the implementation is.
Best regards
Michael

February 9, 2024 at 12:54 pm #15286198

Laura
WPML Supporter since 05/2018

Languages: English (English ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

I can suggest this idea but I don't think it can be easily implemented.

The idea however is that you first create the site in your default language, and only then you translate it. Of course you may need to change something later, but it shouldn't be as common.
When WPML was first created you could only translate manually yourself or send to a translator. You wouldn't send an unedited text to a translator, because you'd need to pay them again for each review. So why you would translate an incomplete text? It would be better to only translate when you're 100% satisfied with the original.

February 9, 2024 at 1:10 pm #15286223

michaelW-144

"It would be better to only translate when you're 100% satisfied with the original."
There are several reasons. In one website for example we create textes for projects/events. The text will change with the progess of the project/event (for example dates, spots, persons etc.), but affect just one language at this time for several reasons (for example the projects take place in Germany, France and Spain, with the same text, but different persons, different times, at different spots etc.). If this effects just the translated text, it is no problem. But if it affects the first language, we have to rewrite the translations.
So it was just an idea from my side! Maybe I am the only one, who struggles with this issue, so there is no need for a change. 🙂
The rest of WPML works perfect for me, by the way! Great work!

Thanks again for your feedback!

Sunny regards from the DR
Michael

February 9, 2024 at 5:38 pm #15287221

Laura
WPML Supporter since 05/2018

Languages: English (English ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

We had some request for this, but as I said, it's technically complex to implement. But we will take the issue into consideration.