TMS > SDL TMS 2011 Service Pack 5 - Product Updates

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:
In some cases, the Rebuild Translation stage creates an incorrect target file by ignoring some of the custom settings from the HTML 5 embedded content processor.

Symptoms:
On the Edit Content Type page, both fields named Included Extensions and Excluded Extensions would not allow more than 50 characters, forcing users to create multiple Content Types when actually one would be sufficient to capture all needed extensions in those fields.

Explanation:
The Content Type Edit page has a validation that restricts the content of that field to 50 characters.

Resolution:
The validation has…

Symptoms:
Sometimes in SDL TMS within the GroupShare Inbox, the Status may not update or the date of the Last Refresh may be incorrect.

Explanation:
When the server hosting the SDL TMS application and the server hosting the TMS Microsoft® SQL database do not share the same date format, the following errors may occur:

Symptoms:
Sometimes, in an environment set up correctly, users can see the tasks assigned to them in the traditional TMS inbox, but when opening the GroupShare Inbox, no jobs or tasks are displayed, except for the message: 

Explanation:
If the initial data retrieval took more than 5 seconds, the GroupShare Inbox would time out and therefore no jobs and no tasks would get displayed…

Symptoms:
It is not possible to roundtrip Studio Packages that use "Spanish --International--" (ES-XM) after :

Explanation:
"Spanish --International--" (ES-XM) is a language supported only by SDL TMS. In the *.sdlxliff file, the source/target language is identified as "es"."es" does not exist in SDL Trados Studio but when…

Symptoms:
When submitting concurrently large amounts of tasks to the next stage, some tasks are stuck in the Moving to next stage status.

Explanation:
A Batch Submit can contain up to 1,000 tasks per request. If the user tries to submit more than 1,000 tasks at the same time, several Batch Submit requests are created. For example, when submitting 2,300 tasks, there will be 3 batches created: two of 1,000 tasks each and…

SDL TMS 2011 SP5 CU2 now has the same set of sdlxliff-based filters as SDL Trados Studio 2014 SP2 CU8, released in February 2015 (see KB article #5375).

Symptoms:
When creating a job in SDL TMS using a Configuration supporting at least one non-wildcard Content Type and at least one wildcard Content Type that has no Excluded Extensions as well, tasks were created only for the files that matched the non-wildcard Content Types.

Explanation:
A chain of events was triggered at the database level and resulted in an incomplete list of available Content Types for job files to be associated…

Symptoms:
During testing, a number of security vulnerabilities have been found to exist with the code of SDL TMS.

Resolution:
For SDL-hosted customers, run this installer just after upgrading to SDL TMS 2011 SP5 CU2. Nevertheless, should this be missing, contact SDL Support to arrange for a hotfix to be deployed.

We are pleased to announce the release of SDL Translation Management System 2011 Service Pack 5 Cumulative Update (CU) 2. For comprehensive information on this release, please be sure to consult the attached Release Notes and any other material and 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…

Symptoms:
The Update TM stage fails for SDLXLIFF-based Content Types when trying to update a Translation Memory (TM) with an empty target segment (empty translation).

Explanation:
If an empty translation is submitted to the Update TM stage, the task is sent to Recovery because updating a TM with an empty translation is not supported for SDLXLIFF-based Content Types. ITD-based Content Types are not affected by this issue as the…

Symptoms:
In the Translation Interface (TI), when using Internet Explorer® 11 (IE11), confirming segments by pressing the Enter key applies a carriage return (new line) within the segment. The Up/DownLeft/Right arrow keys do not allow the user to navigate through the interface or un-confirm segments.

Explanation:
Certain keyboard actions differ in behavior in IE11 compared to other browsers.

Resolution:
The segment confirmation…

Symptoms:
For some languages, Trisoft DITA Content Type will send tasks to Exception at the Extract TC stage. The Task History displays the following message:

Explanation:
In SDL TMS, during the Extract TC for SDLXIFF-based Content Types, if an error occurs when retrieving the matching…

Symptoms:
While Pre-processing legacy XLS files, some formatting is lost. Reported issues:

Explanation:
During the Extract TC stage for legacy XLS files…

Symptoms:
Segments that received Translation Memory matches with missing tags can cause tasks processed with SDL XLIFF-based filters to go to Recovery after the External Machine Translation (EMT) stage.

Explanation:
For some file type filters, certain tags are essential to rebuild the target file. When the required format painting/tags are missing in the target segment, the operation responsible for rebuilding the target file…

Symptoms:
When translating an XLIFF file using the OASIS 1.2 filter (2011 or 2014), the Results from the Machine Translation (MT) provider come out truncated if the segment contains a tag.

Explanation:
When processing a segment translation received from an MT provider, the initial target format of the segment is used to map the received response tags to the existing ones in order to obtain a properly formatted translation…

Symptoms:
This post references a number of fixes included in the SDL TMS 2011 Service Pack 5 Cumulative Update 1 Combined Hotfix.

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:
Pre-Processing can result in failure when handling files from a UNC path.

Explanation:
In an SDL TMS multi-server environment, when using a UNC path for storing and managing files, Pre-Processing fails sometimes during the extraction of the translatable content. This is due to the impossibility to move the temporary extracted file to the final location (for example, to the TC\SRC folder) because Windows® caches…

Symptoms:
You cannot open in SDL Trados Studio an SDLXLIFF downloaded from SDL TMS if custom comments were added to it during custom Pre-Processing.

Explanation:
The transition of the SDLXLIFF file through custom Pre-Processing corrupts the references for the segment's custom comments in the final SDLXLIFF file. In addition, the comments are not displayed on the TMS Translation Interface.

Resolution:
The hotfix enables…

Symptoms:
In SDL TMS 2011 SP5 CU1 and earlier, pre-translated SDLXLIFF bilingual files are overwritten during the Pre-Processing stage, regardless of their match score.

Explanation:
When Pre-Processing pre-translated XLIFF-based bilingual files, the pre-translated match is overwritten during the ApplyTM stage. The initial match is replaced with the best match from the translation memory, even if the translation memory score…

Symptoms:
Review scores applied to a segment in the Translation Interface (TI) are higher than 0 (zero). Yet if the Reviewer needed to remove the initial score and reset the segment score to 0, submitting from the TI failed to update the values properly and the score remained higher than 0.

Explanation:
A faulty algorithm prevented updating the review score to 0. This hotfix enables Reviewers to reset the score to 0 if…

Symptoms:
Multiple issues have been reported around the Project TM creation process.

Explanation:
Whenever the conversion from the .tmx to any Project TM format failed, the entire Project TM process was marked as failed and did not deliver any of the Project TM formats (.mdb, .tmw or .sdltm) to users even if at least one was successful. The Project TM plug-in was reinitializing and retrying but each time failing the conversion…

We are pleased to announce the release of SDL Translation Management System 2011 Service Pack 5 Cumulative Update 1.