Why is term recognition not working consistently?

Since upgrading to Studio/MultiTerm 2017, we have noticed some problems with integration. In the most prevalent instance, terms are not delivered immediately to the Term Recognition window automatically when moving to the next translation unit. The window is simply blank with "No terms found" or whatever. Simply cursoring in and out of the TU is usually enough to get the system to "wake up" and fill in the Term Recognition window properly again.

Nevertheless, this is very frustrating, especially since this was never a problem with TS/MD 2015.

When will this be fixed?

Parents Reply
  • Hi Paul and everybody,
    I have this issue since Studio 2011, and with no version it has been fixed. And I had all of them. Now 2019 R2. It's really annoying! With me, usually, it doesn't help "cursoring in and out", the terms simply aren't displayed. When Studio stops displaying, it will display terms in NO segment. After a while, suddenly it works again. And now, whilst I wanted to check how the "Termbase viewer window" is called, Studio crashed! :-(
    The thing is, I had other issues before with this Termbase viewer window (the terms wouldn't display when I right-clicked on a term with "View term details") and a guy from SDL Support recommended me to NOT save my working files (TM, termbase) inside of Dropbox (because of the syncing feature). Now I save those files outside of Dropbox (and must sync manually every day or couple of days :-( ) but this issue persists!

    Other issues are that I have to logon to my account almost every time I start Studio; if I don't close the search window (Ctrl+F) immediately after the search but later, after translating several other segments, the cursor jumps back to the last found word, etc. etc...

    Other hints were that my antivirus software (Bitdefender) could be responsible, but I excluded already all SDL files from Bitdefender → nothing helps. Frustrating...

    Best,
    Markus

Children