Dear Paul and Jerzy,

Thank you for taking the time to answer my post. English is not my main language and so I hope I will be able to be as clear and complete as I can.  

Paul says : “What makes you think there is a compatibility problem with memoQ? “

The issues I’m having are only occurring with memoQ files, that’s why I thought maybe that was the reason, but of course I can’t be sure of that. The main issue is the constant crashing and about that, I should maybe give some more context. This only happens with memoq files, of which a big part is pretranslated, with many segments consisting of only one or two words in all caps (always takes time to find segment matches) and since a big part is pretranslated, I rapidly browse from one segment to the other (I still have to check the pretranslated segments for errors), it then feels like the segment match search is saturated because of the fast segment change. Then, I stop in one segment, wait for a segment match and the program crashes. Sometimes with a message and sometimes it just suddenly disappears on me. So I have to restart the program which takes 2 or 3 minutes and makes me lose precious time… I also have to say that these are files in which I do a lot of segment merging.

Jerzy says : “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. »

I will try this, but I can’t say I’m glad to have to do this since I would expect improvements from a new version of a program instead of slower performances… Sometimes the deadline is short and you want to begin your work as soon as possible. Sometimes it takes more than 30 minutes to prepare a project. I also wonder : if fragment matching and match repair are off when preparing the project, will the segment search while translating not be even slower than it already is? Sometimes I wait for 3 to 5 minutes before I get a segment search result.

Jerzy says : “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. »

About the wordcount errors : it’s not that I really absolutely need to know the wordcount at all times. I just wanted to state that this problem occurred when starting to work with 2017 SR1. Never had that before or very rarely, and the real problem is that I always have to do the “translation wordcount” task to have a 100% translated file before cleaning it, which, again, takes time.

My hardware is fine, I think, I work with windows 10, 1.80 Ghz processor, 8 ram, 64bit processor.

All these issues occurred since upgrading from Studio 2015 to Studio 2017. I already had a contact with someone from SDL not so long after the upgrade, but no solution was found.

I’m glad to work with SDL, I’m used to it, but I really wish I wouldn’t lose so much time on technicalities especially since I’m going to be on a tight schedule soon going back to school at 43

Again, thank you very much for your time.