Hi Patrice Philippi

Yes I have heard about the challenges when it comes to case sensitively before and in particular with abbreviations as you say as well as and short acronyms.

There is no perfect solution that is out the box but what I can do is highlight some features that users tend to explore.

1. AutoCorrect

Found under - File - Options - Editor - AutoCorrections

But you may find this fully suitable as it would apply to all projects. In the meantime I am sure there are times you dont want IS, TO, BE to always be uppercase 

2. TM Settings

You could adapt or have a dedicated TM for these TD projects.

This is so that you can customise the Variable and Abbreviation resource settings.
Once again, this would require you to list the abbreviations ahead of time, but you would benefit from the quickplace which will help you get it from source side to target side. 

3. Termbases

Lastly and as you briefly mentioned, termbases, which would be my primary reliance.

You list your incorrect formats as well as your approved formats, and import these into a termbase.
This is easily done using Glossary Converter: https://appstore.sdl.com/language/app/glossary-converter/195/

Using a combinations of built in productivity features such as AutoSuggest, you will get these handled appropriately.
Furthermore, you can QA them based on our terminology verification checks

If you have experience or perspective on how we can improve, please do let us know

Lyds 

You'll probably have to use a multi-faceted approach with the features mentioned by Lydia. I would add the following QA features:

Word list: May be useful for more uncommon abbreviations, i.e. could provide too many false positives for things like IS, TO, BE, ARE. At any rate, it allows you to control case.

Regular expressions: If the abbreviations are used in a particular context (i.e. if there is a way to detect when the abbreviations and NOT the regular words are being used), you might be able to use regular expressions to ensure correctness.

Hi Lydia,
Unfortunately, I don't see our this resolve at all the problem, with the Term Recognition window full of "acronym recognized" and listing all definitions for them - in such a way that I don't see the important terminology as all small common words are all also acronyms with many definitions - IS, OR, AT, SO, OF, IN, etc. so a big sentence containing all of them will list 20 or more terms in the window - to a point that the real important terminology becomes invisible, pages down in the window. But at the same time I need to see those 2 letters acronyms when they are used and CAPITATIZE due to their numerous definition - to see which one to pick in context.

Being myself a programmer, it seems like a very easy and useful feature to add to Trados to simply filter the terms is needed to match the TD - uppercase or lowercase as I see the same problem mentionned with Trados 2015, Trados 2017...

- Patrice