Translate
Hello,
I found the includeHomonyms property in the Trados code. I want to set it to false. Do you know where I can find this setting in the UI, or if it's possible to change it programmatically?
Thank you,
Helena
Hello,
I found the includeHomonyms property in the Trados code. I want to set it to false. Do you know where I can find this setting in the UI, or if it's possible to change it programmatically?
Thank you,
Helena
Hi Helena Grulichova , good question -> short answer: this is not accessible. I have asked the question to the team, to confirm if it makes sense exposing this. +Andrei Caia might be able to provide more info.
You were able to locate this property in the Trados code?
Patrick Andrew Hartnett | Developer Experience | Team Lead | RWS Group
Helena Grulichova - To avoid duplicated terms, can you try this option, please? Will this fix the issue? If not, can you please describe in more detail what the issue is/what you are trying to achieve?
Helena Grulichova - To avoid duplicated terms, can you try this option, please? Will this fix the issue? If not, can you please describe in more detail what the issue is/what you are trying to achieve?
Hello,
We use two termbases in our project - the first one is our terminology provider plugin and the second one is a real file termbase which is disabled. In our plugin, we read the real termbase, lemmatize it, and override the Search method. We provide results from the real termbase, but it can lemmatize the source/target segment and terms in the real termbase and find the hits. F8 for verification - usage of terms must work, too. F8 fires the same Search method on all segments in both languages and compares results on both sides based on their entry IDs, right? It seems verification works only with the first termbase (our plugin in this case), right? The Search setting does not help - I suppose it works only for search, not for verification. We do not have trouble with standard term recognition but only with verification of term usage (Verification Settings -> Check for possible non-usage of target terms: true).
When one term is found in the source segment, Trados Studio expects one corresponding term in the target segment with the same entry ID - this works fine. However, if it finds two terms with the same ID in the source segment, it expects FOUR terms with the same ID in the translation. If it finds three occurrences in the source, it demands NINE occurrences in the target. I eventually found that if I use SearchAndMarkup instead of Search and provide exact positions of search results, I can avoid this issue.
Best regards,
Helena
