Improve error for "No source segment found for target segment id='N'"

From Manuel:

I am using Rainbow to apply segmentation to XLIFF files and due to differences in punctuation and spacing between the source and target I get some warnings like this:

Input: /C:/path/to/file.xlf WARNING: No source segment found for target segment id='2': " blabla ". It seems the id (2, in this case) refers to the number of the segment within the trans-unit in the target file. The fact that it provides the text where alignment fails (e.g. "blabla") helps tracking the issue sometimes. However sometimes that text appears very frequently in the file and examining one by one is very time-consuming. Hence, a suggestion meant to improve usability: Would it be possible to include the trans-unit's ID from the source file also in the log? That would help.

This message is GenericSkeletonWriter.getSegmentedText(). Currently it has no direct access to the TU ID.

Comments (2)