We are having a problem with term recognition working in a local Trados Studio 2021 SR2 CU9 project with 4 GroupShare termbases.
A term that is recognized in the standard termbase when selecting the option to search hierarchically until a matching term is found is not found when selecting the option to search all termbases sequentially. This makes no sense.
Any ideas on what may be the root cause?
Here is an update on this issue. I have been contacted by RWS Support in the meantime and they have asked me to try reproduce the issue locally.
Here is what I found out:
I have tested and reproduced the issue with local termbases.
What I found out is that it occurs when for one term in the source text there are term matches in multiple termbases which are different one from the other. If the term match is the same in multiple termbases, all matches are shown in the term recognition window.
Example: Language combination ES > PT
Source text contains: "Llantas de aleación"
Termbase 1 contains: "Llantas de aleación"
Termbase 2 contains: "llanta de aleación"
Target terms are irrelevant for this issue.
Again: when selecting the option to search termbases hierarchically until a match is found, in this case only the match of Termbase 1 would appear. When selecting the option to search sequentially in all termbases, only the closer match will appear in the term recognition, which in this case is also the match of Termbase 1. However, if I deactivate Termbase 1, the match in Termbase 2 is shown in the term recognition window.
But if you have multiple termbases, you would actually want to see all matches regardless of whether they are close or not. This is what the option to adapt the matching settings is actually for.
In the example above, if I modify the terms to be both "Llantas de aleación", both terms are shown in the term recognition window.
Here is an update on this issue. I have been contacted by RWS Support in the meantime and they have asked me to try reproduce the issue locally.
Here is what I found out:
I have tested and reproduced the issue with local termbases.
What I found out is that it occurs when for one term in the source text there are term matches in multiple termbases which are different one from the other. If the term match is the same in multiple termbases, all matches are shown in the term recognition window.
Example: Language combination ES > PT
Source text contains: "Llantas de aleación"
Termbase 1 contains: "Llantas de aleación"
Termbase 2 contains: "llanta de aleación"
Target terms are irrelevant for this issue.
Again: when selecting the option to search termbases hierarchically until a match is found, in this case only the match of Termbase 1 would appear. When selecting the option to search sequentially in all termbases, only the closer match will appear in the term recognition, which in this case is also the match of Termbase 1. However, if I deactivate Termbase 1, the match in Termbase 2 is shown in the term recognition window.
But if you have multiple termbases, you would actually want to see all matches regardless of whether they are close or not. This is what the option to adapt the matching settings is actually for.
In the example above, if I modify the terms to be both "Llantas de aleación", both terms are shown in the term recognition window.
Translate
