Known issues in Translation Manager
The following list describes issues that are known to exist in Translation Manager.
- Performance issue in browser when using the SDL WorldServer v11 API and loading a lot of translation data
- Problem: If users create one or more translation jobs adding up to multiple megabytes of translation data, and if they use the WorldServer v11 API, the Translation Jobs screen showing the jobs may take too long to load in the browser.
- Translation review comments do not flow from SDL TMS to SDL Web
- Problem: This limitation applies to the following example scenario: a reviewer rejects in SDL Web, with a comment to make a specific change. The translator or reviewer in SDL TMS subsequently adjusts the translation, but not in the same way the SDL Web reviewer suggested. The SDL TMS user now cannot communicate details back to the SDL Web reviewer.
- Names of ECL item sent for translation
- Problem: Currently, when an ECL item is sent for translation it is displayed on the translation management system as a string using the format
TCMURI_StubItemName, for exampletcm_1-302_ecl_0-you-196-dist-file.cmp.
- Due date set incorrectly in older versions of SDL TMS
-
Problem: In SDL TMS versions 2007 SP4 to 2011, the due date of a translation job is always set to the creation date of the job plus 1 week, regardless of what the required date was sent in the job request.
- Refresh browser cache after installation
-
Problem: After you have installed Translation Manager, the Translation Manager functionality does not appear in the Content Manager Explorer interface.
Solution: Refresh your browser cache to view the changes in the Content Manager Explorer.