Hugo Zwaenepoel 

Can you also share a screenshot of the original result prior to the repair?  I'm curious what might be causing this.  Can you also share some info on what resources you have attached to your project?

And also a Groupshare Cloud termbase. I checked the TB and do not see any possible cause there ...

Hugo Zwaenepoel 

ok - so if I was in your shoes I'd try and narrow it down a bit.  Try removing each resource one at a time and see which one was responsible for supporting the repair.  Does that point to any one n particular?

OK I'll try that and let you know!

Paul I found out that it's probably due to the frequent occurrence of the NL-FR translation of 'de Heer' (which means Mister, eg Mr Jones) by 'Monsieur'. I suppose that as a result match repair considers 'Monsieur' to be the equivalent of 'de' ... The problem is that our TMs contain a lot of segments with this occurrence. I guess the only solution is to delete those segments from the TMs?

Paul I found out that it's probably due to the frequent occurrence of the NL-FR translation of 'de Heer' (which means Mister, eg Mr Jones) by 'Monsieur'. I suppose that as a result match repair considers 'Monsieur' to be the equivalent of 'de' ... The problem is that our TMs contain a lot of segments with this occurrence. I guess the only solution is to delete those segments from the TMs?

Hugo Zwaenepoel 

I think that is probably the only solution if you want to carry on using Match Repair.  It could be that in the future we will do some work on making the solution more sophisticated to address things like this, but for now you probably don't have a better option.