The step that is not working is the export function. The problem is that when we upload the XLIFF's WPML gives us to a CAT tool, the body of the post is given in one huge segment. The breaks are not happening. This used to not be a problem, about a month and a half ago we exported some posts and when we uploaded it to a CAT tool it was broken up into 90+ strings. Now that same post only gives us 7-10 strings when we upload the XLIFF to the same CAT tool and all of the body is in one string. I have tried exporting the XLIFFS multiple times with different posts and I have tried all three XLIFF versions. We do have to latest update of WPML.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
I'll help you get started while a supporter takes your case.
The XLIFF files takes the content as they are stored in the WordPress database, which means they will show the content exactly as WordPress would store any post or page.
However it's the CAT tools that take this information and then segments it, showing you the strings that you mention you saw before. the XLIFF files never have a unique segment, but say one segment per custom field, gutenberg block, etc (again, this is decided by WordPress, not us).
I'm pretty sure that if you upload the same XLIFF file in 2 different CAT tools you will get 2 different results, because each one has its own way of segmenting the content. the same is also true for our CAT Tool (The advanced Translation Editor).
We have tried uploading the XLIFFs in different CAT Tools, such as Crowdin and Trados, and we get the same result. To my knowledge there have not been any changes we have made to our WordPress settings. If there are any settings in WordPress that you recommend please let us know. This means that without any changes to our WordPress settings WPML went from giving us XLIFFs with 90+ segments to know only giving us 7-10 segments. I will share two files that WPML gave us that worked and two that did not. Hopefully that will be helpful in finding a solution.
1) I do not see any files in the shared folders, please recheck.
2) Can you please explain how are you exporting this XLIFF and sending it for translation? I am trying to clear things up and be sure what method you use. Since you might be also using our integrated translation service option.
Hi Drazen,
Sorry about that. The files should be in the shared folders now.
We are using WPML to export the XLIFF, which our in-house translators then put into Trados to translate.
It should work, as I can see from the old XLIFF file.
Please try one thing, make sure to have a backup just in case:
- Go to WPML > Packages
- Delete packages related to your example page (Change: It's Always a Possibility! )
- It should say something like Page Builder Page 8236, where the number is the ID of the default language page
- Go to WPML > Translation Management > Jobs, canceled if any ongoing jobs for this page
- Send the page again for translation.
- Go to WPML > Translation > Download XLIFF and check if the issue still happens.
Let us know how it goes.
Regards,
Drazen
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
