Administering the WorldServer translation process
For translators and reviewers to perform their tasks as efficiently as possible, you need to manage aspects of the translation process such as locales, business rules, quality models, project types, file types, or scoping configurations.
- Basic setup for creating projects in WorldServer
After you configure your WorldServer instance for the first time, log in to WorldServer and perform a basic setup. The goal of a basic setup is to prepare all the objects required to create a project on the WorldServer 11 interface. These objects are: locales, users, workflows, project types, AIS mounts, and clients. - Working with content in the Asset Interface System (AIS)
The Asset Interface System (or AIS) is the framework that WorldServer uses to access content, which might be stored in a content management system, in a file system, in a database, or in another format. - Setting up locales for translation
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 used to store content in this language (such as ISO-8559 or UTF-8). In WorldServer, locales are treated as groups to which you can add users. - Managing project types
Project types are templates for creating projects. Every time you create a project in WorldServer, you also need to select an appropriate project type. You can add, modify, or delete project types by going to Management > Business Rule Linkage > Project Types. - Configuring business rules
In WorldServer, you can use business rules to automate project creation and notification delivery. For example, you can configure a business rule to check every day for tasks whose due date is approaching and to send an email message to the assignees and to the project managers, reminding them of those tasks. The same applies to project creation: you can configure a business rule to create a new project each time a user modifies an asset under a particular AIS path. - Workflows and process automation
A workflow defines a standard, repeatable process for translating and handling content. Workflows consist of steps and transitions that link the steps together, imposing the order in which the steps occur. - Term database management
A term database, also known as a terminology database or termbase, is an organized record of controlled vocabularies and, optionally, their standard translations. - Translation memory management
By using translation memories, translators can reuse previous translations, reducing translation time and effort and increasing consistency. - Configuring machine translation adapters
WorldServer supports machine translation as an alternative source for fuzzy matches. During the leverage process, WorldServer uses both translation memories (TMs) and machine translation (MT) to produce fuzzy matches. The leverage rules are the same for matches resulting both from TMs and from MT: SP/ICE matches are preferred, then 100% matches, then fuzzy matches. - Managing file types and file type configurations
File types are the main components responsible for segmenting assets in WorldServer. You can have multiple configurations for the same file type, to suit the various types of assets that you need to process. - Managing file type groups
File type groups are particularly useful if you want to assign multiple file type configurations to the same AIS property or to configure multiple file types for a single MIME type. - Scoping modes
Scoping modes are ways in which WorldServer segments assets and calculates leverage from translation memories (TMs). There are two scoping modes: Studio-aligned and WorldServer 9.x. Starting with WorldServer 10, the Studio-aligned scoping mode is the default scoping mode used to create projects. - Scoping configurations for project management
Scoping is the process of comparing content to be translated with previous translations, to determine the remaining translation cost and effort. A scoping configuration is a collection of ranges that describe the quality of a match from the translation memory. Use scoping configurations to determine how many words there are in a particular project and how much the translation might cost based on a selected cost model. - Preparing cost models and cost model rules for scoping
Use cost models to estimate localization costs for projects and cost model rules to apply additional charges and discounts. - Quality models for the review process
Use quality models to specify different error categories and severities that will be used when reviewing translations.