Although term equivalents in the target language can be found by entering a source term in the Termbase Search field, the same source term is not automatically recognized in the Editor view. (No terms are recognized, although a large number are in fact listed in the termbase.)
The project settings for Termbases are the usual: the termbase is enabled. The search settings are the standard ones (Search all termbases in parallell...; all other options deselected).
I'm sure you have set everything up correctly but it would be helpful to see a screenshot of your Studio while in a segment that should have results, and also a screenshot of your project settings for the termbase. That should always be a starting point because otherwise we cannot rule out the more obvious problems.
OK; here it is:
Thanks Mats Linder
Just checking... but what do you see if you show the Term Recognition window instead of the search window here?
I can see that "Breite" is recognised as the red line is over the term, but it won't display in the search pane.
Of course! Stupid of me not to have thought about that.
Could it be a similarly simple solution to the TM lookup problem? I shall try to lower the minimum match value and see what happens. Meanwhile, thanks a lot for taking your time for this (and for finding the first solution)!
BTW, what does the minimum match value percentage refer to? Number of characters? The Help text's "degree of match" is not much help.
BTW, what does the minimum match value percentage refer to?
It's a TM lookup match value. So a default of 70% would be like a 70% fuzzy match.
I get that. But it has struck me that I don't know what the percentage refers to. The number of characters?
Well... not only do I not know how Trados calculates a fuzzy match, but I could not tell you even if I did! I'm sure you are capable of seeing for yourself that it isn't the number of chars! Just edit a TU in the translation results window by removing a letter at a time from the source and see what happens!
Trados has a proprietary matching algorithm that will be based upon some sort of edit distance calculation... which is a sort of character count but not in the way you have suggested here.
So far so good... However, a new problem very much related to this one has appeared: Since the termbase in question is locked, I created a new one for adding term posts during the work. However, for some reason Studio (both 2021 and 2022) refuses to read that termbase. I can add term posts, but they are not "seen" while I work. Some images:
Maybe you have lookahead enabled? That will cache the fact you didn't have any terms before and now you will only see the results of the cache (no results) until you have worked through a few segments and then go back and look. If you disable lookahead it will be instant.
Translate
