WPML xliff custom filter - how to use text from source field as source in Trados and text from target field as target in Trados

Question

I have a custom filter for WPML xliff files. In that filter I translate only the //target elements. Now the client updated the page and sent me again the xliff. Now in Trados I see as source the already translated text. Is there any way to show there the text from //source and to put into the target column the text from //target element? 
 Here are the current settings:

Paul Filkin · Accepted Answer

Sotir Rangelov 
 Your root xpath is incorrect. I often find it helps to start at the bottom of the file as you often see the structure more clearly:

Daniel Hug · Answer

Sotir Rangelov 
 The XML file type is monolingual only. There are several ways to handle a bilingual file like yours, but I know that a proper bilingual XML file type is on the horizon - you should get to Paul Filkin 
 about that. May I assume that you are using Studio 2021?

Paul Filkin · Answer

Sotir Rangelov 
 The only way to achieve what you're after now is to use the XLIFF filetype for your XLIFF. The problem I guess you're having is that WPML is normally pretty awful because they seem to like dumping large CDATA sections into single translation units instead of creating more localization appropriate XLIFF files. 
 As mentioned there is a new filetype on the horizon that will be available via the appstore with the release of Trados Studio 2021 SR2 in a couple of weeks (all being well). This filetype is vry flexible and will allow you to achieve what you're after. You can watch this session from the Elevate Conference (until the end of November 2021... for the benefit of anyone reading this post in the future!): 
 https://app.swapcard.com/event/elevate-the-trados-online-conference/planning/UGxhbm5pbmdfNjc0MjU2 
 It will not be available for Trados Studio 2019, nor for earlier versions of Trados Studio 2021. It will be an SR2 and above plugin only.

Daniel Hug · Answer

Sotir Rangelov 
 You have a couple of options with 2019. One is the bilingual Excel filter - don't remember whether that worked with embedded content processors already. The other one would be that you align source and target using Studio's Aligner and create a new TM with the results. The drawbacks are that it's a bit time-consuming and that you don't know for sure what was entered where. Say they have "Our new product" twice, once it's translated as "Unser neues Produkt" and the other time for SEO reasons as "Neu: unser Produkt", you won't know which one was used where. The benefit is that you have segmented text. Bilingual filters usually won't segment text. 
 Of course you can use the XLIFF file type as Paul points out. 
 I managed using Okapi to produce a bilingual xlf file with full segmentation from a bilingual XML file, but it does take quite some work to set up the process, and it will only work if source and target have the same number of paragraphs. It's lovely if it works but to does not always work. And the initial setup is quite a bit, as I said. 
 Daniel

Trados Studio > 1. Trados Studio

WPML xliff custom filter - how to use text from source field as source in Trados and text from target field as target in Trados

Top Replies