Probability score: 0.8  

Question improvement suggestion: Include any error messages received during the process and specify if any troubleshooting steps have already been attempted.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It seems you are experiencing an issue with fuzzy matches not being displayed for long segments after upgrading to Trados Studio 2024 SR1. Here’s a step-by-step approach to address this:

**Step 1:** Verify the Fuzzy Match Settings  

- Go to **Project Settings** > **Language Pairs** > **All Language Pairs** > **Translation Memories and Automated Translation** > **Search**.  

- Ensure that the **Minimum match value** is set appropriately (default is 70%). You might want to try lowering it to 65% to see if it retrieves more matches.

**Step 2:** Check the Translation Memory (TM)  

- Confirm that the long segment (~160 words / 2000 characters) is indeed stored in the TM and that it has been confirmed correctly.  

- If possible, create a new TM and test if the issue persists with it.

**Step 3:** Test with Different Segment Lengths  

- As you mentioned that shorter segments return fuzzy results correctly, try testing with segments of varying lengths to see if there is a specific threshold where the issue occurs.

**Step 4:** Review Recent Updates  

- Since you upgraded to SR1, check if there are any additional updates or patches available that might address this issue. Sometimes, newly released updates can resolve bugs introduced in previous versions.

**Step 5:** Consider Workarounds  

- If the issue persists, consider using a different fuzzy match threshold temporarily, or manually inputting the translation for segments that should return a fuzzy match.

If these steps do not resolve the issue, it may be beneficial to monitor for any updates from RWS regarding this specific problem, as it could be a known bug introduced in the latest release.  

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

Probability score: 0.8  

Question improvement suggestion: Include any error messages received during the process and specify if any troubleshooting steps have already been attempted.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello,  

It seems you are experiencing an issue with fuzzy matches not being displayed for long segments after upgrading to Trados Studio 2024 SR1. Here’s a step-by-step approach to address this:

**Step 1:** Verify the Fuzzy Match Settings  

- Go to **Project Settings** > **Language Pairs** > **All Language Pairs** > **Translation Memories and Automated Translation** > **Search**.  

- Ensure that the **Minimum match value** is set appropriately (default is 70%). You might want to try lowering it to 65% to see if it retrieves more matches.

**Step 2:** Check the Translation Memory (TM)  

- Confirm that the long segment (~160 words / 2000 characters) is indeed stored in the TM and that it has been confirmed correctly.  

- If possible, create a new TM and test if the issue persists with it.

**Step 3:** Test with Different Segment Lengths  

- As you mentioned that shorter segments return fuzzy results correctly, try testing with segments of varying lengths to see if there is a specific threshold where the issue occurs.

**Step 4:** Review Recent Updates  

- Since you upgraded to SR1, check if there are any additional updates or patches available that might address this issue. Sometimes, newly released updates can resolve bugs introduced in previous versions.

**Step 5:** Consider Workarounds  

- If the issue persists, consider using a different fuzzy match threshold temporarily, or manually inputting the translation for segments that should return a fuzzy match.

If these steps do not resolve the issue, it may be beneficial to monitor for any updates from RWS regarding this specific problem, as it could be a known bug introduced in the latest release.  

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