#983 Background not red when match from a tmx in the tm/mt folder is auto inserted

[Damien Rembert]

When a match from a tmx in the tm/mt folder is automatically inserted (ie 100% match), the background does not go red. It does when the match is manually inserted.
I think it would be clearer if whenever the origin of the translation is in the tm/mt folder the background turned red whether it's manually or automatically inserted.
Actually I think it's especially important that automatically inserted matches are marked, since it means this appears in the editor possibly without my looking at the tm pane (and therefore noticing the origin of the match).

Using OmegaT_5.2.0_Beta_Linux_64.

Not sure if this is a bug, if not could this be moved to Feature Request, please?

Thanks!

[msoutopico]

I don't know what "red background" you're referring to, but here come a couple of tips.

You can "Mark Auto-Populated Segments" in the View menu, and that will affect the background of segments pre-translated with matches from /tm/auto or /tm/enforce.

You can also unselect the option "insert the best fuzzy match" in Options > Preferences > Editor.

[Damien Rembert]

Thanks for the reply

I'm referring to the background of the "target" field of the segment currently edited in the editor pane.
The behaviour I'm expecting is the one described in the documentation:
https://omegat.sourceforge.io/manual-standard/en/project.folder.html#d0e4596
I have the "Mark Auto-Populated Segments" box ticked but the two folders you mention do not apply to every case that requires this behaviour.
The folders /auto and /enforce are for pretty trustworthy translation memories that you would like to insert in the whole project directly, but if you want to use a translation memory made by using Machine Translation (which I think is what the "MT" in /mt stands for), getting a special heads up for you to check every segment from that tmx extra carefully as you go then the behaviour I describe would be great...
Again, maybe I misread the documentation and this ticket should be a feature request but I have a vague memory of it working that way in the past.

Maybe a more convenient temporary fix than disabling the automatic insertion of fuzzy matches (since you might have other perfectly good translation memories), I would recommend putting the tmx file in a /penalty-21 folder (change the number in the name of the folder to be just under the automatic insertion threshold for fuzzy matches, 21 works for me as matches need to be 80% or above to be inserted with my settings).

[Briac Pilpré]

I didn't know about this feature: it works when you explicitely use the "Replace with Match or Selection" on a match from tm/mt on the active segment (so the red background isn't kept after leaving the segment).
If there's a 100% match in a tm/mt entry, it will be used before the segment is activated, thus you will never see the red background.
If you have something set in the preference Editor ‣ Prefix, the prefix should always be inserted whatever the match % is so you can check the quality of the MT match.

[Jean-Christophe Helary]

Fixed in https://sourceforge.net/p/omegat/bugs/1144/.