Why is Studio 2017 not giving me a fuzzy match result for a almost identical segment that was previously translated?

Dear Studio 2017 users,

I was working on a project with lots of fuzzy matches against the project TM. However, I noticed that Studio does not seem to offer me a fuzzy result from the TM when it's supposed to. For example, a segment "No plasma" is in the project TM, but I didn't get a result in the translation results window when I was working on a new segment called "No Plasma".

I believe the client prepared this project using either Studio 2011 or 2014. I did upgrade the TM using ReindexTMs with both Re-Index and Uplift enabled. Are there other settings I can adjust that would make Studio 2017 recognize No Plasma as a fuzzy match from the TM segment No plasma?

Thank you so much for your advice!

Chunyi

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Why is Studio 2017 not giving me a fuzzy match result for a almost identical segment that was previously translated? Dear Studio 2017 users, I was working on a project with lots of fuzzy matches against the project TM. However, I noticed that Studio does not seem to offer me a fuzzy result from the TM when it's supposed to. For example, a segment "No plasma" is in the project TM, but I didn't get a result in the translation results window when I was working on a new segment called "No Plasma". I believe the client prepared this project using either Studio 2011 or 2014. I did upgrade the TM using ReindexTMs with both Re-Index and Uplift enabled. Are there other settings I can adjust that would make Studio 2017 recognize No Plasma as a fuzzy match from the TM segment No plasma? Thank you so much for your advice! Chunyi
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Parents

0 Jesse Good over 9 years ago

Hi Chunyi,

Would you be able to show a screenshot?
In my experience, matching is problematic with short phrases because only a few small differences can cause huge differences in the percentages. However, I would expect your case to appear since it is only a capitalization difference.

Another thing to try out is lower the minimum matching percentage (fuzzy match threshold), which is set at 70 percent as the default.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Chunyi Chen over 9 years ago in reply to Jesse Good

Hi Jesse,

Thank you for your input. This is a real project, so I am afraid I can't post a screenshot here:)
I have lowered the minimum matching percentage to 60. (Is there a way to be sure this change will apply in future projects not just this project?) I will report if I see any improvement with this modification.
Thank you again, and have a nice weekend.

Chunyi
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul Filkin over 9 years ago in reply to Chunyi Chen

Chunyi Chen said:
Is there a way to be sure this change will apply in future projects not just this project?

Hi Chunyi,

You need to make this change to your Project Templates, if you are using them, or to your default template in File -> Options. Then all new projects will have the desired settings preconfigured.

Regards

Paul

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Chunyi Chen over 9 years ago in reply to Paul Filkin

Hi Paul,

Can you tell me exactly where I can find this setting in file>Options. I could only find this setting in Project Settings>Translation Memory and Automated Translation>Search, but it's for this particular project only.
Thank you for your help!

Chunyi
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Lucia Vargas over 8 years ago in reply to Paul Filkin

Hi Paul,

First I would like to say thanks because I see you are very dedicated and always strive to really answer our concerns regarding Studio. You have helped me solve issues in the past.

I have also been experiencing this since the latest update of Trados came available (the one where the Trados logo changed and all).

Always when I translate a sentence, then three segments later, for example, comes another segment very similar but maybe only one word is changed and I get nothing in the TM results. If then I go to settings of the TM search, I change something (like lessening the percentage of TM match, or ticking the option boxes ("Search for fuzzy matches even if exact match found", and the other two), I come back to the editor and this time the TM results give me the appropriate fuzzy match. Later on I continue and it happens again, so I come back and change again something in the TM search parameters and again in the editor I get the fuzzy match.

So, because of this behaviour, I guess it is some kind of bug... It is really annoying, I preferred the way Trados worked before, but I am also sure that hopefully the Trados team will solve this :)

Thank you,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Jerzy Czopik over 8 years ago in reply to Lucia Vargas

Have you already tried to switch Look Ahead (File -> Options -> Editor -> Automation) off?

_________________________________________________________

When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Lucia Vargas over 8 years ago in reply to Jerzy Czopik

Hi Jerzy, thank you so much, indeed, this worked perfectly. I now get the matches when they are suppossed to appear. I had been experiencing this a lot but I am glad I finally came here to ask. I wonder, though, what is the purpose of this Look Ahead function in Trados? I will make some research later, thanks!

I hope Chunyi had also solved the issue as well.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul Filkin over 8 years ago in reply to Lucia Vargas

Hi Lucia Vargas ,

The idea behind the Look Ahead function is to increase the look up performance and reduce any lag, in particular when working interactively with machine translation. So the idea is that Studio looks ahead at what is about to be translated and fetches the results in advance of you getting there. These results are cached and are immediately available when you enter the next few segments.

The drawback of this approach is that new information in your translation memory from the previous segment won't be available to you, and this can also affect your terminology. I know the development team are looking at ways to reduce this drawback since the idea itself is actually very helpful.

Regards

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

0 Paul Filkin over 8 years ago in reply to Lucia Vargas

Hi Lucia Vargas ,

The idea behind the Look Ahead function is to increase the look up performance and reduce any lag, in particular when working interactively with machine translation. So the idea is that Studio looks ahead at what is about to be translated and fetches the results in advance of you getting there. These results are cached and are immediately available when you enter the next few segments.

The drawback of this approach is that new information in your translation memory from the previous segment won't be available to you, and this can also affect your terminology. I know the development team are looking at ways to reduce this drawback since the idea itself is actually very helpful.

Regards

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

0 Lucia Vargas over 8 years ago in reply to Paul Filkin

Hi Paul,

Thanks for the explanation, it makes sense, that is what was happening, that the latest addition in my TM would not appear as a match a few segments later when an obvious match was there. I disabled it, as Jerzy suggested, and I stopped having this issue. But I hope in the future, as you said, the development team solves it and we can profit from the idea of having this Look Ahead tool.

Best regards,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Ignacio Niveiro over 6 years ago in reply to Paul Filkin

Hi Paul Filkin,

Is this issue with Look Ahead being looked into? Because in Trados 2019 SR2 it's still happening... and it's really problematic sometimes.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul Filkin over 6 years ago in reply to Ignacio Niveiro

Ignacio Niveiro

All I can tell you is that the development team are aware of the problems. I don't know when we can expect a solution to problem in an update.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Why is Studio 2017 not giving me a fuzzy match result for a almost identical segment that was previously translated?