<b>Background of the issue: </b>
I am trying to translate pages by exporting XLIFF files, translating them, and then importing the translated XLIFF files. The issue can be seen on this page: hidden link.
<b>Symptoms: </b>
When I open the page in the WPML Advanced editor, the translated texts imported through the XLIFF file do not appear. Instead, there is no Albanian translation for the original English texts.
<b>Questions: </b>
Why are the translated texts not appearing in the WPML Advanced editor after importing the XLIFF file?
Is there a problem with the imported XLIFF files?
here I insert the link to the XLIFF file for the page: hidden link
please take a look and let me know if there is any syntax error in it.
Please note that this is the expected behavior. The XLIFF translations uploaded to WPML do not automatically show up in the Advanced Translation Editor (ATE). While the translations will be visible on the front end after uploading an XLIFF file, they will not appear in the ATE. If you wish to use the ATE, you will need to re-translate the content there.
Hi and Thanks for your reply.
the problem I face is actually we have a pricing page: hidden link
this page is created with elementor and elementor pro and uses a few html widgets.
there are complex HTML+CSS+Javascript designs in them.
when I uploaded the translated xliff file and loaded the page, unfortunately the page was messed up. I noticed that the issue is with these html widgets.
but when I Opened the page with ATE and manually translated the page and hit complete, the page rebuilt successfully and with a bit manual CSS edits it became acceptable.
I use a tool that I made myself for Automatic Translation of XLIFF files (with help of generative AI -gemini- and a n8n workflow) and it works perfect and saves me money and time. so I seek a solution that solves this issue.
Thanks in Advance
ATE was designed and developed to make translations easy while handling all the technical aspects in the background.
I suspect that your tool may have disrupted complex HTML, CSS, and JavaScript elements during translation, without accounting for their structure. Even changing a single character could result in a broken page or malfunctioning code, and when you uploaded the translated XLIFF file, the translated page doesn't work as expected.
We are not able to debug third-party tools, so you would need to investigate this on your side to determine exactly what happened during the translation process. Comparing the downloaded and uploaded XLIFF files could be a good starting point.
However, if you continue to experience these issues, I recommend using ATE for your future translations to avoid such problems.
Thank you, while I am investigating the issue I noticed some unexpected behavior in WPML functioning.
when a page translation job is created, it appears in translations section for translate, where I can export it to XLIFF file.
if translated page does not exist, and is created for first time it will be generated from XLIFF file.
but when I want to retranslate the page I do not see any difference in the final page. (it seems it does not reflect changes)
I did the following for new translation to be done:
I deleted the translated page and I added a translate job for it and then it recreated the page and reflected the changes.
what I expect is that even when the translation is complete and I reupload the revised XLIFF file for same completed job it reflects the changes.
even when I want to regenerate the job, the page that I want to translate does not appear in the list of Pages in Translation Dashboard , unless I make a small change to the original page then I can see the page in the list of pages and I can create the job.
even when I make changes to the job and translate it and then upload it I do not see any changes in the final result. I suspect there is any cache that prevents the changes to reflect.
or maybe the XLIFF file just consider additional changes and not the contents that are already translated. this becomes a problem when the layout of the page is broken and I am trying to fix it by reuploading the revised translation job.
I want to be able to simply import revised XLIFF file for same job and changes be reflected.
also I have another request, and that is how can I integrate export and import of XLIFF files with my Custom WordPress Plugin. I will be thankful if you can share any developer documentation on this. so I can automate the whole process.
Thank you in advance
The results you are seeing are expected behavior. There is no way "to simply import revised XLIFF file for same job and changes be reflected." You need to follow the steps you described to upload the translated XLIFF file.
