Associating Assets with Locales
Once you have created locales and set up your folders or assets, you need to designate which folders or assets are associated with which locales. You specify this in Management > Asset Interface System > View and Change Properties.
All folders and assets have properties. A folder or asset's locale is one of the properties. Other properties include which translation memory and which term database the folder or asset should use.
For each property, a folder or asset has one of the following values:
You only need to associate the top-level folder or asset for each locale. You do not need to explicitly set the locale, or any other properties, of any subfolders or assets, since they will inherit the property from the parent.
Example: In the file system illustration in the previous section, you would set the locale for the English folder to be English, the French folder to be French, and so on; all sub-folders will
inherit the locale of the parent folder.
In the SQL database illustration in the previous section, you would set the locale at the table or identifier level that indicates language. If your level 1 identifier is language, you would set locale at this level.
After indicating which folders belong to which locales, you need to create
linkage, which defines the relationship between your source folders and target folders. You create linkage in Management > Business Rule Linkage > Linkage. That is, which folders are in the original language, and which folders are to contain the translated content.
Linkage tells WorldServer which source folders should be translated and placed into which target folders. You can link your source folder to multiple target folders if, for example, you are translating an English source into French, German, and Japanese.
NOTE: If you want to create a project to manage the editing of source files, with no target language, and no translation, you can create such a project without linkage configured.
Basic steps to creating English to French linkage in the Linkage Editor.
If you do not plan to create workflow and projects, after creating linkage you can translate, edit, or export assets from Explorer. If you do plan to create workflow and projects (recommended), proceed to the next section.
Create a user for each person who will use WorldServer, including translators, reviewers, project managers, and administrators. You will need these users when creating workflow. Add new users in Management > User Setup > Users.
NOTE: User name must be no longer than 20 characters. The password must be at least 7 characters and cannot be the same as the user name.
When creating users, you are also asked to specify user type, workgroup, and workflow role.