1. General - Recent Threads

RE: AI bridge translation does not use terms of my groupshare server termbase, local termbase works

RWS Community AI — Thu, 09 Jul 2026 08:48:18 GMT

Hello,

Yes, this is correct. AI-based features, such as Language Weaver or other AI-driven functionalities in Trados Studio, often require secure HTTPS connections to ensure data security and compliance with modern encryption standards. If your GroupShare server is running on HTTP without SSL encryption, the AI bridge translation feature will not be able to access the termbase on the server due to the lack of a secure connection.

Here’s how you can address this issue:

**Step 1:** Verify your GroupShare server configuration.

- Check whether your GroupShare server is configured to use HTTP or HTTPS. This can typically be done by reviewing the server settings or consulting with your IT team.

**Step 2:** Enable SSL encryption for your GroupShare server.

- If your server is currently running on HTTP, you will need to configure it to use HTTPS. This involves obtaining an SSL certificate and applying it to your server. Your IT team or server administrator can assist with this process.

**Step 3:** Update the server URL in Trados Studio.

- Once your GroupShare server is configured to use HTTPS, update the server URL in Trados Studio to reflect the secure connection (e.g., change `http://` to `https

AI bridge translation does not use terms of my groupshare server termbase, local termbase works

Fanxiang NIE — Thu, 09 Jul 2026 08:47:46 GMT

Environment: Trados studio 2026, groupshare server is updated to the latest 2020 SR2 CU15.

AI tells me this is because my server runs on HTTP with no SSL encryption, and AI mandate HTTPS connection. Is this true?

MultiTerm Extract - Export fail

Inés Rodríguez-Borlado Garzón — Fri, 12 Jun 2026 13:37:39 GMT

Export fails in MultiTerm Extract 2024.

Product version: MultiTerm Extract 2024

Workflow:

Import bilingual XML file.
Validate terms.
Select Export > XML.
Confirm the export settings and click OK/Finish.

Expected result:
The validated terms are exported to an XML file.

Issue:
The export window closes immediately without any error message, and no XML file is generated.

Troubleshooting already performed:

Uninstalled and reinstalled MultiTerm Extract 2024.
Repeated the process with the same XML file.
The issue persists.

Could you please advise how to export the validated terms correctly, or whether there are any known issues with XML export in MultiTerm Extract 2024?

Thanks.

RE: MultiTerm Extract - Export fail

Anca Stoian — Tue, 16 Jun 2026 05:53:30 GMT

Hi Inés Rodríguez-Borlado Garzón

Multiterm Extract is no longer supported and some issues may rise from using it.

Please check this app https://appstore.rws.com/plugin/34?tab=documentation

projectTermExtract app is allowing you to extract term candidates from your Project, or specific files within a project.

Best regards,

Anca

RE: MultiTerm Extract - Export fail

Inés Rodríguez-Borlado Garzón — Mon, 15 Jun 2026 14:03:06 GMT

It does not work.

Could you please advise?
Thanks

RE: MultiTerm Extract - Export fail

RWS Community AI — Fri, 12 Jun 2026 13:38:01 GMT

Hello,

Thank you for providing detailed information about the issue you're encountering with MultiTerm Extract 2024. Based on your description, it seems the export process is failing without generating an error message or an XML file. Here’s a step-by-step guide to help you resolve this issue:

### Step 1: Verify MultiTerm Extract Version

- Ensure you are using the latest version of MultiTerm Extract 2024. Check for updates within the application and install any available patches or updates. Updates often address known bugs or issues.

### Step 2: Check the XML File

- Validate the bilingual XML file you are importing to ensure it is free of inconsistencies or errors. Use an XML validation tool to confirm the file's structure and content are correct.

### Step 3: Test with a Different File

- Try importing and exporting a different bilingual XML file to determine if the issue is specific to the file you are using.

### Step 4: Adjust Export Settings

- When exporting, carefully review the export settings. Ensure that the output location has sufficient permissions and that the file path is not too long or contains special characters.

### Step 5: Run MultiTerm Extract as Administrator

- Launch MultiTerm Extract 202

Antidote connector problem with Antidote refreshing constantly as soon as a file isn't tiny.

Patrice Philippi — Tue, 02 Jun 2026 21:30:17 GMT

I am using the Antidot software from Druid to spellcheck/grammar check my translation in Trados.

When dealing with a small file, the Antidote 12 software interact properly with Trados Studio 2024 (SR1 18.1.3.6657).

But for example, when opening Antidote 12 on a medium file of 12k, it took 4 minutes until the Antidote windows was opened. Then I just moved the Antidote window and again, a "refreshing" popup goes on for 4 more minutes. I then page down, and again Antidote is refreshing for 4 more minutes.

A few months ago, the connector between both software was working fine and I was able to run Antidote smoothly on bigger files.

I contacted Antidote and run their "diagnosis" software, they came back to me saying all fine - there is a problem with the connector provided by Trados. So Trados needs to fix it.

Did anyone else experience the same bug?

IS MY OLD DEEPL TRANSLATION PROVIDER OK TO REGISTER WITH DEEPL AGAIN?

Cristiana Cocco — Thu, 16 Apr 2026 10:44:01 GMT

I HAD DELETED EVERYTHING A MONTH AGO.I registered with DeepL, and everything changed. I have the API plan and the API key, but it doesn't work. Do you think I should change the DeepL translation provider?

RE: IS MY OLD DEEPL TRANSLATION PROVIDER OK TO REGISTER WITH DEEPL AGAIN?

RWS Community AI — Thu, 16 Apr 2026 10:44:22 GMT

Probability score: 0.6

Question improvement suggestion: Provide specific details about the error message you are encountering with the API key and clarify whether you have checked the validity of your DeepL API key.

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

Hello! Thank you for your question regarding your DeepL Translation Provider and the issues you're experiencing. Let's go through some steps to help you resolve this.

**Step 1:** Ensure that you have the latest version of the DeepL Translation Provider installed. You can do this by navigating to **Add-Ins** → **RWS AppStore** → **Installed plug-ins** and uninstalling the current version. Then, reinstall the latest version from the RWS AppStore.

**Step 2:** Check that your Trados Studio is up-to-date. Go to **Help** → **Check for updates** to ensure you have the latest build installed.

**Step 3:** Verify that you have a valid DeepL API key. Log into your DeepL account and check your API key under the account settings. If the key is invalid or expired, you will need to generate a new one.

**Step 4:** Confirm that your DeepL subscription is active and that you have the appropriate plan (Pro Advanced or Ultimate) that supports API access.

**Step 5:** If you continue to experience issues, check the health status of your DeepL Machine Translation Provider in the RWS AppStore. If it shows "Not Configured," follow the steps to validate the configuration.

If you have followed these steps and are still facing issues, it may be worth considering switching to another translation provider, especially if the DeepL service does not meet your needs or if the problems persist.

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

RE: Unable to update Trados TM

RWS Community AI — Wed, 21 Jan 2026 12:04:22 GMT

Probability score: 0.6

Question improvement suggestion: Please provide the exact error message you received when trying to update your Trados TM, as well as the version of Trados Studio you are using. 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 experiencing difficulties updating your Trados Translation Memory (TM) with your SmartCat TM. Here are some steps you can take to troubleshoot and potentially resolve the issue:

**Step 1:** Check the Error Message

Make sure to note the exact error message you received when attempting the update. This information is crucial for diagnosing the problem.

**Step 2:** Upgrade Translation Memories

Instead of using the default import option, try using the "Upgrade Translation Memories" option. This can often resolve issues related to importing TMs. You can find more information about this in the Trados Studio help documentation.

**Step 3:** Verify File Compatibility

Ensure that the TM files you are trying to import are compatible with your version of Trados Studio. If you are using legacy TM files, make sure you have all the necessary files (e.g., *.tmw, *.iix, *.mdf, *.mtf, and *.mwf) for the import to work correctly.

**Step 4:** Check for Updates

Make sure that your Trados Studio is updated to the latest version. You can check for updates by going to Help > Check for Updates within the application.

**Step 5:** Clean Up the TMX File

If you are importing a TMX file, consider cleaning it up by removing overly long translation units, as this can sometimes cause import failures.

**Step 6:** Test with a Simple Path

If your TM is located on a network drive, try copying it to your local C:\ drive and attempt the import from there. This can help avoid issues related to network paths.

If you continue to experience issues after trying these steps, please provide the exact error message and the version of Trados Studio you are using for further assistance.

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

Unable to update Trados TM

kushali varma — Wed, 21 Jan 2026 12:01:40 GMT

Hello team,

I have been trying to update my Trados TM with my SmartCat TM but I have not been able to as I got the below error message.

I am ahppy both my Trados and SmartCat TM (on email since the files are big and heavy) and would really appreciate if someone can guide me how this can be fixed.

Big thanks in advance.

How to use Azure openAI in Trados Studio 2024

Bettina Weinmann — Fri, 19 Sep 2025 12:20:10 GMT

Dear all,

does anybody know which Azure openAi option we can use to only do some minor tests regarding the integration of LLM/Azure in Trados 2024 and machine translation?

There are numerous options on the Azure price list (Azure OpenAI Service – Preise | Microsoft Azure, country Germany) and we don't know which is/are suitable.

Furthermore, is there anyboday who has already set up an Azure account and can quickly guide us through this process?

Thank you for your help!

Sabrina

RE: How to use Azure openAI in Trados Studio 2024

Sherefedin Mustafa — Thu, 01 Jan 2026 20:21:11 GMT

Dear All,

I would appreciate some input from colleagues who have this actually working in Trados Studio 2024 SR1.

I have followed the recommended setup exactly as described:

Azure OpenAI access enabled
Azure OpenAI resource created (West Europe)
Model deployed (gpt-4o-mini)
Endpoint and API key copied from the Azure OpenAI resource

However, in Trados Studio 2024 SR1 (18.1.3.x), the built-in OpenAI Provider for Trados only exposes a connection form with:

OpenAI-style model selection (gpt-3.5, gpt-5, etc.)
Mandatory Reasoning effort
Model type “Chat Completions (Reasoning)”
No field for Azure deployment name

As a result, Trados sends OpenAI-native parameters (e.g. reasoning_effort) that are not accepted by Azure OpenAI, leading to 400 errors such as “Unrecognised request: reasoning_effort”.

The documentation suggests that Azure OpenAI can be configured by entering Endpoint, API key and Deployment name, but that Azure-deployment-specific UI does not appear in my Studio 2024 SR1 installation.

My question to the community:
Has anyone successfully connected Azure OpenAI deployments (e.g. gpt-4o-mini) directly to Trados Studio 2024 SR1 using the built-in OpenAI Provider?
If so:

Which exact Studio build / plugin version are you using?
Do you see a deployment-based Azure OpenAI configuration screen (without reasoning parameters)?

Any confirmation, workaround, or clarification would be greatly appreciated.

RE: The AppStore contents -- app or plugin? (Not an important question)

Mats Linder — Tue, 04 Nov 2025 14:49:29 GMT

I just found the answer here:
https://docs.rws.com/en-US/trados-studio-2024-sr1-1187677/improved-rws-appstore-user-experience-1230546

I'll compare that with the AI reply and see if it makes me even wiser.

The AppStore contents -- app or plugin? (Not an important question)

Mats Linder — Tue, 04 Nov 2025 14:40:55 GMT

I have noticed that some providers call their product "plugin" while others use the term "app". Is there a real difference between the concepts, or is it just a question of preference?

RE: The AppStore contents -- app or plugin? (Not an important question)

RWS Community AI — Tue, 04 Nov 2025 14:41:19 GMT

Probability score: 0.6

Question improvement suggestion: Clarify whether you are looking for a technical distinction between "app" and "plugin" or if you are interested in the terminology used in the context of the RWS AppStore.

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

Hello!

The terms "app" and "plugin" can often be used interchangeably, but there are some distinctions that can be made based on context and functionality. Here’s a breakdown:

**Step 1: Definition**

- **App**: Generally refers to a standalone application that can perform a specific function or set of functions. In the context of the RWS AppStore, apps can enhance the functionality of Trados Studio or MultiTerm and may operate independently of the main software.

- **Plugin**: Typically refers to a component that adds specific features to an existing computer program. In this case, plugins are integrated into Trados Studio to extend its capabilities.

**Step 2: Usage in RWS AppStore**

- In the RWS AppStore, you will find both apps and plugins. Some developers may choose to label their products as "plugins" to emphasize their integration with Trados Studio, while others may use "apps" to highlight their standalone functionality.

**Step 3: Preference**

- Ultimately, the choice of terminology may come down to developer preference or marketing strategy rather than a strict technical difference. Both terms aim to convey that the product enhances the user experience in some way.

In summary, while there may be subtle differences in how "app" and "plugin" are perceived, they often serve similar purposes in the context of the RWS AppStore. 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

RE: Does the Antidote Verifier plugin support the new Antidote 12?

Patrick Arbaut — Sat, 04 Oct 2025 15:24:08 GMT

Hi Cylvie,

Thanks for getting back to me so quickly. I’ve just installed a trial version of Trados 2024 SR1 along with the Antidote Verifier 4.1 plugin. I can confirm it works perfectly with the latest version of Antidote 11. I opened an older project of about 2,000 words that included a few tags, made some edits, saved them, and returned to the Trados interface—no issues at all.

Thanks again!

Patrick

Does the Antidote Verifier plugin support the new Antidote 12?

Cylvie Frechette — Sun, 10 Nov 2024 15:56:50 GMT

Does the Antidote Verifier plugin support the new Antidote 12? I am using Studio 2021 SR2. I have already asked Druide, the makers of Antidote, but they are deferring to RWS for confirming the plugin compatibility, as Trados AppStore is the author of the plugin.

RE: Does the Antidote Verifier plugin support the new Antidote 12?

Cylvie Frechette — Tue, 30 Sep 2025 13:47:10 GMT

Hello Patrick,

As far as I am concerned, I am still running Antidote 11 with Studio 2024 and all is running well. I am awaiting a clear confirmation of version compatibility before installing Antidote 12.

Cylvie

RE: Does the Antidote Verifier plugin support the new Antidote 12?

Patrick Arbaut — Mon, 29 Sep 2025 14:27:39 GMT

Hello,

Any updates on the compatibility between Trados 2024 and Antidote? Oana’s last post was 10 months ago, and since then, Trados 2024 SR1 has been released. Is the issue limited to Antidote version 12?

I’m currently using Antidote 11 with Trados 2022, and everything works perfectly. I recently purchased Trados 2024 and came across this post. I’d prefer to keep using Antidote 11.

I understand that Druide’s website states Antidote 11 is only compatible with Trados 2022, while version 12 is supposed to work with Trados 2024—but that doesn’t seem to be the case.

So, is it possible to continue using Antidote 11 with Trados 2024 SR1? Is upgrading to Antidote 12 truly necessary, assuming it actually works?

I'd really appreciate any feedback from users who’ve tested Antidote 11 or 12 with Trados 2024 SR1.

Has anyone managed to get a stable integration? Any tips or workarounds would be welcome. Thanks in advance!

P.

RE: How to use Azure openAI in Trados Studio 2024

Patrick Andrew Hartnett — Fri, 26 Sep 2025 09:12:08 GMT

Hi Bettina Weinmann , I'll try help you as best I can, although I haven't setup this up in Azure, there is a lot of documentation around this from MS to help create minimal walk-through underneath.

Recommended models (balance of quality/speed/cost)

Default for testing and most production: gpt-4o-mini (OpenAI or Azure OpenAI). Lowest cost, very fast, strong translation quality.
When quality really matters: gpt-4o. Better handling of nuance/formatting; higher cost and slightly slower.
Not recommended for MT: o1/o3 (reasoning-focused, slow/expensive) and 3.5 family (older, weaker quality/formatting).

Useful Links

RWS AppStore (plugin + docs/screenshots): https://appstore.rws.com/ (search “OpenAI Provider”)
Azure OpenAI access: https://aka.ms/oai/access
Azure OpenAI model availability by region: https://learn.microsoft.com/azure/ai-services/openai/concepts/models
Azure OpenAI pricing: https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/
Data/privacy (Azure OpenAI): https://learn.microsoft.com/azure/ai-services/openai/overview#data-privacy

Quick Azure OpenAI setup (minimal-cost)

Access and subscription
- Ensure your Azure subscription has Azure OpenAI enabled (https://aka.ms/oai/access).
Create the resource
- Azure Portal > Create resource > Azure AI Services > Azure OpenAI.
- Choose an EU region that has your target model (often West Europe or North Europe; Germany regions may not have all models).
Deploy a model
- Go to Azure AI Foundry (https://ai.azure.com) or the resource in the Portal.
- Create a Deployment for gpt-4o-mini (or gpt-4o). Give it a short deployment name, e.g., gpt4o-mini.
Get connection details
- From the Azure OpenAI resource: copy Endpoint (looks like https://YOURRESOURCE.openai.azure.com), and one of the Keys.
- Note the API version your deployment supports (for chat/completions; a recent 2024 date is fine).

Configure the OpenAI Provider in Studio 2024

Install the OpenAI Provider from the RWS AppStore.
Studio > Project Settings > Language Pairs > Translation Memory and Automated Translation > Add > OpenAI Provider.
Choose a backend:
- OpenAI API: paste your OpenAI API key; Base URL https://api.openai.com/v1; Model gpt-4o-mini or gpt-4o.
- Azure OpenAI: select Azure; paste Endpoint (root URL only), API key, Deployment name (the one you created), and API version.
Suggested settings for translation:
- Temperature: 0.0–0.2 for consistent, non-creative output.
- Ensure “chat/completions” is used.
Put the provider near the top of your MT list so it’s queried during interactive translation and pre-translate.

RE: Updating plugin - developer form

Paul Filkin — Wed, 04 Jun 2025 08:31:35 GMT

Just to close off this thread. There is a wiki in the Developer community that clarifies the process: 06 Submitting apps for signing and/or publication

It's worth noting that this forum here is a user forum and not intended for developers. If you are a developer and have questions around development of plugins you should use the developer forums.

Updating plugin - developer form

Aleksandra Timofejeva — Mon, 19 May 2025 13:33:37 GMT

Hello!

I know that previously (and perhaps currently too), plugin signing was done via e-mail. Is that stil the case?

I have heard that there is a developer form to fill and attach plugin for signing, but it is beta access. If so, is it possible to get access to that form?

Thank you!

RE: Updating plugin - developer form

Aleksandra Timofejeva — Tue, 20 May 2025 09:42:41 GMT

Thank you a lot! :)

RE: Updating plugin - developer form

Oana Nagy — Tue, 20 May 2025 09:41:51 GMT

Aleksandra Timofejeva I will email you directly 🙂