Random segmentation results

Question

Trados Studio 2024 - 18.0.2.3255: 
 I get random segmentation results, and do not understand why. I cannot reproduce the correct result that we had before, and that I managed to obtain again in one of my tests today. But I use exactly the same source file, template and settings... 
 - Until now, our segmentation settings worked correctly and automatically did not segment in this translation unit: 
 *.* - All formats|*.*| 
 - But now, in 9 cases out of 10, there is a segmentation after the 3rd character (*.*) - I tried adding an exception to the "Full stop" rule, but it does not have any effect, perhaps because of the "*" followed by a space (3rd and 4th character). Or is the problem due to the fact that the characters * and | have very special meanings in regular expressions? - The only correct segmentation result (no segmentation) I achieved was just after having reset the "segmentation settings" to the default settings. But this did only work once. ► Does anyone else experience the same kind of random behaviour with segmenation? ► Is there any rule or exception that allows me not to segment after *.*? 
 
 Correct segmentation that we had before and that I achieved once today: 
 
 Incorrect segmentation that I obtain in most cases (with exactly the same settings...): 
 
 I would appreciate your help!

RWS Community AI · Accepted Answer

Probability score: 0.7 
 Question improvement suggestion: Provide specific examples of the segmentation rules you have set and any changes made to the settings prior to experiencing the issue. 
 In the meantime, based on the information you have provided, here is a suggested answer to your question: 
 Hello, 
 It sounds like you're experiencing some frustrating segmentation issues in Trados Studio 2024. Let's break down the steps you can take to address this: 
 **Step 1:** Review Segmentation Rules 
 - Open your Translation Memory (TM) in the Translation Memories view. 
 - Right-click on the TM and select **Settings**. 
 - Navigate to **Language Resources** and select **Segmentation Rules**. 
 - Click on **Edit** to review the existing rules, particularly the **Full stop** rule. 
 **Step 2:** Add Exceptions 
 - If you haven't already, consider adding an exception to the Full stop rule. Click on **Add** and then **Advanced View**. 
 - In the **After break** dialogue box, you might want to add a specific string that accounts for the asterisk and space, such as `\s*[*]`. This could help prevent segmentation after the third character when it follows the specified pattern. 
 **Step 3:** Test Your Changes 
 - After making adjustments, test the segmentation with your source file again to see if the changes have resolved the issue. 
 - If the problem persists, try resetting the segmentation settings to default and then reapplying your custom rules. 
 **Step 4:** Check for Updates 
 - Ensure that your version of Trados Studio is up to date, as updates may include fixes for segmentation issues. 
 **Step 5:** Community Feedback 
 - Since you mentioned that others might be experiencing similar issues, consider sharing your findings in the RWS Community to gather insights from other users who may have faced the same problem. 
 By following these steps, you should be able to refine your segmentation settings and achieve the desired results. If you continue to face challenges, please provide more details about the specific rules you have set, and we can explore further solutions together. 
 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

Trados Studio > 1. Trados Studio

Random segmentation results