#1017 Enforced matches are ignored on the CLI with Okapi XLIFF filter

[msoutopico]

Preconditions

Source fies: Translated XLIFF files, the sample segment has a translation that comes from the e
TM: The sample segment as an enforced match in one of the TMs in /tm/enforce

Steps to reproduce

1. Unzip project package attached.
2. Run OmegaT on the project on the command line (java -jar /path/to/OmegaT.jar project --mode=console-translate).
3. Check the target file and the 3 master/exported TMs

Expected result

The match coming from the TM in /tm/enforce is used as the translation. The 3 exported TMs contain the master version of the translation.

Actual results

Matches coming from the TM in /tm/enforce are ignored and the original translation from the source XLIFF file is maintained. The 3 exported TMs are empty.

Additional information

The expected results are the actual results when you load the project in OmegaT (GUI) and press Ctrl+D.

[Briac Pilpré]

I can't reproduce the bug in 5.3.0 and in the current version.

When launching from both Powershell and WSL/Ubuntu, the target files have the expected "Enforced translation 1 - DEFAULT" translation and the three TMs are correctly generated.

[msoutopico]

I found the problem. I was running it on WSL and the symlink from /mnt/c/Users/souto/AppData/Roaming/OmegaT to ~./omegat was wrong :/ My bad that I didn't see that Okapi plugin was not being loaded, I've ashamed of myself. Thanks for looking into it.

[msoutopico]

The bug can be dismissed.