Jane Božinovski

What happens if you click on a few segments further down the document and then go back to the one you were originally in?  Or even if you close the file and open it again?  It sounds as though you may be falling foul of the Lookahead feature.  If you use this, and it's on by default, then Studio caches the results in advance for a few segments to speed up performance.  But a negative side-effect of this is that when you add a new term that happens to be in the next couple of segments it will not be shown because Studio cached the results at a time when it wasn't available.

You can disable lookahead here and also test that to see if it helps:

Jane Božinovski

What happens if you click on a few segments further down the document and then go back to the one you were originally in?  Or even if you close the file and open it again?  It sounds as though you may be falling foul of the Lookahead feature.  If you use this, and it's on by default, then Studio caches the results in advance for a few segments to speed up performance.  But a negative side-effect of this is that when you add a new term that happens to be in the next couple of segments it will not be shown because Studio cached the results at a time when it wasn't available.

You can disable lookahead here and also test that to see if it helps:

Hi Paul,

thanks very much for your prompt answer. It seems my termbase language differed from the language I had selected in the translation project - one was English US, and the other vanilla English. I opened a new termbase using English US and it suddenly started working. Devil's in the details!

I disabled lookahead just in case.

Cheers,

Jane

Jane Božinovski

Excellent... glad you figured that out.  You could recreate your termbase to be based on just EN and not en-US or en-GB for example.  Then it'll always work.  This may help if you do need to separate the variants but still like this approach:

https://multifarious.filkin.com/2014/04/08/yanks-versus-brits/