SDL Trados Studio 2015 Service Release 3 - Release Notes
SDL Trados Studio 2015 Service Release 3
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 contained in SDL Trados Studio 2015 SR3 (version 12.3.5262.0). For more information on all hotfixes and enhancements included in SDL Trados Studio 2015 SR3, see the following list.
SDL Trados Studio Service Release 3 (Build 12.3.5262.0) (released on 2 March 2017)
SDL Trados Studio Service Release 3 (SR3), build 5262, supersedes SR2 and includes all previous updates for SDL Trados Studio 2015 as well as the following enhancements and fixes:
Compatibility with SDL Trados GroupShare 2017
This service release introduces compatibility with SDL Trados GroupShare 2017. Users must install this service release to be able to access server-based resources in SDL Trados GroupShare 2017. Previous versions of SDL Trados Studio 2015 are not supported for use with SDL Trados GroupShare 2017.
Localized some missing strings in the user interface.
Fixed issue with server connection to Trados GroupShare getting lost when running a batch task on a server-based project.
Fixed an issue where users that had access to a large number of translation memories on a Trados GroupShare server (over 5000) could not connect to one of that TMs.
Resolved an issue where SDL WorldServer packages (WSXZ) could not be opened in Studio when files had similar names.
This service release contains the same PerfectMatch component as Studio 2017 CU2 or later.
Fixed several occurrences of the following error: Internal error: Multiple tags with the same ID '843' have different start tag properties.
Fixed an Object reference not set to an instance of an object error when applying Perfect Match.
Fixed a problem where tags were not matched correctly and <pm> tags were created instead, leading to damaged target files or errors when attempting to save target files.
This service release contains the same segmentation engine as Studio 2017 CU2 or later.
Addressed segmentation errors occurring when opening specific files in Studio with the following error message: The document cannot be processed since it contains unexpected contents.
Fixed a problem where text with superscript was not offered for translation if it occurred within a source comment.
Fixed an issue where the segmentation hint May exclude was no longer working correctly for tag pairs in a segment when it also contained a placeholder tag whose segmentation hint was set to Include with text.
Enhanced the whitespace processor such that extra whitespace is no longer added in CDATA content processed with the HTML filter for the Chinese target language.
Fixed a problem where a full stop followed by an internal tag was not segmented correctly, leading to changed segment size and, as a result, an unexpected leverage loss in pre-translation and interactive translation.
The segmentation hint Include with text no longer leads to translatable content being omitted unexpectedly from translation in specific cases.
File Type Support
Fixed a problem where MIF files translated to Persian were empty due to language information missing in MIF tags
Fixed the following error: Failed to save target content: Extra 'marker' reference tag within the segment ID 'n'
Fixed a problem where all anchored frames with those not set to At Insertion Point as its anchoring position were offered for translation
Fixed a problem where the MIF file type did not expose text in cross-reference (xref) tags for translation.
Fixed the following error: Failed to save target content: Missing 'textinset' reference tag within the segment ID.
Fixed the following error: Failed to save target content: Index was out of range. Must be non-negative and less than the size of the collection.
Fixed the following error: Failed to open source file: Index was out of range.
Adobe InDesign IDML
Fixed problems where target IDML files could no longer be saved with SDL Studio 2015 SR2 CU7.
Fixed the following error: Failed to save target content: Unable to cast object of type 'System.String' to type 'Sdl.FileTypeSupport.Filters.Idml.FileFormat.Datacontainers.AResource'.
Fixed the following error: The 'cns' start tag on line 1 position n does not match the end tag of 'cf'.
Fixed the following error: Failed to save target content: Missing '<xr name="" type="" value="Editorseite „Übersicht“"/>' reference tag within the segment ID ''. Please run the Tag Verification to see details.
Microsoft Word DOCX 2007-2016:
Fixed the StartIndex cannot be less than zero.Parameter name: startIndex error when straight quotes were missing in an index entry field.
Fixed a problem where a target document could not be created when non-breaking hyphens were located in index entry fields.
Enhanced word count behaviour for Word .docx files such that the Count as one word option Are hyphenated now also applies to optional hyphens.
Fixed a problem where text after a chart remained in the source language after generating the target file.
Fixed a problem where under certain circumstances translations were not saved to the target file when saving target.
Added a new file type for handling Microsoft Excel files, called Microsoft Excel XLSX 2007-2016:
This cumulative update contains a new Microsoft Excel file type (Microsoft Excel 2007-2016) that, over time, will replace the legacy Microsoft Excel file type (Microsoft Excel 2007-2013) as the default file type for handling Microsoft Excel documents. This will be similar to the Microsoft Word file type that has replaced the legacy file type in previous Studio releases.
To activate this file type, in the File Types list of the default or any custom project template, uncheck the Microsoft Excel 2007-2013 file type and activate the Microsoft Excel 2007-2016 file type instead. This will give you access to the new file type for any new projects based on your project template.
The new file type contains a large number of enhancements and bug fixes throughout all areas of file type processing, such as handling pivot tables, SmartArt objects, embedded content, and much more.
Enhanced the DITA XML file type such that the synph element is now defined as inline rather than structure by default
Enhanced the DITA file type to handle .ditamap files out of the box
Fixed a problem in the DITA file type where an entity defined with brackets [like this] would corrupt the target file
Fixed the Failed to save target content: Index was outside the bounds of the array error.
The XML file type no longer adds a whitespace at the end of processing instructions.
Fixed a problem where entity references from comments were incorrectly parsed
Fixed the error An error occurred when applying the stylesheet to the XML file when previewing a specific .xml file.
Fixed a problem where trying to select an element using substring(parent::*/@id,1,7) would break the XPath when trying to edit it again.
Fixed a problem where embedded content was offered for translation even within protected content.
Fixed a problem where SDL Trados Studio stopped working when opening a specific XML file.
Fixed a problem where the target file entity was displayed as HTML Entity (hex) ¥ instead of the actual value ¥.
Fixed a problem where the embedded content processor set to process only the content found in "text" would also process "plaintext".
Fixed the Length cannot be less than zero / Parameter name: length error displayed when opening a specific file.
Other fixes in file types:
RegEx: Segmentation hint is now used for tags like \\n and \\r.
Regular Expression Delimited Text file type: Fixed a problem where text was not extracted for translation as expected if the opening pattern contained line break characters.
Portable Objects (PO): Empty plural forms from PO files are no longer incorrectly marked as translated and confirmed.
HTML: Fixed a problem where meta charset value was not added if a different meta tag already existed.
The SDL Trados Studio 2015 Service Release 3 (SR3) installer is available for download from your SDL Account.
NOTE: Applying the service release may take some time, as the SDL Trados Studio installation is analysed before the update to ensure the service release update can be performed successfully. As a rule of thumb, applying the service release update will take roughly the same time as installing the application. To apply the update, do as follows: