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?
Paul For the record, this issue still exists in TS 2019 R2, and turning off the lookahead feature "fixed" it.
Hi Stefan, thanks for sharing and confirming! I have successfully tested the same workaround (turning off lookahead) recently with Studio 2019 SR-1 and SR-2 when a customer complained about term recognition issues (and even Studio crashes) with a large local termbase.Kind regardsChristine