https://community.rws.com/product-groups/trados-portfolio/trados-studio/Any any question in here related to working with Trados Studio, MultiTerm or Machine Translation within Trados Studio. This is also a great place to discuss subtitling, working with regular expressions, XPath and AutoHotKey.en-USTelligent Community 12 Non-Productionhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60917/mixed-flat-and-hierarchical-paths-in-json-files-with-rws-built-in-json-file-type/193021Fri, 17 Apr 2026 14:20:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:489c2cd8-71aa-418f-b567-8bd58443a879RWS Community AIProbability 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 AIhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60917/mixed-flat-and-hierarchical-paths-in-json-files-with-rws-built-in-json-file-type/193020Fri, 17 Apr 2026 14:20:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e3afb119-d7cb-4a9f-ac47-031f5e7008d9Bernadette HauryIn 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.https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60917/mixed-flat-and-hierarchical-paths-in-json-files-with-rws-built-in-json-file-type/193019Fri, 17 Apr 2026 14:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:112e3a78-bda7-49b9-955e-1755ec101266Bernadette HauryIn 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.https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60917/mixed-flat-and-hierarchical-paths-in-json-files-with-rws-built-in-json-file-typeFri, 17 Apr 2026 14:16:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:864dc274-1ed6-4d03-9a59-d92917b33478Bernadette HauryIn 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?https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60917/mixed-flat-and-hierarchical-paths-in-json-files-with-rws-built-in-json-file-type/193018Fri, 17 Apr 2026 14:16:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f7c91ced-9921-41a9-9065-a7fbbc1b0d2dRWS Community AIProbability 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 AIhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/multiterm/56801/multiterm-glossary-does-not-show-terms-after-windows-update-trados-studio-2022-sr2---17-2-11-19134/193017Fri, 17 Apr 2026 13:43:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f9b27771-6828-45b0-839e-5efb9eb1be88Steve RawcliffeGreat that this worked for you! Just for anyone else stumbling across this thread ... what worked for me was View > Reset window layout . No idea why, but it did!https://community.rws.com/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/192998Fri, 17 Apr 2026 06:28:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:aa3605e1-d4d7-46a2-91a7-6b5725620987Jesús PrietoLaura 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.https://community.rws.com/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/192997Fri, 17 Apr 2026 06:23:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c1b40b58-86b3-4d57-b109-487694034d19Jesús PrietoLaura 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.https://community.rws.com/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/192996Fri, 17 Apr 2026 06:22:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e7f020bf-a1cb-482d-b795-edd782388e0bLaura SpinelliI tried the File>Option way and it worked! Thank you very much for your support! Have a nice dayhttps://community.rws.com/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/192995Fri, 17 Apr 2026 06:18:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:19028b72-0d69-409c-94ba-e882ec52b4e1Laura SpinelliThank you Jesús! In Project Settings and then started creating the new project. Is there a workaround?https://community.rws.com/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/192994Fri, 17 Apr 2026 06:11:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:a9613605-8a9f-4388-b525-da86f4196defJesús PrietoLaura 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.https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/multiterm/60907/failed-to-initalize-view-multiterm-studio-editorview/192993Fri, 17 Apr 2026 02:51:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:a8f000bc-13d7-403d-abfd-eca7f5fa6f5eSofía GalliI solved it by following these steps, if anyone else encounters this problem: gateway.rws.com/csmhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60910/analyze-files-not-updating-properly-in-studio-2024-sr1Fri, 17 Apr 2026 01:31:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:75af4e63-3eba-4d86-80c5-025310c073c8Tania MartinsHello, 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.https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60910/analyze-files-not-updating-properly-in-studio-2024-sr1/192992Fri, 17 Apr 2026 01:31:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:d6ed1783-bc19-4cb8-b095-cb9a507b1169RWS Community AIProbability 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 AIhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60908/request-to-change-default-logic-for-advanced-display-filter-2-0-and-to-orThu, 16 Apr 2026 22:50:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:9d72d5a0-da7b-466b-905e-497ce3bbca60Youngrok KimIn 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.Contents tapAdvanced Display Filter 2.0ANDORhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60908/request-to-change-default-logic-for-advanced-display-filter-2-0-and-to-or/192991Thu, 16 Apr 2026 22:50:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ce2e23d0-7d9a-4479-b103-271824f4999cRWS Community AIProbability 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 AIhttps://community.rws.com/product-groups/trados-portfolio/trados-studio/f/multiterm/60907/failed-to-initalize-view-multiterm-studio-editorviewThu, 16 Apr 2026 18:21:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:623ba934-c515-42be-bc92-aba7632e11aaSofía GalliHi! I have a problem launching MultiTerm 2024. I've tried everything that has been suggested in the forum: - Changing the name to 'Multiterm18_old'. - Uninstalling and installing the program several times. - Changing the name of the file coresettings.xml to settings.xml - Running the program as an administrator. - Repairing the program in the Uninstall programs folder. - Changing the location of the folder when installing it. - And adding the program to my antivirus whitelist. Before Multiterm crushed, I tried adding some functions from Create Ribbons, I think it's called. I added them in the Termbases sections and, when I closed the program, it stopped working. I don't know what else to do to launch the program and have access to the dashboard. Could you help me with a new unthought solution? Thank you!MultiTerm 2024https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/multiterm/60907/failed-to-initalize-view-multiterm-studio-editorview/192990Thu, 16 Apr 2026 18:21:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:41621b27-2caf-41e1-892f-ab0cee645b9fRWS Community AIProbability score: 0.8 Question improvement suggestion: Provide the exact version of MultiTerm you are using and any specific error messages you encounter when trying to launch the application. In the meantime, based on the information you have provided, here is a suggested answer to your question: Hello! It sounds like you've already taken several thorough steps to troubleshoot the issue with MultiTerm 2024. Here’s a structured approach to try and resolve the problem further: **Step 1:** Ensure all RWS applications are closed, including any background processes related to MultiTerm. **Step 2:** Navigate to the following folder on your computer: `C:\Users\Your User Name\App Data\Roaming\Trados\Multi Term` (Replace "Your User Name" with your actual Windows username.) **Step 3:** Rename the folder corresponding to your MultiTerm version (e.g., "Multi Term17" for MultiTerm 2022) to something like "Multi Term17_old". **Step 4:** Check for any XML files in that folder, particularly `Settings.xml`, `Base Settings.xml`, `Plugincache.xml`, and `User Settings.xml`. Rename these files by adding "_OLD" to their names. **Step 5:** Restart your computer to ensure all changes take effect. **Step 6:** Launch MultiTerm again, preferably using "Run as Administrator" by right-clicking the application icon. **Step 7:** If the issue persists, consider reinstalling MultiTerm. Uninstall it via Control Panel, restart your computer, and then reinstall the latest version from the RWS website. **Step 8:** If you recently added functions from Create Ribbons, it might be worth resetting any custom settings or checking if those changes are causing the issue. If these steps do not resolve the problem, please provide any specific error messages you encounter, as this 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 AIhttps://community.rws.com/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/192989Thu, 16 Apr 2026 18:03:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c799d679-155d-4963-bfde-9eb2187992f5Laura SpinelliDear all, I work with Trados 2024 SR1, the box to ignore the unsupported versions is selected. Is there another solution?https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/60903/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/192985Thu, 16 Apr 2026 15:44:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:1836de61-962f-4fa0-9996-5bf8b550a4bfAna SaboHi Cristiana 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,