Setting up SDL WorldServer
If you are using SDL WorldServer as your translation system, you need to define Locales, Clients, Project Types, Workflows and a Filter Group for ITS before you can configure Content Manager for translation.
Note: This section provides an overview of the essential configuration tasks only. For detailed information on configuration, see the SDL WorldServer documentation.
- Defining Custom component application its+xml
To handle translations from the Content Manager correctly, you need to create a custom component to process assets with an SDL Web extension. - Defining Filter Group ITS
Filter configurations determines how the translatable assets for the project are processed. The Filter Group uses a custom component to extract the translatable text in SDL Web assets. - Creating Project Types
A Project Type is a template for creating projects. - Defining custom component types for translated content
To handle translations from the Content Manager correctly, you need to create custom components in SDL WorldServer that you then include in your Workflow. - Defining Workflow
You need to define Workflows for your SDL Web translations that include certain workflow steps. - Defining Workflow for Review and Preview in SDL WorldServer
If you want to include Review and Preview steps as part of your SDL Web translations, you need to define Workflows accordingly. Review and Preview are both optional and one or both can be defined. - Creating Clients
A Client represents a group of users who require translation services. A client can comprise an entire organization, or a department within an organization. You need to set up clients and associate them with Project Types. - Creating Locales
A locale is a user defined combination of a language specific to a place (such as English spoken in the United States) and a default encoding that is used to store content in this language (such as ISO-8559 or UTF-8).