Documentation Center

Issues resolved in Trados Studio 2021 SR1

This list details the issues that were resolved in the Trados Studio 2021 SR1 release:

General resolved issues

Languages in cloud termbases not mapped automatically. (LG-24959)
Trados Studio can now correctly map the language pairs of a cloud termbase to the languages of the downloaded cloud project. This means that you no longer get an error message when translating cloud project segments for which termbase results are available.
Offline deactivation code truncated in the Product Activation window. (LG-25195)
Trados Studio now inserts the complete deactivation code when pasting it using the context menu or the CTRL + V shortcut.
New terms added to first cloud termbase, regardless of language pair. (LG- 25742)
Trados Studio no longer adds new entries to the first termabse available in the attached translation engine. Instead, it first filters out the termbases that do match the language pair of the current project file. This ensures that new terms are added to the first relevant cloud termbase in your cloud translation engine.
[Localization]'Sign Out' text from 'Contact your LC admin' page is trimmed in French and Spanish UI. (LG-25235)
"Sign Out" text from "Contact your LC admin" page is now fully visible for the French and Spanish UI.
Locked segments number is not displayed in Trados Studio. (LG-24839)
Wrong language pair for POST /translations/v2/translate. (LG-23117)
Fixed error that occurred when retrieving translation results from neural machine translation providers in projects with language variants.
Studio tries to get a shared termbase even if the termbase sharing link has expired, resulting in superfluous error. (LG-22171)
Fixed issue where users got the following error message "Termbase [id] is not available any more" which is no longer displayed when using Language Cloud termbases with revoked or expired sharing links.
Link for "Trouble Signing in" - Language Cloud not pointing to an available article. (LG-18541)
The link for "Trouble Signing in" on the Language Cloud sign-in page is now pointing to an available article.
If GroupShare Organization name contains a plus sign (+) or ampersand (&), Translation Memories are not selectable/visible anymore in Trados Studio. (CRQ-19978)
Fixed issue where Translation Memories are now visible and usable when using GroupShare Organization names that contain a plus sign (+) or ampersand (&) in Studio.
Missing Ribbon Icons part of Advanced tab. (CRQ-19234)
Fixed issue where the icons in the Advanced tab are visible also if the segment is empty.
Standard XLIFF Filter disappears form the list of file types after extension plug-in is loaded. (CRQ-19171)
Fixed an issue where loading a custom XLIFF file type would cause the standard XLIFF file type to no longer be available after restarting Studio.
"The requested data file could not be located" error when deleting from disk a TM opened in TM view. (CRQ-17128)
Fixed an issue where an error occurs in Translation Memory and Automated Translation tab in Project Settings if the attached local translation memory is deleted from the disk or it could not be found. A friendly message is now shown and the translation memory is then removed from the list.
GroupShare Project Resource Libraries are visible in Trados Studio. (CRQ-16482)
Fixed an issue where dynamic resources were displayed under "Filter" rather than displaying only organizations and project resources while interacting with server-based GroupShare translation memories.
Match Value score disappears from the Segment Status Column. (CRQ-15523)
Fixed an issue where translation results match values coming from aligned translation unit would disappear if the target segment is edited.
Term recognition fails when there are no spaces in between tags or between tags and terms. (CRQ-12970)
Fixed an issue where no terms are retreived for term recognition in Studio if there is no space between tags or between tags and terms.
Alignment: Error message when Aligning Multiple Files 'The method or operation is not implemented'. (CRQ-12724)
The intemittent error 'The method or operation is not implemented' no longer occurs when attempting to align files from multiple folders.
Missing localization for header of "Advanced Display Filter" window. (CRQ-12460)
Added localization for "Advanced Display Filter" window header.
Confirm and Translate until Next Fuzzy Match command in Studio 2017 SR1 and Studio 2019 SR2 not working as expected. (CRQ-8901)
The Confirm and Translate until Next Fuzzy Match operation has been changed to stop on confirmed segments when the TM returns an exact match with applied penalties (e.g. multiple translation penalty). All the existing rules for deciding when to stop the translate to fuzzy operation have not been changed.
Connection to server TM lost after 12 hours: An error has occurred whilst using the translation provider [TM_Name]: One or more errors occurred. (CRQ-10873)
Fixed connection issue to GroupShare translation memories being lost after 12 hours.
Target comment on segment level is not preserved when applying TM or copying source. (CRQ-14276)
Fixed issue for not preserving comments at target segment level after applying translation results or by copying source to target. The Clear Target command will still delete such comments by design.
Custom file type added under "Additional installed File Types exist" after each restart of Trados Studio. (CRQ-18946)
After selecting a custom file type from "Additional installed file types exist" there are correctly added and persisted to the File Types list and no warning is displayed to the page.
Auth0 login authentication keeps only one GroupShare server connection at a time. (CRQ-19336)
Fixed issue when using multiple GroupShare server connections via Auth0 provider Studio would keep only one single connection alive. From now on users are kept logged in for each GroupShare server connection instance.
Auto-substitution dates and times has no defaults when using LC TMs. (LG-25672)
Fixed dates and times auto-substitution not returning default values for Language Cloud translation engines containing translation memories.
[LC Project]: The notification messages are not removed when switching from Files view to the Editor. (LG-24450)
The displayed notifications for available files in Studio when accepting new tasks for a Language Cloud project are now cleared when opening the downloaded files using all "Open in Editor" mechanisms.
[New project] Error displayed when trying to create new local projects with large files from Welcome view. (LG-25851)
Fixed an issue where local projects could not be created from Welcome view when using large files (files larger than ~20MB).
[LC Project]: Enhancement - The location is not displayed in Studio for resources from Language Cloud. (LG-24557)
Enhanced resources available in the new Language Cloud project wizard by displaying their locations under each resource . Change available for the following resources: Project templates, File type configurations, Translation engines, Pricing models, Workflow models.

Resolved File Type issues

[HTML, XML]: Lost focus at scrolling when prioritizing and de-prioritizing parser rule. (LF-5325)
Fixed an issue regarding losing focus when prioritizing or de-prioritizing parser rules, by scrolling to the correct position in order to be visible in the Parser section for XML and HTML from the Options window.
[HTML]: Next button not working over parser rules list. (LF-5324)
Next button working as expected for parser rules in HTML filter page from Options window.
[Xliff 2] Change the resegmentation logic to match the specs. (LF-5323)
Improved resegmentation logic for XLIFF 2 to increase performance.
FrameMaker 10.*] Write corresponding escape sequence when a non-breaking space character is introduced in variables and references. (LF-5321)
Addressed community feedback idea regarding FrameMaker 10 filter to correctly handle escape sequence when a non-breaking space character is available in variables and references.
HTML: Translatable property for attributes issues with conditions. (LF-5310)
Addressed community feedback issue for HTML parser rules for sharing translate property attributes in two segmentation rules with the same element name.
[Xml1, Xml2 Dita preview] Change how the dita2html xsl is loaded. (LF-5306)
Added new option in DITA preview giving users the option to decide which type of transformation to be used in order to load the preview faster. Users can now choose between built-in transformation or DITA toolkit specified by the user.
[Photoshop]: Fonts are lost after round-trips with Aspose. (LF-5301)
Fixed issue for Photoshop filter in which fonts were lost after round-trips.
Improve whitespace normalization in XLIFF 2.0. (LF-5295)
Improved the whitespace normalization in XLIFF 2.0.
[Visio] Html preview. (LF-5215)
Added HTML preview for Visio filter.
Add support for the css-style attribute. (LF-5178)
Added support for css-style attribute in XLIFF 1.2 filter.
Support merging comments over multiple segments in DOCX. (LF-5157)
Fixed community idea for comments spanning multiple segments in the same paragraph.
Support segmentation in PO for sections with empty msgstr. ( LF-5156)
Added support for segmentation in portable object file type to support empty msgstr.
Review handling of invalid HTML/XML files. (LF-5155)
Added warnings or errors if the HTML parser detects "partial" HTML tags.
Improve creation of parser rules. (LF-5154)
Improved creation of parser rules by being able to select multiple entries/tags and to import additional files after a parser was created so that adding entries/tags are easier.
Change display text for footnotes. (LF-5153)
Fixed issue by displaying the number of the footnote instead of the TagID in the document for Microsoft Word documents.
Review handling of inline Code element in HTML. (LF-5152)
Fixed issue by changing the default segmentation hint from "May exclude" to "Include".
Improve HTML preview based on feedback. (LF-5145)
Improved HTML preview by changing the scrolling with word wrap to avoid lateral scrolling.
Add new options for JSON parser rules. (LF-5141)
A new option for JSON parser rules was added, to extract certain values from a specific path.
Optimised 'batch' import flow can fail to align placeables. (LCC-10772)
Fixed issue when using optimized batch import flow failed the TUs to be tokenized. Ensure TUs are always tokenized with bundle support before segment hashes are generated.
Optimise file-based TM import. ( LCC-10708)
Optimized file-based TM import. This also prepares future enhancements around server-based TM imports.
DOCX: Failed to save target content: The XPath expression evaluated to unexpected type System.Xml.Linq.XAttribute. (CRQ-21340)
Fixed issue when trying to save a .docx with content control in footer failed with the following message: "Failed to save target content: The XPath expression evaluated to unexpected type System.Xml.Linq.XAttribute."
MIF V2 generates "Value of '-254999745' is not valid for 'red'" error when trying to open a mif file in Studio 2021 CU1. (CRQ-21321)
Fixed issue when using a MIF V2 filter in Studio, files can not be processed and "Value of '-254999745' is not valid for 'red'. 'red' should be greater than or equal to 0 and less than or equal to 255" error occurs.
XLSX: The document cannot be processed since it contains unexpected contents. (CRQ-21271)
Fixed issue that was causing the following error message when creating a project when using .xlsx files "The document cannot be processed since it contains unexpected contents".
JSON: "Object Reference Not Set ..." error message when using the "Generate Target Translation". (CRQ-21242)
A specific error message is displayed now when using a source file that has a duplicated key in the root object instead of the error message "Failed to save target content: Object reference not set to an instance of an object".
JSON file segments are extracted based on the order of the rules instead of the text position in the file. (CRQ-20977)
JSON file segments are now extracted based on the order of the text position in the file instead of the order of the rules.
Custom XML: Segmentation not working correctly when segmentation hint is set to "Exclude" for ph tag. (CRQ-20123)
Fixed issue when segmentation hint for a self-closing tag (ph) was set to "Exclude" was not working correctly and the text following this tag is moved outside of the segments.
Segmentation: Studio doesn't segment at semicolon (while using the default Hebrew segmentation rules). (CRQ-19391)
Fixed issue in Studio when using default Hebrew segmentation rules.
Trados Studio: Softbreak segmentation rule causes "The document cannot be processed since it contains unexpected contents." (CRQ-19320)
Fixed issue that was causing the following error message when creating a project using .docx files with specific segmentation rules "The document cannot be processed since it contains unexpected contents".
Project creation fails with the error "The document cannot be processed since it contains unexpected contents" when using .docx file containing character formatting and TM with custom segmentation rule. (CRQ-18959)
Fixed issue that was causing the following error message when creating a project using .docx files containing character formatting and TM with custom segmentation rule"The document cannot be processed since it contains unexpected contents".
DOCX: Text with tracked changes extracted between segments. (CRQ-18751)
Fixed issue where segments where incorrectly split when using Word 2007-2019 filter with "Apply Track Changes before opening".
Trados Studio 2019: The document cannot be processed since it contains unexpected contents. (CRQ-18583)
Fixed issue that was causing the following error message when creating a new project using custom Regular Expression Delimited Text Document file type filter "The document cannot be processed since it contains unexpected contents".
IDML: tblref is extracted as inline instead of structure tag. (CRQ-18465)
Changed the segmentation into a tblref placeholder to be May-Exclude instead of the old Includewithtext.
Unnecessary multiple translations after enabling recognition of alphanumeric strings. (CRQ-5475)
Multiple translation units are no longer created unnecessarily after enabling the recognition of alphanumeric strings.