Idea Delivered Partially

PerfectMatch does have a hidden feature whereby it will attempt to merge up to three segments. So if in a predecessor document, one or more segments have been merged to include up to three segments in one, then PerfectMatch should still be able to leverage such merged segments. Split segments are not supported at this stage.

PerfectMatch to check for merged/split segments

It would be ideal if PerfectMatch could take split or merged segments into consideration. It would especially be useful when you use PerfectMatch to load a new version of a document you are translating. Split/merged segments are not filled because the segmentation re-applies the same patterns as it did by the segmentation of the first document. PerfectMatch could check if the previous version has split/merged segments and make some tests (especially for merged segments) on the new version to see if the content could be re-used at these specific locations

Laurent Pierret

  • Why PerfectMatch only? It would be great to have a pre-translate checkbox, smth like "Split/merge segments where it gives better result"? I translate a file which is updated on a regular basis. It contains a couple of dozens identical tables with different numbers but same headings. One of such headings is 'Remaining To Go' split in two halves with paragraph mark. Both 'Remaining' and 'To Go' can be translated into my native language with one (and the same) word. As a result, I have two identical  words. Filtering is useless here because I can filter but can't merge segments as filtered. Pre-translate is not only useless but even sabotaging because it leaves the halves wrongly separated and skips the segments as they are already confirmed. I have to use 'Find' to merge such segments manually. It would be much easier if it was automated.

  • Hi Daniel. Is it a configurable settings or is it embedded in the functionality itself? I can't find any corresponding setting. If it is part of the functionality, it does seem to be working in a reliable way.

  • Hi Laurent - has been available since Studio 2014, if I remember correctly - but has been in the product for a while.

  • Hi Daniel. Thank you for the quick feedback. Is this feature available in version 2015 already or from 2017 only?