Marc Riera

I agree with you that the issue has deeper implications and I also find strange that a user could be paid less due to statistics not matching the threshold. I initially raised the issue because I found there was a change of behaviour that was not documented anywhere, and I did not find anything in the documentation implying the threshold would affect statistics. Personally, I find two acceptable solutions: Decouple statistics from the TM threshold (legacy behaviour). Add a note in both in the user...

I can confirm the problem exists in 5.3 and is not present in 5.2, where there is no option to adjust the match threshold.

Yes, the numbers are slightly different in 5.7.1, but there is the same big change in the statistics when changing the threshold.

Match statistics are affected by fuzzy match threshold

Sorry if I was not clear, I ran the original test with OmegaT 6.0.0 with the new XLIFF filter (the one based on StaX). I have the legacy filter disabled. I just ran the same test with the latest weekly build (6.1.0 Beta) and the same happens. I am attaching the log in case there is anything useful. Thanks!

Unable to use XLIFF file as TM

Link to GitHub pull request with the patch: https://github.com/omegat-org/omegat/pull/37

Allow users to choose Apertium server