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.
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…
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…
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…
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…
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…
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…
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…
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
For full…
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…
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…
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
For full details on all that is…
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…
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…
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…
Symptoms:
After upgrading to SDL TMS 11.0.1, for tasks created using Legacy file types and only for some languages, the creation of the Project TM in the .mdb format is failing.
Explanation:
With SDL TMS 11.0.1, there is more alignment introduced in the designation of language codes. This had a side-effect on the Project TM creation for some languages, for tasks that use Legacy file types. This only affects the Project TM…
Symptoms:
When applying a match from the Translation Memory for a segment that contains curly brackets, such as the {0} placeholder, the task is sent to Recovery.
Explanation:
This error is a side effect of the additional information logging that was added in the SDL TMS 11.0.1 release.
Resolution:
Logging has been corrected and now .sdlxliff-based tasks containing segments with curly brackets are no longer sent to Recovery…
We are pleased to announce the General Availability of SDL TMS 11.0.1. This is the first update on the SDL TMS 11.x branch and delivers some important updates, new features, and defect fixes.
Included in this release:
Symptoms:
Tasks prepared with the Custom XML (Embedded Content) Pre-Processing tool have a partial Project TM or no Project TM created, despite the fact that TM matches are applied to the SDL XLIFF file.
Explanation:
When using the Custom XML (Embedded Content), the .sdlxliff file generated at Pre-Processing contains a specific file structure. This structure flags which segments are generated using the base processor and…
Symptoms:
Initial issue:
Symptoms:
For Custom Workflow steps, the Vendor User allocation remained as "Not allocated" when the authorizer submitted a task from the Authorization/PJM Authorization step, rather than using the Authorization screen to select a Vendor.
Explanation:
The situation was caused by an issue with the “Workflow Step Type” value in the database. This value is used to determine which Vendor User should be allocated by…
Symptoms:
In some cases, some tasks terminated before the Authorization/PjM Authorization workflow step were incorrectly marked as "Authorized".
Explanation:
A TMS stored procedure was incorrectly marking tasks as "Authorized" in the database, when the tasks terminated before or after the Pre-processing step, but before the Authorization step.
Resolution:
The solution corrects the procedure so that these…
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:
In a multi-server environment, sometimes when a timeout occurred on server A and server B picked up the tasks, the sequence of actions happening at database level were managed badly, generating an overlap. This overlap led to the creation of duplicate entries in the database, as well as to incorrect multiple possibilities to access the TMS task, for the same action to be performed. The overall environment isn…
Translate
