This could be a helpful tip for some people:

I use multiple TMs all the time, and it could be, that their order changes or I want to include the same rules (segmentation and other TM-specific) all the time or I want to change rules for just one project, but not modify my general TMs etc. etc. To make it easier, my TM list for the project looks like this:

The top one is always the one I named "Language Resources". As you can see, it is enabled, but neither looked-up nor used for concordance or for update. And it does not even include any translation units! So what is it good for? It just contains the (may be complex) segmentation rules I want to apply, and a variable list which is not project-specific.

You could create various such non-looked-up zero-TU-TMs with different rules and always put the one with the segmentation rules and/or variables at the top of the project's TM list to maintain a logical and easy overview.

This could be a helpful tip for some people:

I use multiple TMs all the time, and it could be, that their order changes or I want to include the same rules (segmentation and other TM-specific) all the time or I want to change rules for just one project, but not modify my general TMs etc. etc. To make it easier, my TM list for the project looks like this:

The top one is always the one I named "Language Resources". As you can see, it is enabled, but neither looked-up nor used for concordance or for update. And it does not even include any translation units! So what is it good for? It just contains the (may be complex) segmentation rules I want to apply, and a variable list which is not project-specific.

You could create various such non-looked-up zero-TU-TMs with different rules and always put the one with the segmentation rules and/or variables at the top of the project's TM list to maintain a logical and easy overview.

What a good idea, Horst-Helge Liefers 

Thank you!

Ali :D