I might blame other software had the shortcuts not worked everywhere else after the BAM*

*Bug Appearance Moment.

Hi Adrian Komiński

Have you tried running a Windows Repair on Studio via the Control Panel?

It and other reset methods are described here:

Repairing your installation of SDL Trados Studio

If none of the solutions given on the above webpage help, you can then get free help with installation issues that are preventing you from working here:

Thanks for all the notes, but all I can say, having read this:

community.sdl.com/.../20730

is BULLLLLS**IT! Now we know it's a bug on your end, GIVE US A HOTFIX NOW (thinking I'm too demanding? I paid several hundred dollars for this, and we're in capitalism - get used to it)!

No one can work efficiently without basic shortcuts such as ctrl+a and ctrl+z.

I'm deeply disappointed with your attitude, SDL. The guy in the link above reported the issue on Dec 12. Now I'm reporting the same thing. This should have been immediately pointed out to the dev team and the dev team put on alert - if you treat your business seriously. You should have told me it's a known/suspected issue and you're working on it. Instead you're making some vague remarks and suggesting it's my problem (or maybe it was someone unaffiliated suggesting it - nevermind).

Again, I demand an immediate investigation into the problem. This is a serious dealbreaker; it just happened to me once again, and I refuse resetting the app several times a day. The problems with TM errors after SP1 are enough to make one pissed, and your ill-famed reputation for replacing one bugs with others is too well known in the industry for me to just decide living with this like that until maybe someone deals with it some time.

Btw. please be so kind and at least link me a resource with instructions on reverting to pre-SP - if at all possible. If it isn't, it definitely should be, because every single of your SPs have known to be a disaster for many of us.

Just happened again. Guess what helped - re-opening the translated document. Resetting layout doesn't help. What about that reversion to SR0? So far the only positive change I've seen with SR1 is correction of the "While you project" typo I had reported in the "ideas" section - the rest is just new bugs.

The same issue in my case. This never happened for Studio 2011 and 2014 which I also own. In my opinion, Studio 2019 is much more unstable and unpredictible software (not to use more unkind words).
Apart from this issue, I also experience "Search feature" not working for multiple documents in Editor. Search works for the first document opened in Editor only. When I press Ctrl+F in another document, it simply won't open/work. I must close all the other documents to use the search feature in a particular document. Very, very annoying. It worked ok in the previous versions.

Also there are issues with termbase settings window not loading. It never happened in Studio 2011 and 2014.

Finally, there is an issue with using the concordance for the selected/marked text in the source column. When I select a part of a segment and try to do concordance search for it, the concordance will search for the whole segment and not the selected/highlighted part. In order to search for the selected/highlighted part, I must click on the source segment again (and sometimes highlight a fragment/part again because it gets deselected). This is a real nuisance.
You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you.

The same issue in my case. This never happened for Studio 2011 and 2014 which I also own. In my opinion, Studio 2019 is much more unstable and unpredictible software (not to use more unkind words).
Apart from this issue, I also experience "Search feature" not working for multiple documents in Editor. Search works for the first document opened in Editor only. When I press Ctrl+F in another document, it simply won't open/work. I must close all the other documents to use the search feature in a particular document. Very, very annoying. It worked ok in the previous versions.

Also there are issues with termbase settings window not loading. It never happened in Studio 2011 and 2014.

Finally, there is an issue with using the concordance for the selected/marked text in the source column. When I select a part of a segment and try to do concordance search for it, the concordance will search for the whole segment and not the selected/highlighted part. In order to search for the selected/highlighted part, I must click on the source segment again (and sometimes highlight a fragment/part again because it gets deselected). This is a real nuisance.
You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you.

"You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you."

This! Less conferences, more bughunting. Or how about you finally provide us with an actually working Word preview for which we paid money?

I downloaded the recent update, and duuh - issue persists, obviously. At this stage, what helps every time is switching between documents or windows within Studio. After this, all shortcuts work until some another time when the bug comes up again, for no apparent reason.

I did run Studio repair some month ago, I did try resetting layout, but I didn't post the support ticket yet. You know how it is - you can't afford doing it during working hours, and you REALLY don't feel like it PAST the working hours.

Both me and Łukasz work in the Polish Windows system (apparently), so that might be a hint.

EDIT: Also, the ctrl+n (new project) shortcut started "malfunctioning" recently. It wouldn't work until I hit "n" twice quickly. VERY odd. Works fine after Windows reset.

Looks like it might have something to do with Windows, alas. But that's not our problem. If you have issues with Microsoft, then resolve them. All I can tell is "ctrl+a" works fine elsewhere whenever it fails in Studio.

Adrian Komiński said:

"You would do us a much better favour, if you shifted some focus from your aggresive marketing to improving the actual code. Thank you."

This! Less conferences, more bughunting. Or how about you finally provide us with an actually working Word preview for which we paid money?

Well... we could ask the marketing team to spend their time fixing bugs but I don't think it would be very productive!

The Word preview.  Please log a case for this.  Make the time instead of posting in here.  You already know I can't repro your issues and whilst I don't doubt you are having real problems we're never going to get to the bottom of it unless we can work with you in your system.

Adrian Komiński 

Adrian Komiński said:

Also, don't treat us like idiots, Paul; you know what we're talking about: shifting focus in business usually involves firing and hiring.

Enough said.

Adrian Komiński said:

Why, in the other thread you basically admitted the preview lags like hell on your part also! Maybe it doesn't crash and such - but so what. You guys know nobody is seriously going to use this feature if it performs so poorly.

I asked you to contact support because you said you had no time to do this.  I get some lag with the word preview, not with the html preview.  If you don't log it and make sure the right people hear this then your complaints, and note that we don't see this community full of complaints like this, will not be heard in the right place.  So you can continue to complain in here if this is how you'd prefer to spend your valuable time, or use it where it will do the most good.

Having said this it may be that we'll never be able to address this in the realtime Word preview (the one that actually uses word) as the problem is not only down to what we can do.  There isn't another CAT tool that offers a preview like this (and I mean preview, not where you work in Word in the first place) so you don't have a comparison to understand the issue.  But it's really not straight forward since Microsoft moved their focus to the cloud as we lose the hooks we used to be able to tap into.

Perhaps we should just remove it and leave you with the html preview and then we won't get these sort of complaints anyway.

However, my point is you are wasting your own time complaining again and again about this in the community.  Log a case with the support team if you're not getting enough satisfaction here.

Adrian Komiński said:

What I'm seeing from SDL is symptoms of ignoring the obvious shortcomings of the software (which the ignoring has been observed in the industry for years and years - there's no denial of that).

I completely disagree with you here.  We always have many things to address in the software ranging from critical bugs to minor ones, from work under the hood to enable complex features and sometimes what appears to an outsider to be the simplest of fixes.  In addition to this we have been doing a lot of work to bring the variety of products that SDL have under one set of core components so that we are able in the future to manage the product more easily and ensure we can focus the development resource we have on more productive things.

So I absolutely deny that and you only have this impression because you really don't know.  I don't blame you for that, but I would prefer to see a more productive approach to the problems.  No amount of publicy attempting to shame SDL into doing something will work.  If we have not addressed something yet it's because it's either more work than you realise to achieve it right now, or a very low priority compared to other things that need to be addressed right now.

Throwing more developers at the problems is also not the answer.  You can probably read a lot about that if you're really interested.

Adrian Komiński said:

One of such symptoms of ignorance is not even mentioning the Word preview issue in SR1 release notes, regardless of the underlying reasons for the problem. This is one of the ways to treat your clients as idiots.

This is also not as clear cut as you think.  What exactly do you think we should do here?  Some customers complain about things from time to time and they are not always right.  Sometimes they are.  Even when they are right the testing we do, which is more extensive than people think, might not find the same issue.  Studio is a big product, is affected by so many things from the operating system you have to the applications you use, to the languages you work in and a lot more.  So testing can only find so much.  The release notes cannot possibly include every problem we have not fixed but are aware of.  They need to be reasonably useful and so include most (but not all) of the things we have fixed, and an indication of the most important known issues that affect the majority of users.

Adrian Komiński said:

If you ignore your problems, then expressing disappointment can best, and should be done in public. If I report a ticket, it most likely won't help in the "global perspective" - and most likely won't help with my particular issue, because the problem seems to be related with the core code. Hence, it would be a waste of time, as compared to voicing disappointment out in the open. Also, note that most people just don't give a toss about voicing it, and simply switch to more reliable competitors.

I've probably addressed this already.  You can keep complaining about the same thing in public if you like.  We won't be ignoring you, but we also won't be rushing to add more information to that which we are already aware of.  If you have the ability to raise it with support you should do this.  Nobody is ignoring the issues... but I realise you have no idea of what we are really doing and I can't easily change that.

Nobody is ignoring anything. Core code is not where the problem of this particular issue lies.

It's not just an issue in Polish. I have these problems several times each day typing in English and French. As others have stated, I never experienced these problems in earlier versions of Studio. Of course, I've had problems with every single version of Studio, but the current problems seem even more aggravating.

Interesting! I wonder why it's not experienced/reported by other people then. Don't they use shortcuts like ctrl+a?