My plugin's translation results are not displayed alongside those from other plugins in Trados 2024.

I'm developing a translation plugin for Trados 2024.
A user reported that the translation results from my plugin are not displayed alongside those from other plugins.

This is the first time I've received such a report specifically for Trados 2024.
Is there a known solution to this issue?

Also, could this be the same phenomenon as described in this post?

 Translation Results window does not show results from multiple MTs in Trados Studio 2024 - 18.0.2.3255 

==================================================

I’d like to investigate the issue myself, but in order to reproduce the phenomenon, I need to install third-party plugins.

When I try to use these plugins, I get the message:
“You are not currently subscribed to a machine translation package.”

Are there any plugins available for testing that can be used without a subscription?
Or is a subscription absolutely required in all cases?

emoji
  • Probability score: 0.6  

    Question improvement suggestion: Provide specific details about the plugin you are developing, including its name and any relevant error messages or behaviors observed during testing. This will help in diagnosing the issue more effectively.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello,  

    It sounds like you're encountering a challenging issue with your translation plugin in Trados 2024. Here’s a step-by-step approach to help you investigate and potentially resolve the problem:

    **Step 1:** Verify Plugin Compatibility  

    Ensure that your plugin is fully compatible with Trados 2024. Check for any updates or documentation that may indicate changes in the API or functionality that could affect how results are displayed.

    **Step 2:** Test with Other Plugins  

    To reproduce the issue, you may need to install third-party plugins. If you are receiving a message about not being subscribed to a machine translation package, it may be necessary to check if there are any free plugins available for testing purposes. Unfortunately, many plugins do require a subscription, but you can look for trial versions or community-supported plugins that might not have this restriction.

    **Step 3:** Review the Reported Issue  

    Since you mentioned a user reported this issue, gather more details from them. Ask if they have any specific error messages or if they can provide screenshots of their setup. This information can be crucial in diagnosing the problem.

    **Step 4:** Investigate Known Issues  

    You referenced a community post regarding similar issues. Review that post and any related discussions to see if there are known solutions or workarounds that could apply to your situation.

    **Step 5:** Debugging  

    If possible, implement logging within your plugin to capture any errors or unexpected behavior when it attempts to display translation results. This can provide insights into what might be going wrong.

    **Step 6:** Reach Out for Support  

    If the issue persists and you cannot find a solution, consider raising a support ticket with RWS. Provide them with detailed information about your plugin, the specific issue, and any steps you have already taken to troubleshoot.

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI

    emoji
  • Could setting TranslationProviderInfo.TranslationMethod to "Other" be related to the issue?

    =========================

    class TranslationProviderFactory : ITranslationProviderFactory
    {

    public TranslationProviderInfo GetTranslationProviderInfo(Uri translationProviderUri, string translationProviderState)
    {
    TranslationProviderInfo info = new TranslationProviderInfo();
    info.TranslationMethod = TranslationMethod.Other;
    info.Name = "MyAddinName";
    return info;
    }

    emoji