Translation Results Window and Fuzzy Matches

happy sad sad

I have noticed that I seem to have more unhappy than happy faces in my blog entries. That doesn’t mean that I would generally be more unhappy with Trados Studio — quite the contrary actually. I guess, I played most of my happy face cards during the first few hands and now I’m left reporting these relatively minor annoyances that surface every so often during my translation work. Really, I like the top 5 features I listed earlier so much that an occasional annoyance here and there isn’t really that bad. Of course, I would like to see a good program getting even better since there seems to be plenty of room for improvement.

Having said that, here’s my complaint of the day. Or there are actually two related problems. First of all, I don’t like the way fuzzy matches are indicated using the “track changes” type of markings instead of the highlighting used in Trados 2007. This has bothered me from the beginning but I was hoping that I would get used to it. Maybe I will one day, but it hasn’t happened yet. Seemingly, I’m not the only one with this problem — the “return of the highlighting” is one of the most requested features on ideas.sdl.com. Trying to figure out the fuzzy match differences, when they are marked like this, is somehow more difficult and takes more time, and I find myself often just figuring out the differences by comparing the new source segment with the fuzzy target segment without even looking at the Translation Results Window. You can modify to certain extent how these markings are applied but these customization options don’t include highlighting.

The other reason why I have started to overlook the Translation Results Window is the way fuzzy matches seem to be calculated. I have received absolutely weird fuzzy matches. Here are some examples (click the images to see them better):

When using the previous versions of Trados, I lowered my fuzzy match setting down to 50% or 60% because it often brought me good partial matches that would have otherwise been overlooked. I guess, with Studio it’s better to keep this setting closer to the default 70%.

Advertisements

5 Responses to “Translation Results Window and Fuzzy Matches”

  1. Michael Schubert Says:

    Amen, brother! After six months with Studio, my instinctive response to the new fuzzy markup has been and remains the same as yours: ignore it and compare manually. As for the match rates, ditto: I have seen the most unbelievably useless 70%+ matches! One more reason to refuse any rate discount based on Trados matches.

  2. Reino Says:

    Agree totally!

  3. AMI Says:

    Dear Tuomas,
    I am struggling with Studio as well. I am currently working on a project with more than 100 000 segments in the TM, ranging back to 2008. My main problem is to get the latest (most recent) segments to display at the top of the ‘list’ in the translation results. Do you know of any trick for that?

    Thanks!!
    Astrid

    • Tuomas Says:

      Hi Astrid,

      You could create one or more filters (based on a date) and use the filter penalties to prioritize your matches. This works better if you have a certain date that can separate the “good” matches from the “less desirable” ones.

      You can access the Filter setup through Project Settings (or Options if you want to use the filters for other projects as well) > Translation Memory and Automated Translation > Filters.

      Hopefully that helps.

      -Tuomas

  4. Marinus vesseur Says:

    You hit the nail on the head. Fuzzy matches lower than 75% are now practically useless, which can be a real problem if you give your clients discounts based on fuzzy match percentages.
    Keep this in mind the next time you’re asked to make an offer for translation of a document that contains many fuzzy matches.
    Like you, I catually like many of the improvements in Studio, but the “Fuzzy Match Issue” is a major annoyance and still completely unresolved in SP3.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: