Hi Adrian Dunbar 

I can't reproduce any of these problems so I guess it has something to do with your settings.  I created a short video as it's easier for you see what I've done.  Hopefully you can help me to mirror your situation:

Adrian Dunbar said:

Putting a wildcard term in like "target comp*" will not prevent this.

Not surprising as this isn't supported.  The fuzziness is controlled in the project settings.

Hi Paul:

I went through your steps and in creating a new project the termbase on the new project seems to be recognizing the terms properly in the verifier.  However, in my current project, it's creating errors that otherwise wouldn't have been registered in the test project.  In the current project, the verifier seems to be giving all sorts of inconsistent trouble. In some places, I can't get the verifier to recognize the term at all, even by using term insertion. For one term, I'm getting an error even though it does not appear in those segments. So the problem seems to be that the verifier isn't recognizing these terms at all. If I edit source in the term file and copy whole segments over, then the issue seems to not reoccur in the test file. But if I create a new project from the same file, no matter how the terms are filled (TM/leverage), the same exact problems persist.

Here is an example of where I am getting an error for the term "compliance risk" in a file where the term "compliance risk" is clearly used in the segment yet the verifier cannot tell that it is there:

 The problem with the plural/variants not being recognized either keeps occurring, but is not the only problem with these files.

I did, however, find this seems to work on this particular file: clear all formatting prior to translation in MSWord and create a project. If any formatting is kept, then the verifier simply won't work. Maybe it's due to formatting?

Hi Paul:

I went through your steps and in creating a new project the termbase on the new project seems to be recognizing the terms properly in the verifier.  However, in my current project, it's creating errors that otherwise wouldn't have been registered in the test project.  In the current project, the verifier seems to be giving all sorts of inconsistent trouble. In some places, I can't get the verifier to recognize the term at all, even by using term insertion. For one term, I'm getting an error even though it does not appear in those segments. So the problem seems to be that the verifier isn't recognizing these terms at all. If I edit source in the term file and copy whole segments over, then the issue seems to not reoccur in the test file. But if I create a new project from the same file, no matter how the terms are filled (TM/leverage), the same exact problems persist.

Here is an example of where I am getting an error for the term "compliance risk" in a file where the term "compliance risk" is clearly used in the segment yet the verifier cannot tell that it is there:

 The problem with the plural/variants not being recognized either keeps occurring, but is not the only problem with these files.

I did, however, find this seems to work on this particular file: clear all formatting prior to translation in MSWord and create a project. If any formatting is kept, then the verifier simply won't work. Maybe it's due to formatting?