Import tmx to a client provided project without overwriting fragment matches

Question

Hi! 
 I get a tmx-file with a machine translation from my client, but when I import it via project settings - all langages pairs - translation memory and automated translation, the MT overwrites any other resources that would normally show up, i.e. in the fragment matches window I get the message "Exact match found (no fragment search performed). Also, the machine translation is usually (not always) top of the list, even though there are 100 % or CM matches from other translation memories, in the Translation results window. I obviously don't want to miss any "real" translations, so how do I make the MT "less important"? I want other TM matches to have precedence, and I want to still be able to see fragment matches. I have tried to create a local TM and import the MT tmx there (via Translation memoy view in Trados), but then it doesn't show up at all. 
 I use Trados Studio 2022 SR2, and when importing the tmx-file, I have no idea which settings to use, so I only use the pre-chosen ones. I'm not very familiar with Trados, so I might very well have missed something obvious. 
 
 Kind regards 
 
 Rosanna Lithgow

RWS Community AI · Accepted Answer

Probability score: 0.8 
 Question improvement suggestion: Provide specific details about the settings you used when importing the TMX file and clarify if you have adjusted any of the default settings in the Project Settings. 
 In the meantime, based on the information you have provided, here is a suggested answer to your question: 
 Hello Rosanna, 
 Thank you for your detailed question! It sounds like you're encountering a common challenge when working with Machine Translation (MT) in Trados Studio. Here’s a step-by-step guide to help you prioritize your Translation Memory (TM) matches over the MT results and ensure that fragment matches are visible: 
 **Step 1:** **Adjust Project Settings** 
 - Go to **Home > Project Settings**. 
 - Under **Language Pairs > All Language Pairs > Translation Memory and Automated Translation > Search**, ensure that the option **Look up segments in MT even if a TM match has been found** is **unchecked**. This will prevent MT from overriding TM matches. 
 **Step 2:** **Set Minimum Match Value** 
 - In the same settings area, check the **Minimum match value**. You may want to set this to **100%** for pre-translation tasks. This way, only segments with exact matches will be pre-populated, and MT will not be used unless there are no TM matches. 
 **Step 3:** **Enable Fragment Matching** 
 - Still in the Project Settings, under **Segment Fragment Matching Options**, ensure that **TU fragment** is checked. This will allow fragment matches to be displayed. 
 **Step 4:** **Check AutoSuggest Settings** 
 - Go to **File > Options > AutoSuggest** and ensure that the **Fragment Matches** option is selected. This will help you see fragment matches as you type. 
 **Step 5:** **Review the Fragment Matches Window** 
 - If you want to see fragment matches even when there are TM results, go to **File > Options > Editor > Fragment Matches Window** and ensure that the option **Display results from the Fragment Matches window if the TM lookup returns no results** is selected. 
 **Step 6:** **Pre-translate Your Files** 
 - After adjusting these settings, run a **Pre-translate** batch task to ensure that your TM matches are prioritized and that the MT does not overwrite them. 
 By following these steps, you should be able to see your TM matches more prominently and still access fragment matches without them being overridden by MT results. If you continue to experience issues, please double-check the settings and consider creating a new Project TM specifically for this task. 
 I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again. 
 RWS Community AI

Seraina Hartmann · Answer

Hi Rosanna Lithgow 
 It actually is always there in the Editor view: 
 
 But if a TM match is found, it automatically jumps back to the Translation Results Window (red arrow). 
 This is default behaviour. 
 Studio only jumps to the Fragment Match Window if no matching TU can be found the TM. In your case, there is always a matching TU form the TM as you created a TM which contains a match for every segment. Therefore, Studio will never jump into the fragment section automatically. 
 The only way to pin the Fragment Matches Window is to right click on the window and set it as "Floating": 
 
 You can now move it wherever you like (e.g. to a second screen) 
 
 or integrate it in the Editor View by moving to the position you'd like to have it displayed: 
 
 Result:

If you later on whish to change the Window Layout, click on Reset Window Layout under the View tab:

Maybe this helps. 
 
 Best 
 Seraina

Trados Studio > 1. Trados Studio

Import tmx to a client provided project without overwriting fragment matches

Why you can’t see them in the Fragment Matches window

Why you can’t see them in the Fragment Matches window