The preview in Word behaves in an unpleasant and unreliable manner on my PC. Be it "Microsoft Word" or "Embedded" display mode, the yellow highlight is laggy, it often takes several seconds for the highlight to "find its place" in the document - jumping between sentences (or text fields, for instance) before settling on the target one. It sometimes disappears and reappears without any intervention on my part; often the whole preview (in Microsoft Word) will crash and then reopen. Sometimes the highlight won't display at all.
All this makes this important feature pretty much a useless waste of time.
I've had problems with alleged Office incompatibility in the past - see https://community.sdl.com/product-groups/translationproductivity/f/90/t/18778
...but I have a genuine MS Office downloaded from a Microsoft online source. The MS Word (Office) is Professional Plus version 1809 (compilation 10827.20138, Quick install [or whatever the English translation of this is]). Regarding the "quick install" - when installing Office I couldn't choose any "installation mode", whether quick or slow, so I'm not sure what this is about.
My question is: has anyone experienced anything similar? How does the highlight work in your case - does it switch between sentences/words/text fields in the blink of an eye, or is there significant delay?
If my Word is a suspect, then WHICH Word version exactly should I buy to be sure that it will work properly? Is the most expensive box version available in physical stores the ONLY option? That would be pretty ridiculous and unfair, and would probably cause problems to about half of the users who purchase their Office on the web, have it included with their PCs, etc.
Needless to say Word preview worked beautifully in Trados 2011 with Office 2007... (couldn't help it, Paul)
BTW: I created a new topic since the issue from the former one somehow resolved itself: Trados won't refuse creating a preview anymore - but it still works like crap.
EDIT: tried doing the embedded preview, and Trados actually gave me an error, so... yeah, should've posted this in the old thread. But then, I don't even need the embedded preview at all.
One silly thing with the external preview ("Microsoft Word") is that you can't set it to display the source document content - and you can't disable its auto-updating/refreshing, which, as I believe, partly (or wholly) causes the lag and instability. All this gives an impression that the developers have just intentionally left us with a function that is slow and unreliable. Hopefully I'm wrong though, and it's just my case.
On this we can agree!
Adrian Komiński said:Needless to say Word preview worked beautifully in Trados 2011 with Office 2007... (couldn't help it, Paul)
But the problem here is not Studio, it's Word. Once Microsoft moved to their click to run installer they stopped providing the required components that are needed to be able to deliver an embedded preview. So we have had to try and find other ways to make this work.
Adrian Komiński said:EDIT: tried doing the embedded preview, and Trados actually gave me an error, so... yeah, should've posted this in the old thread. But then, I don't even need the embedded preview at all.
Today I run the click to run version and can actually achieve all three variants of the preview without the problems you descibe so would be inclined to look at external influences first. These would be things like you security software and available permissions to be able to run both applications smoothly. Try disabling your security software temporaily, and any backup software you might be running and see if this helps. If it does add things back in until you find the cause of your issue.
Well, since I'm sitting here looking at a crashed Studio screen again, I'll stick my oar in. I have Office 2007. I have been using it with all the Studio versions for years. But things went pear-shaped when I installed Trados 2019. Preview crashes Studio. Word grammar check no longer works. And somehow this is the fault of Microsoft? I'm not seeing it. If there is a way to revert to 2017, please advise.
Had it not been for (way) faster project saving and DeepL compatibility, I too would have stuck with the reliable Office 2007 and Studio 2011 (though many could probably disagree with me on the reliability of 2011)! There haven't really been any meaningful improvements over the past 10 years, and 2019 is significantly slower than 2011 in terms of smoothness of navigation/switching, scrolling segments etc. 2011 always ran beautifully on an Intel Core Duo and never gave me serious and/or frequent problems. Now I'm running 2019 on an Intel i5 from 2017 and daydreaming about the good old times.