We are pleased to announce the release of SDL Translation Management System 2011 Service Pack 6. For comprehensive information on this release, please be sure to consult the attached Release Notes at the bottom of the page and the Knowledge Base articles referenced on this page.
As part of SDL’s strategy to deliver a consolidated localization ecosystem, we are pleased to announce that with this release, SDL TMS now su…
Symptoms:
In some cases, when source files have been uploaded to SDL TMS in a .ZIP file of nested folders, it was not possible to download those files from the Job's Items and the Task Status Summarypages or from the Online Translation Interface page.
Explanation:
The issue was caused by a restriction of 4 parameters, implying a four-folder structure for the source file's path. For example, a valid path would be like this…
Symptoms:
If a match has duplicate tag IDs in the translation memory, applying it during the ApplyTM stage sends the task to Recovery with this information in the logs “An item with the same key has already been added.”
Explanation:
SDL TMS consumes a specific external Component responsible for sorting the TM candidates matching, based on criteria such as score, last modified date and usage count. As this Component…
Symptoms:
For a Configuration in use within a Project, it is impossible to retrieve the Configuration's details from third-party applications that use the Java Content Transfer API (CTA), therefore preventing the integration from working.
Explanation:
When a user needs to create a job request from a third-party application, using CTA, a request is sent to SDL TMS to get the Configuration's details. An issue was identified…
Symptoms:
In some cases for Legacy Content Types, tasks coming from an External Machine Translation (EMT) Engine for processing get stuck in the EMT queue.
Explanation:
When matches are returned from the EMT Engine, the ITD bilingual file needs to be rebuilt. Sometimes SDLX would crash due to a buffer overflow, leading then to an access violation. This would block the rebuild of the affected ITD file, preventing the next…
Symptoms:
To answer growing demands of supporting more features, as well as Google Docs and Libre Office 4, a new Microsoft® Word 2007-2016 File Type (Tech Preview) has been made available.
As the SDL TMS user community is also a large consumer of these file types and of SDL Trados Studio, we are happy to announce the availability of this File Type Tech Preview (delivered in June 2015 by SDL Trados Studio) in a new…
Symptoms:
When the format painting is broken or missing, the ITD is prevented from being rebuilt. Consequently, the content from the matches from the Machine Translation engine are reverted in the SDL TMS database and therefore they are not included in the ITD file.
Explanation:
After matches are returned from the Machine Translation engine, they are transferred into the ITD file. If the format painting is broken, this…
Symptoms:
There were issues identified after delivering the hotfix from "8680: Hotfix for defect TMS-6026 for SDL TMS 2011 SP6 CU1" with Microsoft® Internet Explorer 11 (IE 11) users who could no longer use the downloading and submitting functionalities from the Inbox.
Symptoms:
You are a user created in Organization A, which is parent-organization to Organization B. You have the "View Job" permission granted for Organization B. When navigating to Home > Inbox , without selecting a specific organization in the navigation tree, you can see jobs from Organization B, but no link is available to get to the Job Summary page.
Symptoms:
Using Microsoft® Internet Explorer 11 (IE 11) does not work for some functionalities in SDL TMS, for example, selecting Jobs for PerfectMatch on the Job Creation portal.
Explanation:
The way to handle the browser detection for IE 11 has become obsolete, not allowing an appropriate identification of the browser. This in turn did not permit the rendering of some data in SDL TMS.
Resolution:
The fix provides an…
Symptoms:
When using SDL Nexus Service with FTP configurations a SfbLicenseException error in the Event log may be displayed indicating that the license validation failed:
The license key is invalid or has been deactivated. Please contact ComponentForge Sales Team at sales@componentforge.net.
Explanation:
This happens when the license for the third-party component used to establish the FTP connections has expired.
Resolution…
Symptoms:
When navigating to the Reports area in SDL TMS, sometimes after selecting the report to be run, an SDL Buddy error page was displayed. This prevented the user from drawing reports.
Explanation:
The issue happened in some cases due to a change in how the state of the report's format type is stored in the user session.
Resolution:
The fix addresses the error and reports can be drawn without any issue.
SDL-hosted…
We are pleased to announce the release of SDL Translation Management System 2011 Service Pack 6 Cumulative Update 1. For comprehensive information on this release, please make sure to consult the Release Notes and other materials attached to this article, as well as the Knowledge Base articles referenced on this page.
Customer Satisfaction:
One of the major focuses of this release lies in defect fixing, delivering about…
Symptoms:
Within the stages of a workflow in SDL TMS, costs are only updated at the Pre-processing and Update Invoice stages. Even if dynamic cost variables are added or updated between these stages, the job cost in SDL TMS is not updated. SDL TMS solves this limitation by calculating job costs ‘on demand’ whenever it receives a request to display this information through the user interface.
SDL TMS should take…
Symptoms:
When SDL TMS receives matched segments containing one of these 3 character entities < , > or & from SDL BeGlobal, SDL TMS escapes the returned characters, therefore displaying incorrect characters.
For example, the string: "This is a document with a <1> placeholder" gets displayed as: "Este es un documento con un < 1> marcador".
Explanation:
SDL TMS was operating a double…
Symptoms:
SDL Studio GroupShare servers, when used in the context of the integration between SDL TMS with SDL Studio GroupShare, experience some performance issues because of SDL TMS polling information at a high frequency.
Explanation:
In SDL TMS 2011 SP6, the frequency at which SDL TMS requested the Status, File Status and Progress data from the GroupShare server was set to 2 minutes. As multiple SDL TMS servers may integrate…
Symptoms:
For tasks pre-processed using a Legacy Content Type in SDL TMS, when opening a Studio Package in SDL Trados Studio and selecting all the ITD files to open in a merged document, the GUID of the ITD file is displayed in the file tree instead of the file's actual name.
Explanation:
During the creation of the Studio Package, if the pre-processing was performed using a Legacy Content Type, the resulting ITD files…
Symptoms:
This article references a number of fixes included in the Combined Hotfix 1 for SDL TMS 2011 Service Pack 6.
Explanation:
The Combined Hotfix addresses the following issues and defect numbers. Click the defect number to get more details for each individual fixed issue:
Symptoms:
An issue has been identified for .sdlxliff-based Content Types, specifically with files containing tag-only segments. The SDL XLIFF provided by SDL TMS after pre-processing would not render these segments properly: the target translation would shift by 1 each time a tag-only segment is encountered.
Explanation:
The exhaler, responsible for getting the task segments from the SDL TMS database and for creating the…
Translate
