Analyze files, no fuzzy matches

Hi!

I frequently get bilingual files (xliff) from my client that need to be analyzed for discounts. Since I updated to Studio 2021 I get no fuzzy matches when analyzing files, only 100 % matches or context matches. Still I can see in the bilingual file that there are several fuzzy matches. What I do is I create an empty TM and import the clients xliff-file into the TM. Then I run the text file against that TM. Before I used to get the fuzzy matches in the analyze files report but not anymore. What could I be doing wrong?

Linn

emoji
Parents Reply
  • Hi!

    Thanks for the answers, but this still didn´t resolve my problem. When I get the XLIFF from the client, I always open it in Trados Studio (Editor), and that way I can see all the matches, both 100 % and fuzzy matches. The problem is that I can´t analyze the XLIFF for fuzzy matches, and I need the analyze to give discounts for 85-99 % matches. But as you can see in the attached reports above I get no fuzzy matches in the analyze report. This worked before I updated to Studio 2021.

    What I usually do is I create an empty TM (have now checked that the language pairs of the TM match the imported XLIFF, and I have the AnyTM option), and then I import the clients XLIFF into that TM just to make the analyze. But Trados now seems to import all the fuzzy matches as 100 % matches. 

    So my question is, why can´t I analyze the clients XLIFF for fuzzy matches (85-99 %)?

    emoji
Children
  • Hi ,

    Trados now seems to import all the fuzzy matches as 100 % matches

    That’s the expected behavior. You import an XLIFF to a TM and the matching information is not kept in the TM, just in the XLIFF. Anything imported will be a 100 % match. Draft segments will appeared as 100 % after importing them to the TM, so if I understand your workflow correctly, you shouldn’t tick the Report internal fuzzy match leverage checkbox. Please try unticking it.

    why can´t I analyze the clients XLIFF for fuzzy matches (85-99 %)?

    If the above doesn’t help, are you sure you and your client have the same TMs? I mean, same name and same content?

    Also there are slight differences in total number of segments, words and characters. Different TMs may explain the difference in segments and words, but I believe that the difference in characters can be explained only by a difference in the document being analyzed…

    emoji