Alonso Santamaria 

This happens unfortunately on many machines with pre-installed Office 365 (including all my PCs), mainly if your Normal.dotm does contain any macros. Usually you see then a message appearing and telling you, that Word has deactivated all macros for security reasons. Unfortunately, I do not know any solution for this and from what I know even Trados does not provide any soultion here.

You could try to remove all macros from your Word Normal.dotm and try again. If this does not help, only the use of Hunspell is a reliable solution. At least this is what I use.

Alonso Santamaria 

This happens unfortunately on many machines with pre-installed Office 365 (including all my PCs), mainly if your Normal.dotm does contain any macros. Usually you see then a message appearing and telling you, that Word has deactivated all macros for security reasons. Unfortunately, I do not know any solution for this and from what I know even Trados does not provide any soultion here.

You could try to remove all macros from your Word Normal.dotm and try again. If this does not help, only the use of Hunspell is a reliable solution. At least this is what I use.

Hello. 

Thank your for your kind answer. I have news for you, it also happens on machines without the pre-installed Office 365... I have a 365 license and I actually uninstalled the pre-installed Office and made a clean installation from my own license. I have also modified the normal.dotm to suit my preferences and every time this happens it went back to default. 

Good day!

I'm afraid removing a preinstalled Office 365 is not really possible for an average user as we are. Preinstalled parts of software on branded machines like Dell in my case are deeply integrated somewhere in the system and even if you unistall these, traces remain, at leas in the Windows registry.

Absolutely. Even not being an average user, it is too intrincate to address it to that depth. An I certainly did not.

Alonso Santamaria , Jerzy Czopik 

Allow me to draw your attention to a solution outlined here:  Trados 2024 and LanguageTool

At this point, this is still a pretty manual process of getting it going (although by no means difficult). But if there is more interest it might push me over the threshold to write an AHK script that automates the integration of this spelling/grammar checking solution. It also has some features that I always hoped (still hope) Trados would provide, such as defining a notification level (note, warning, error) for each individual regex check.

But this thread is about a spellchecker/ grammar-checker.

Looking forward to your replies!

Daniel

Thank you very much, Daniel. I followed (quickly this time) the thread you mention and it may be a nice alternative.

My concern is that the Hunspell dictionary's vocabulary is rather poor for real life complex legal or technical documents. Even some rather simple words are not there. An MSWord spellchecher crashes each time I open any Office document for whatever reason, so I have to quit and restart Studio. Uncomfortable. 

But if there is an alternative offering advanced features and a rich dictionary, it is a dream come true. I am not sure I understand the underlying data for the solution.

Alonso Santamaria 

LanguageTool is a spellchecking /grammar checking app. There is a free online version and a free downloadable version (run on your own machine), and there is a paid online version. You can use its native interface or integrate it into anything you like using the API provided – there are integrations for all major browsers, Word, OfficeLibre etc.

https://languagetool.org

There is an app on the Trados Studio AppStore that integrates LanguageTool into Studio, but I think the developer has not yet published a version for 2024, so you'd need to run it with Studio 2022. Since I upgraded to 2024, I was looking for a way to use LanguageTool with Studio, and I came across a small tool called “CheckMate”: https://okapiframework.org/wiki/index.php/CheckMate

CheckMate is part of a bigger (free) toolkit called the Okapi Toolkit. It can read many file formats, amongst those is SDLXLIFFF.

So you can run Checkmate, tell it to check the SDLXLIFF files that your Studio project saves, and re-check whenever the files are updated (i.e. whenever you save your project or a file within your project).

In the CheckMate configurations there is the option to connect to your local LanguageTool “server” - if you run LanguageTool locally, that's how it will run. If you do that, LanguageTool will check your Studio project whenever you hit the save button.

There is one caveat: CheckMate has a bug that makes it ignore region codes, so all Spanish is generic Spanish, not ES-pt or whatever. Fine for me, as German does not vary that much, but for EN or ES this might matter a lot. LanguageTool supports region codes, but CheckMate currently has this bug.(https://bitbucket.org/okapiframework/okapi/issues/1368/languagetool-integration-in-checkmate)

It's not as convenient as Darek's Studio integration – you have to find the segment manually where the error is reported. So it's a bit of work to set up, it's a bit clunky, but I value it highly as I find LanguageTool very, very useful. And, as mentioned, CheckMate does have some checks that I always hoped Studio would provide, and it does not provide it (yet), such as regex checks with custom error levels (notify me for this, but shout out loud if that).