Issues resolved in Trados Studio 2019 SR2
This list details the issues that were resolved in Trados Studio 2019 SR2.
Main application issues
- Fixed issue with Trados Studio window getting lost after switching from a multiple-display setup to a single-display setup.
- Fixed issue with importing packages containing termbases with special characters in Name.
- Fixed issue in the Create File Type wizard with fields not being pre-populated.
- Fixed issue with regular expressions not being interpreted as expected in QA checks and also updated the online documentation with better RegEx examples.
- Fixed issue with importing return packages when the filename contains umlauts (CRQ-14805).
- Fixed the
Failed to verify document: Wrong target expression of grouped searcherror when verifying certain documents (CRQ-14724). - Pre-translate using server-based TMs now also applies for files with track changes (CRQ-14634).
- Fixed the
Culture is not supported. Parameter name: culture 4096 (0x1000) is an invalid culture identifiererror when trying to edit a language resource template with custom settings for Dutch (Suriname) (CRQ-14580). - The copy, find/replace, select all and undo functions are now available for the last file that is open for translation (CRQ-12959).
- Track changes are now correctly applied when using server-based TMs (CRQ-12360, CRQ-14364).
- Fixed the
Value cannot be null. Parameter name: sourceerror when trying to run a batch task from Projects view on a project published on GroupShare 2015 SR2 (CRQ-8802). - If the option for this is active, fuzzy matches are now displayed even if exact matches were found in server-based TMs (CRQ-5887).
- Fixed
Object reference not set to an instance of an objecterror when performing the Finalize batch task on two virtually merged SDXLIFF files (CRQ-5155).
File Types and Core Components issues
- General
-
- Empty files are now better handled by all file types.
- Some of the legacy file types in the file type list are no longer available.
- Fixed issue with parsing custom number separators.
- Improved handling of tags and other non-feature tokens in fragment matching.
- Fixed TM import inconsistencies with the Overwrite existing translation units option.
- We made the batch TM import more robust when dealing with invalid segments.
- Fixed issue with batch confirming more than ten segments.
- We have removed the MatchRepair maximum length constraint and enhanced the way matches are detected.
- Fixed issue with importing specific TMXs with Japanese and Spanish (CRQ-14950).
- Fixed issue for custom RegEx file type settings generating target files with lines of content missing (CRQ-14464).
- Navigating to bookmarks on a cell table will not select the whole row in the target file anymore (CRQ-14306).
- Fixed issue with segmentation when an inline tag pair is placed after a full stop (CRQ-14147).
- You can now Save Target As when there are comments added without Author (CRQ-14070).
- Fixed issue with empty tag pairs not being included in the segment (CRQ-13951).
- XML v1 file type
-
- Fixed issue with extracting entities.
- Better error handling when parsing CDATA embedded within inline tags.
- Fixed the
An error occurred when applying the stylesheet to the XML fileerror when previewing an XML file containing an absolute DTD URL (CRQ-13894). - Fixed wrong segmentation if a sentence contains a locked tag pair (CRQ-14335).
- Escaped entities are not converted to
[[SDLENTITYREF[..]]in the target XML file anymore (CRQ-14112).
- Microsoft Office file types
-
- Whitespace is now kept when segments are left untranslated.
- Fixed
Invalid archive structureerror when opening DOCX file generated from Office365 (CRQ-14214). - Tracked changes over spaces are now carried in the target file when translating to Arabic (CRQ-14555).
- Translating a PPTX file in Studio 2017 or 2019 renders the target file unusable in certain circumstances. (CRQ-13976).
- Fixed issue with soft line break shown as paragraph marker for PPTX files (CRQ-14160).
- Fixed
The current context information context type 'sdl:paragraph' is different than expected 'x-tm-table-cell'error for DOCX files (CRQ-14224). - Smaller/greater than sign followed by a non-breaking space is now recognized by Trados Studio (CRQ-13985).
- In Right to Left target languages, when soft break is used, English text is not set to Arabic in target Word file anymore. (CRQ-13574).
- The character order for E٤٢٠ is now preserved when converting to Word for Right to Left Languages. (CRQ-13572).
- Microsoft Visio file type
- Implemented TQA and Track Changes.
- Adobe FrameMaker file type
- FrameMaker 2019 is now supported.
- IDML file type
-
- Emoji character is now kept during translation.
- You can now retain Trados Studio comments as PDF comments in the target file.
- HTML file type
- Introduced embedded content processing.
- XLIFF file type
-
- Target text structure is now the same when source text contains
<target/>for non-translatable elements or when it does not contain<target/>for non-translatable elements (CRQ-14539). - Fixed the
Failed to save target content: A valid XML prefix, namespace, and local name must be specified for the entity named 'version'error when saving a file which contains the "/" character in the namespace (CRQ-11882). - Fixed the
Index out of range (5). It must be a number from 0 up to the number of items in the collection (2). Parameter name: indexerror when opening an XLIFF file (CRQ-14138). - Embedded content tagging now works for XLIFF files (CRQ-14458).
- Fixed
The document cannot be processed since it contains unexpected contentserror when opening a XLIFF file (CRQ-13991).
- Target text structure is now the same when source text contains
- PerfectMatch
-
- Fixed issue with PerfectMatch not inserting the original translation sometimes in regulatory industry flow (CRQ-11273).
- Fixed handling of duplicate content to choose the correct translation in Perfect Match regulatory industry flow (CRQ-14487, CRQ-14237).
- Fixed issue with Perfect Match not being applied after merged segments (CRQ-14511).
- Fixed issue with Perfect Match not translating some segments (CRQ-14630).
- Fixed PerfectMatch not merging three segments as expected under certain circumstances (CRQ-13854).