Hi Helena Grulichova ,

        Does this article help you : https://developers.rws.com/studio-api-docs/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html?tabs=standard

Best regards,

Cornea Robert

Hello,

I do not see how to get all entries from a termbase with the new API. SDL.Terminology.TerminologyProvider.Core provides only the Search functionality, but I want to access all entries. I use code similar to the sample code: https://developers.rws.com/multiterm-api-docs/apiconcepts/entry.html How can I replace the MultiTerm API now?

Best regards,
Helena Grulichova

Hi Helena Grulichova ,

         There is no way currently to retrieve all the entries. What is the scenario that you are trying to solve ?

Best regards,

Cornea Robert

We are loading all entries from a term base and lemmatizing them, and then using the lemmatized forms for search and verification. We also have a custom term base viewer where we allow users to add/edit/delete terms (it ensures the plugin).

Hello!

Indeed, Studio Terminology API lacks this functionality. For this, you will still need to use Sdl.MultiTerm.TMO.Interop. You mentioned that you encountered an error when using the TMO. Can you please paste here the full stack trace so we can assist further?
Not sure if the path mentioned above is correct, you should try adding to your project <MultiTermFolder>$(MSBuildProgramFiles32)\Trados\MultiTerm\MultiTerm18</MultiTermFolder>

Andrei

Hi there Helena - just to add to what Robert and Andrei were saying - if you install MultiTerm Desktop, we hope that you would get all required functionality, as MultiTerm Desktop brings its own TMO.dll and other infrastructure for such use cases to work. So in your case, you may end up with a kind of hybrid model - migrate code to the Studio terminology provider where possible but also keep TMO functionality where still needed. Thanks, Daniel

Hello,

I was able to include a reference to Sdl.MultiTerm.TMO.Interop.dll from $(MSBuildProgramFiles32)\Trados\MultiTerm\MultiTerm18. Now I have these issues:

#1 I inherited from ITerminologyMarkupProvider instead of ITerminologyProvider (due to this issue: includeHomonyms). However, now SearchAndMarkup is not being hit - only the Search method is called. If I revert to using the Search method, the issue with duplicating search results persists. If there are two hits in the source text, it expects four hits in the target text when it verifies term usage. If there are 3 hits in the source, it expects 9 hits in the target. The issue remains unresolved, and now I cannot use the workaround.

#2 I have a custom Termbase Viewer (according to https://developers.rws.com/studio-api-docs/apiconcepts/terminology/displaying_entry_content.html?tabs=tabid-1%2Ctabid-2%2Ctabid-3). It implements the ITerminologyProviderViewerWinFormsUI interface. Now the Initialize method (Initialize(ITerminologyProvider, CultureCode, CultureCode)) is not being called at all. How can I pass the TerminologyProvider to the control now?

Best regards,
Helena

Hello,

#1
SearchAndMarkup is not being hit anymore; it seems to be a bug introduced with the SR1 release. Can you give me more info about your scenario, please? I am not sure I understand why includeHomonyms is an issue for the Search method, but not for SearchAndMarkup.

#2
Is the TerminologyProviderViewerWinFormsUI used?
See:

Hello,

#1 We implemented a TerminologyProvider with the Search method but encountered an issue when users verify term usage (F8 + 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.

While debugging, I discovered there is a condition regarding includeHomonyms in your code which is not accessible to us. If includeHomonyms is true, it multiplies the occurrences in the source. If it is false, it would not do this. That is why I wanted to set it to false somehow.

I eventually found that if I use SearchAndMarkup instead of Search and provide exact positions of search results, I can avoid this issue. I'm not sure why, but it doesn't multiply the search results then and avoids the code with the includeHomonyms condition. If you could either fix the multiplication issue or allow me to configure includeHomonyms from the plugin, I wouldn't need to use SearchAndMarkup. The setting: Search hierarchically until a matching term is found does not help.

#2 Yes, I use it exactly as shown in your screenshot. It worked before SR1. The Control getter is being hit (it loads the correct control) but it doesn't hit the Initialize(ITerminologyProvider, CultureCode, CultureCode) method of TerminologyProviderViewerWinFormsUI. I use this method to get the TerminologyProvider object and then pass it to the Termbase viewer control.

Best regards,
Helena

Hi Helena Grulichova,

About the plugin issue you're experiencing - to help diagnose and resolve it properly, it would be really helpful if we could take a look at the source code.
Would you be able to share the plugin code with us? If you prefer not to share the actual code, no worries at all - a dummy version that shows what you're trying to achieve or reproduces the issue would work perfectly fine.
Just wanted to let you know that any code you share will only be used for troubleshooting this issue and will be deleted once we've got everything working again.
Feel free to send the files however is easiest for you.

Thanks,
Andrei

Hi Helena Grulichova,

About the plugin issue you're experiencing - to help diagnose and resolve it properly, it would be really helpful if we could take a look at the source code.
Would you be able to share the plugin code with us? If you prefer not to share the actual code, no worries at all - a dummy version that shows what you're trying to achieve or reproduces the issue would work perfectly fine.
Just wanted to let you know that any code you share will only be used for troubleshooting this issue and will be deleted once we've got everything working again.
Feel free to send the files however is easiest for you.

Thanks,
Andrei

Hi Andrei, 

Yes, I can share the code with you. Where can I send the files?

Thanks,
Helena

You can send it to acaia@rws.com. You can send the files directly if the size allows; if not, you can send me a OneDrive link or something similar.