Daniel Hug 

I seen it in the past and I believe that the fix was doing all those changes from the Translation Memory view (instead of the Editor view, for example).

Daniel Hug did you get it fixed by using the TM View?

Hi ,

I encounter the same phenomenon when I use the TM view.

Steps to reproduce:

1) Open TM in TM view, close TM, select "Settings", select "Language Resources", select "Segmentation Rules" (in my case, that is for en-GB, first language in the list.

2) Add "vanilla rule" using the basic view, entering any Description (rule name) and OK-ing out.

3) Ok out of the Segmentation Rules dialogue.

4) OK out of the Settings dialogue

5) Remove the TM from the list.

6) Open the TM again, close to make "Settings" accessible, select Language Resources"/"Segmentation Rules" and the new rule is not in the list any more.

Can you replicate that?

Daniel

Hi ,

I encounter the same phenomenon when I use the TM view.

Steps to reproduce:

1) Open TM in TM view, close TM, select "Settings", select "Language Resources", select "Segmentation Rules" (in my case, that is for en-GB, first language in the list.

2) Add "vanilla rule" using the basic view, entering any Description (rule name) and OK-ing out.

3) Ok out of the Segmentation Rules dialogue.

4) OK out of the Settings dialogue

5) Remove the TM from the list.

6) Open the TM again, close to make "Settings" accessible, select Language Resources"/"Segmentation Rules" and the new rule is not in the list any more.

Can you replicate that?

Daniel

Daniel Hug 

This bug was already present in S2022. And I think it was resolved there. Astonished to find it again in S2024...

Jerzy Czopik 

Is there a workaround?

Daniel Hug 

AFAIR no, apart of using a version of Studio free from this bug. And I have just tested, the most recent Studio 2022 is also affected by this very bug. The segmentation rules can be modified, but are forgotten as soon as you close the settings window. Very bad indeed.

I can make these settings stick on a Language resource Template, it seems. Not ideal, but if you have to create a custom setting, this would be a workaround. FYI

 Daniel Hug See short video and I cant reproduce what you are saying.
I ran my test with TM's that originated from 2022 and 2024 TM.

In my case (naughty me) I have my TM folder being backedup on OneDrive. Sshhh dont make a fussy as it goes against best practice but it was a way of testing if there was a severe sync delay.  Do you have OneDrive that could be impacting?  I assume this is general issue for you and not something that is TM specific?

I also did a search on logged development items with the criteria being: segmentation rules (AKA broad search)
I found: Change for custom Variables/Abbreviation/Segmentation Rules list in file-based TM is not saved when modified from TM Settings via New Project wizard or Project Settings. Dev item: LG-28256.

But in your case you have an issue within the TM Maintenance View.

Out of curiosity, do you have custom fields?

Are you able to share your TM so I can reproduce?

This also happens with Trados 2021 SR2. When you use the Translation Memories view, your chances to store a new rule rise to 50/50. Not always but sometimes it manages to save the rule. Try several times.

 , this issue is not user-specific. Many users had reported it either. Here is one of them: community.rws.com/.../146081
Plus this one with video: community.rws.com/.../bug-in-segmentation-rules

Stepan Konev I didnt realise it goes that far back.
That said Dev item LG-28256 is still open and I will see if more information can be obtained from the teams

I tried to do exactly what you did, and found that segmentation rules stick in German, but not in en-GB. You are testing with en-US. Could you test with en-GB to see whether it's dependent on the exact language?

I don't use OneDrive.

I do have custom fields.

Daniel Hug en-GB worked like a charm.
As per the bug raised, I suspect its your custom fields.

Custom fields have nothing to do with the issue. I never used a single custom field or remote locations, but I can reproduce the bug at any time with my Trados 2021.