Setting Up Linkage
This chapter describes how to create linkage, which defines the relationship between the source folders (which contain assets in the original language) and the target folders (which contain translated content). In the Basic Setup Guide, click Set Up Linkage or go to .
Linkage determines:
- Which assets are translatable (or which folders contain translatable assets).
- Where the target version of a translated asset should be stored the first time it is translated.
As an example, the following figure shows linkage which has been configured from a folder called English_Website (containing assets in English) to a folder called German_Website (containing assets in German).
Figure 1. Linkage between English Website and German Website
In this example, WorldServer allows translation of assets in the English_Website folder to German. The first time File_A in the English_Website folder is translated from English to German, an asset called File_A will be created in the German_Website folder.
For a given pair of locales, you do not need to link every source folder and asset with every target folder and asset. Only link the top-level folder of the source locale to the top-level folder of the target locale. By default, all child folders and assets under this top-level folder inherit this linkage.
You can link your source folder to multiple target folders if, for example, you are translating an English source into French, German, and Japanese.
We recommend that you create workflow and projects to assist you with your work in WorldServer. After you create linkage, make sure you read and follow the instructions in Authentication Types and then to Workflow Design. If you do not plan to create workflow and projects, you can start to translate, edit, or export assets from Explorer immediately after creating linkage.
If you want to create a project to manage just the editing of source files, with no target language, and no translation, you can create such a project without linkage configured.