There are several reports about a freeze of Trados Studio with high CPU load in previous versions. I have never noticed this there. Now I have the new version 2021 and it happens again and again. It's the same circumstances as described several times and it happens when confirming a segment. SDL should not blame virus scanner / spell checker / online resources for the error, because the previous version 2019 worked without problems and still does.
SDL should not blame virus scanner / spell checker / online resources for the error, because the previous version 2019 worked without problems and still does.
2021 is not 2019 so what makes you think your security software doesn't have a problem with components that are not in 2019 at all?
Perhaps you can help by providing more details such as your Studio log files? You can send these to pfilkin@sdl.com and we can investigate this to try and help pinpoint the problem.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I have sent you a log file to the given address.
Additional info: When I deselect the MS Word Grammar Checker in the project settings (not in the general options, it is still selected there), the problem seems to disappear.
But again: the high CPU load is in Studio itself, not in a related 3rd party software.
When I deselect the MS Word Grammar Checker in the project settings (not in the general options, it is still selected there), the problem seems to disappear.
I have a suggestions in this case.
I would have pulled the MS Word Grammar Checker application from the appstore years ago as it's a hacked solution and we won't be spending any time attempting to improve it. There is no API from Microsoft for this feature so if it wasn't for the fact a few users still like it despite the problems it causes I would have removed it by now.
The LanguageTool plugin, which will be available for 2021 soon, is a better solution according to users who work with it.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
You have made a new version MS Grammar Checker 3.0.0.0 for Studio 2021 and offer it under Plug-ins. Then it should actually work!
I’m being quite frank with you. We made sure it was possible to install it in 2021 and that is all. How well it works or not is nothing we are going to address at all because the plugin itself is a hack to make it work with MS Word.
If your problem goes away when you don’t use it and you have unchecked the setting I mentioned (which is as good a solution as you’ll get from us in relation to his plugin) then you should stop using it.
I explained why we we even released it, because I would have preferred to remove this from the AppStore altogether.
Quite frankly if we receive more feedback like this I will simply remove it and I’ll only make it available to users prepared to use it despite its deficiencies and on their request.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
First of all, thank you VERY much for suggesting to get rid of the MSWord Grammar Checker.
I had the same issues described above and it was driving me mad. So I uninstalled the app and installed the LanguageTool plug-in instead, as suggested above.
However, this caused even greater issues (i.e., errors "The requested data file could not be located" and "A pane's docked state cannot be determined until it has been associated with a DockAreaPane", and Studio crashing completely whenever I tried to confirm a segment). And yes, I did try to resolve this, too, by renaming/deleting the "TranslationMemoryRepository.xml" file and "Studio16" folder as suggested elsewhere, but to no avail. I even uninstalled and re-installed Studio, which didn't help either.
In the end, as it turned out, the issue was the newly installed LanguageTool plug-in! I disabled it and voilà, now Studio works fine (and as a test, I re-enabled it just to face the same errors and crashes again).
So, long story short, I just wanted to add to your valuable advice that I would strongly advise against installing the LanguageTool plug-in, too.
Translate
