Starting from SDL WorldServer 11
, you can import custom file type configurations from SDL Trados Studio
into SDL WorldServer
to ensure that your documents are processed and segmented consistently across both products and to avoid creating them twice.
Before you begin, make sure that the file type whose configuration you want to import exists both in SDL WorldServer
and in SDL Trados Studio
. Also, do not change the extension
of the configuration file you export from SDL Trados Studio (*.sdlftsettings)
If you want to import a Custom XML (Embedded Content Processor)
configuration that uses a specific processor to handle embedded content, make sure you import the configuration of the processor before importing the Custom XML (Embedded Content Processor) configuration.Note
: In SDL Trados Studio, default file type configurations are exported as empty files. Therefore, you cannot import them into SDL WorldServer. However, if you make changes to Default configurations in SDL Trados Studio
and export them as new configurations, the files will no longer be empty and you will be able to import them into SDL WorldServer.Procedure
1- Go to Management > Linguistic Tool Setup > File Types .
2- Next to the name of the file type for which you want to import a configuration, click Import
. Here is an example:
3- In the Import Studio File Type Configuration
window, click Browse
4- Find the *.sdlftsettings file you want to import, select it, and then click Open > OK
5- After the import, for the file types that use embedded content processing, the name of the imported configuration is the identifier from SDL Trados Studio.
For all the other file types, the name of the imported configuration is the name of the file. You can rename it as needed after the import by opening it in SDL WorldServer, change the name and click Save.
You cannot overwrite imported configurations. To import the latest version of an existing configuration, you have to delete it from SDL WorldServer
, export it again from SDL TradosStudio
, and import it again into SDL WorldServer
. As an alternative, you can export the configuration with a different
file name and import it into SDL WorldServer
, which will keep both versions.
Relevant only for the Custom XML (Embedded Content Processor File Type:
After you import configurations for embedded content processors
, do not rename them. The Custom XML (Embedded Content Processor)
file types that use those configurations will still be linked to their original name.