MadCap Lingo and Studio 2015

Question

One of our customers sent us files for translation using MadCap Flare. We are using Studio 2015 and the files seemed to work fine in Studio. We translated the files, reviewed them, cleaned and saved them in the same folder structure in which they were delivered. 
 However, our customer wants to use the files in MadCap Lingo and they are having trouble with our translated xlf files because the source is overwritten. 
 When opening the target files in Notepad++ both the source and target are visible. 
 Does anyone have any experience with MadCap Lingo and Studio 2015? A quick reply would be appreciated, of course the customer needs the files yesterday. 
 Kind regards, 
 Anthoinette

Paul · Accepted Answer

Hi Anthoinette, 
 
It sounds to me as though you have created a custom xml filetype that extracts the source text from the source element of the xliff, and then just overwritten it with the translation. This is not the way to work with these files. You should do one of the following: 
 
1. Handle them as xliff files in Studio and then the translation will be written into the target by default, or 
2. Copy the source into the target element and then translate the target element with a custom xml filetype 
 
Both of these methods will provide you with the desired file for your customer. 
 
Regards 
 
Paul

Tyke · Answer

Hi Anthoinette, 
 
I regularly receive xlf files from a client, either from MadCap Flare or MadCap Lingo and the client does not have any problems at all reading in the translated files that I return. I have the xlf file type installed and it works fine. There is just one thing that must not be done and that is the source text must not be edited in any way at all. 
 
Regards 
Ben

Trados Studio > 1. Trados Studio

MadCap Lingo and Studio 2015