Hi John Fry ,

I can't recreate the same as you get, so I get hits from my TMs first, if they are on the top of the list. However, may I suggest to check the TM minimum match value, maybe lower a bit, to 90% or lower to see if that gives priority in the hit results over machine translation.

In my case, it's lowered to 70, nevertheless the rule is that the TMs are prioritized as they are first at the top.

If that fails again, try with a new project, new file created from scratch and no project templates, to avoid inheriting settings from the earlier Studio version.

Hope it helps?

Regards,

Oana

Hi John Fry ,

I can't recreate the same as you get, so I get hits from my TMs first, if they are on the top of the list. However, may I suggest to check the TM minimum match value, maybe lower a bit, to 90% or lower to see if that gives priority in the hit results over machine translation.

In my case, it's lowered to 70, nevertheless the rule is that the TMs are prioritized as they are first at the top.

If that fails again, try with a new project, new file created from scratch and no project templates, to avoid inheriting settings from the earlier Studio version.

Hope it helps?

Regards,

Oana

No, the TM results are fine, the problem is with the MT results only. The problem is that if I use multiple MT engines, no matter how I order them in Settings, the Language Weaver results are displayed first (at the top of the Translation Results window). The results of the other MT engines then appear below the Language Weaver result in the desired order. But there is no way to dethrone Language Weaver from the top spot. This started happening after the latest upgrade. 

 John Fry ,

Thank you for the clarifications, John. While I haven't managed to recreate the issue, at least on my side and with my machine, I know the appstore team is already aware of this situation and are investigating it. So we'll most likely address the issue and fix it in the next plugin update.

Regards,

Oana