SDL TMS 11.0 - Product Updates

SDL TMS 11.1 - General Availability

Mariana Gheorghe — Thu, 25 Aug 2016 12:37:00 GMT

We are pleased to announce the General Availability of SDL TMS 11.1.
This is the next major update on the SDL TMS 11.x branch and delivers some important updates, new features, and defect fixes.

For more information, see SDL Community post here.
Don't forget to subscribe to this new area to receive updates notifications!

The SDL Community team.

SDL TMS 11.0.2 and SDL TMS 11.0.3 | TMS-10384 | Intermittent recoveries - No Application specific plug-in directory found

Mariana Gheorghe — Thu, 11 Aug 2016 15:47:00 GMT

Symptoms:
For instances of SDL TMS using the SDL MultiTerm integration, tasks would intermittently go to Recovery with the following error message: No Application specific plug-in directly found.

Explanation:
The Sdl.Core.PluginFramework.dll library can be called by SDL MultiTerm but also by SDL TMS when handling Custom File Types.
The issue would occur if this library is first loaded to execute an SDL MultiTerm operation by a worker process and, while this worker process is still alive then SDL TMS needs to process a file that exercises a Custom File Type. At this point, SDL TMS is trying to use the library from the Multitier location which generates an error and sends the tasks to Recovery.

Resolution:
The fix consists in performing the SDL MultiTerm operations in a different application domain thus allowing SDL TMS to load the Sdl.Core.PluginFramework.dll correctly.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

This hotfix is delivered for two different versions of SDL TMS, therefore, depending on the current installation, customers who host SDL TMS themselves should download one of the following installers:

If the TMS instance is running TMS 11.0.3, then download the installer for SDLTMS11.0.3 Hotfix for TMS-10384.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

No Pre-requisites

OR

If the TMS instance is running TMS 11.0.2, then download the installer for SDLTMS11.0.2 Hotfix for TMS-10384.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU2/Hotfix.

Pre-requisites on top of SDL TMS 11.0.2:

- Hotfix for TMS-9984

SDL TMS 11.0.3 | TMS-10698 | Locked elements in segments sometimes missing after External Machine Translation steps

Mariana Gheorghe — Wed, 10 Aug 2016 08:10:00 GMT

Symptoms:
In some cases, for segments containing locked elements, those elements would be missing when the translated strings were returned from a Machine Translation provider.

Explanation:
A generic issue was identified. Although the source segment was sent to the Machine Translation provider, when merging the translated strings back, SDL TMS was using the old target segments rather than the source segments.
This was incorrect because the target segments are not necessarily the same as the source segments before the strings are sent to the Machine Translation provider; for example, a typical workflow may have the Apply PerfectMatch and Apply TM steps before the EMT steps.

Resolution:
SDL TMS now maps the segments returned from the Machine Translation provider with the source segments, therefore preserving the elements present in the new target segments.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS11.0.3 Hotfix for TMS-10698.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

Pre-requisites on top of SDL TMS 11.0.3 (in this order):

- Hotfix for TMS-10122
- Hotfix for TMS-10540
- Hotfix for TMS-7295
- Hotfix for TMS-10643

Notes:
This issue was detected in a previous version of SDL TMS.
Per SDL Engineering policy, the Engineering team provides hotfixes for the latest release of SDL TMS to encourage our customers to run the latest version of SDL TMS to benefit from the latest features and fixes.

SDL TMS 11.0.2 and SDL TMS 11.0.3 | TMS-10643 | Incorrect identification of Placeholder tags

Mariana Gheorghe — Thu, 28 Jul 2016 16:07:00 GMT

Symptoms:
For segments containing more than one placeholder tag (also known as “self-closing” tag), the bilingual file becomes invalid after system actions like pre-processing, task upload, preview, rebuild translation. All placeholder tags are displayed as if they are identical.

Explanation:
When generating the bilingual file on an SDL TMS instance, a specific property for the placeholder tags was missing, therefore showing mistakenly all those tags as identical.

Resolution:
The property is no longer missing for placeholder tags. Any newly processed files are now valid.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

If the TMS instance is running TMS 11.0.3, then download the installer for SDLTMS11.0.3 Hotfix for TMS-10643.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

Pre-requisites on top of SDL TMS 11.0.3 (in this order):

- Hotfix for TMS-10122
- Hotfix for TMS-10540
- Hotfix for TMS-7295

If the TMS instance is running TMS 11.0.2, then download the installer for SDLTMS11.0.2 Hotfix for TMS-10643.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU2/Hotfix.

Pre-requisites on top of SDL TMS 11.0.2:

- Hotfix for TMS-10384

SDL TMS 11.0.3 | TMS-7295 | Locked repetitions get machine translated string propagated if first occurrence is not locked

Mariana Gheorghe — Fri, 22 Jul 2016 15:22:00 GMT

Symptoms:
Your file contains the same source string multiple times. The first occurrence is unlocked but the repetitions are locked. When the translated string is returned from a Machine Translation (MT) provider, this string is correctly inhaled for the unlocked string but is mistakenly overwriting the content of the locked repetitions.

Explanation:
When inhaling the data from the MT provider, there was no check to see if the repetitions were locked or not.

Resolution:
With this fix, locked repetitions will no longer be altered. Also, an extra check is also now in place to secure not overwriting repetitions that are 100% match and/or confirmed, just like for non-locked segments.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS11.0.3 Hotfix for TMS-7295.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

Pre-requisites (in this order):

- Hotfix for TMS-10122

- Hotfix for TMS-10540

SDL TMS 11.0.3 | Invalid target files for custom file types using the Custom XML (Embedded Content) pre-processing tool

Mariana Gheorghe — Mon, 18 Jul 2016 14:39:00 GMT

Symptoms:
When using a custom file type based on the “Custom XML (Embedded Content)” pre-processing tool, the target files are invalid because the custom filetype id is overwritten by the default one.

Explanation:
The issue occurred at upload, where an unnecessary reset of the filetype id to the default filetype id was applied when uploading bilingual files.

Resolution:
With this fix, the custom filetype id is preserved throughout the translation chain.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer forSDLTMS11.0.3 Hotfix for TMS-10361.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

SDL TMS 11.0.3 | Tags in locked sub-segments are wrongly represented in SDLXLIFF files when opened in SDL Trados Studio

Mariana Gheorghe — Mon, 11 Jul 2016 15:25:00 GMT

Symptoms:
Tags in a locked sub-segment are wrongly exposed in the SDLXLIFF file created by SDL TMS when a TM match is applied to such segments.
When the file is opened in SDL Trados Studio, tags in locked sub-segments are exposed as a plain text instead of the nice purple representation. As a result, the target files will be corrupted.

Explanation:
Modifications were recently made in SDL TMS to handle the order/anchoring of tags. These modifications didn’t apply yet to tags in locked sub-segments.

Resolution:
With this fix, tags in locked sub-segments will now be handled properly.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer forSDLTMS11.0 Hotfix for TMS-10540.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

Notes:
This issue does not affect word counts.
The issue does not occur if the task is opened in the SDL TMS Translation Interface.
Jobs affected with this issue will need to be recreated.

This issue was detected in a previous version of SDL TMS. Per SDL Engineering policy, the Engineering team provides hotfixes for the latest release of SDL TMS to encourage our customers to run the latest version of SDL TMS to benefit from the latest features and fixes.

SDL TMS 11.0.3 | Terminated tasks don’t have the proper values in the SDL TMS database.

Mariana Gheorghe — Wed, 29 Jun 2016 14:22:00 GMT

Symptoms:
In some cases, tasks terminated before the Authorization/PjM Authorization workflow step were incorrectly recorded in the database and had the “Terminated” status marked as false (0), no “Terminated date” and a wrongly inserted “Authorized date”.

Explanation:
A TMS stored procedure was incorrectly recording those three values.

Resolution:
The solution corrects the stored procedure so that these terminated tasks are now properly identified in the database.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS11.0.3 Hotfix for TMS-10094.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3/Hotfix.

Note:
This issue was detected in a previous version of SDL TMS.
Per SDL Engineering policy, the Engineering team provides hotfixes for the latest release of SDL TMS to encourage our customers to run the latest version of SDL TMS and benefit from the latest features and fixes.

SDL TMS 11.0.3 | SDL TMS 11.0.3 Release Announcement (June 2016)

Mariana Gheorghe — Tue, 28 Jun 2016 15:12:00 GMT

Symptoms:
You wish to upgrade the very latest version of SDL Translation Management System.

Explanation:
We are pleased to announce the General Availability of SDL TMS 11.0.3.
This is the third update on the SDL TMS 11.x branch and delivers some important updates.

Included in this release is

More flexibility for Attributes
The availability of the Job Create page from the Projects area
A number of defect fixes

For full details on all that is delivered in this release, please refer to the SDL TMS 11.0.3 Release Notes available on the SDL Documentation Center.

Resolution:
SDL-hosted customers should contact SDL Support to arrange for the upgrade to be deployed.
Customers who host SDL TMS themselves should download the installer forSdl_Tms_11.0.15811.3.iso from the following FTP site:ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU3

Users are advised to refresh their browser cache after every SDL TMS upgrade.

SDL TMS 11.0.1 and 11.0.2 | ITD-based tasks intermittently blocking the External Machine Translation process

Mariana Gheorghe — Wed, 15 Jun 2016 18:04:00 GMT

Symptoms

The External Machine Translation (EMT) intermittently ends-up completely blocked because of some ITD-based tasks failing.

Explanation

This issue was caused by an Access Violation happening inside the SDLX-ITD filter.

With the SDL TMS 11.0.1 release and in order to support the SDL LanguageCloud Machine Translation providers, the EMT needed to be refactored so that, from that release onwards, the EMT operations would start from an SDLXLIFF format.
This implied an additional conversion for the ITD-based files types from ITD to SDLXLIFF and back after the EMT is applied.

This conversion exposed an issue in the SDLX-ITD filter which would crash with an Access Violation error. This error was not handled, therefore no retry could happen and subsequently, the faulty tasks would not go to recovery but rather block the entire EMT process.

Resolution

The SDLX-ITD filter Access Violation is addressed. The intermittent EMT process issue is now fixed.

For this issue, we are providing 2 versions of this hotfix:

- One hotfix compatible with SDL TMS 11.0.1

- One hotfix compatible with SDL TMS 11.0.2

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves can download either:

- the installer for SDLTMS11.0.1 Hotfix for TMS-9667 from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU1/Hotfix.

- the installer for SDLTMS11.0.2 Hotfix for TMS-9667 from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU2/Hotfix.

Note:
This issue was detected in SDL TMS 11.0.1.
As SDL TMS is a cumulative application, this hotfix will also be available in the next release.

SDL TMS 11.0.2 | The order/anchoring of tags was lost when updating a TM with translations from SDLXLIFF where tags were shuffled around at translation

Mariana Gheorghe — Fri, 27 May 2016 16:14:00 GMT

Symptoms:
While editing a segment, the user moves tags in the target text to suit the language needs. The translation then updates the translation memory. On the next job, if the same source segment is sent for translation, although the TM returns a 100%, the order of the tags is lost.

Explanation:
When updating the TM, the tags are stored in the TM in a different format than they are represented in an SDLXLIFF file. When converting from one format to the other the tag order\anchoring from the source format was not preserved.

Resolution:
With this fix, the order of the tags is now respected in the next job, for the same source segment.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS11.0.2 Hotfix for TMS-9984.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU2/Hotfix.

Note:
This issue was detected before SDL TMS 11.0.2.

SDL TMS 11.0.2 | SDL TMS 11.0.2 Release Announcement (May 2016)

Judith de Jong — Wed, 04 May 2016 15:21:00 GMT

Symptoms:
You wish to upgrade the very latest version of SDL Translation Management System.

Explanation:
We are pleased to announce the General Availability of SDL TMS 11.0.2.
This is the second update on the SDL TMS 11.x branch and delivers some important updates.

Included in this release is

support for processing bundles from the newly released SDL Passolo 2016
a number of defect fixes

For full details on all that is delivered in this release, please refer to the SDL TMS 11.0.2 Release Notes available on the SDL Documentation Center.

Resolution:
SDL-hosted customers should contact SDL Support to arrange for the upgrade to be deployed.
Customers who host SDL TMS themselves should download the installer forSdl_Tms_11.0.14627.2.iso from the following FTP site:ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU2

Users are advised to refresh their browser cache after every SDL TMS upgrade.

SDL TMS 11.0.1 | Inconsistent default segment status of pre-translated 100% matches from ITD files in a Studio Package when opened in Studio

Judith de Jong — Thu, 14 Apr 2016 15:15:00 GMT

Symptoms:
In SDL Trados Studio, you open a Studio Package containing an ITD-based task containing segments with 100% matches received from a translation memory at pre-processing. Those segments are displaying Status = "Translated" instead of Status = "Draft".

In SDL Trados Studio, the "Translated" status is the equivalent of "Confirmed" in SDL TMS or SDLX Edit, which is an inconsistent with they way these segments are shown in the Translation Interface in SDL TMS or even when coming from an .sdlxliff-based task.

The issue does not happen for tasks created with .SDLXLIFF-based file types. These tasks display "Draft" as status in SDL Trados Studio, which is the correct equivalent of "Not Confirmed" in SDL TMS.

Explanation:
When opening the Studio Package containing the ITD, the segment status was set to Translated as if the option to "Automatically confirm 100% matches" was applied, therefore leading to a status inconsistency between the SDL TMS Translation Interface and SDL Trados Studio.

Resolution:
To make sure that users have the same experience across applications, this fix is now making sure that the behaviour for segments which received 100% matches from a translation memory is the same and it displays 100% Draft.
Additionally, we have modified the Statistical data passed to Studio for the affected tasks, so that users have the same information throughout the supply chain.

PRE-REQUISITE for this hotfix:

Hotfix TMS-9267. For more information, click here.
Hotfix TMS-9396. For more information, click here.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer forSDLTMS11.0.1 Hotfix for TMS-5097.exe from the following FTP site:ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU1/Hotfix.

Note:
This issue was detected in a previous version of SDL TMS. Per SDL Engineering policy, the Engineering team provides hotfixes for the latest release of SDL TMS to encourage our customers to run the latest version of SDL TMS to benefit from the latest features and fixes.

SDL TMS 11.0.1 | Older Java CTA not fully compatible with the latest changes in TMS 11.0.1.

Judith de Jong — Fri, 08 Apr 2016 15:08:00 GMT

Symptoms:
You have just upgraded to TMS 11.0.1 and your integration, which is using an older version of Java CTA, is no longer working properly.

Explanation:
Changes made on the latest SDL TMS release include new items in the CTA communication XMLs, of which older versions of Java CTA are not tolerant.

Resolution:
This fix currently makes SDL TMS 11.0.1 respond depending on the version of the Java CTA caller. The integration should now work properly again.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer forSDLTMS11.0.1 Hotfix for TMS-9580.exe from the following FTP site:ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU1/Hotfix.

Note:
This issue was detected in SDL TMS 11.0.1.

SDL TMS 11.0.1 | Intermittent Recovery for ITD-based tasks retrieved at EMT retrieval step

Judith de Jong — Thu, 31 Mar 2016 12:57:00 GMT

Symptoms:
You are using the External Machine Translation (EMT) for ITD-based tasks. For some larger tasks, the EmtApplyExecutor archiver plugin may time out when retrieving data from the Machine Translation provider.

When the plugin retries the retrieval action, it does not find the already created temporary .sdlxliff file and therefore throws the task in Recovery with a message indicating "Converter callback message: Warning: Unexpected error when detecting file type".

Explanation:
When the mechanism used to retrieve data from the machine translation provider was trying to retrieve data for the second time after a first time out, it was looking for that .sdlxliff temporary file.

Unfortunately, this file would have already been deleted at plugin timeout. Without that file, the retry action could not proceed and SDL TMS would be sending the file to Recovery.

Resolution:
With this fix, the temporary file is now preserved in the folder and the task proceeds properly through the EMT retrieval step.

SDL-hosted customers should contact SDL Support to arrange for this hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer forSDLTMS11.0.1 Hotfix for TMS-9396.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/CU1/Hotfix.

Note:
This issue was detected in SDL TMS 11.0.1.