File types and core components changes

This section contains an overview of changes and improvements brought to file types and core components in this release.

General

  • Fixed an issue where Trados Studio did not display the name of the originating Translation Memory (TM) in match results when working with cloud projects that used the Language Cloud Translation Engine, aligning Studio's functionality with the Online Editor and providing translators with essential information for their workflow. (CRQ-33178)

  • Segments containing different types of numbers, with or without separators, are now auto-propagated correctly, according to the number format from the TM settings. (CRQ-25551)
  • Fixed a performance issue that resulted in longer waiting times when opening for translation files that contained SmartArt and formatting, with Turkish or Arabic as the source language. (CRQ-36512)

Microsoft Word

  • Trados Studio now ensures smooth opening of .DOCX files with comments, regardless of the comment extraction setting, resolving the following error message that would sometimes occur in this context: "The document cannot be processed since it contains unexpected contents'". (CRQ-37147, CRQ-3507)
  • Fixed a segmentation issue where text with comments was incorrectly extracted outside of the segments when working with a specific .DOCX file. (CRQ-37711)

HTML5

  • When the Read as Character option is enabled and the Write as Entity option is disabled in the cloud File Type Configurations settings for HTML5 files, the "apos" and "quot" entities are now correctly rendered as their corresponding characters (' and ") in the generated target files, ensuring that the output accurately reflects the desired formatting and maintains the integrity of the translated content. (CRQ-37050)

Added support for language variants

  • We have introduced support for the custom language Russian-Israel (RU-IL), enabling users to accurately localize content for the Russian-speaking audience in Israel. (CRQ-31539)
  • We have deprecated the legacy support for Hmong using the language code zh-x-hmn-SDL and replaced it with dedicated support for Hmong (hmn) and Hmong Daw (hmn-mww) to provide a more accurate and inclusive representation of the Hmong language variants. (CRQ-35268)
  • We have aligned the language support in Trados Studio with recent Windows 11 additions:
  • nds-DE (Low German (Germany)), nds-NL (Low German (Netherlands)), doi-Deva-IN (Dogri (Devanagari, India)), ff-Adlm-SN (Fulah (Adlam, Senegal)), mai-IN (Maithili (India)), ccp-Cakm-BD (Chakma (Chakma, Bangladesh)), ccp-Cakm-IN (Chakma (Chakma, India)), pcm-Latn-NG (Nigerian Pidgin (Latin, Nigeria)), ceb-Latn-PH (Cebuano (Latin, Philippines)), sat-Olck-IN (Santali (Ol Chiki, India)), su-Latn-ID (Sundanese (Latin, Indonesia)), ff-Adlm-BF (Fulah (Adlam, Burkina Faso)), ff-Adlm-CM (Fulah (Adlam, Cameroon)), ff-Adlm-GH (Fulah (Adlam, Ghana)), ff-Adlm-GM (Fulah (Adlam, Gambia)), ff-Adlm-GN (Fulah (Adlam, Guinea)), ff-Adlm-GW (Fulah (Adlam, Guinea-Bissau)), ff-Adlm-LR (Fulah (Adlam, Liberia)), ff-Adlm-MR (Fulah (Adlam, Mauritania)), ff-Adlm-NE (Fulah (Adlam, Niger)), ff-Adlm-NG (Fulah (Adlam, Nigeria)), ff-Adlm-SL (Fulah (Adlam, Sierra Leone))

Deprecated support for legacy file types

As part of our continuous evolution and focus on providing the most relevant and up-to-date file type support, several file types have reached their End of Life (EoL) status and will no longer be supported starting with Trados Studio 2024:

  • FrameMaker 8.0 v 2.0.0.0
  • XML1
  • SubRip

These file types have been replaced by more current versions for a long period of time across several Trados Studio releases. For example, the SubRip file type using the *.srt format was replaced by the Subtitle file type for a long time. Besides supporting the *.srt format, the newer Subtitle file type supports all of the following formats:*.vtt, *.sbv, *.sub, *.ttml, *.xml and *dfxp.

Even with these old file types end-of-lifed, you will still be able to work on SDLXLIFF files based on these types in Studio 2024, but you won't be able to preview or save as target. This means you can roundtrip such files and send them back to your work giver who may still use the old file types.