Michael Bauer

Quite a tricky question really and depends on a couple of things.  First of all, if you disable the memsource filetype and instead add *.mxliff to the File dialog wildcard expression for the default XLIFF filetype in Studio then this filetype has the ability to segment the file as you need if processed with the appropriate TM.

However, this may not be successful if the memsource XLIFF has been prepared with <seg-source> to control the segmentation of the XLIFF as the person preparing the file intended (read "intended").  You could remove all the segmentation markup but in my opinion this would not be wise.  Your best bet is to take the file back to your customer and ask them to prepare it properly for you.

Michael Bauer

Quite a tricky question really and depends on a couple of things.  First of all, if you disable the memsource filetype and instead add *.mxliff to the File dialog wildcard expression for the default XLIFF filetype in Studio then this filetype has the ability to segment the file as you need if processed with the appropriate TM.

However, this may not be successful if the memsource XLIFF has been prepared with <seg-source> to control the segmentation of the XLIFF as the person preparing the file intended (read "intended").  You could remove all the segmentation markup but in my opinion this would not be wise.  Your best bet is to take the file back to your customer and ask them to prepare it properly for you.

Thanks Paul, I'll try that - I did a search in one of the files for seg-source and couldn't find anything so fingers crossed. There's unfortunately no chance of this client to fix their approach, I'd have a better chance of teaching cows to sing Puccini ;)

Test delivered some files, your solution seems to be working, at least for now, many thanks!