Hi Domenico Lombardini,

Please check that Studio and Multiterm have both updated to the latest build, as follows:

Studio: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

Multiterm: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

After that please remove and open the termbase again

Regards,

Hi Oana,

thank you for your reply.

They are both updated to the latest build.

I have also tried to deactivate the "LookAhead" function, as I have seen around this could help. But, term recognition is still not working.

Thank you anyway

Domenico

Hi Domenico Lombardini,

I have tested term recognition from my side and it works fine so then I think of couple of things to try.

Please refer to this article from the knowledge base and follow the instructions provided there, particularly the part with re-organizing the termbase and adding the files to antivirus/security suite:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0038785

Nevermind Studio version, it works for the latest as well, as there are basic rules.

Let me know if this works!

Regards,

PS: LookAhead is only for the TM (translation memory) so it does not have an effect on the termbase.

Hi again,

Unfortunately, none of the solutions worked (I've tried both re-organizing the TB and adding the files to the exclusion of the security suite).

However, I'm now having problems with the overall project (Studio suddenly shuts down, TMs get corrupted easily...). I guess something went wrong at level of  project creation.

Thank you

Dear Oana,

I am confused by your statement:

Oana Nagy said:

LookAhead is only for the TM (translation memory) so it does not have an effect on the termbase.

As far as I can remember, Lookahead was introduced to also address delays in the termbase look-up.

The Studio Online Help has a paragraph on "LookAhead for terminology" which says:

"LookAhead pre-fetches term recognition results. This means that term recognition results are displayed faster for slower server-based termbases or termbases stored on network drives.

If you add new terms, these are not recognized for the next two segments."
https://docs.sdl.com/LiveContent/content/en-US/SDL%20Trados%20Studio%20Help-v5/GUID-57E9A51A-3C9D-4500-AEEB-4F5412794A9C#url=/LiveContent/web/search.xql%3Fc%3Dt%26pub%3DSDL+Trados+Studio+Help-v5%26lang%3Den-US%26action%3Dsearch%26query%3Dlookahead&sid=lcSearch.runSearch1561284649273&currentQuery=lookahead&currentScope=&eventType=lcContent.loadDocGUID-A57EB808-DEDE-4CC7-94D3-10EDC09BB7F8&query=lookahead&scope=&filename=GUID-A57EB808-DEDE-4CC7-94D3-10EDC09BB7F8.xml&docid=GUID-A57EB808-DEDE-4CC7-94D3-10EDC09BB7F8&inner_id=&tid=891525dc-39e9-4d98-b0e7-a90241d193a7&addHistory=true&resource=&toc=false )

Kind regards

Christine

Christine Bruckner said:

I am confused by your statement:

Oana Nagy said:

LookAhead is only for the TM (translation memory) so it does not have an effect on the termbase.

As far as I can remember, Lookahead was introduced to also address delays in the termbase look-up.

Indeed... Oana Nagy is incorrect here.  Lookahead definitley affects terminology look up as well.

Christine Bruckner said:

I am confused by your statement:

Oana Nagy said:

LookAhead is only for the TM (translation memory) so it does not have an effect on the termbase.

As far as I can remember, Lookahead was introduced to also address delays in the termbase look-up.

Indeed... Oana Nagy is incorrect here.  Lookahead definitley affects terminology look up as well.

Thank you Paul Filkin and Christine Bruckner for correcting me on this.

I keep on learning... :-)