Hello, Julie,

Will try to help.

So, example of fuzzy list:

Take a note on the Synonyms column, which contains codes of fuzzy matches used in Studio analysis files. If yours is incorrect, try to edit them manually to reflect attached image.

Next, example of fuzzy scheme:

Only fuzzy types included in a fuzzy scheme will be used during analysis import. You can choose default fuzzy scheme in global plugin settings, and in each customer editing form. Example of default fuzzy scheme in settings:

And then, for a project with empty customer, I selected a project in the list and clicked Recalc. wordcount to view analysis contents:

Hope something from this answer will help you to determine an issue!

Hello Eugene,

Thank you for your help.

I have checked everything and updated the fuzzy list, as some Synonyms did not match.

I made sure that everything else is the same as shown on your screenshots and in your instructions, but the fuzzies are not detected, even when I change to a default fuzzy scheme.

So this should not be why the fuzzies are not recognized.

Hello, Julie,

Strange. May I ask to attach analysis report you're trying to import? I will check/test it locally. Maybe some bug...

Sent via email

Hello, Julie,

Thank you! But there is a small problem - message was blocked by some internal antivirus system. Is there any other means of sending it? For example, cloud drive and share with me, or send to my other address: yauhenkuchynski at gmail dot com

Hello Eugene,

I have just sent it to you.

Please let me know if you still can't open it, and I will try a cloud share in that case.

Hello, Julie,

I've tested the report and confirm that it doesn't work. The reason is that fuzzy matches are counted as internal fuzzies, not as conventional fuzzies. So, I suppose this is a bug and plugin needs a fix.. Right? Or not?

Hello Eugene,

Thank you so much for checking.

I never realized Trados recognizes the fuzzies as different ones (internal vs conventional) so I did not think it could be a problem for the plugin. And I suppose it is a bug if the plugin was meant not to differentiate them in the analysis. In any case, it will be most useful if a solution could be provided regarding this problem and for the plugin to take everything into account in the breakdown.

I may work on files with internal and/or conventional fuzzies, depending on the client sending me the files and how they process them. As for now, most often the calculation breakdown for these projects is inaccurate, so I have to manually correct them for the quotes and invoices. And it can be a little delicate and fastidious to bypass the issue sometimes.

Please let me know if you think it is doable. 

I can't thank you enough for your efforts!

Hello Eugene,

Thank you so much for checking.

I never realized Trados recognizes the fuzzies as different ones (internal vs conventional) so I did not think it could be a problem for the plugin. And I suppose it is a bug if the plugin was meant not to differentiate them in the analysis. In any case, it will be most useful if a solution could be provided regarding this problem and for the plugin to take everything into account in the breakdown.

I may work on files with internal and/or conventional fuzzies, depending on the client sending me the files and how they process them. As for now, most often the calculation breakdown for these projects is inaccurate, so I have to manually correct them for the quotes and invoices. And it can be a little delicate and fastidious to bypass the issue sometimes.

Please let me know if you think it is doable. 

I can't thank you enough for your efforts!

Hello, Julie,

Sorry, but I forgot to mention earlier, that new version (5.1.1) was published on the App store, where this issue was fixed!

Hello Eugene,

Thank you so much for the update!