Hi Andreas Conow

You are right in that when making segmentation rules, they only apply to new projects and to be specific to files that have not already been parses (not in *.sdlxliff format)

However what is odd, is you say 

Andreas Conow said:

When I close and open Trados the new rule will vanish completely.

As the segment rules should not be removed from your TM.

What format is your TM, meaning file based or sever based?
Can you reproduce this with other TM's?

Looking forward to your clarifcations

Lyds

Hi Lyds,

thank you for your suggestion, I tried with other TMs, there the changes work just fine, only this one causes the problem.

It is a file-based SDLTM from Italian to German, and oddly, only the source language is affected - just to see what happens, I added the same new rule "semicolon" in source and target language, ok .. ok .. ok, closed Trados, opened anew and within the source settings (Italian) the new rule is gone:

whereas in German (target) the changes are saved and the new rule "semicolon" still shows:

The other TMs will save the changes in source and target, so it is probably the specific file that might be corrupted or some other setting interfering with the canges within the source settings...

To eliminate eventual interferences, before adding the new rule, I removed any project from the list that uses this specific TM... 

I´m tempted to persuade my clients to avoid the semicolon  but if you have any idea let me know,

Thanks

Andreas

Hi Lyds,

thank you for your suggestion, I tried with other TMs, there the changes work just fine, only this one causes the problem.

It is a file-based SDLTM from Italian to German, and oddly, only the source language is affected - just to see what happens, I added the same new rule "semicolon" in source and target language, ok .. ok .. ok, closed Trados, opened anew and within the source settings (Italian) the new rule is gone:

whereas in German (target) the changes are saved and the new rule "semicolon" still shows:

The other TMs will save the changes in source and target, so it is probably the specific file that might be corrupted or some other setting interfering with the canges within the source settings...

To eliminate eventual interferences, before adding the new rule, I removed any project from the list that uses this specific TM... 

I´m tempted to persuade my clients to avoid the semicolon  but if you have any idea let me know,

Thanks

Andreas

Andreas Conow - could you send me your TM seeing as this is TM specific