• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 430 subscribers
  • Views 5363 views
  • Users 0 members are here
Options
Related

Studio 2019 not populating fuzzy matches during translation

Francesca Collodo

I am translating a technical document with a high proportion of fuzzy matches. I have been noticing, that sentences that differ by just one word, are not finding any matches from the TM. To check, I have closed the file, run pre-translate files, and all of the matches are populated.

Is this in any way related to the inability to upgrade TMs in 2019?

Is that fix high priority, as a big part of the sell of 2017 (let alone 2019) was the benefits of this new TM feature?

I'd really appreciate a timescale for fixes, as with this fault in particular, I'm going to have to work in 2017. Having just shelled out for an upgrade, this isn't great news. But I'll be translating every segment from scratch, when I'm getting paid on fuzzy matches otherwise.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi

    It sounds to me as if you are simply pre-translating on default settings. Perhaps you made this change so long ago in 2017 you forgot how it works? At least it sounds as though this is the problem.

    If you mean this is happenning when you work interactively then the problem may be caused by the use of lookahead, which you might also have turned off a long time ago and forgot.

    So please try checking that your default for pre-translation is lowered below 100% if that's the problem, and also try deactivating lookahead. The real benefit of lookahead is when working with machine translation in realtime... other than that it is often a feature better switched off.

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • 0
    Hi

    It sounds to me as if you are simply pre-translating on default settings. Perhaps you made this change so long ago in 2017 you forgot how it works? At least it sounds as though this is the problem.

    If you mean this is happenning when you work interactively then the problem may be caused by the use of lookahead, which you might also have turned off a long time ago and forgot.

    So please try checking that your default for pre-translation is lowered below 100% if that's the problem, and also try deactivating lookahead. The real benefit of lookahead is when working with machine translation in realtime... other than that it is often a feature better switched off.

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children