Checkmate - Can't find trailing white space mismatch in source/target

[Former user]

Hello. Even though the option "warn if a target entry has a difference in trailing white spaces" checked in Checkmate settings, I can't get the tool to actually display these errors.

I also added a regex under Patterns to check for .\s+ in source (+ is just there to include more than 1 spaces) and check for <same> in target. I also tried w/o using + in source regex, with the same result (no matches).

Still, the tool doesn't find anything and I know that I have the target segments are missing spaces after periods.

Am I doing something wrong?

I'm using 1.8.0_121 release of Checkmate.

[BN]

a self-correction - .\s+ should have an extra \ in front of it. Bitbucket removed it for some reason.

[YvesS]

Things depend on what type of file you are processing. If it is an XLIFF 1.2 file, I would guess that it does not have the attribute xml:space="preserve" set,or it is present but set to "default". See http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#xml_space for details on XLIFF 1.2 and white-spaces.

If you add (or update) the xml:space="preserve" attribute in the <file> element of your document, and the extra/missing white-spaces should be flagged. Placing it on <file> will affect all <trans-unit> in that <file>. You can also place it on selected <trans-unit> elements.

[YvesS]

Another way to get the XLIFF white-spaces checked if your files do not use xml:space is to create a filter configuration (.fprm file) for XLIFF (okf_xliff) where you set the option "Preserve whitespace by default".

See http://okapiframework.org/wiki/index.php?title=Understanding_Filter_Configurations for more information on how to create custom filter configurations. To use your custom configuration in CheckMate, make sure to specify it in the "Configuration" field of the "Input Document" dialog when you add the file to the session. See http://okapiframework.org/wiki/index.php?title=Input_Document for details.