It is very annoying. I believe it's beacuse the Studio developers test only in a vanilla environment (if they actually test at all), i.e. with no macros in Word.

André Stryger 

André Stryger said:

I believe it's beacuse the Studio developers test only in a vanilla environment (if they actually test at all), i.e. with no macros in Word.

There is no need for comments like that.  Please be constructive if you have something you'd like to add to the discussion that will be helpful.  In this case it would perhaps be useful if you told us what macros you think we should include?  It might also be useful if you told us what other software we should include. After all, if we are not going to test in a vanilla environment what single environment containing the things you believe everyone uses should we have?  Or maybe you can suggest a range of environments that you think we should test against... in addition to the different language operating systems we already test against?

Just to say the MS Word spell check issue is now 4 months old. It's frustrating and spoils my user experience.

The workaround suggested by Sorin Dolha (opening Word first, then in Studio clicking through error messages) is OK, but his comment that the workaround is good enough in case of emergency sums it up quite aptly. An emergency shouldn't last 4 months.

I sometimes forget to open Word first, then find I've been switched to Hunspell. I can never ever shut down Windows until I've clicked through more Visual Basic still open messages.

When might this issue be solved? 

Thanks Sorin, I tried your Alt+Tab hack and, as unprofessional as it sounded at first, it actually worked! :) Yes, I have to do that again and again after starting Trados but it's much less of a hassle than having to work with Hunspell (which is a poor option for Hungarian).

Thanks a lot!

Currently if you want to use Trados Studio and the Word spell check enabled inside it, you are not allowed to have any macros in Word. That's not acceptable.

I would suggest you invite more real users to test in their environment. Regarding macros in this case it doesn't matter which macro. Having any macro is the problem since apparently Studio copies the Word template file into a temporary folder and Windows (or Word) and that creates havoc with Word.

Correction: Having any macro is the problem since apparently Studio copies the Word template file into a temporary folder and that creates havoc with Word.

By the way, as a proficient proofreader I must say that the review mode in Studio is utterly insufficient. I would like to contribute to a proper understanding of what this task really involves. I would like to discuss this with you outside of this forum if you're interested. :-)

André Stryger 

André Stryger said:

I would like to discuss this with you outside of this forum if you're interested. :-)

I would far prefer you to create a new thread specifically for this and we can discuss it here.  I think opening a discussion like this to all our users would be far more valuable and also carry more weight.  We could then take any concrete suggestions from the discussions and provide them as ideas in the ideas site so the product manager could consider them for inclusion in the product.

Has anything been done with the macro issue?