1. Trados Studio - Recent Threads

RE: Mixed flat and hierarchical paths in JSON files with RWS built-in JSON file type

RWS Community AI — Fri, 17 Apr 2026 14:20:50 GMT

Probability score: 0.7

Question improvement suggestion: Provide specific examples of the flat JSON structure you are working with, including the exact key names and their expected values, to help clarify the extraction issue.

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

Hello,

To extract both flat and hierarchical JSON paths in Trados Studio 2024, you can follow these steps:

**Step 1:** Ensure that your JSON file is correctly formatted. Use an online JSON validator to check for any syntax errors.

**Step 2:** In Trados Studio, go to the file type settings for the RWS JSON file type. Under the 'Parser' section, navigate to 'String value extraction'.

**Step 3:** For the hierarchical JSON files, you can use the JSON paths you mentioned: `$..content`, `$..title`, `$..date`, and `$..key`. Make sure these paths are correctly set up in the extraction rules.

**Step 4:** For the flat JSON paths (e.g., `"buttons.next"`, `"titles.version"`), you can specify these paths directly in the extraction rules. Use the format `$['buttons.next']` to ensure that keys with dots are correctly interpreted.

**Step 5:** If you encounter issues with extraction, consider using a recursive search path like `$..element` to capture all instances of a specific element, or adjust your extraction rules to ensure that both flat and hierarchical elements are included.

**Step 6:** Test your settings with a sample JSON file to verify that both types of elements are being extracted correctly. If you still face challenges, please provide specific examples of the flat JSON structure you are working with, as this will help in diagnosing the issue more effectively.

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

Mixed flat and hierarchical paths in JSON files with RWS built-in JSON file type

Bernadette Haury — Fri, 17 Apr 2026 14:16:35 GMT

In Trados Studio 2024, the built‑in RWS JSON file type does not reliably extract flat JSON dictionaries where dots are part of the key name (e.g. "buttons.next").

Escaped JSON paths ($['buttons.next']) sometimes work, but wildcarding and consistent extraction are unreliable. There is no longer a regex‑based JSON file type or capture‑group support in Delimited Text Files to extract values only.

Is there a supported way in Studio 2024 to handle flat key‑value JSON dictionaries in the same project as hierarchical JSON, without preprocessing or manual key protection?

RE: Mixed flat and hierarchical paths in JSON files with RWS built-in JSON file type

Bernadette Haury — Fri, 17 Apr 2026 14:20:42 GMT

In 3 out of 4 files, I've got $..content, $..title, $..date and $..key elements I want to extract for translation, which I've set up in the JSON file type settings parser. The 4. file contains flat JSON paths only, which I need to translate all. Such as "buttons.next", "titles.version", etc.

RE: Mixed flat and hierarchical paths in JSON files with RWS built-in JSON file type

Bernadette Haury — Fri, 17 Apr 2026 14:19:27 GMT

RE: Mixed flat and hierarchical paths in JSON files with RWS built-in JSON file type

RWS Community AI — Fri, 17 Apr 2026 14:16:53 GMT

Probability score: 0.6

Question improvement suggestion: Provide specific examples of the JSON structure you are working with, including both flat and hierarchical elements, to help clarify the issue.

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

Hello,

To handle mixed flat and hierarchical JSON paths in Trados Studio 2024, you can follow these steps:

**Step 1:** Ensure that your JSON file is properly formatted. Use an online JSON validator to check for any syntax errors.

**Step 2:** In Trados Studio, navigate to the file type settings for the built-in RWS JSON file type. Here, you can define the extraction rules.

**Step 3:** For flat JSON dictionaries where keys contain dots (e.g., "buttons.next"), you can try using escaped JSON paths like `$['buttons.next']`. However, as you've noted, this may not always work reliably.

**Step 4:** If wildcarding and consistent extraction are problematic, consider using the JSON Path settings to specify rules for extracting values. You can use a recursive search path like `$..element` to capture all instances of a specific element.

**Step 5:** If you encounter issues with extraction, you may need to create a custom file type using the Regular Expression Delimited Text option. This allows for more flexibility in defining how to extract translatable text from your JSON files.

**Step 6:** Test your settings with a sample JSON file to ensure that both flat and hierarchical elements are being extracted correctly.

If you continue to experience difficulties, please provide specific examples of your JSON structure, as this will help in diagnosing the issue more effectively.

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: Failed to open .idml file >> the version is too new an not supported by Trados 2022

Jesús Prieto — Fri, 17 Apr 2026 06:28:49 GMT

Laura Spinelli

That's the second option, it works because you create a new project afterwards. Gglad it worked!

And you know that there is still a third option (editing a project template), depending on what you want to accomplish.

Failed to open .idml file >> the version is too new an not supported by Trados 2022

Nico D'Hert — Mon, 16 Jun 2025 06:57:36 GMT

I tried to open a .idml file and I got the following error : The selected file was created by a newer version which is not supported yet.(see printscreen her below)

How can i fix this ?

Is there an update from Trados coming soon ?

RE: Failed to open .idml file >> the version is too new an not supported by Trados 2022

Jesús Prieto — Fri, 17 Apr 2026 06:23:05 GMT

Laura Spinelli

[quote userid="210644" url="~/product-groups/trados-portfolio/trados-studio/f/studio/58093/failed-to-open-idml-file-the-version-is-too-new-an-not-supported-by-trados-2022/192995"]In Project Settings and then started creating the new project[/quote]

If you did it in Project Settings and created a new project, then the setting is not in the new project. Could you please check? I'd do it in Project Settings and then re-add the IDML file to the same project.

RE: Failed to open .idml file >> the version is too new an not supported by Trados 2022

Laura Spinelli — Fri, 17 Apr 2026 06:22:00 GMT

I tried the File>Option way and it worked! Thank you very much for your support! Have a nice day

RE: Failed to open .idml file >> the version is too new an not supported by Trados 2022

Laura Spinelli — Fri, 17 Apr 2026 06:18:53 GMT

Thank you Jesús! In Project Settings and then started creating the new project. Is there a workaround?

RE: Failed to open .idml file >> the version is too new an not supported by Trados 2022

Jesús Prieto — Fri, 17 Apr 2026 06:11:29 GMT

Laura Spinelli

Where did you tick the Process unsupported file versions checkbox?

In File > Options? This will only kick in the next time you create a project using the default template.
In Project Settings? This will apply only to the actual project.
In a project template? This will only kick in the next time you create a project using this template.

RE: Analyze Files not updating properly in Studio 2024 SR1

RWS Community AI — Fri, 17 Apr 2026 01:31:56 GMT

Probability score: 0.6

Question improvement suggestion: Provide specific details about any error messages encountered and clarify if any troubleshooting steps have already been attempted.

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

Hello,

It seems you're experiencing issues with the Analyze Files function in Trados Studio 2024 SR1 not reflecting your translation progress accurately. Here are some steps you can take to troubleshoot and potentially resolve the issue:

**Step 1:** Ensure that your Translation Memory (TM) is properly connected to your project. Go to **Project Settings > Language Pairs > All Language Pairs > Translation Memory and Automated Translation** to verify this.

**Step 2:** Check that the Analyze Files batch task is enabled. Navigate to **Project Settings > Language Pairs > All Language Pairs > Batch Processing** and ensure that the Analyze Files option is checked.

**Step 3:** Run the Analyze Files batch task again. Right-click on your file in the Files view and select **Batch Tasks > Analyze Files**.

**Step 4:** If the issue persists, try running the following batch tasks in order:

- **Word Count**

- **Translation Count**

- **Analyze Files**

**Step 5:** Consider creating a new project with the same settings to see if the issue replicates there.

**Step 6:** Ensure that your Trados Studio software is up-to-date, as updates often include bug fixes that could resolve your issue.

If none of these steps resolve the problem, please provide any error messages you may have encountered and detail any troubleshooting steps you've already taken. This information will help in diagnosing the issue further.

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

Analyze Files not updating properly in Studio 2024 SR1

Tania Martins — Fri, 17 Apr 2026 01:31:38 GMT

Hello,

I am using Trados Studio 2024 SR1 (18.1.3.6657) and I am seeing strange behavior with Analyze Files.

I have a project with 3 files:

2 files are already translated 100%
1 file is still in progress

When I run Analyze Files, the statistics do not seem to update according to my translation progress.

Example:

the 2 completed files still show a lot of no match / non-100% content
the third file keeps showing the same analysis figures even after I translate and review many more segments
for example, it still shows 3034 new / no match words

Additional info:

TM update is enabled
segments are translated and confirmed normally
Translation Count reflects progress better, but Analyze Files does not

In previous Studio versions, Analyze Files seemed to update more accurately as I progressed.

Has anyone else seen this in Studio 2024 SR1?
Any workaround or known explanation?

Thank you.

Request to Change Default Logic for Advanced Display Filter 2.0 (AND to OR)

Youngrok Kim — Thu, 16 Apr 2026 22:50:32 GMT

In Trados Studio's Advanced Display Filter 2.0, the source and target input fields on the Content tab have an AND relationship by default. However, the purpose of using this filter is to identify cases where the source and target expressions are incorrect. Therefore, please change the default setting to OR instead of AND.

RE: Request to Change Default Logic for Advanced Display Filter 2.0 (AND to OR)

RWS Community AI — Thu, 16 Apr 2026 22:50:58 GMT

Probability score: 0.6

Question improvement suggestion: Provide specific examples of how the current AND logic affects your workflow and what specific scenarios would benefit from changing it to OR.

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

Hello,

Thank you for your suggestion regarding the Advanced Display Filter 2.0 in Trados Studio. Changing the default logic from AND to OR could indeed enhance the usability of the filter for identifying incorrect source and target expressions. Here’s a step-by-step approach to how you might present this request to the development team:

Step 1: **Clarify the Purpose**

Explain that the primary goal of the Advanced Display Filter is to identify discrepancies between source and target segments. Highlight that an OR relationship would allow users to see segments where either the source or target expression is incorrect, which is crucial for quality assurance.

Step 2: **Provide Use Cases**

Include specific examples of scenarios where the current AND logic limits your ability to effectively identify issues. For instance, if you are looking for segments where the source contains a specific term but the target does not, the AND logic would exclude these segments from the results.

Step 3: **Suggest the Change**

Propose that the default setting be changed to OR, while still allowing users the option to select AND if they prefer that logic for specific cases. This flexibility would cater to different user needs and enhance the overall functionality of the filter.

Step 4: **Encourage Feedback**

Invite other users to share their experiences and thoughts on this change, which could strengthen the case for the request.

By presenting your suggestion in this structured manner, you can effectively communicate the benefits of changing the default logic in the Advanced Display Filter.

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: Failed to open .idml file >> the version is too new an not supported by Trados 2022

Laura Spinelli — Thu, 16 Apr 2026 18:03:49 GMT

Dear all, I work with Trados 2024 SR1, the box to ignore the unsupported versions is selected. Is there another solution?

RE: I DELETED MY OLD DEEPL TRANSLATION PROVIDER, AND I CAN NO LONGER INSERT THE NEW DEEPL TRANSLATION PROVIDER PLUGIN. WHY? I USE TRADOS STUDIO 2019

Ana Sabo — Thu, 16 Apr 2026 15:44:11 GMT

HiCristiana Cocco

From 28 February 2026, DeepL discontinued support for outdated authentication methods used by older versions of CAT tools. For further details, please see: https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods

The Trados AppStore Team implemented support for the new authentication methods from DeepL starting from Trados Studio 2022 (i.e. Trados Studio 2022, 2024 & 2026 ...). This means that the DeepL Translation Provider will no longer work in Trados Studio 2021 and earlier versions: - DeepL plug-in no longer working in Trados Studio since the support for outdated authentication methods was discontinued by DeepL - RWS Customer Support

Kind regards,

I DELETED MY OLD DEEPL TRANSLATION PROVIDER, AND I CAN NO LONGER INSERT THE NEW DEEPL TRANSLATION PROVIDER PLUGIN. WHY? I USE TRADOS STUDIO 2019

Cristiana Cocco — Thu, 16 Apr 2026 12:27:19 GMT

Cannot open Powerpoint file with embedded Excel files

Martha Fillastre — Thu, 16 Apr 2026 08:02:02 GMT

I'm trying to create a project with a Powerpoint file containing embedded Excel files. I'm using Studio 2024 and the file cannot be converted. I get an out-of-memory error. It is a big file (145 kb). Any help with this?
Thanks in advance

Martha

RE: Cannot open Powerpoint file with embedded Excel files

RWS Community AI — Thu, 16 Apr 2026 08:02:21 GMT

Probability score: 0.7

Question improvement suggestion: Provide the exact error message you are receiving, as well as the operating system 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 Martha,

It sounds like you're encountering an out-of-memory error when trying to open a PowerPoint file with embedded Excel files in Trados Studio 2024. Here are some steps you can take to resolve this issue:

**Step 1:** Open Trados Studio and navigate to `File > Options > File Types`.

**Step 2:** Select `Microsoft PowerPoint 2007-2016` and go to the `Common` section.

**Step 3:** Disable the option for `Embedded Excel charts and sheets`. Click `OK` to save your changes.

**Step 4:** Try to recreate your project in Trados Studio with the modified settings.

If the issue persists, consider the following workaround:

**Step 5:** Open the PPTX file in Microsoft PowerPoint (preferably 2013 or later).

**Step 6:** Go through each slide that contains embedded Excel spreadsheets. Double-click on each spreadsheet and make a minor change (like adding and removing a space in a cell).

**Step 7:** Save the PowerPoint file after making these changes.

**Step 8:** Now, try opening the modified PPTX file in Trados Studio again.

This process should help extract the content of the embedded Excel files for translation. If you continue to experience issues, it may be beneficial to reduce the file size by splitting it into smaller parts or simplifying its content.

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: "Undo" option not working in Studio 2019

Jesús Prieto — Thu, 16 Apr 2026 07:47:51 GMT

Sorina Cuibus

I've experienced this as well. No specific steps, it just happens after using Trados Studio for a while, in my case it doesn't happen every day, not even every week. When Undo stops working, restarting Trados Studio solves the issue.

"Undo" option not working in Studio 2019

Katarzyna Müller — Mon, 18 Mar 2019 17:12:29 GMT

I upgraded to 2019 form 2014, ever since the "undo" option is greyed out and ctrl+Z does not work. I found a solution on a forum, which is resetting the settings to default, but this solution is only temporary, I need to repeat it for each new file! So if I want to use "undo" option I have to set up my working space from scratch every single time. This is very annoying and I know other users are struggling with other basic shortcuts too, such as Ctrl+V. Is SDL going to patch this bug?

RE: "Undo" option not working in Studio 2019

Sorina Cuibus — Thu, 16 Apr 2026 06:18:22 GMT

Fredrik Nylund Thank you for your feedback

In case you still encounter this, please post this separately for better visibility.

It would be helpful also for the development team, if you have specific steps to reproduce or if you can mention the actions performed before you encounter this.

Thank you

Regards,

Sorina

RE: Trados Studio 2021 cannot open a package (..xliff.wsxz file)

Fabienne Mardon — Tue, 14 Apr 2026 16:33:30 GMT

I have just installed TradosStudio2021_SR2_CU12_9338

And now it works..but still my versions of Trados (laptop and desktop) do not connect to the Internet... it has never worked so
I have to check for updates manually....

Trados Studio 2021 cannot open a package (..xliff.wsxz file)

TOSHIAKI IZUMI — Mon, 16 Jun 2025 06:44:02 GMT

As I need to move from my old PC (Win10) to a new PC (Win11), I installed Trados Studio 2021 to the Win11 machine.

I deactivated Trados on the Win10 machine, and activated Trados on the Win11 machine.

As far as I opened previous projects, I did not have any problem.

However, I could not open the package that I exported from World Server.

The downloaded package seems not to be linked to Trados Studio as seen with a blank icon (instead of Trados Studio icon) on top (see attached).

When I open the package so as to be associated with Trados Studio, Trados Studio opens but the project is not embedded.

Would you please let me know how I can fix this problem.