Jolanta Durazzano 

I just recovered your error stack from the spam filter.  It went there because you posted it s plain text into the thread.  There are two ways to add the error file to here:

1. attach the xml error file (copy/paste of a file won't work).  Do that by using the "Insert -> Image/video/file" feature in the small menu below where you are typing your reply, or
2. use the "Insert -> Code" feature and copy paste it after selecting xml (just because the markup applied makes it easier to read)

I cut out your error message and inserted it as code so you can see what it looks like in your post above.

Now that we have it... note the references to "LanguageToolStudioPlugin".  The fact you see this tells me you have not applied the fix in the KB I gave you as this would probably have resolved your issue... or you did it and then added the plugin back in.  Please close Studio and delete these folders:

c:\Users\%username%\AppData\Roaming\Trados\Trados Studio\17\Plugins

c:\Users\%username%\AppData\Local\Trados\Trados Studio\17\Plugins

c:\ProgramData\Trados\Trados Studio\17\Plugins

Then download the ones you want and install them via the integrated AppStore in Trados Studio to make sure you have the correct versions for your version of Trados Studio.  If the problem reoccurs repeat it and don't reinstall that plugin.  We can then advise the developer of this plugin that you're having this problem.

Hi Paul, thank you very much for your patience and reply. Unfortunately the "LanguageToolStudioPlugin" already some time ago did not work well with either Studio 2019 or Studio 2021 and now the same thing is repeating with Studio 2022. That time Darek (who is Polish like me) intervened and fixed the problem for me. I will now follow your instructions and see if the error will be eliminated. Good day - Jola

Jolanta Durazzano 

The LanguageTool plugin works perfectly in my case. I have a paid account there and use it in Studio. Never had problems, when using the current version of the plugin, which you can install via Add-Ins from within Studio.

It is very important to go that way, as this makes sure you'll get the most current plugin for your Studio version. And it is also advisable to check from time to time for updates. Usually Studio will inform you about updates, but doing that manually cannot harm.

Thanks 1000, Paul. I followed all your advice and it seems that the "LanguageToolStudioPlugin" app now also works in Studio 2022. I probably had an outdated version and did not make the correct settings. But what does "KB" mean?

Thanks also to Jerzy. Unfortunately I don't use the paid version of the "LanguageToolStudioPlugin", because I haven't so much work lately and the expense of 29.00 Euro/month doesn't seem justified to me, as I already pay for API Deepl and API Google. Pozdrawiam serdecznie

Jolanta Durazzano 

Jolanta Durazzano said:

But what does "KB" mean?

It means Knowledge Base.

GRAZIE!

Jolanta Durazzano 

Well, the monthly price isn't that high, if you pay for one year (6,66 EUR/month) or even two years (just 5,41 EUR/month), so even if not too much work I would consider this instead of the local version. The online way is more reliable IMO.

languagetool.org/.../premium_new

Oczywiście, że to nie jest drogo, ale czy za taką przystępną cenę można używać do LT do korekty (głównie tekstów polskich i włoskich) w Studio 2022? Bo widziałam, że API kosztuje 29 Euro miesięcznie....?

Jolanta Durazzano 

API to nazwa interfejsu programowania. Sama apka Darka jest darmowa, nie kosztuje nic. Dlatego całkowity koszt tej przyjemności to właśnie ta roczna opłata za dostęp premium. Używam tego narzędzia od kilku lat, zwłaszcza do korekt PL. Spisuje się doskonale, oczywiście nie mogąc zastąpić dodatkowej pary oczu czy starannego czytania własnego. Na niemiecki spisuje się znacznie gorzej. Nie wiem, jak będzie z italiańskim, bo ten język jest mi niestety obcy