• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 436 subscribers
  • Views 514 views
  • Users 0 members are here
Options
Related

False alrams with Terminology verifier

Caitlin Wang

Dear Mr./Mrs.:

The Terminology verifier function in Trados keeps reporting a huge number of errors like "Target segment does not contain the translated term for "specific term", but the term is actually in the target.

Is there any way to avoid such false alarms by changing the setting?

Currently the relevant settings on my Trados go like these and the target language is Khmer.

Screenshot of Trados Studio Terminology Verifier settings showing options for validation criteria, including checks for non-usage of target terms set to Warning, forbidden terms set to Error, and terms without the target equivalent set to Note. Minimum match value is 100, search depth is 200, and term repetition threshold is 4.

But adjusting search depth or "Term repetition threshold" seem to have no effect in reducing false alarms.

Is there any other way to perform an effective verfication of terms?

Regards

Caitlin

Generated Image Alt-Text
[edited by: RWS Community AI at 7:35 AM (GMT 1) on 17 Jul 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

      

    Hi Caitlin,

    You don't say which version of Studio you are using. If it is Studio 2024, then the 100% Minimum match value is genuinely 100% and will even find plurals of terms in the termbase as incorrect 'false positives'. I have also found that false positives can be triggered by punctuation or by 'tags', for example, in previous versions of Studio especially.

    I played around with this and found that if I reduced the Minimum match value by just 5% to 95%, plurals were not flagged up as false positives.

    The other advantage of reducing the Minimum match value from 100% is that it applies also to the Source. Therefore, if your source text contains, for example, a different person of a verb than the infinitive that is in the termbase, then it will be recognised more readily with a lower percentage.

    Have a play around with reducing the Minimum match value percentage and see if it solves your issue.

    I'm copying in   as I've been meaning to feed back to him on this very subject for quite some time!

    All the best,

    Ali Smiley
    emoji
Reply
  • 0

      

    Hi Caitlin,

    You don't say which version of Studio you are using. If it is Studio 2024, then the 100% Minimum match value is genuinely 100% and will even find plurals of terms in the termbase as incorrect 'false positives'. I have also found that false positives can be triggered by punctuation or by 'tags', for example, in previous versions of Studio especially.

    I played around with this and found that if I reduced the Minimum match value by just 5% to 95%, plurals were not flagged up as false positives.

    The other advantage of reducing the Minimum match value from 100% is that it applies also to the Source. Therefore, if your source text contains, for example, a different person of a verb than the infinitive that is in the termbase, then it will be recognised more readily with a lower percentage.

    Have a play around with reducing the Minimum match value percentage and see if it solves your issue.

    I'm copying in   as I've been meaning to feed back to him on this very subject for quite some time!

    All the best,

    Ali Smiley
    emoji
Children
No Data