Kihwan Jung 

I don't believe you can do this unless you use some script to take the TM result, cut the target from your translation after inserting it (so it's now on your clipboard), clear the target (which will remove the score) and then paste the result back in from your clipboard.  Probably pretty simple using AutoHotKey for example.

Alternatively, just work with the results and remove them all after you're done: https://appstore.rws.com/Plugin/38

I'm interested to know why you want to do this?  Perhaps you think it's a problem because of the way you're working?

The issue is that even when I leverage my own TM , not the one provided by the client, the segment still shows as 100%.

However, reviewers typically don't spend much effort reviewing segments marked as 100%. Of course, if a 100% match is from the client's TM, a thorough review isn't necessary. But if the segment is a 100% match from my own TM, it requires a reviewer's check.

Therefore, if segments from my TM and the client's TM are both displayed identically as 100%, it can create confusion during the review process.

Kihwan Jung 

I'm somewhat confused with this response from you.  Your original post was about suppressing or removing the display of match rates in the editor (so that no percentage appears in the segment when TM content is inserted).

Your last reply shifts into a review workflow issue, complaining that when a client TM and personal TM both produce “100%” then reviewers can’t tell the difference.

These are two different problems:

• Display of match percentages in the editor.
• Differentiating sources of TM matches for reviewers.

I have already answered your first point, so on your second.  Whilst it is possible that a client TM 100% match is better than one coming from your own unrelated TM that is no guarantee it shouldn't be reviewed.  That decision is either one coming from your client because they don't want to pay for 100% matches, or one you have decided on for productivity reasons.  But whatever the reason I don't see what this has to do with being able to disable the match rate from anywhere.

Perhaps you should share some example images clearly showing why this is something you feel the need to do?  Perhaps we are misunderstanding each other on the basis of terminology, or maybe it's just me.  Pictures can help.

You're right. Even a 100% segment from the client's TM requires review. So, let me give you a slightly different example.

1. The client has requested a review from a reviewer.

2. The file contains several fuzzy matches from the client's TM. The client has asked to review the segments except for the 100% matches because they believe the 100% segments are quite accurate and don't need a review.

3. Of course, it would be simple to lock the 100% segments that are outside the scope of work, but unfortunately, the client isn't that meticulous.

In this case, if the translator used a 100% match from their own TM instead of the client's TM, the file the reviewer receives will display two types of 100% matches: a 100% match from the translator's TM and a 100% match from the client's TM.

At this point, the reviewer needs to review the translator's work while skipping the 100% segments from the client's TM. However, if the translator used a 100% match from their own TM, the reviewer can get confused, as they can't distinguish whether the segment is a 100% match from the client's TM or the translator's TM.

Therefore, the translator would remove the 100% for segments leveraged from their own TM, leaving only the 100% from the client's TM, so the reviewer doesn't get confused.

Honestly, this situation doesn't happen often, but it has occurred occasionally, which is why I asked about this feature. However, based on your answer, it seems like this isn't possible with Trados's default features. I'll just have to solve this by either using my usual copy-and-paste method or trying your suggestions. Thanks for the answer, and you can just forget this one!

Kihwan Jung 

Perhaps the solution is to use attributes on the TM itself so that the translator can see where the TM match came from?  You could even penalise all TMs apart from the clients TM if this is a problem.

Kihwan Jung 

Perhaps the solution is to use attributes on the TM itself so that the translator can see where the TM match came from?  You could even penalise all TMs apart from the clients TM if this is a problem.