Coded-text mode for Issue data in QualityChecker

The QualityChecker steps currently provide an Issue with text and positions in "display" mode (how the original segment looks like).

This is not OK when the client of the steps need to work at the TextFragment level, for example to present the user with the segment to modify and merge the corrected segment back into the initial source document.

We need a mode that allows the client to get the Issue object with:

the source and text field being the coded-text string for the source and target
the source and target start and end position referring to the coded-text rather than the display text.

This mode should be set to false by default for backward compatibility and the methods of the AbstractChecker should remain backward compatible as well.

Comments (3)