Studio 2017 SR1 wordcount goes nuts

Question

Hello all, 
 I downloaded SR1 the day before yesterday. It doesn't change much to the issues I'm having since purchasing 2017, multiple crashes and very (very very) slow context searches for segments with a single all caps word... 
 But a new issue is the constant faulty translated words wordcount (you know, below and on the right ot the screen, when your translation is finished but trados says there are still words to translate and then you have to perform the "number of translated words" (nombre de mots traduits) task to have the right number or percentage of translated words. 
 Besides, I often import tmx files in an existing sdltm file when creating a project and it goes slower than with the first version. 
 Furthermore the preparation of the project is also slower than before. 
 So, not very impressed with the corrective at the moment... 
 
 Cheers to you all 
 
 Ann

Jerzy Czopik · Accepted Answer

The project preparation (here the analysis and populate project translation memories or pretranslate task) ARE slower, because they use fragment matching and match repair. When preparing a project, switch this option off and check then. I do that very often - I switch this option off for preparation and finalization of projects. However, as preparation is usually done in parallel to other work, it does not hurt that much, so I can leave the setting switched on for this. Finalization often needs to be faster, as you have to deliver soon - and waiting only because of fuzzy match repair being on does not make sense at this stage. 
And no, there are no MemoQ issues in Studio - all MemoQ files can be processed without any problem. 
As for the wordcount in the lower right corner - this is just an orientation, very useful and much better than just a percentage. But to have exact numbers you can switch to Files view, where you can have the exact number of words still left to translate. If this is not shown correctly, just run "Translation wordcount" batch and the data will be exact again.

Jerzy Czopik · Answer

In this very specific case, where your file is more pretranslated than not and you have more short segments, do not use fuzzy match repair and switch off the look ahead feature. This two are responsible for the delays. In your case mainly the Look ahead feature is of no use, as you stop in pretranslated segments, while the TM has already prefetched the next hit for the next NOT translated segments. This is why it then takes so long. 
 
In the end of the day it is like with all new products in life. A new TV has many improvements, but we mainly use only few (like the Internet access to watch movies via my Amazo account). What we never use is Internet browsing with the TV or media streaming from our network. So is the TV really better than the old one? Same with improvements in Word, where an average user has never utilized more than 10% (my guess) of program features. 
Studio has many improvements, which do not necessarily fit in every job. So for proofreading jobs for example all fragment matching and fuzzy repairs are of really no use, so it is better to switch them off. 
This is like driving a car - when you are in the city, you drive slow and can switch it in Eco mode (at least it is what I can do in my car). The engine response is like would you have removed at least 50% of its power. The accelerator pedal feels like rubber - you keep pressing it, but nothing really happens. But you are driving with speed limit to 50 km/h, so it is not necessary to use the whole engine power, which would bring this very same car in less than 5 seconds up to 100 km/h. Your benefit is reduced fuel consumption. But then you go with this car on the motorway ans switch it to Sport mode. It now feels like would you have a completely different model. Not only it takes less than 5 seconds to go for 100 km/h, but even if you are fast or very fast and then still push the accelerator pedal further down, the car jumps forward like a jet during take-off. So is Studio too - exactly adaptable to your needs. And when you do that, your benefit is less effort for better quality in shorter time.

Paul · Answer

Hi Gérard LAMBERT , 
 
Have you tried turning off Lookahead? This may account for the apparent non working TMs that work when you restart Studio. Look in File -> Editor -> Automation

Trados Studio > 1. Trados Studio

Studio 2017 SR1 wordcount goes nuts