• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 4942 views
  • Users 0 members are here
Options
Related

Studio 2017: QA Terminology Verification issues (false positives/negatives)

Jacob Dunlap

I'm having trouble getting terminology verification to work properly in Studio 2017.  As reference, I spent many years using Wordfast Classic, which has a very binary term verification system:  either the source term is in the target or it's not, and the program reliably flags missing terms.  That's how I want Studio 2017 to behave, but I can't seem to get it to work.  I have tried setting the "minimum match value" to 100 but that results in many false positives.  I'm not even sure what "search depth" and "repetition threshold" do, for that matter.

If anyone could give me some advice on how to get Studio to just warn me when the exact terms in the termbase are not present in the target segment, I would appreciate it very much!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • 0 in reply to Paul

    I can't send the project file as I'm under pretty strict NDAs.  I have a couple of redacted screenshots showing the issue, though.  Here are my settings:

    Here is one example:

    As you can see, the Japanese term 枠体 is in the source, the term is recognized, and the equivalent is in the target, but Studio is flagging it as being missing.  (Both instances were present in the target and were flagged.)

    One more example:

    Again, 測定器１ is in the source, the term is recognized, the equivalent is in the target -- but Studio flags it.

    Incidentally, although these segments were imported through the Legacy Converter, the same behavior happens when working directly in Studio.

    If there are any apps that offer more reliable QA with respect to terminology I would be happy with those as well, by the way.

    Thanks!
Children