Hello Julia Jeong ,

I cannot replicate this in either 2017 or 2019

Maybe its worth checking a few basics here as it appears to be intermittent-

Julia Jeong said:

Sometimes, it works, but mostly it doesn't work.

Are you using maybe a wireless keyboard (batteries) or do you notice if you might have a sticky key?

Perhaps try closing all other programs and just running Studio to see if there might be a shortcut conflict with another program.

Hello Julia Jeong ,

I cannot replicate this in either 2017 or 2019

Maybe its worth checking a few basics here as it appears to be intermittent-

Julia Jeong said:

Sometimes, it works, but mostly it doesn't work.

Are you using maybe a wireless keyboard (batteries) or do you notice if you might have a sticky key?

Perhaps try closing all other programs and just running Studio to see if there might be a shortcut conflict with another program.

No, there is nothing wrong with my laptop. I don't use wireless keyboard, and there is no sticky key. When "ctrl + A" is not working in Trados, this function works normally in other programs such as Excel, Chrome, and etc. This has NEVER happened in Trados 2017, so it is very irritating. The only resolution is to shut down Trados, and then restart it again, which is time consuming. And the problem is, the function still doesn't work after working on one file. It's like this:

1. Ctrl + A doesn't work. So I shut down Trados 2019 then restart it.

2. Open a xliff file in a project, and use Ctrl + A, which works. After completing translation, I close this file, and open another file in the same project.

3. Ctrl + A doesn't work in this new file. Ctrl + A works normally in other programs. Other shortcuts are also working in Trados 2019, but Ctrl + A doesn't work at all no matter what I try. The only way is to restart the program AGAIN.

Is it possible to downgrade to Trados 2017? This problem is so annoying that I would like to go back to Trados 2017.

Welcome Back. I heard, it is possible.

Hello Julia Jeong ,

I am sorry you are having issues with the shortcut- but if this was a Studio issue, we would see an awful lot more cases reported.

When such issues are reported, I and many others do try to replicate - sometimes with success- sometimes without. When we cannot replicate a specific issue, this is very difficult to investigate as im sure you will appreciate.

I would suggest first, you make sure everything is really up to date -

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3392/how-to-part-1-trouble-shoot-unexplained-errors-and-unwanted-behaviour-in-studio-multiterm Parts 1 and 2 and see if the issue is resolved.

If not, it might be worth disabling installed plugins and then enabling one by one until a possible culprit is identified.