Documentation Center

Known issues in Translation Manager

The following list describes issues that are known to exist in Translation Manager.

Authorizing SDL BeGlobal Translation Jobs
Problem: You can authorize all translations of SDL BeGlobal Translation Jobs, even for Target Publications for which you do not have access rights and permissions.
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 example tcm_1-302_ecl_0-you-196-dist-file.cmp.
Solution: The ECLItemName should be used instead of the StubItemName so that you can trace the item back to the one in Content Manager.
Authorization Required column is present when SDL WorldServer is configured

Problem: If SDL WorldServer is configured, the Authorization Required column should not be visible in the user interface for Translation source configuration and Translation target configuration sections.

Solution: If SDL WorldServer is configured, ignore the setting as it is only relevant for SDL TMS and SDL BeGlobal.

A Javascript error is thrown in Internet Explorer 9 and 10 when sorting on To-From

Problem: In Internet Explorer 9 and 10, when you add an item to an existing job, in the dialog that opens a Javascript error is thrown when you try to sort entries by clicking the From/to column.

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.