We are constantly reviewing and improving our products. We release enhancements and fixes to resolve customer issues as and when required. This article lists the enhancements and fixes for Trados Studio 2024 to date. Hotfixes are bundled into service releases or cumulative update patches that are installed automatically using the AutoUpdate functionality in Trados Studio.

Downloading and Installing Cumulative Updates
A cumulative update is usually applied when you use the AutoUpdate functionality available in Trados Studio. Follow the on-screen instructions to download and apply the update. RWS recommends that you use AutoUpdate.

 

NOTE: Applying the update may take some time, as the Trados Studio installation fully replaces the previously installed version. As a rule of thumb, applying the update will take roughly the same time as installing the application originally. However, you can also apply the patch manually, as follows:

1. Close Trados Studio 2024.
2. Download the ZIP file TradosStudio2024_CU2_3255.zip from our Download Center. It will typically be placed into the Downloads folder on your machine by your browser.
3. The ZIP file contains an .exe file. Extract this file to a temporary folder of your choice, such as C:\temp. This .exe file applies to all editions of Trados Studio 2024.
4. Double-click the .exe file. This will install the latest release and replace as well as update the files in the Trados Studio 2024 installation folder as appropriate.

After the update release has been installed and Trados Studio or your PC restarted, the issues described in this article should no longer occur.

Cumulative Update 2 for Trados Studio 2024 (Build 18.0.2.3255, Released on 5th of February, 2024)

Enhancements

Added support for long file paths and names

Studio now supports working with projects and packages that have file paths and names over 190 characters. To benefit from this change, you must be running Windows 10 version 1607 or later. This change applies to local, cloud, and GroupShare project and package types - but not WorldServer. Support for long paths in WorldServer projects is planned for a future update.

Added option to include Verify Reports in return packages

When creating a return package with Include Verify Reports enabled, Trados Studio will now include a Verify Files report in two ways: for projects where User must run verification before returning the package is enabled, Studio automatically runs a new verification and includes that report. For all other projects, it includes the most recent Verify Files report for the selected files.

Aligned Linguistic Review outcome names between Trados Studio and the Online Editor 

We’ve standardised the Linguistic Review task outcome names in Trados Studio to match the Online Editor, replacing Accepted and Rejected with Approved and Request Corrections for better consistency across the Trados platform.

Accessibility improvements 

Building on the accessibility enhancements introduced in the 2024 release with UIA integration and further refined in CU1, this update brings a suite of new improvements that make Trados Studio even more inclusive and user-friendly. Roundtripping projects using the Manager view for project management, and Editor view for editing translations will now be more streamlined.

Enhanced Manager View experience

• Better keyboard navigation between files and projects

• Enhanced narrations for menus, buttons, and status updates

• Screen readers now read disabled button states and correctly identify menu elements

• After creating a new project, keyboard selection remains in the expected location

Streamlined project creation

• Screen readers provide clearer guidance when adding files and selecting languages for a new project

• Improved focus retention during project setup

Editor refinements

• Screen readers now read segment status in the Translation Results window and when moving between source and target text

• Improved accessibility across translation memory and concordance features

Stability and performance

• Resolved screen reader compatibility issues

• Fixed focus and selection behavior with single-file projects

• Enhanced overall stability when using assistive technologies

Added support for multi-region deployment

Following our recent launch of the Canadian instance of the Trados Cloud platform, we've expanded Trados Studio's cloud capabilities to include support for the new Canada region alongside our existing European infrastructure. This means that Canadian organizations can now better meet their data residency requirements, while all users in the region will benefit from improved performance through local infrastructure.

Studio automatically detects your region settings from your Trados Cloud account (Europe or Canada) with no additional configuration needed. Your content remains in your chosen region unless explicitly allowed otherwise. You need separate cloud accounts to access different regions - one account cannot access by design both European and Canadian regions simultaneously.

To get started with the Canadian region, contact your account manager.

AppStore plugin updates

The AppStore includes significant improvements to two essential plugins for Trados Studio 2024:

AI Assistant has been updated to version 1.1.6.2, introducing enhanced terminology-matching capabilities. Previously limited to 100% matches, the app now incorporates fuzzy terminology matches based on the project's minimum match threshold settings for more flexible and accurate terminology usage in AI prompts.

Alongside this, the Language Weaver Provide provider has been upgraded to version 2.0.4.0, featuring improved compatibility for Project Automation when working with both Language Weaver Edge and Language Weaver Cloud environments.

For your convenience, the apps come updated in CU2. Check future updates using the built-in AppStore functionality. Trados and third-party developers are constantly adding new Trados Studio apps to our AppStore. To discover all new additions and updates, sort by Newly added in Studio’s integrated AppStore or use the Product version filter on the website version of the AppStore.

 

Fixed issues

• Trados Studio now automatically inserts non-breaking spaces before and after chevrons used as quotation marks in French (Switzerland) projects, aligning its behavior with the French (France) sublanguage. (CRQ-39374)

• Fixed an issue where downloading files from cloud projects caused the Files view navigation pane to reset to the main project folder, instead of retaining the previously selected folder. (LG-43202)

• Fixed the Failed to create setting page error that occurred when accessing Translation Memory and Automated Translation settings under Project Settings and other locations. (LG-45868, LG-45908)

• The No Markup display setting in Review mode no longer resets after accessing General Settings. (LG-45960)

• Fixed an issue where a 'Collection was modified' error message would incorrectly display when switching from Editor to Projects/Files view. (LG-46766)

• Fixed an issue where users with limited permissions could previously check out, translate and download files from Groupshare projects while having Restrict file downloads for this project option enabled. (LG-45299)

• Fixed an issue that caused incorrect term language mapping in the Termbase Viewer, affecting multilingual projects with similar language variants like Serbian (Cyrillic, Serbia) and Serbian (Latin, Montenegro). (LG-46270)

• Fixed an issue that caused Trados Studio to crash when translating a single document. The Translation Memory and Document Settings window now works correctly and displays as expected. (LG-45905)

• Fixed an issue that occurred when deleting content using Del or Backspace after the content was removed from the TU, throwing an Object reference not set to an instance of an object error. The editor now properly handles deletion commands when no content remains. (LG-31169)

• Fixed an issue where JAWS was not reading the full context of Translation Results. Now, JAWS will read both the segment number and segment status. (LG-45224)

• Fixed an issue where the Edit TQA button in the Review ribbon remained disabled when modifying existing Translation Quality Assessment (TQA) entries. (LPB-6629)

• Cloud projects with Bilingual Engineering tasks no longer display a ‘Key not present in the dictionary’ error after task completion and file upload. This resolves the workflow interruption in projects created from the Translation & Review workflow template. (LG-45946)

• Fixed a terminology matching limitation that previously restricted terminology suggestions to 100% matches only in AI Assistant. This fix enabled the new enhanced terminology capabilities now available in AI Assistant 1.1.6.1, which incorporates fuzzy terminology matches based on project threshold settings. (CRQ-40545)

• Trados Studio now handles missing namespaces in custom XML2 file-type filters more effectively by displaying appropriate warnings in the Create File Type wizard. Previously, a resource error was shown, preventing you from addressing the issue while creating custom XML file types. (CRQ-40344)

• Fixed ‘Value cannot be null’ error that occurred when adding or editing segmentation rules in the Translation Memory Settings window. (CRQ-40166)

• Fixed an issue where projects failed to properly assign users during creation when phase names were modified in the Trados GroupShare Console. Previously, this resulted in an ‘Internal Server Error’ and defaulted all assignments to the project creator. (CRQ-39921)

• Fixed an issue in the Project Automation API where HTML files could not be processed due to a dependency version mismatch, resulting in null FileTypeId values after scanning. Previously, this prevented HTML files from being properly processed in automated workflows. (CRQ-39749)

• Fixed an issue where term verification would cause excessive memory consumption leading to a 'System Out of Memory' exception. The fix improves memory management during verification processes, ensuring stable performance even with large projects. (CRQ-39491)

• Fixed an issue where bookmarks in virtually merged files would navigate to incorrect segments based on file opening order. Bookmarks now correctly navigate to their intended locations regardless of how files are opened or merged. (CRQ-39367)

• Parser rules and detection settings would be lost when creating multiple XML2 file type filters consecutively from .sdlftsettings files. Settings now persist correctly when creating new filters, even after closing and reopening the Options window. (CRQ-39035)

• Fixed an issue where the Terminology Verifier was generating false positives for Indian languages, incorrectly flagging correctly translated terms as missing. The fix improves term recognition accuracy across Indian language scripts, particularly for Odia and similar writing systems. (CRQ-38942)

• Users without Write TM permission would receive ‘One or more errors occurred’ messages when retrieving matches from server-based translation memories in the Editor. This issue is now fixed. (CRQ-37235)

• The QA Checker would not flag segments as untranslated when the target text was removed using tracked changes. This issue is now fixed, and the verifier now properly identifies such segments as missing translations when source text is present. (CRQ-37220)

• Fixed an issue where PowerPoint notes weren't being translated when generating target files from cloud .sdlxliff files, even when notes translation was enabled in the cloud project settings. Target files now correctly include translated notes content. (CRQ-36707)

• Trados Studio would fail to import cloud packages containing termbases with special characters (such as ampersands) in their names. This is now fixed to ensure proper handling of special characters in termbase names during package import. (CRQ-36054)

• Trados Studio would fail to connect to GroupShare servers using custom ports if the server URL was entered without the protocol prefix (http:// or https://). This is now fixed to ensure that server addresses with custom ports are handled without requiring manual protocol specification. (CRQ-35862)

• Fixed an issue where Copy, Cut and Paste options in the context menu would become disabled after navigating to segments using the Comments pane. These editing options now remain active regardless of how segments are accessed. (CRQ-35594)

• Fixed an issue where missing placeholder tags were only detected during verification when the Check for tag ID mismatch option was enabled. Tag verification now properly identifies missing placeholder tags regardless of tag ID mismatch settings. (CRQ-35397)

• Manual generation and inclusion of verification reports in return packages was causing workflow inefficiencies for freelance translators and project managers. This issue has been resolved through the implementation of automatic verification report handling, as described in the Added option to include Verify Reports in return packages enhancement above. (CRQ-27920)

• Added the ability to control Search both project and main translation memories setting through the Project Automation API's TranslationMemorySettings class. This enhancement provides API access to all TM search configuration options. (CRQ-35266)

• Fixed an issue where users with capitalized letters in their Windows domain usernames were unable to change phases in server-based projects, despite having the Change Current Phase permission. (CRQ-4531)

File Types and core components enhancements 

• We updated the Aspose.PDF and Sautin versions to the newer available versions, namely Aspose.PDF for .NET 24.9 and Sautin 2024.9.26. (LCC-19208, LCC-19207)

• Fixed an issue where .exe and .dll files could not be processed using the .NET Libraries filter due to a missing assembly dependency. These files can now be opened for translation using the default filter settings. (CRQ-39240)

• To optimize the size of PowerPoint files during the generation of HTML previews, we eliminated embedded videos and cropped images from the original PowerPoint presentations. (LCC-19149, LCC-18864)

• We fixed the behavior for handling the preview of files with empty segments in Microsoft Office package via FPS 5.4.27. (LCC-18894)

• The Spanish (Latin America) language option has been removed from the available resources for project creation, as it was previously deprecated. (LCC-18420)

• Fixed XML attribute parsing error in XML 2.0 filetype when handling double quotes inside single-quoted attributes. (CRQ- 39896)

• Custom XML entities are now preserved as non-translatable placeholders in XML 2.0, preventing corruption during target file generation. (CRQ-39514)

• PowerPoint preview now displays Asian characters correctly in grouped text boxes instead of showing blank squares. (CRQ-38628)

• Java Properties files now correctly show Asian characters in target files without requiring BOM in source files. (CRQ- 37601)

• Excel no longer extracts data validation messages from hidden cells for translation.(CRQ- 36504)

• DOCX files with custom fields now generate correctly for RTL languages without file generation errors. (CRQ- 36437)

• Custom currency pair TEUR now correctly auto-localizes to EUR in target languages. (CRQ- 34697)

• "Save Target As" now works correctly for PowerPoint files without showing errors in rare cases. (CRQ- 34636)

• We added the Haitian Creole (Haiti) custom language to our list of supported languages. (CRQ- 31593)

• The Excel file type now lets you choose whether to extract data validation messages while still translating cell content. (CRQ- 27334)

Known issues

• When creating projects via the Public API, email files (.msg, .eml) are not recognized as translatable formats because the Email file type is not currently working correctly in this context. For projects that include email files, make sure to use the user interface until this issue is resolved.

• As previously mentioned, support for long file paths and names does not work for WorldServer projects and packages. This will be addressed in a future update.

Cumulative Update 1 for Trados Studio 2024 (Build 18.0.1.2259, Released on 10th of October, 2024)

Enhancements

Changes to accessing shared cloud resources with a subscription license

Previously, when using a subscription license, you couldn’t select another cloud account for doing translation work and use its resources. You might have seen that you activated a subscription license but it wasn’t possible to select a different cloud account. Now, with the new mechanism you can freely select other accounts where you have been assigned translation work. (LPB-6171)

Improved term recognition for higher efficiency

We have introduced an option to make term recognition distinguish all upper-case terms from other casing. This will allow you to switch on case-sensitive term recognition and filter out unwanted results, making it easier, for example, to recognize acronyms such as CAT vs. cat. (CRQ-35146)

Expanded Bookmarks view for improved visibility

In response to your feedback, we've enhanced the default Bookmarks view in the editor. Previously, the view was very narrow, showing only one bookmark at a time. Now, the default view has been expanded to display multiple bookmarks (up to 5) without requiring manual resizing.

Batch completion of cloud tasks

We’ve added the ability to mark multiple cloud files (referred to as tasks in our cloud platform) for completion, which will save you significant time compared to selecting each file separately. By design, the Complete Task action will be available if all of the selected tasks are of the same type - typically translation or review.

Enhanced Find & Replace functionality

We’ve enhanced the Find & Replace feature in Studio with a new feedback prompt.
When you perform a Replace All operation, you will see a pop-up message that will inform you of the number of replacements made during the operation. If you're familiar with Microsoft Word, you'll recognize this behavior—it's similar to Word's Replace All functionality. We have implemented this feature based on community feedback.

File-based terminology improvements 

We're continuously working in our ongoing effort to improve Studio's terminology management capabilities. In this update, we’ve made progress in providing key terminology features in Studio, focusing on file-based terminology:

• When you create a file-based termbase you can now select the location where you want to save it, removing the previous limitation of a fixed default path.
• You can now use an existing file-based termbase as a template instead of server-based when choosing Use an existing termbase as a template option.

Added support for custom file types from cloud projects

We have added support for custom file types from cloud projects allowing Studio to retrieve file type settings and project details from the cloud. The filetype settings are now synced in real-time with the changes online and set to read-only in Studio.

Option to show or exclude synonym terms in Term Recognition

We have added a new search option in the termbase search settings called Display synonyms separately in the Term Recognition view. When this option is selected, synonym terms will appear separately in term recognition view. This option is not activated by default. A synonym refers to multiple terms defined on the same language within the same entry, and therefore sharing the same entry ID in the termbase.

Color coding for Translation Quality Estimation (TQE) results for projects that come through GroupShare

We’ve added full color coding support for TQE results when opening projects from GroupShare in Studio. The behavior is identical to the one for cloud projects, thus ensuring that your TQE results will now display properly and be color coded as expected.

Manager view improvements

Project Files grid in the Manager View is now resizable

We've changed how the Project Files grid in the Manager view behaves in order to make sure that it automatically resizes whenever the Studio window is resized. This change ensures that all columns of the Project Files grid can be accessed or scrolled to whenever the Studio window is resized.

Improved drag-and-drop functionality

We've refined the drag-and-drop functionality by aligning Trados Studio's behavior with familiar Windows interactions.

• .sdlproj files: Dragging and dropping such files onto the Manager view now automatically opens and activates the project, instantly listing its files. This mirrors the experience of double-clicking an .sdlproj file in File Explorer.

• .sdlppx files: Dropping an .sdlppx file now launches the Open Package wizard, consistent with double-clicking the file in File Explorer.

Folder structure pane

We added a new folder structure pane to the Manager view that visualises the project's language and folder structure. In this release, this panel is read-only. In future releases, we will add more options and navigation capabilities.

Manager view settings persist

We've added the ability to keep any changes you make to the Manager view's interface when closing Studio. This ensures that you won't have to modify the interface to your liking every time you open Studio.

Create single-file projects from the Manager view

We've improved the projects list functionality in order to give you the ability to create single-file projects directly in the Manager view. You can do this by dragging-and-dropping your file in the projects list section, and then creating the project in the window that appears.

Accessibility improvements

We have made significant improvements to accessibility within the Manager view to ensure a smoother and more inclusive experience for all users. The following areas have been enhanced:

• All tabs are now fully navigable using the Tab key.
• You receive clear feedback when a tab is opened.
• Screen readers are now able to read relevant information, such as tab titles, drop-down values, and table headers.
• Focus is placed appropriately on elements within the tabs, making navigation more intuitive.
• Unnecessary information is no longer read aloud, improving the user experience.
• Access to statistics charts has been removed to simplify the interface.
• Drop-down menus are now more accessible to screen reader users, with appropriate announcements and information.
• We improved tables to provide clear information about their structure and content.
• The focus remains on the appropriate element after actions are performed, preventing unexpected navigation.

Improved keyboard-only support

We've added several keyboard shortcuts in Manager view to improve your ability to use Studio with their keyboard only. You can find a list of functions and their shortcuts below:

• Open the Project burger menu: Ctrl + Shift + F10
• Open the Context menu: Shift + F10
• Create a new local project: Ctrl + N
• Create a new cloud project: Ctrl + Alt + N
• Open a project: Ctrl + O
• Open a GroupShare project: Ctrl + Alt + G
• Open a package: Ctrl + Alt + K

After accessing most of these functions, you can then navigate through the available options using the Tab key, and select your desired option by pressing Enter.

Plugins updated to the latest versions

We've updated the Language Weaver and OpenAI provider plugins (part of the new AI Assistant functionality) to their latest available versions. Additionally, starting with the CU1 release, you will be able to update these two apps manually from the App Store as well.
 

Translation Quality Estimation (TQE) enhancements

Previously, TQE results and color coding were only available for cloud-based projects. This feature has been expanded to include all projects, including those passing through GroupShare.
TQE data for all eligible projects will now be displayed with color coding, providing a quick visual reference for quality estimation regardless of the project's origin.

App updates via AppStore integration

Starting with this release, you can now update both the OpenAI and LanguageWeaver plugins directly through the AppStore integration.
We will provide detailed information about what's new in these apps with each release. You can perform routine updates seamlessly through the AppStore.

File Types and Core Components enhancements 

• Added support for the newly released version of Adobe InDesign and InCopy as previously it could only be processed when the Process unsupported file version option was checked. (LCC-17816, LCC-17815) 

• Updated our services to the latest Language Registry version so that newer languages are also supported.  (LCC-18197)

• Changed the technology for generating PPTX previews from the old structure Aspose generated preview to the newly introduced HTML5 output model. (LCC-17697)

• Improved the fuzzy match scoring mechanism so that it returns more accurate results. (LCC-16364)

• Enhanced our TMX import functionality to properly handle field values from MemoQ Translation Memory (TM) exports. This improvement addresses the issue where field values were not being imported correctly, despite the successful import of the .TMX file content. (CRQ-38024)

• Improved our TMX import process to handle field data from Déjà Vu and other third-party exports more effectively. Studio recognizes and imports fields even when they lack explicit type declarations, and accommodates variations in TMX header formats. By aligning more closely with the flexible TMX specification, we've made it easier for users to transition between tools and make full use of their existing translation resources. (CRQ-33274)

• Enhanced the behavior for handling the <note> element in TMX files more robustly so that translation units with note elements no longer stop Studio from importing the TMX content. (CRQ-35328)

• Updated the Entity filter settings in our XML/HTML handling to allow the definition of entities with duplicate Unicode values. (CRQ-37986)

• Added a new section to the Subtitle file type settings, called Writer Settings. This section allows you to configure the handling of the encoding for the source file. (LG-43209)

• Addressed the issue related to the QuickInsert option recently missing from the HTML5 file type. (CRQ-38574)

• We fixed an issue related to updating legacy translation memories for cases when the Translation Memory Update task failed. (CRQ-37911)

• Resolved an issue in our XML processing, specifically within the W3C ITS Compliant filter configuration, where escaped HTML entities were not being correctly handled during translation. (CRQ-37838)

• Fixed an issue in our handling of Java Properties files, specifically addressing the Java Properties source files which were missing BOM. Previously, this meant that in the translated content several unicode sequences would appear instead of the correct Asian characters expected. (CRQ-37601)

• Fixed the issue related to the Information Note content control in the source Microsoft Word files previously causing Studio to fail when saving the target file. (CRQ-37264)

• Resolved an issue related to the display and handling of certain Unicode control characters in our online translation editor, particularly addressing discrepancies between Windows and macOS environments. (CRQ-37141)

• Resolved an issue in our JSON file type handling when using the HTML 5 Embedded Content Processor. This fix addresses an error that occurred during the Target File Generation stage when applying formatting through quick inserts. (CRQ-36813)

• Resolved an issue where certain special characters (&, <, >) within Field codes in Word documents were causing corruption in the generated target files. (CRQ-36592)

• Fixed a preview generation problem for content coming from PPTX sources, so that characters are no longer merged when previewing the file in the Korean target translation. (CRQ-36501)

• Fixed an issue for Microsoft Word source files containing comments that would incorrectly disappear in the translated output, although the comment box itself was displayed. (CRQ-36256

• Fixed an issue of saving the target content of a Photoshop file for situations where the following error appeared “Arithmetic operation resulted in an overflow". (CRQ-35168)

• Resolved an issue with font mapping for newly added target languages in Adobe InDesign CS4-CC IDML file configurations. Previously, when adding new language font mappings that weren't in the default set, the selected fonts were not being applied correctly to the target language in the IDML output. (LCC-18467)

Fixed issues

General

• For users receiving work via Automatic Role Assignment in GroupShare, Studio now sends a notification informing them that Check In and Change the phase actions are possible, and that they no longer have rights to view that GroupShare project or project file after changing the phase. (CRQ-37734)

• Fixed an issue with the OpenAI Provider plugin in AI Assistant which caused Studio to crash under certain circumstances when opening a file. (CRQ-39858)

• Fixed an Unexpected token error in OpenAI Provider in AI Assistant which would occur when the operating system’s language was set to French. (CRQ-39825)

• Fixed an issue related to WorldServer packages that sometimes wouldn’t open and returned the “There is an error in XML document” message during importing terminology data. (CRQ-39707)

• Fixed the “Invalid Parameter” error occurring under rare circumstances when working with AutoSuggest in the Editor during typing. (CRQ-39347)

• Fixed an issue that caused the API FileTypeId field to be null for HTML files. (CRQ-39749)

• We corrected the cursor placement behavior after tags and at the end of segments in RTL languages. The Left arrow and End keys now function as expected, allowing you to continue typing where intended. (CRQ-39302) 

• Fixed an issue with the term recognition behavior so that Studio no longer fails to recognize expected Asian languages source terms, when manual termbase searches find them with 100% match scores. (CRQ-39289, CRQ-34205)

• Fixed an issue when closing the Task Sequences window during a custom flow that would cause Studio to shut down with the “Value cannot be null error”. (CRQ-39252)

• Fixed the behavior of importing translation memories for situations involving certain rare date formats which previously failed with the message: "Import failed. The file could not be processed." (CRQ- 39051)

• Fixed a problem in the API where calling the method TranslationProviderManager.GetTranslationProviderFactories would result in a missing method exception (System.MissingMethodException). (CRQ-38812)

• Fixed an issue where the name of the open TM was not showing on the corresponding tab in the Translation Memories view. (CRQ-38793)

• Fixed an issue within the Language Processing Rules menu so that its details are now displayed. (CRQ-38772)

• Fixed an issue of recently used translation memories not being displayed in the Translation Memory view after closing and restarting Studio. (CRQ-38744)

• Fixed a synchronization issue that incorrectly prompted you with a "Do you want to overwrite the local version available in your account" message in the Studio editor although no changes were performed online. (CRQ- 38731)

• Fixed the behavior for the Reset to Defaults button within the File Types menu so that it executes faster and triggers no error. (CRQ- 38688)

• Fixed an issue with the Project Details and other UI labels defaulting to English when Studio was set to French or other UI languages. (CRQ-38609)

• Fixed an issue that caused slow performance when loading the list of GroupShare users and occasionally led Studio to enter a "Not Responding" state. (CRQ-38209)

• We fixed an issue with the Passolo icon appearing grayed-out on the Home tab in the Welcome view. (CRQ-38065)

• We fixed an issue related to cloud projects with a large number of files that when opening all files for translation would cause Studio to stop working. (CRQ-37820)

• Fixed the issue related to Chinese source terms not being shown as recognized in Studio although they could be found as 100% matches in Termbase search. (CRQ-37440)

• Fixed a hyperlink in the Cloud Sign In window that was incorrectly redirecting to https://oos.sdl.com/ instead of https://languagecloud.sdl.com/lc/login when clicking on the subscription name. This ensures correct redirection to cloud accounts for authentication. (CRQ-37115)

• Fixed an issue which caused PowerPoint notes to not be translated in the target file when using an .sdlxliff file from the cloud. (CRQ-36707)

• Fixed an issue with Studio freezing when opening multiple cloud project files from different cloud-based projects. (CRQ-36538)

• Fixed an issue where multiple authentication windows appeared when resuming work in Studio after extended inactivity caused security tokens to expire. (CRQ-36529)

• Resolved an access issue for Trados Freelance subscription holders. Users can now access Trados Team resources (translation engines, translation memories, and termbases) when working on projects from different accounts. This fix enables Trados Studio subscription license users to collaborate on Trados cloud projects, removing previous restrictions on these essential resources. (CRQ-36442)

• Fixed term verification issues in Studio 2022 SR1 and later versions. This resolves incorrect warnings and missed verifications, particularly for Chinese and Japanese termbases. You can now expect more accurate results (fewer “false positive” results) when using the Check for possible non-usage of the target terms option. (CRQ-35926, CRQ-35764)

• Fixed an issue with GroupShare server project files not displaying the canceled status correctly in Studio, and causing errors when handling the files or project. (CRQ-34049)

• Fixed an issue with Update TM functionality, which caused Translation Memory (TM) field values to persist in project files and templates after changing the main TM. Now, switching TMs properly clears old settings (CRQ-34048)

• Fixed an issue with the Retain Studio target comments in target file not being displayed in Studio for projects created in the cloud. (CRQ-33270)

• Improved term recognition to correctly display synonyms in the term recognition window. Previously, when a segment contained both a main term and its synonym, only the main term was shown. Now, synonyms are displayed alongside their main terms when the new Show synonyms separately in Term Recognition view option is selected. (CRQ-32223)

• Fixed several issues relating to Japanese fonts which would cause corrupted characters to display in various windows. (CRQ-23402, CRQ-25211)

• Fixed an error that occurred when trying to add a Translation Quality Assessment (TQA) comment on a segment where a merged TQA Addition item exists. (CRQ-25036)

• Fixed an issue with the Parser window under specific file type settings not displaying correctly on French UIs. (CRQ-21984)

• Fixed an issue where Automated Translation (AT) matches displayed corrupted characters in the Translation Results window on Asian Operating Systems, particularly Korean OS. This problem occurred specifically when segments also contained fuzzy Translation Memory (TM) matches. (CRQ-13679)

• Fixed an issue for RTL languages that occurred when using the Next button after accepting the existing Tracked changes. Previously, some of the changes were not selected at all. (CRQ-13666)

• Fixed an issue with TM fields on All Language Pairs level which caused it to not update after a change is made at a specific language level. (CRQ-13383)

• We fixed the TM navigation behavior that wasn’t working when searching for potential duplicates. (CRQ-12903).

• We analyzed the issue related to font adaptation for Asian languages, namely, using English UI on a Korean OS. Font Adaptation for Korean language and within Microsoft Word files works as designed. This means that the graphical engine will fallback to highly similar fonts whenever a glyph cannot be rendered in the font you chose initially. (CRQ-6943)

• Fixed an issue where Check for possible non-usage of target terms was verifying terminology against the wrong sub-language. Previously, Studio checked against the first alphabetically listed sub-language in the termbase, rather than the defined target language. Now, terminology verification correctly matches the specific target sub-language, ensuring more accurate warnings and improving translation consistency across regional variants. (CRQ-5348)

• Fixed an issue where term from the Term Recognition window couldn’t be checked when working with multiple server-based termbases. The problem occurred when the default termbase used general language pairs (e.g., German-Italian) and other termbases used more specific language variants (e.g., German (Germany)-Italian (Italy)). (LG-44661)

• When trying to migrate a local TM to cloud, Language Processing Rules were not displayed in the drop-down menu from the Migrate Local Translation Memories to Cloud wizard. The issue has been fixed. (LG-44719)

• The Last Used By system field was not being updated for local Translation Memories (TMs) when segments were automatically confirmed as 100% matches or Context Matches (CM). This issue has been fixed. (CRQ-35335)

• Fixed an issue where Language Processing Rules prepared in GroupShare were not displayed when creating a new server-based Translation Memory (TM). (LG-44357)

• The translation actions in the Manager view drop-down menu now appear in the correct order: Translate > Review > Sign Off. (LG-44108)

• Fixed an issue that caused target plural terms to be incorrectly flagged by term verification when source terms have the same ending, regardless if they're plural or singular. (LG-43848)

• Fixed an issue where the Reset to Defaults button was not working on some settings pages. In particular, resetting language pair-specific settings didn't properly revert to All Languages settings, leaving unnecessary entries in project files. (LG-34056)

• Fixed an issue with the interface when creating project packages, where the Task drop-down list under the Review Project Packages step had an Error option. (LG-44432)

• Fixed an issue that caused Translation Memory tabs to display the wrong name when viewing them in the Translation Memory view. (LG-45142)

• Studio did not properly reflect the Canceled status when users canceled files in Trados GroupShare, making them unavailable. This led to several errors when users handled these files or projects. The issue is now fixed. (CRQ-34049)

• Previously, closing the Task Sequences window in the custom flow would cause Studio to shut down unexpectedly, displaying a "Value cannot be null” error. The issue has been fixed. (CRQ-39252)

• Fixed an issue in the editor's Bookmarks functionality where the default bookmark items Last segment and Last segment in project could be inadvertently removed using the Delete key. These items are now protected against accidental deletion.

• Fixed an issue where temporary folders from plugin installations weren't automatically removed. Previously, you had to manually delete these folders after restarting Studio in some cases. Now, the system cleans up these temporary files upon restart, streamlining the plugin installation process. (LG-44643)

• Fixed an issue where the Preview functionality was disabled for the first translation file opened in the editor after starting Studio. Previously, the Preview window and disabled keyboard shortcuts were not working when opening the initial file. (LG-44692, LG-44857)

• Fixed an issue that caused the Comments tab to disappear from the toolbar when reviewing a file. (CRQ-40022)

• We’ve changed the previous default AutoSave folder location to %AppData%/Trados/Trados Studio/<studio-version>/AutoSave to prevent both folder synchronization issues and access issues sometimes occurring when working with projects hosted on OneDrive. (CRQ-39839)

• Fixed an issue where you would see an unexpected layout in the editor for a few seconds when opening your first file after launching Studio. Now, when you start Studio and open that initial file from a project, the editor displays the correct layout immediately. (LG-44786)

Known issues

Check spelling not Supported for Japanese & Chinese 

The Check Spelling feature doesn't support Japanese and Chinese due to the lack of dictionaries in Hunspell. While Studio supports Word spellchecker integration, the Microsoft Word API does not provide spell-checking dictionaries for these languages, likely due to the complexity of their spellchecking needs.

Installation fails when the folder name contains Eastern European characters 

This issue occurs when the folder name contains Eastern European characters, throwing an "Error reading the suite file" message.
Workaround: Rename the user folder to remove any Eastern European characters before installing Studio. 

Insufficient error handling when a file's location is unavailable

When using remote storage solutions (e.g., DropBox, OneDrive) for project files, Studio may encounter issues accessing or writing to these files. This limitation can affect editing, saving, auto-saving, or previewing files. Cloud synchronisation services may occasionally cause file locations to become temporarily inaccessible, leading to this unexpected behavior in Studio.

Termbase creation wizard not localized in other languages

Currently, all steps in the Termbase Creation wizard are only available in English. This issue will be addressed in a future update