SDL Managed Translation Connector

You have to provide valid credentials here.

Figure 1. Account Configuration

The connector creates new projects for every translation job (which may contain several XMLs) using a project creation option.

Therefore, pleases click on Update Projects and Workflows to fetch all available project creation options.

SDL uses its own language codes whereas FirstSpirit uses language abbreviations.

Consequently, you have to tell SDL which language code to use for a given FirstSpirit language.

Figure 2. Languages

Conveniently, the list will be updated whenever you query for project creation options.

In order to make an SDL project available to TranslationStudio, you have to create a new project by clicking on the button add.

Figure 3. Project Settings

The project created here will be made available to TranslationStudio’s language mappings requires the following information:

Please do not forget to save your changes

The connector monitors the translation progress and downloads files marked as completed automatically.

When a translatable file is stored in an SDL project, a unique identifier (UID) is created by SDL which allows the connector to specifically find this particular file at a later stage.

This UID is stored by TranslationStudio and used to monitor the translation progress of the respective file. After a translated file has been downloaded, its UID is removed from TranslationStudio’s monitoring database.

Importantly, the connector does not change any states, neither of individual files not of the respective SDL project.

If you upload a file into SDL manually TranslationStudio will not be able to monitor the file’s progress sine its UID is not known. For example, you might have downloaded a translatable XML file from SDL to check its content (and have it removed from the SDL project). Thereafter, you may wish to upload the file to SDL again and have it translated. However, since the UID has changed, TranslationStudio will not be able to monitor this file. Fortunately, this is a rather rare scenario but it is sufficient to provide an insight into how the SDL connector works.

Since there are a few things to configure, it is recommended to create a working configuration in a stage or development environment which allows you to test your SDL and TranslationStudio settings extensively.

It is recommended to submit only a single file first instead of bulk files.

Once you find that all settings are correct, you then transfer those settings to your production environment.

The following list of potential issues might be helpful to avoid problems:

The connector cannot access SDL
Assuming that the credentials provided are correct, please make sure that the SDL api URL is accessible by the server hosting TranslationStudio. You may find further error notifications in TranslationStudio’s log file.

Although some files are uploaded, some translatable files do not appear in SDL
This is a common issue but solved just as easily. Usually, it is related to missing language configurations. Please make sure that both, the source and target language, have a correct language code assignment.

Translated files are not being imported
There are a few potential causes for such a situation.

First, make sure that the respective file marked as completed. A mere 100% completion indicator does not suffice. TranslationStudio will only download files that are marked as completed specifically.

Second, you may want to check whether the file has been downloaded and is still waiting to be processed (see TranslationStudio’s working/translated folder).

Finally, you may always consult the log files to see if there is any other problem, such as rules not met by page or section templates (these may have been introduced only after the translatable file has been stored in SDL).

Please note that you can always download a translated file manually and store it in TranslationStudio’s working/translated folder.

SDL does not show a 100% match although all terms should be known
This is an issue with SDL and is not related to TranslationStudio.

Please do not hesitate to contact your helpdesk if you experience other issues not mentioned above.