Symptoms:
The integration with SDL MultiTerm 2015 does not provide the correct terminology hit for Spanish (Modern) and Spanish (International).
This issue is still present, even after installing the hotfix for TMS-6976.
Explanation:
The issue may happen when the termbase contains only one language pair.
In SDL MultiTerm, some languages are defined explicitly using custom cultures, which therefore do not map with SDL…
Symptoms:
When using SDL TMS 11.1 and MultiTerm 2015, the integration does not provide any terminology hit for Spanish (Modern) and Spanish (International).
Explanation:
The language recognition works in different manners in SDL TMS and SDL GroupShare (MultiTerm). If any of the application changes the language mapping, the integration then fails.
Resolution:
This fix provides an update to re-align languages with SDL…
We are pleased to announce the General Availability of SDL TMS 11.2.
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:
In rare cases, segments containing locked content tags and placeholder tags come back from the SDL BeGlobal Machine Translation step with both tags marked with the same reference ID.
Explanation:
Tags contained in a segment can be of different nature. For each tag, a reference ID is generated. The ways these IDs are generated are different, depending on the nature of the tag. In exceptional cases, the same…
Symptoms:
At the SDL BeGlobal Machine Translation step, segments containing locked elements tags within paragraph tags sometimes fail and are sent to Recovery.
Explanation:
When receiving XLIFF segments from SDL BeGlobal, for incorporating the strings contained in <ph> tags, SDL TMS expected placeholder tags but no locked content. Consequently, the locked content could not be converted into placeholders tags.
Resolution…
TMS-11235: Tag numbers do not match in some cases after EMT propagation
Symptoms:
After a file has been translated through the EMT framework, you find duplicate segments with complex tagging information which have not been translated correctly.
Explanation:
The issue was caused by the tag matching logic between the repetition segment and the first occurrence of the segment. The logic was based on the content of the tag.
Symptoms:
The QA check for format painting, triggered either from the Translation Interface or by the system workflow step, fails for segments containing two tags that represent the same format painting entity.
Explanation:
An issue in the Core Components used in TMS caused this behaviour.
Resolution:
This fix makes TMS interprete those tags correctly and no unjustified error is found by the QA check anymore.
SDL-hosted…
Symptoms:
You search for an archived job and when you click its link to display the data, the expected page hangs and no data is populated.
Explanation:
The .js file called to populate the data for archived jobs was not configured adequately to support the new TMS 11.1 ribbon, delivered in replacement of the old toolbar.
Resolution:
The fix ensures that the archived jobs data can be viewed, using the new ribbon.
SDL…
Symptoms:
Tasks containing segments with locked tags were coming back from machine translation with incorrect tags.
Explanation:
When sending segments containing locked tags to machine translation, TMS needs to build an internal reference for those tags.
This reference is then used when the segments come back from the machine translation provider in order to place the tags adequately in the translation.
The way the…
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.
We are delivering further extensions and innovation for SDL TMS interactions with other tools involved in the localisation flow:
Translate
