Detecting language please wait for.......
when merging segments in Studio 2019 SR-2 CU 5 (18.104.22.168), automated translation is applied - although I have deactivated the corresponding option:
This is quite annoying as the MT proposal overwrites the content in the target segment that I have entered before merging (so I need to copy my draft translation to Notepad before merging in order to ensure that it is not lost).
This happens both with SDL NMT and with the DeepL plugin (I have the latest versions installed).
I have not yet tested the final beta of CU6, but the final draft of the release notes does not mention a potential fix (SDL Trados Studio 2019 SR2 CU6 - Final Beta (22.214.171.12495)
I have now also deactivated "Perfrom lookup when active segment changes" and "Apply best match after successful lookup" - but still the MT proposal overwrites the target segment content after merging
Now I have found it: "Apply better match if found in TM after merging segments" needs to be activated, and actually blocks the MT proposal from being inserted in the merged target segments. But this option is misleading as MT matches are not "found in TM".
Hello @Christine Bruckner
I know what you mean, I was faced with this problem many many times. And what you found is all the more misleading given that I am using a French software version and that TM in English is MT in French and vice-versa, and you never know... the translation...
So the simple question is: if we want to avoid the issue you raised, should we check or uncheck the "Apply better match if found in TM after merging segments" box?
Hi Gérard, we need to un-check the option "Apply better match if found in TM after merging segments" to avoid that any match (from TM or MT) overwrites our translation draft when segments are merged.