Edited post:

The solution here was, to quote Francesca "The termbase that was added as the default to my project, did not in fact even support my target language".

So the posts hereafter did not apply to Francesca's problem.

Hi Francesca Collodo

I was going to suggest you try clicking on Reset Window Layout here with the document open for translation/review/sign-off, whichever mode you're having this problem in:

That is still worth trying but it sounds as if your termbase is not connecting to your translation in Studio now.

Can you still see your terms in MultiTerm? Is MultiTerm the latest version as here?

Also... it may be that you unticked something in the hitlist settings that only took effect after you closed Studio down.

So, how do your project settings look here:

and most important do you have this box ticked here:

in your project settings for the translation you're having these problems with.

If your termbase is corrupt, it is possible to export it and import it into a new termbase but let's look at the above first...

All the best,

Ali :)

Hi Francesca Collodo

I was going to suggest you try clicking on Reset Window Layout here with the document open for translation/review/sign-off, whichever mode you're having this problem in:

That is still worth trying but it sounds as if your termbase is not connecting to your translation in Studio now.

Can you still see your terms in MultiTerm? Is MultiTerm the latest version as here?

Also... it may be that you unticked something in the hitlist settings that only took effect after you closed Studio down.

So, how do your project settings look here:

and most important do you have this box ticked here:

in your project settings for the translation you're having these problems with.

If your termbase is corrupt, it is possible to export it and import it into a new termbase but let's look at the above first...

All the best,

Ali :)

Hi Ali

Thanks so much for trying to help me, it is hugely appreciated :)

I have done all of the above checks, and my settings are all as you suggest. All of the terms appear if I load the termbases in Multiterm, and if I click on "View term".

However, poking around this morning, I have discovered that the problem seems to be, because the project has two termbases. A project-specific one, and a general one that the agency uses.

In this case, the terms that are being found, are being found in the TB that is NOT the default.

If I move it up and make it the default, they display.

So I do at least have terms displaying from one TB. And term recognition is working, so if I see that a term has been recognised in the lower priority TB, I can click on it to view the translation.

Far from ideal behaviour, though. Any other ideas?

I have taken some screenshots for you now:

How the results are appearing in the Term Recognition window

Clicking "View term" shows that the English translations are available

And my settings:

Francesca

Hi Francesca Collodo 

can you check that the languages are all mapped here:

Hi Francesca

A couple of questions...

Have you followed Jerzy's advice in one of your other threads and tried the solutions suggested here?:

Studio Reset etc

Perform the Windows Repair on MultiTerm 2019 Core and Desktop also. Are the instructions simple enough?

Second question - does the termbase behave correctly if you're working on the same project in Studio 2017?

As an aside, I see you translate for the wonderful company I do most of my work for :-)
I usually blank out anything that gives that away ;-)) 

Have a wonderful weekend, despite the weather. I'm going to be working but I love my work so that's no hardship!

All the best,

Ali [:D]