"Probability score": 0.8

"Question improvement suggestion": Please provide more information about the specific settings you have in place for segmentation rules in Trados Studio. Also, it would be helpful if you could share any error messages you've encountered while trying to solve this issue.

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

Hello Rita,

It seems like you're dealing with a segmentation issue in Trados Studio 2022 SR2. The software is likely treating the brackets as separate segments due to the current segmentation rules.

Here's a step-by-step guide on how you can modify the segmentation rules:

Step 1: Open Trados Studio and go to the "File" menu.

Step 2: Click on "Options" and then select "Language Pairs".

Step 3: Choose "All Language Pairs" or the specific language pair you're working with.

Step 4: Click on "Common" and then "Segmentation Rules".

Step 5: In the "Before break" and "After break" fields, you can modify the rules to avoid segmentation between brackets. You might need to use regular expressions to achieve this. For example, you could add a rule that ignores a period (.) if it's followed by a closing bracket ()), which might solve your issue.

Please note that modifying segmentation rules can affect the entire project, so it's recommended to test these changes on a small portion of your text first to ensure they produce the desired results.

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

I cannot find step4

"Probability score": 0.7

"Question improvement suggestion": Please provide more specific details about the issue you're encountering. Are there any error messages appearing when you try to find the "Segmentation Rules" option? Also, it would be helpful if you could share a screenshot of what you see in your settings.

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

Hello,

I'm sorry to hear that you're having trouble finding the "Segmentation Rules" option in Trados Studio 2022 SR2. Here's an alternative way to access it:

Step 1: Open your Translation Memory (TM) in Trados Studio's "Translation Memories" view.

Step 2: Right-click on the TM and select "Settings".

Step 3: Go to "Language Resources", select "Segmentation Rules" and click on "Edit".

Step 4: Select the "Full stop" rule and click on "Edit".

Step 5: Click on the "Add" button to add an exception.

Step 6: Set a name for your exception and click on the "Advanced View" button.

Step 7: Leave the "Before break" dialogue box as it is and at the "After break" dialogue box please add this string: \xa0

Step 8: Press "OK" when closing the dialogue boxes.

Please note that these steps are for editing the segmentation rules within a specific Translation Memory. If you want to change the rules for all your projects, you'll need to adjust the settings in the "Project Settings" menu instead of the "Translation Memories" view.

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

Dema Solutions SRL 

I think it's actually the asterisk as it might be seen as formatting used for emphasis like a heading for example.  I have no real evidence for this, but noted that if I remove them the segmentation doesn't occur.

thanks Paul.

Any idea how to avoid that from happening?

 Dema Solutions SRL 

Right now I don't, but I'll investigate a little with the dev team today.

I do wonder why you want to prevent this though?  It looks like a desirable feature since you'd get better leverage when it's segmented.

I guess if you are using a TM that was created by some tool that didn't do that then now you don't get the matches and perhaps that's the reason?

Dema Solutions SRL 

Could you upload a short sample file? That would allow us to play around a bit.

Hi Paul, that's exactly the reason, the TM was created in a different tool and is now making me lose leverage for those segments.

But... thanks to your comment I think I managed to find the rule, I have added the asterix to the exclusion list in full stop rule!

\.+[\p{Pe}\p{Pf}\p{Po}"-[\u002C\u003A\u003B\u002A\u055D\u060C\u061B\u0703\u0704\u0705\u0706\u0707\u0708\u0709\u07F8\u1363\u1364\u1365\u1366\u1802\u1804\u1808\u204F\u205D\u3001\uA60D\uFE10\uFE11\uFE13\uFE14\uFE50\uFE51\uFE54\uFE55\uFF0C\uFF1A\uFF1B\uFF64]]*

it now looks as I intended!!

thank you so much for your help as usual!

Rita

Daniel Hug 

Here's one I created when I tested it:

{
	"A_TFDDTBRIEF_RS": "(*Fig.*) (Schema di montaggio della rete RS)",
	"A_TFDDTBRIEF_RD": "(*Fig.*) (Schema di montaggio della rete RD)"
}

And another format using an array I checked out of interest:

{
  "A_TFDDTBRIEF": [
    "(*Fig.*) (Schema di montaggio della rete RS)",
    "(*Fig.*) (Schema di montaggio della rete RD)"
  ]
}

The same result occurs with the OOTB JSON and also with the SuperText app., which is what makes me think the asterisk has some special meaning.  I just cannot find any evidence for this meaning yet!

Dema Solutions SRL 

Nice work!! You did well to find that in there!!