Long XLF segments from client's CMS export

Question

Hello! This question was asked during the Q&A session this afternoon, and I believe Paul said that it's a high-level query so posting here:

We have received an XLF from a client containing really long segments - how can we re-segment these long segments so it's easier for the translators to work on them, but also so it doesn't affect the XLF from being re-imported into the client's CMS at the end of the project?

Thanks in advance for any assistance on this point!

Paul · Answer

Miranda Sambidge 
 Thanks for sending the question into here... more space and time to answer it! But first note that this isn't the best way to prepare XLIFF and if you have a willing client they might be prepared to listen and follow the intent of the XLIFF specification to avoid these sort of workarounds. 
 If they won't you basically have two options: 
 
 use the embedded content filter in the XLIFF filetype 
 treat the file as if it was monolingual and handle it using a custom XML filetype 
 
 So I mocked up a file like this: 
 
 In Studio when I open it I see this which is probably reprepsentative of what you are seeing: 
 
 It's all in just three segments, one for each of the Translation Units in my file. To solve this I need to use the embedded content option and add a few rules to pick up the tags and exclude them to force the segmentation:

Now when I open the XLIFF I get this: 
 
 Depending on the complexity of the content in your CDATA section (which is what I believe you have) this is probably the simplest solution. But if not then just create a monolingual filetype and handle it that way. In my example there is no target element in the XLIFF yet, so I just opened it with Studio, copied source to target and saved the target file. Now I have this one: 
 
 I can now create a custom XML filetype to translate the target element alone and use the embedded HTML filetype to handle the markup and segmentation. So my filetype has two simple rules: 
 
 The embedded content processor is set up like this: 
 
 The result is this: 
 
 I didn't dwell on how to create a custom XML filetype but if you need more help with that this may help: 
 https://multifarious.filkin.com/2014/06/01/custom-xml/ 
 I also put my sample here so you can have a play... that may help too: 
 dumped_XLIFF.zip

Trados Studio > 1. Trados Studio

Long XLF segments from client's CMS export

Top Replies