For more information on all hotfixes and enhancements included in the cumulative updates for SDL Trados Studio 2014 SP2, see the following list.
Cumulative Update 12 (Released on 12 April 2016)
This cumulative update (CU) includes all previous cumulative updates for SDL Trados Studio 2014 and the following enhancements and hotfixes:
- Custom machine translation engines created using Language Cloud Trainer are now showing correctly in SDL Trados Studio 2014.
- Fixed the Multiple tags with the same ID 'x' have different start tag properties error.
- Enhanced the XLIFF file type handling so that Studio now treats self-closing and empty tags correctly.
- Made enhancements to the Analyse Files batch task:
- Analysis results also include fuzzy matches with the minimum match value; previously these were excluded from the results.
- Analysis results no longer differ during and after project creation when files are sorted differently in the Files View; the analysis now always uses alphabetical sorting internally.
- Fixed an issue where the tag order in locked content was not saved correctly in Translation Memory.
- Fixed an issue where a hyphen imported from TMX was not inserted correctly in the target segment.
Cumulative Update 11 (Released on 15 September 2015)
This cumulative update (CU) includes all previous cumulative updates for SDL Trados Studio 2014 and the following enhancements and hotfixes:
- Fixed problem with adding files into an existing project using the SDL Trados Studio Integration API.
- Fixed unexpected warning messages when running the Update Main Translation Memories batch task.
- Context information was not being updated correctly in translation units which lead to less-than-expected context match leverage. This issue is now fixed.
- Fixed the An error has occured whilst using the translation provider NX_INternal_TM: Value cannot be null. Parameter name: Ics concordance search error when using Korean as source language.
- XML file type: An XML file could not be opened after the The document cannot be processed since it contains unexpected contents error was thrown. This issue is now fixed.
- TTX file type: Tag ID mismatch and different number of tags in bilingual file populated by PerfectMatch lead to leverage loss. This issue is now fixed.
- XLIFF file type: Invalid target language XLIFF files were generated if empty source tags were present in the source XLIFF document. This issue is now fixed.
- Microsoft PowerPoint file type: Text was missing in the target file when there was a hidden group of objects after the text in the source document. This issue is now fixed.
- Issues fixed in the Adobe FrameMaker MIF file type:
- Fixed the Failed to save source content: The 'para' start tag on line 1 position X does not match the end tag of 'cf'. error when saving MIF files as source or target.
- The Show as per expression is now correctly handled in Studio 2014.
Cumulative Update 10 (released on 13 May 2015)
This cumulative update (CU) includes all previous cumulative updates for SDL Trados Studio 2014 and the following enhancements and hotfixes:
- Fixed the Object reference not set to an instance of an object error when the Edit Source mode is still active in a document.
- Fixed the TranslationProviderThrewException error when running the Confirm and Translate until Next Fuzzy Match using Language Cloud.
- Improved performance when typing over commented text.
- Fixes in the TM update batch task settings introduced with CU9:
- Add as new translation is again set as the default option (this reinstates the default used in CU8 and earlier) for the translation memory update batch tasks.
- Users can now decide if to use the SDLXLIFF user metadata or the TM User ID to update Created by and Changed by system fields.
- When working with server-based translation memories, we will release CU04 for GroupShare soon, which will enable this functionality. CU04 and details will be released in KB article 7246
- Fields are no longer replaced in translation unit in translation memory when confirming a segment populated from TM during interactive translation.
- When working with server-based translation memories, we will release CU04 for GroupShare soon, which will enable this functionality. CU04 and details will be released in KB article 7246
- Fixed inconsistent translation in the German user interface for embedded content.
- Enhanced rendering for Lao language.
- Fixed the Translation Provider Threw Exception error when combining server-based and file-based project TMs in a project that connects to a GroupShare server running a pre-CU2 version of GroupShare 2014 SP2.
- Fixed opening a project from GroupShare notification emails with HTTPS.
- HTML: The Always normalize option now works even if entities are present.
- XLIFF: The encoding of the XLIFF file is no longer changing when creating a project.
- XLIFF: Tags are no longer doubled in the target translation if the target is empty.
- SDLXLIFF files are no longer rendered unusable if a TM system field value from a Translation Unit contains an ampersand. For this fix to work, the SDLXLIFF files need to be regenerated by running the appropriate batch task in SDL Trados Studio (such as Pre-translate).
- HTML: <br> tags inside non-translatable elements no longer cause issues in the HTML filter.
- DOCX: Fixed the Unexpected end of file has occurred error when saving as a target or enabling the preview for the attached file.
- Integration API enhancements:
- It is now possible to trigger the activity of translation providers through the API. This helps with scenarios where users need more control of when to use a translation provider beyond the options available in the Studio user interface for this.
- The active file and active project file are now exposed through IntegrationApi.Document.
- It is now possible to access and update segment and paragraph unit properties.
- It is now possible to get the segment pairs for a paragraph.
- Added a new property to Document to show if the TM provider is available; also added an event to show if the active segment content is ready for processing after running and applying a TM search.
- It is now possible to define your own AutoSuggest provider icon.
- The Editor user interface is now refreshing properly when locking a segment via the integration API.
Cumulative Update 9 (released on 11 March 2015)
This cumulative update (CU) includes all previous cumulative updates for SDL Trados Studio 2014 and the following enhancements and hotfixes:
- Fixed an error that occurred when double clicking on a translation unit in the Translation Results Window.
- Fixed the following error message in the Update from External Review batch task: Review documents were found but were not successfully added to the project for the following project files.
- Fixed the Fuzzy autopropagation not initialised error when disabling the Enable Auto-propagation option after changing the Minimum match value to a fuzzy match value.
- When reusing an item from the display filter drop-down list, it is no longer autocompleted with the wrong case.
- The messages generated in the new global tag verifier now include information on the changed tags.
- The tag verifier check is no longer performed when the Tag verification option is unchecked under Verification settings.
- When using the Add as new translation option, the user interface is now refreshed to give the user better feedback that the translation has been added.
- The new Fast import option available when returning project packages (kits) to WorldServer is now unchecked by default.
- Fixed the remaining issues with the Update Project TM batch task where it fails with an Input string was not in a correct format error.
- HTML: closing tags no longer get removed from the target if the <strong> element is declared as inline.
- XML: Fixed the The document cannot be processed since it contains unexpected contents error when opening an XML file in Studio.
- DOCX: Fixed the Failed to save target content: An error occurred while parsing EntityName, Line x, position x error.
- DOCX: The combination of a content control and document title field no longer prevents saving the translated file.
- DOCX: Other fixes where target files could not be saved in certain circumstances.
- The Usage count, Last used on and Last used by are now recorded and updated properly.
- The import into translation memory no longer stops on corrupt files and now continues to process other files.
- The The file at the location ... does not exist error no longer occurs when using a Turkish version of Windows 7.
- Hebrew terms can now be added successfully to MultiTerm when adding the term from within Studio.
- Fixed the Failed to verify document: Sequence contains more than one matching element error in term verification.
- In the print preview, extra spaces are no longer inserted around formatting and revision content.
- The Latest News tab in Studio now correctly retrieves and displays the RSS feed.
- The new options in Term repetition threshold and Enable recognition of two-letter term are now available in the localized versions of the Studio user interface.
Cumulative Update 8 (released on 11 February 2015)
This cumulative update (CU) includes all previous cumulative updates for SDL Trados Studio 2014 and the following enhancements and hotfixes:
- Added new import options to both the import and the Update Translation Memory batch tasks. These options address similar requirements as were available in SDL Trados Translator's Workbench (as shipped with SDL Trados 2007 and earlier) when target segments differ (add new translation unit, overwrite existing, keep most recent, keep oldest). These options are available both at user interface and at API level.
NOTE: SDL Studio GroupShare 2014 SP2 needs to be updated to offer the same functionality. See KB article 7246 for more details.
- IMPORTANT: In CU8, the default setting for the Update Translation Memory batch task is to overwrite existing translation units rather than add them. If you want to keep separate translation units (for instance, those added during translation using the Add As New Translation command) be sure to make the selection for adding translation units.
- When creating or editing a server-based translation memory in GroupShare, the alphanumeric string option is now only active if Studio is connected to a SDL Studio GroupShare 2014 SP2 CU02 server. For all previous GroupShare versions, this option is inactive.
- After rejecting a deleted tracked change or accepting an added tracked change, translations are also autopropagated now.
- Improved verification reports (created when using the Verify Files batch task) with segment numbers and enhanced navigation (you can click on a number in the report and it will take you to the segment in the file).
- Fixed a problem with updating segment content via the SDL Trados Studio Integration API.
- Fixed term verification if a segment contains more than three forbidden terms. It now works for two-letter terms also.
- Fixed the Update Project TM batch task failing with an Input string was not in a correct format error in specific circumstances.
- Note that this is partially fixed in this cumulative update. For it to work, use the Add new translation option under Existing TUs in the batch task settings. If you use Overwrite you may still get the issue the first time you run the update. However, this error then disappears for the second run, even with the Overwrite option. This issue will be completely resolved in the next cumulative update.
- The Add As New Translation option now works correctly and adds a new translation unit to the translation memory with the alternate translation. However, the Studio Editor does not update automatically to show the new translation unit. This will be addressed in a future cumulative update. To manually refresh the Editor, press
[Ctrl+Shift+T]
or use Advanced > Look up translations to look up the newly added translation. - A number of issues have been fixed in the following file types:
- XML: Fixed embedded content performance issues with large files, including addressing the error message The operation completed successfully.
- XML: Files with non UTF-8 encoding in source are now saved with the appropriate target encoding instead of UTF-8.
- XML: Enable entity conversion is now disabled by default for new file types.
- XLIFF: Whitespace located at the end of a tag no longer creates duplicate tags in the target file.
- XLIFF: Status mapping / attribute is now correctly written into the target document.
- DOCX: Character styles are no longer lost and replaced by paragraph styles when adding the styles to the Styles list in Studio.
- DOCX: Custom
docproperty
field in footers is now retained correctly in target file. - DOCX: Addressed issues with complex content controls.
- XLSX: TextBox content is now extracted if the worksheet contains a pivot table.
- XLSX: Addressed the error Object reference not set to an instance of an object while parsing certain files in Studio.
- XLSX: Curly brackets in formulas are no longer replaced with "ARRAYARRAYROW" in the target file.
- HTML: Addressed the error Failed to save target content: startIndex cannot be larger than length of string.Parameter name: startIndex when translating
alt
attributes for img
elements. - HTML: Formatting tags now get closed properly in the target file under all circumstances.
- HTML: HTML: Meta Content Attribute translation is now preserved in the target file even if the META element is preceded by an HTML comment.
- HTML: Addressed error Failed to save target content: StartIndex cannot be less than zero when META is defined like:
*content="text/html; charset=utf-8"*
- HTML: Text is now imported into Studio even if only the
br
tag is present in the segment. - HTML: Text is now imported for translation also when
br
tags are present inside elements which are marked as Not Translatable. - HTML: Content with tracked changes is now preserved in the target file.
- Fixes for SDL WorldServer support in SDL Trados Studio:
- The WorldServer WebServices DLL has been whitelisted to allow third party developers to develop plug-ins that use this API.
- There is a new Fast Import option for return packages to perform the import into WorldServer asynchronously.
- Enhanced the live WorldServer translation memory lookup.
- The WorldServer translation provider in Studio now displays custom attributes in the Translation Results window.
- Resolution
-
The cumulative update is automatically applied when you use the AutoUpdate functionality available in SDL Trados Studio 2014. AutoUpdate is turned on by default, so you will automatically be notified of the update as soon as it is available. Follow the instructions on screen to download and apply the update.
NOTE: Applying the update may take some time, as the SDL Trados Studio installation is analyzed before the update to ensure the patch can be installed successfully. As a rule of thumb, applying the patch will take roughly the same time as installing the application.
SDL recommends that you use AutoUpdate. However, you can also apply the patch manually, as follows:
- Close SDL Trados Studio 2014.
- Download the ZIP file
Studio-KB5375-12.zip
from our FTP site (click here to download). - Extract the files to a temporary folder of your choice, such as C:\temp. The ZIP file applies to all editions of SDL Trados Studio 2014.
- Double-click the file
Studio-KB5375-12.msp
. This will install the latest cumulative patch and update the files in the SDL Trados Studio 2014 installation folder as appropriate.
After the cumulative update patch has been installed and Studio restarted, the issues described in this article should no longer occur.