For some years now I'm using my own TerminologyProvider deriving from AbstractTerminologyProvider. It works quite well but from time to time it just won't find some terms. At first I though that there must be some error in my code (and sure enough there were a few in the beginning) but after checking and double checking and debugging I'm more and more convinced that there is more going on. And I think it also affects MultiTerm users (see all those postings at https://community.rws.com/search?q=Term%20Recognition).

Let's have a look at the workings of a TerminologyProvider:

public interface ITerminologyProvider : IDisposable
    {
       ...

        IEntry GetEntry(int id);

        IList<ISearchResult> Search(string text, ILanguage source, ILanguage destination, int maxResultsCount, SearchMode mode, bool targetRequired);
    }

The relevant steps of the ITerminologyProvider interface here are Search which is triggered when the user activates a segment. The TerminologyProvider is supposed to return a list of ISearchResults. Those are then processed within Studio which subsequently queries the TerminologyProvider via GetEntry to deliver the full entry to diplay it in the Term Recognition pane.

What I found is that every now and then the process inside Studio gets stuck and GetEntry won't be called  (which in turn might even block all further calls to GetEntry in that batch).

I have not been able to pin this down to specific terms and couldn't find anything in the logs. I tried a lot: dates, search strings with non-breaking spaces .... Here is something quite rare - a term Studio consistently doesn't like - which came up yesterday. I hope it helps someone to pin this down:

Though I have p.m. in my glossary and hand it back to Studio in my Search implementation, Studio consistently doesn't call GetEntry. I disabled Date and Time and Acronym Recognition in my TM but it didn't make a difference.