Idiom® Technologie's mission is to fill the need for an enterprise-class software solution that could enable large global enterprises to achieve their globalization objectives.
Idiom® Technologies was founded in January 1998. Its mission was to fill the need for an enterprise-class software solution that could enable large global enterprises to achieve their globalization objectives. The company introduced WorldServer™ later that year.
Today, WorldServer is the solution of choice for the entire globalization supply chain. Global enterprises such as Adobe Systems, Baxter Healthcare, eBay, Mattel, Motorola, Oracle, Travelocity.com and Continental Airlines choose WorldServer software to power translation and localization operations.
These companies are joined by innovative Language Service Providers like iSP, Localize Technologies, One Planet and WH&P that use WorldServer to add value to their client offerings. And with WorldServer™ Desktop Workbench, independent translators freely enjoy the benefits of WorldServer-enabled translation and localization.
Idiom is headquartered in Waltham, Massachusetts. With offices throughout North America and Europe and a partner network that spans the globe, Idiom is ideally positioned to accelerate and optimize your globalization efforts.
These recommendations apply to all servers. See also the additional recommendations for your operating system.
Additional Recommendations for Windows Servers
The following additional recommendations apply if you use a Windows server:
Additional Recommendations for Solaris and Linux Servers
The following additional recommendations apply if you use a Solaris or Linux server:
This section explains the steps necessary to install WorldServer on a Windows NT or Windows 2000 server.
To install WorldServer
To create the WorldServer content database after installation
If you did not specify to automatically create the database during installation (step 10 in the previous procedure), you need to do the following:
This section explains the steps necessary to install WorldServer on a Solaris or Linux server.
Cross-Platform Database Configuration
If you have WorldServer installed on Solaris or Linux and will use a SQL database, follow the configuration steps in this section. If you have the SQL Server client tools installed, complete the following steps to seed the Database:
A locale is a country, language, or site for which content is globalized. You create a locale for each language or country you plan to use with WorldServer, including the source language and each target language. The source language is the language from which you are translating, and the target language is the language to which you are translating.
Example: You have an American English intranet site and want to globalize this site for your offices in France, Germany, Japan, Spain, and Mexico. Create a locale for your source American English site, and a locale for each target site. Although both Spain and Mexico sites will be translated into Spanish, the dialect is different, and there are different employee benefits available to each, so you should create a locale for each.
Create locales at Management>Business Rule Linkage>Locales. When creating a locale, you select the encoding of the locale's content. For the locale associated with your source content, specify the encoding in which the content is stored. For a locale associated with target content, the encoding you specify will be the encoding of content that is created or modified and saved in WorldServer. Changing the encoding of a locale does not automatically change the encoding of the corresponding content; if you change the encoding of a target locale, all existing target content will still be stored in the previous encoding, while any new content, or content that is saved in WorldServer, will be saved in the new encoding.
To work on your content in WorldServer, you need to specify where it is and in what type of structure. You do so in Management>Asset Interface System>AIS Mounts.
The mount is your point of connection. WorldServer provides the ability to add the following content connections:
File System Connection
In a file system connection, where your content is in a file system directory, the mount is the top-level folder or directory in which all of your content is stored. Specify the name, type, and path of your mount.
After creating your mount, you add folders in Explorer. Within your mount, you may already have a directory structure for your source files. When globalizing this content, you should replicate the source directory structure and content for each target language. Although WorldServer will create target folders and files as you translate material, it does not copy folders and files that do not have translatable content (for example, a folder of image files). You can do this copying directly in Explorer. You should have a top-level folder for each locale.
You can achieve this structure by adding the folders in your file system, or by copying and adding folders in Explorer.
SQL Database Connection
The SQL connector requires that you have a special license from Idiom. Once you obtain a SQL license key, navigate to Management > Administration > Licenses and add the SQL license key provided by Idiom Professional Services.
In a SQL database connection, where your content is in a SQL database, the mount is the database.
Once you specify the database configuration, you need to specify and configure the tables that you can access through WorldServer.
You begin to configure a table by configuring its columns. Specify the following for each column:
You then specify the hierarchy that will appear in Explorer.
In Identifier Hierarchy, at the top level is the table, then the column or columns you designated as identifier columns. If you have more than one identifier column, you can change the order of the columns as needed by clicking "Move up" (for example, if you have "ID" nd "language" as your identifier columns, you may want "language" to be higher in the Explorer hierarchy than "ID"). Clicking "Join" will join the columns as a hierarchy level (for example, if you join language and locale identifiers, "English+England", "English+US", and so on would be hierarchy levels).
You also choose one of the identifiers to be the asset level. The asset-level identifier is the identifier that will become an asset in Explorer; it is the lowest hierarchical level visible in Explorer. Content that is hierarchically lower than the asset-level is contained within the asset-level. For example, you may want to designate the language as the asset level, which means that all of the content for the table that is in a particular language will appear as one asset in Explorer. This saves you from having a very large number of assets generated by individual strings.
Interwoven TeamSite Connection
The TeamSite connector requires that you have a special license from Idiom. Once you obtain a TeamSite license key, navigate to Management>Administration>Licenses and add the TeamSite license key provided by Idiom Professional Services.
To configure a TeamSite connection, you need to first install and configure all necessary third-party software, and install the command-line tool server on the machine where TeamSite is installed.
To install the command-line tool server
The ClearCase connector requires that you have a special license from Idiom. Once you obtain a ClearCase license key, navigate to Management > Administration > Licenses and add the ClearCase license key provided by Idiom Professional Services.
The section below provides "Config Spec Template" examples that may be useful when configuring the ClearCase mount.
Config Spec Template Examples
Config Spec Templates need, at a minimum, a Name and a Config Spec. For the most part, the config spec you enter is a standard ClearCase config spec. For example, if you wanted to create a plain main-LATEST config spec template you could just enter:
element * CHECKEDOUT
element * /main/LATEST
If you want to get more advanced, you can use template parameters to allow the users (when they create a "branch") to specify parts of the config spec. Template parameters work like substitution arguments and are specified in the config spec itself. The parameter definitions are located in the config spec comments and affect the final generated contents of the config spec. The simplest of the parameters is the "VAR" parameter. This takes the form:
$VAR name Prompt
Where 'name' specifies a replacement token. The Prompt is the prompt provided to the user creating the branch from this template. For example, the following template could be defined:
# $VAR base Enter the branch type name
# $VAR label Enter the label to branch from
element * CHECKEDOUT
element * .../
Notice how the $VAR definitions are in the config spec comments - this is required. Also, note that the config-spec definition uses the "
In addition to the $VAR parameters, we support three additional types of parameters. Parameters can be of type $SELECT to restrict the substitution to a list of predefined choices. The syntax for this parameter type is:
$SELECT name [ choice1 | choice2 | ... ] Prompt
When creating a 'branch', the user will have to select the option from the choices specified here. Insert as many choices as desired, but remember that all parameter definitions have to be on one line.
Similar to $SELECT parameters we also offer $BRANCH and $LABEL parameters. These types simply prompt the user to select from the branch types or label types already defined in ClearCase. The syntax for these commands is:
$BRANCH name Prompt
$LABEL name Prompt
For example, using the three selection types in a template:
# $BRANCH active_branch Select branch to work on
# $LABEL base_label Select label to branch from
# $SELECT when [ now | yesterday ] What timestamp of 'main' do you want
element * CHECKEDOUT
element * .../
element * /main/LATEST -time
Aside from the template arguments, we also support one template command: the ability to create new branch types. The syntax for this is quite simply:
As opposed to template arguments, where the user supplied string is substituted for the occurrences of the parameters
# $VAR base Enter the branch name
# $VAR label Enter the label to branch from
element * CHECKEDOUT
element * .../
This will cause WorldServer to create the branch type automatically once the user creates an instance of a branch using this template. Note that the $MKBRTYPE command needs the angle brackets around the variable it is using (otherwise WorldServer would create a branch type called simply "base"). Arguments can be combined to enforce naming conventions or almost anything. For example:
# $VAR base Enter the branch name
# $VAR user Enter your username
# $VAR label Enter the label to branch from
# $MKBRTYPE auto_
element * CHECKEDOUT
element * .../auto_
Eprise Participant Server Connection
The Eprise connector requires that you have a special license from Idiom. Once you obtain an Eprise license key, navigate to Management > Administration > Licenses and add the Eprise license key provided by Idiom Professional Services.
Before configuring the Eprise mount, you need to install and configure all necessary third-party software and install the Participant Server (PS) Deputy.
Idiom recommends that WorldServer, the PS Deputy, and PS reside on separate servers.
Although the deputy can run on the same server as WorldServer or PS, performance is usually better using the recommended architecture. The deputy is a CPU intensive application that can degrade the performance of other applications running on the same server.
Installing the Participant Server Deputy
The PS deputy manages communication between WorldServer and Participant Server. If you are planning to use an architecture other than the one recommended by Idiom, please consult with Idiom Professional Services as to the correct installation procedure to use.
The PS deputy server requirements are as follows:
To install the PS deputy, do the following:
Configuring the Participant Server Deputy
If for any reason you want to change the deputy configuration, you must locate and modify the deputy.properties file located in the deputy installation directory.
The following summarizes the settings you can modify:
After making any changes, you need to stop and start the Idiom Process Monitor service.
After installing and configuring the PS deputy, you need to enter the Eprise license key provided by Idiom Professional Services in Management > Administration > Licenses. Then you can configure your Eprise mount at Management > Asset Interface System > AIS Mounts.
The BroadVision connector requires that you have a special license from Idiom. Once you obtain an BroadVision license key, navigate to Management > Administration > Licenses and add the BroadVision license key provided by Idiom Professional Services.
Before configuring the BroadVision mount, you need to install and configure all necessary third-party software.
The CVS connector requires that you have a special license from Idiom. Once you obtain an CVS license key, navigate to Management > Administration > Licenses and add the CVS license key provided by Idiom Professional Services.
Before configuring the CVS mount, you need to install and configure all necessary third-party software.
The X-Hive connector allows an X-Hive database to be mounted in WorldServer and for core X-Hive objects (libraries, documents, and blobs) to be manipulated through the WorldServer Asset Interface System. The connector exposes AIS nodes for X-Hive libraries and documents. Newly created documents contain the starting XML specified in the mount configuration. While writing XML documents, the connector automatically assigns unique identifiers as the attributes of certain elements defined within the mount configuration. The X-Hive connector also allows the user to predefine XQuery templates, enabling the non-technical user to easily utilize the power of XQuery for finding data contained within the X-Hive database.
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.
Workflow automates the globalization process with steps, assignees, and logic. When you create a project, tasks are created and assigned to the assignees (users or workflow roles) specified in the first workflow step. Once that first step is completed, the task moves to the next step and assignees in the workflow. Each asset follows the workflow individually; that is, in a project, one asset could be complete, while another has not progressed past the first step.
NOTE: You can optionally use workflow roles if you repeatedly use the same multiple users for a particular role, for example, French translation.
You can create different workflows to meet your needs. You create workflow in the Workflow Editor, accessed from Management>Workflow>Workflows.
In the Workflow Editor, you create steps and transitions between the steps. The Workflow Editor provides the following five types of steps:
You create a transition between each step to indicate the path of the workflow. You can use transition order when a step can proceed in more than one possible direction. This transition order determines the order in which the next steps appear in the Complete Task dialog box.
A project pulls together all the pieces - the source and target assets, their linkage relationship, and the workflow. You create a project in the Explorer. In addition, when you create a project, you specify a workgroup.
Once you create a project, tasks are assigned to the users or workflow roles specified in the first workflow step. A task is an asset that follows the steps in the designated workflow. If the assigned user is set up to receive email notification (in Tools > Personal Preferences), that user will receive an email message with information about the assignment.
NOTE: Email notification must be configured in Management>Administration>Email for email notification to function.
You can access the new project from Assignments > Projects. The task list for the project contains all the tasks for the project. The tasks are assigned to the assignee(s) that were specified in the workflow for the project.
This is the minimum that you need to do to create a project. There is additional setup required to use the advanced features of WorldServer, including translation memory and term databases.
This chapter outlines the additional setup you need to do to take advantage of the WorldServer advanced features. The setup steps in this chapter are not required to create a project in WorldServer; however, the functionality enabled by completing this setup allows you to optimize your content globalization process through WorldServer. Complete the setup for each advanced WorldServer feature that you want to use.
Creating User Types
A user's user type determines what WorldServer functionality that user can access. You may want to have multiple levels of access, based on the user's function in the globalization process. For example, you may not want to allow a translator to have the ability to modify the translation memory. The user type allows you to specify on a granular level what the users of that type can access. You create user types in Management > User Setup > User Types. You specify a user's user type in Management > User Setup > Users.
By default, WorldServer provides an Administrator user type, which allows access to all functionality, and a Translator user type, which allows access to functionality that a Translator would typically need. You can modify these user types or create new user types.
Creating Content Categories
The content categories you create in Management > AIS Categories > Content Categories are used for the WorldServer Content Wizard on the Home tab. When you create/upload an asset using the Content Wizard, you are presented with the content categories to determine the type of asset. This is also where you point to WorldServer entry forms you may have created.
Creating Entry Forms
Entry Forms forms allow inputting and editing of content with the aid of a custom HTML form, which can provide users with controls such as WYSIWYG editing, input validation, and content preview. In addition, Entry Forms provide a powerful means for administrators to integrate WorldServer content creation, editing, and validation with any of their existing systems.
WorldServer 6.5 introduces support for writing Entry Forms in Microsoft's .NET framework. A WorldServer DLL is provided which allows custom code to communicate with WorldServer in a much the same way that Java-based Entry Forms do.
By default there is one workgroup that you can specify when creating a project. However, you can use multiple workgroups to indicate business units or related topic matter. This can help you track the progress of projects and issues related to a particular subject or business unit.
Example: Your e-commerce site has three distinct areas: personal computers, software, and computer accessories. You have different groups of people with expertise in each of these areas. Thus, you have a personal computers business unit, a software business unit, and an accessories business unit. You can create workgroups to correspond to each of these business units. When you create a project, you specify the appropriate workgroup. You can then use the "View" drop-down menu to sort the project and issues lists for your locales and workgroups.
You create workgroups in Management > User Setup > Workgroups.
You can customize certain components in Management > Administration > Customization.
The WorldServer online help provides detailed information about configuring and using these custom components. Idiom Professional Services can provide you with information about any additional custom components.
Setting up Default Workflows
The default workflow table (Management > Business Rule Linkage > Default Workflow Table) allows you to specify which workflow to use by default when globalizing a particular source asset for a particular target locale. Although this is merely a tool of convenience when manually creating a project, it is a necessity when creating a project automatically with a rule.
Creating Rules and Recurrences
A rule allows you to automate project creation and/or notification under specified circumstances. Create rules in Management > Business Rule Linkage > Rules. This reduces the amount of manual change checking and project creation a project manager has to do. It also insures that projects are created or notification sent on a regular basis to keep the globalization process up-to-date.
Rules can be executed manually or on a recurrence. A recurrence is a time schedule that you create in Management > Business Rule Linkage > Recurrences.
NOTE: If you plan to execute a rule on a recurrence, you need to create the recurrence first.
Example: You want to be notified and have a new project created for any new or changed assets in your top-level source folder (/Web/English). You want WorldServer to check for new or changed assets daily at midnight. First you set up default workflow for the source-target pairs about which you want to create a rule. Next you create a recurrence that specifies every day at 12:00 AM named "Daily-Midnight". Next you create a new rule that specifies what you want to occur. Your final rule will look something like: For all new or changed assets under /Web/English, initiate project New Material for locales German and French and workgroup default following default workflow and send notifications to user Admin (admin) about assets. Execute this rule on schedule Daily-Midnight.
The rules creation wizard walks you through the steps of creating a new rule.
NOTE: To have a rule automatically create a project, you need to have a default workflow specified for each source-target pair for which you are creating a project. Specify default workflow in the default workflow table.
By default, routine WorldServer maintenance tasks are performed daily at 1:00 a.m. If you want to perform these tasks more or less frequently or at a different time, you need to create a recurrence named GC_TASK (casesensitive) with the days and times you want to perform maintenance tasks.
Using AIS Masks
An Asset Interface System (AIS) Mask is a named collection or "basket" of other specific WorldServer objects that a WorldServer administrator
associates with an AIS mount or folder. When users access and process assets in that folder (or its sub-folders), WorldServer displays only the object instances that are defined in the associated AIS Mask.
Using AIS Triggers
AIS Triggers are actions invoked by an event in the AIS (save, create, etc.). AIS Triggers provide the ability to add custom extensions to the basic functionality. This mechanism acts as a notification engine when changes to AIS contents are made.
To use triggers, you do the following:
Creating Workflow Roles
When creating workflow, you can specify individual users or workflow roles. Using workflow roles allows you to specify a group of users in a click as opposed to having to select each user. It also decreases your workflow maintenance, allowing you to reuse a workflow for multiple locales with multiple users. Create workflow roles in Management > Workflow > Workflow Roles.
Example: You work with several French, Spansh, and Japanese translators (each a member of the appropriate locale). You can create a Translator workflow role that includes all of your translators. Then you can design a workflow for translation projects that specifies this workflow role as the assignee instead of having to design three separate workflows, one for each locale. This allows you to reuse workflows for different locales. When you create a project that needs to be translated into the three languages, you can use the same workflow for the three projects (or project group).
NOTE: When a task is assigned to multiple users, one of the users claims the task to indicate that she will perform the necessary action (for example, translate) for the task.
Setting up Translation Memories
Translation memories make it easier to translate the same files as they change multiple times, ensuring consistency and reducing the time and cost of translation. When you translate an asset or task and save to translation memory, the source and target pairs populate the translation memory. When you translate those assets again, all unchanged source segments will have a 100% target match. The source segments that may have changed slightly will have a lower-scoring match that you can access in the Translation Workbench in the browser by clicking the translation memory button for the segment.
You can use the default WorldServer translation memory for all your assets, or you can create multiple translation memories to meet different needs. You set up translation memories in Management > Linguistic Tool Setup > Translation Memory Setup.
Example: If you are globalizing your corporate Web site, your intranet site, and your software, you could create a different translation memory for each globalization effort. This may help increase the amount of useful translation memory matches, and reduce inaccurate or inappropriate matches.
If you are using multiple translation memories, be sure to set the translation memory property for your top-level target assets in Management > Asset Interface System > View and Change Properties.
NOTE: Tools > Personal Preferences provides default settings for translation memory matches.
Creating TM Groups
TM groups are a means of associating multiple translation memories under a single organizational unit. A TM group offers the choice for looking up a text in multiple TMs at once.
A TM group consists of one of more "Lookup TMs", used for searching, and a single "Update TM" for saving translations. Each one of the Lookup TMs has a different priority within the TM group. The Update TM can be any of the TMs available in WorldServer, and does not need to belong to the group.
Example: Typically, TM groups are used for associating TMs of related languages like Spanish-Mexico or Spanish-Argentina, where it would be useful to perform lookups in more than one TM at once.
Another typical use is for grouping a read-only TM and a write-only TM. The read-only TM would be a master TM that has all entries reviewed and presumed to be correct. On the other hand, the write-only TM will hold only new translations that require review before being imported into the master TM
Setting up Term Databases
A term database allows you to manage standard terminology that must be translated in a particular way every time, such as a tag line or feature name. The term database is useful when you are translating in the Translation Workbench in the browser, where you can click the term database button for a particular segment to view applicable term database entries. You can also access term database entries from the Translation Workbench for Windows. This helps in translation consistency and efficiency.
You can use the default WorldServer term database for all your assets, or you can create multiple term databases to meet your needs. You set up term databases in Management > Linguistic Tool Setup > Term Database Setup.
Example: If you are globalizing your corporate Web site, your intranet site, and your software, you could create a different term database for each globalization effort. This may help increase the amount of useful term database matches, and reduce inaccurate or inappropriate matches.
If you are using multiple term databases, be sure to set the term database property for your top-level target assets in Management > Asset Interface Syste > View and Change Properties.
Creating TD Groups
TD groups are a means of associating multiple term databases under a single organizational unit. A TD group offers the choice for looking up a text in multiple TDs at once.
A TD group consists of one of more "Lookup TDs", used for searching, and a single "Update TD" for saving entries. Each one of the Lookup TDs has a different priority within the TD group. The Update TD can be any of the TDs available in WorldServer, and does not need to belong to the group.
When you create a cost model for scoping, you specify the cost per word for each translation memory matched segment category. That is, you fill in a cost (if any) for words with ICE (in-context exact) match, 100% match, a cost for words with 75%-99% match, and so on.
You can configure the ranges that appear when creating a cost model and when scoping an asset or task. There is always a category for 100% matched segments. You can change the default scoping categories in Management > Linguistic Tool Setup > Scoping Configuration.
NOTE: If you choose to change the default configuration, you must do so before creating cost models and projects. Any cost models and scoping information created prior to changing the scoping configuration will be unusable.
Setting up Cost Models
When you determine the cost (with the scoping tool) of a project, folder, or asset, you select a cost model. You can determine the word count scope without a cost model. You can create multiple cost models to meet your needs (for example, if you have multiple translation vendors with different pricing). Set up cost models in Management > Linguistic Tool Setup > Cost Model Setup. In addition, you can configure the ranges that appear when creating a cost model and when scoping an asset or task.
You can configure some aspects of the markup filters in Management > Linguistic Tool Setup > Filter Configurations. You can have multiple filters configured for each filter type.
All WorldServer folders and assets have properties. A folder or asset's properties determine the associated locale, the translation memory that is used during translation, the term database in which you search from the translation workbench, and other behavior. The Change Properties dialog box is where you set and modify properties for your folders and assets (Management > Asset Interface System > View and Change Properties).
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 property. You do not need to explicitly set properties for sub-folders or assets since they will automatically inherit the property from the parent.
Creating Useful Links
Useful links are URLs that are displayed on the Home tab. You can provide links to corporate style guides, glossaries, and the like. Useful links are accessible to specified locales and workgroups. Configure useful links in Management > Administration > Useful Link Setup.
You configure the email a user receives for new tasks, issues, and notifications (as set in their personal preferences) in Management > Administration > Email. To take advantage of email notification, specify the message text, who the email is from, and the SMTP server. In addition, for email notification to function, valid email addresses must be specified for users (Management > User Setup > Users), and users must have email enabled in Tools > Personal Preferences (default setting).
Setting up Personal Preferences
Each user has a set of personal preferences. You can only set your own preferences. You can choose a variety of personal preferences for email notification, user interface appearance, translation memory matches, and others. Personal preferences are configured in Tools > Personal Preferences.
Visual SourceSafe Integration
WorldServer uses workflow steps to automatically check files out of Visual SourceSafe when translation begins, and back into Visual SourceSafe when it is complete. These workflow steps only work on a Windows platform. Visual SourceSafe integration requires an additional Idiom license key.
All Visual SourceSafe parameters are configured general.properties (typically C:\Program Files\Idiom WorldServer\tomcat\webapps\ws\WEBINF\classes\config\general.properties). The following values need to be configured:
Below is a sample configuration:
# Visual SourceSafe configuration
vss_ss=C:/Program Files/Microsoft Visual Studio/VSS/win32/SS.EXE
NOTE: You need to restart WorldServer any time that you make a change to general.properties for it to take effect.
This automatic step checks a source or target file out of Visual SourceSafe (VSS). If the file does not exist in VSS, WorldServer will automatically create subprojects as needed and add the file to the VSS database. If the target file does not exist on the file system, WorldServer will automatically create an empty file in the appropriate target directory. Below is a summary of the step's parameters and return values.
This automatic step checks a source or target file into Visual SourceSafe. If the file is not checked out, the step is skipped. Below is a summary of the step's parameters and return values.
VSS and WorldServer on Separate Servers
VSS check-in/out can work with WorldServer running on one server, and the VSS database running on another. Please do the following:
WorldServer Service Desk is a Web application for business users and other content owners to submit documents to be translated, monitor their progress, and download translated documents, without the need to know how to use WorldServer itself.
This chapter describes how to set up Service Desk for use within your own organization. It describes these high-level steps:
Acquiring and Installing a License
Idiom WorldServer Service Desk requires a license. To install it:
Creating Source and Target Folders
In this section, you create folders accessible to WorldServer. These folders will contain source content and target content.
We recommend that you organize the folder hierarchy as follows:
Idiom recommends this organization because locales require configuration and setup, but the settings you establish are inherited at lower levels in the file hierarchy. It is also valid to organize with document-type at a higher level of the hierarchy, but doing so requires much more work when you add a new locale.
As an example, say that your project requires languages English, German, and Spanish. In addition, you have workflows for two document-types, Marketing and Sales. We recommend that you organize folders as follows, where the first level is the AIS mount:
We recommend that you design your own file hierarchy now and refer to it as you work through the steps in the next few sections.
Establishing a Mount
To add folders:
Creating and Associating Locales
Use WorldServer to create locales and associate them with the folders you created earlier.
To create a locale:
To associate locales to the folders you created earlier:
Creating Linkage between Source and Target Locales and Folders
A linkage establishes a relationship between two locales. More specifically, a linkage associates a source locale with its target. For example, say that for your project, your source is in English and you are translating to German and Spanish. You need to create a linkage between English and German, and another between English and Spanish, as follows:
Create Service Desk users. For example, create a user who does project management in Service Desk and WorldServer, and create nother user who submits files to be translated:
Creating a Vendor (optional)
Decide which translation vendor you will use to estimate the cost of projects submitted by Service Desk users, or create a new one:
Creating a Cost Model (optional)
Create a cost model to automate the process of estimating the cost of translations:
NOTE: You can create multiple cost models in WorldServer. Service Desk uses the cost model you most recently selected to use with Service Desk (the Use for Service Desk Projects option.) If you have not selected any cost model for use with Service Desk, your Service Desk users cannot estimate costs before submitting content to be translated.
Creating a Workflow
Work with someone who knows how to create workflows to create a workflow for each document-type you are working with. The basic steps are:
Adding Content Categories
Content categories correlate to the document-type folders you created earlier. As an example, if you created folders for Sales and Marketing, you might want to create content categories for marketing materials and sales white papers. In this step, you create the document type for which you created folders earlier:
Setting up Default Workflows
When you set up default workflows, you are associating the document types with the workflows. Proceed as follows:
Customizing Service Desk
You can change the appearance of Service Desk pages by modifying styles in the servicedesk.css file. If you are running WorldServer on Windows using the Tomcat server installed by Idiom, the file is in the following directory:
You can also replace the header graphics with a graphic of the same dimensions. If you are running WorldServer on Windows using the Tomcat server installed by Idiom, the graphics are in the following directory:
In this release, you cannot add text to Service Desk pages, nor can you add pages.
The Home tab is the first WorldServer page you see when you log in. It provides at-a-glance information about your current projects, issues, and notifications with links to the project list, task list, or notification list, as applicable. It also features the following:
Using Useful Links
Useful links can be any URL (external to WorldServer) that has been set up for your locale and workgroup. For example, you could have a link to your corporate glossary, which would be useful to translators. Useful Links are set up in Management > Administration > Useful Link Setup.
By default, there are links to the Translation Workbench for Windows installer, the Launcher for Windows, and EntryForms.zip (files and instructions for creating WorldServer entry forms).
Using the Content Wizard
The Content Wizard allows you to create/upload, or edit an asset and submit it for approval without using the WorldServer Explorer or creating a project. The wizard walks users through the necessary steps. This feature requires that you configure Content Categories.
Using the WorldServer Setup Guide
The WorldServer Setup Guide provides you with step-by-step instructions for how to set up a project for the first time. After you have completed some of this initial setup, you will not need to complete it again each time you create a project that uses the same source files, linkage, and workflow.
Click the link to the guide, and then click each step to navigate to the appropriate page and to read the instructions for that step. Once you are done, you can close the setup guide.
Shortcuts are internal WorldServer links. You can create a shortcut to bring you from the Home tab to any other page in WorldServer. This is useful for pages that you use frequently, such as the task list for a project you are currently working on.
A shortcut is created by clicking the shortcut icon at the bottom left of the page to which you want to jump. The shortcut appears on the Home tab in the WorldServer Shortcuts section. You can delete these shortcuts when you no longer need them by clicking the "x" next to the link.
Working with Announcements
You can use announcements to communicate general information to the users in your locale and workgroup. After allowing adequate time for these users to read an announcement, you can delete the announcement.
Explorer allows you to manipulate and work with assets and folders. Explorer is where you add folders and assets, where you can scope assets, and where you create projects. In addition, if you need to edit, translate, or export an asset without creating workflow and a project, you can do so in Explorer.
NOTE: To refresh the view of your assets without refreshing the entire page, right-click the folder on the left and choose "Refresh".
Searching for Assets
You can search for assets in Explorer by selecting a particular mount or folder and specifying the text to search for (optionally case-sensitive). The search returns a link to each asset that contains the search string.
A search within an XML repository mount provides additional options and search and replace capability.
You can select one or more assets from the same folder by Shift- or Ctrlclicking the assets to select. To select assets from multiple folders, select the assets from the first folder as usual, and right-click the selection and choose "Remember Selection". The selection appears in the Current Selection window. You can then navigate to another folder, and do the same. Once you have all the necessary assets selected, you can choose an action.
Editing and Translating Assets
You can edit and translate source and target assets in Explorer. When you select a source asset or an asset that is not linked, the Freeform Editor opens. When you select a linked target asset, the Translation Workbench opens. The Segmented Assed Editor, the Freeform Editor, and the Translation Workbench function in the same way as when accessed from the task list.
In addition, you can use the Launcher to edit assets externally, in their native application. Using the Launcher requires some installation and configuration steps. See the WorldServer online help for details about installing, configuring, and using the Launcher.
You can submit content that you have created or edited for approval from Explorer. This creates a project using the default workflow.
Exporting and Importing Assets
You can export assets to work with them offline in the Translation Workbench for Windows or an outside CAT tool. When you export an asset, the corresponding target asset is locked automatically (whether it already exists or not). The translation memory is exported with it. After translating the asset offline, you import it back into WorldServer.
When you import an asset, WorldServer checks if the asset is still locked by you. If the asset is no longer locked by you, WorldServer will not import it, since there may have been changes made to it. The source and target segments of the translated document populate the translation memory if you select that option upon import. The translation memory from the offline tool does not get imported into WorldServer translation memory, since the offline translation memory may contain irrelevant or incorrect matches. However, you can import offline translation memory (TMX format) into a WorldServer translation memory.
Locking and Unlocking Assets
You can lock assets or folders that you do not want other users to modify. Assets are automatically locked when you save changes in the Translation Workbench or Freeform Editor or when you export.
Conversely, you can unlock assets to allow other users to modify them. Assets are automatically unlocked upon import or task completion.
Accessing the Viewer
The Viewer allows you to see assets from Explorer. This is helpful while you are working on an asset and want to see a preview. With certain file types, you can also edit the asset from the Viewer. You can access the Viewer by selecting an asset and clicking "View" or through the Translation Workbench or Freeform Editor.
You can add, delete, copy, download, or upload assets as needed from Explorer. Adding and copying folders allows you to set up target folders directly in WorldServer. Downloading and uploading assets allows you to bring assets into WorldServer for globalization, and to take assets from
WorldServer once they have been globalized.
Working with ClearCase
The ClearCase connector requires that you have a special license from Idiom. Once you obtain a ClearCase license key, navigate to Management > Administration > Licenses and add the ClearCase license key provided by Idiom Professional Services.
When you have a ClearCase mount configured, you have access to multiple ClearCase commands from within the Explorer.
You can compare versions of XML documents in Explorer. This feature allows you to compare one version of an asset stored in the XML repository against another version of the same asset. You can choose to view the XML data of the versions or an in-context change-tracking PDF document.
You can determine how many words are in a particular folder or asset, and how much translation will cost, based on a selected cost model.
NOTE: You need to set up a cost model (Management > Linguistic Tool Setup > Cost Model Setup) and locales (Management > Business Rule Linkage > Locales) before using the scoping tool.
To scope assets, select the assets and choose Projects > Scope.
Generating Publishing Output
You can generate final output for content (for example, a PDF manual or a compiled help system). You must have Publishing Output configured in Management > Administration > ustomization.
You create projects in Explorer after you have set up the following:
Adding to a Project
You can add new assets to an existing project. The assets that you add need to have proper linkage configured. Once the assets are added to the project, they will become new tasks that will start at the first step of the designated workflow.
A task is an individual work assignment that is generated when an asset that is part of a project reaches a human step in the workflow. A task has the action that corresponds to the current workflow step, and the assignee or assignees that were specified for the current workflow step.
Example: In your two-step workflow, the first step is "Translate", and the assignee is the French Translator workflow role. When the project is created, tasks are generated with an action of "Translate", assigned to the French Translator workflow role. Each user in the French Translator workflow role will have these tasks in their task list. Once a task is completed, it disappears from the task list of the translator and moves to the next step, which may be "Review", and is assigned to Jacques, the reviewer specified in the workflow. Jacques now has the task in his task list.
Since there can be more than one assignee for a task, a user who wants to work on a particular task must claim it. Claiming a task prevents other users from working on it. You can explicitly claim a task or automatically claim it by opening the task in the Translation Workbench or by exporting it.
You can view and work with your tasks in the Project List.
Viewing the Project List in Tree View
The project list provides information about the projects with which you may be involved. When you view the project list in "Tree View", you see the project list organized by project groups. A project group is two or more projects that share the same name and workgroup, are created at the same time and contain the same assets, but have different locales.
When viewing projects in tree view, you are able to see project groups at the highest level, then, by expanding a project group, you can see the individual projects (shown as locales), and if you expand the project, you can see the individual assets (tasks). You are able to perform the same actions in the project list in tree view as you are able to perform in the project list in traditional view and in the task list.
Viewing the Task List
Each project has a task list, which displays the tasks in the project. To view the task list, click the project name link. You can choose to view all tasks claimed by you, all tasks assigned to you, all active tasks (all except hidden and deleted tasks), or all tasks in the project from the "View" drop-down menu.
Using the Viewer
The viewer allows you to see, and sometimes edit, the asset on which a task is based. This is helpful while you are working on a task and want to see a preview. You can view the source asset or the target asset in the following list:
You can access the viewer from the task list by clicking the asset link, or from the Translation Workbench by clicking "View".
When a workflow step is assigned to multiple users or to a workflow role consisting of multiple users, the corresponding tasks will appear in each assignee's task list. The user who will work on the task must claim it to prevent other users who are assigned to the task from making changes to it. You can claim a task explicitly by selecting it and clicking "Claim", or automatically claim it when you export or open it in the Translation Workbench. Once you claim a task, work on it, and complete it, the task will stay claimed by you if it should return to the step that was assigned to you (for example, if the task progressed to a review step and then returned to the translate step where it was claimed by you, it would still be claimed by you).
Conversely, you can unclaim a task that you will not complete so that other users can claim and work on the task.
Working on Tasks with a Human Step
When a task is at a human step, you can open it in the Translation Workbench in the browser, or you can export the task to the Translation Workbench for Windows, Trados, or SDLX. With at least one task selected, clicking the "Translate" button launches the Translation Workbench.
Editing Tasks Externally
When a task is part of a project that does not use linkage, it can be edited externally, using the Launcher. When a project does not use linkage, it is generally because the project is set up as a means of tracking source file editing, as opposed to translation.
Exporting and Importing Tasks
You can export tasks to work on them offline in the Translation Workbench for Windows, Trados, or SDLX. When you export a task, it is automatically claimed, and the corresponding target asset is locked. The translation memory is exported with it. After translating the task offline, you import them back into WorldServer.
When you import a task, WorldServer checks if the task is still claimed by you, and if the corresponding target asset is still locked by you. If the task is no longer claimed, or the asset is no longer locked, WorldServer will not import it, since there may have been changes made to it. The source and target segments of the translated document populate the translation memory if you select that option upon import. The translation memory from the offline tool does not get imported into WorldServer translation memory, since it may contain irrelevant or incorrect matches. However, you can import offline translation memory (TMX format) into a WorldServer translation memory.
Changing Task Status
Task status helps you keep track of your progress in completing the assignment. Changing the task status has no effect on the task itself. For example, changing the task status to "Completed" does not complete the task, it is simply an indication to you that you are ready to complete it. The task status changes to "In Progress" automatically when you save changes in the Translation Workbench. Also, the task status changes to "Exported" when you export a task, and "Imported" when you import a task.
NOTE: You cannot manually change a task status to "Exported" or "Imported".
Viewing Task Information
By clicking the task number link in the task list, you can view the general information of a task, including the project name, workflow, and the source and target asset paths as well as the task history and a diagram of the workflow.
Viewing Project Information
By clicking the "View Project Information" link, you can view the general information of the project, including the locale, workgroup, description, and creation date.
You can also access the scoping information by clicking the appropriate link. In the Scope dialog box, you can view the word count and pricing information by selecting the appropriate cost model. You can also download the cost information to a comma-separated values (CSV) file that you can open in spreadsheet software to further refine, review offline, or distribute. You must have at least one cost model set up (Management > Linguistic Tool Setup > Cost Models) before you can access cost information.
Logging Task Issues
Issues are problems that arise when globalizing content. Issues can be associated with a particular task (task issues), or can be assigned to a user or workflow role (independent issues).
To log a task issue, click the issues link for the appropriate task. A task issue remains with the task while it progresses through the workflow steps. You can modify and close these issues in the Assignments > Issues page, along with task-independent issues. To log an independent issue, you do so in the issues list.
Example: There is a typo in one task. Since this issue only involves one task, and is not related to any particular user, you should log a task issue from the task list. In addition, the marketing manager reports that there is a missing graphic on one of the Spanish Web site's pages. Since there is no current project or task associated with this problem, you should log an independent issue from the issues list.
Setting Due Dates and Custom Attributes
You can set a due date for a group of tasks, or for the entire project. A due date can help translators to prioritize tasks. You can set a project due date when creating a project. Set or change a project due date from the project list, and a task due date from the task list.
In addition, you can create and set custom attributes for a project.
Reassigning and Modifying Task Assignees
The Reassign command allows you to reassign a task to another user. This only reassigns the current workflow step of the task. Any subsequent steps remain the same.
The Modify Task Assignees allows you to modify the assignees of all workflow steps of a task.
You can move particular tasks to an existing or new project, if the need arises. To add a task to an existing project, the project must have the same locale, and you must have permission to add tasks to the project. You can also choose to create a new project with the selected tasks. When you create a new project, the tasks will enter the project at the same workflow step they were at when you moved them, since the workflow is designated at the tasklevel.
You can cancel tasks that you do not need to do any work on. For example, if you have a task that contains an image with no translatable attributes, you can cancel it. When you cancel a task, it is canceled from the project entirely.
Downloading Task Assets
You can download the source or target assets of a task if you store your final translated files in a different location than the target folders in Explorer. Downloading the assets should be the last step of the workflow, after all translation and review is completed. To bring the assets back online, you can upload them in Explorer.
Changing Task Priority
When a project is created, its tasks are assigned a priority by default. If you have permission to do so, you can change the priority of all the tasks within a project from the project list, or of individual tasks from the task list.
Completing a task forwards it to the next step in its workflow.
Example: You have a two-step workflow with a translate step and a review step that circles back to the translate step if rejected, or progresses to the Finish step if accepted. When the translator finishes translating the task and clicks "Complete", the task moves to the reviewer. When the reviewer finishes reviewing the task and clicks "Complete", there is a choice to accept or reject the translation. If the translation is accepted, the task is finished. If the translation is rejected, the task circles back to the translator for corrections.
When you click "Translate" in the task list or the Explorer, the Translation Workbench launches in the browser. The Translation Workbench in the browser allows you to translate and review tasks or assets without leaving WorldServer.
You can also translate tasks or assets offline in the Translation Workbench for Windows or in Trados or SDLX if you have a large number of tasks or prefer to translate offline.
This chapter explains the concepts in the Translation Workbench in the browser.
About the Segmented Asset Editor
When a task is part of a project that does not use linkage, it can be edited using the Segmented Asset Editor. When a project does not use linkage, it is generally because the project is set up as a means of tracking source file editing, as opposed to translation.
The Segmented Asset Editor allows you to edit assets and tasks without a target file. The Segmented Asset Editor is used if an asset has a locale set up and its media type has a filter associated with it. The asset is segmented and is shown in the Segmented Asset Editor. You can choose to edit the asset in the browser, to switch to the Freeform Editor, or to download the asset and edit offline. You can also access the Viewer from the Segmented Asset Editor.
However, if an asset does not meet these requirements, but is textual, the Segmented Asset Editor is not available, and the Freeform Editor appears instead. In this case, both online and offline modes are available.
If an asset does not meet these requirements and is not textual, only the Freeform Editor in offline mode is available.
Translation Memory Matches
When you open the Translation Workbench, the target is populated with 100% matches. A 100% match occurs when a segment has been translated and saved to translation memory before, whether in the same asset, or in a different asset with the exact same segment. When a segment has 100% match, the target segment has a blue bar to its left.
A 100% in-context match occurs when the exact same segment has been translated in the exact same context (same segment, same document). Incontext matches are locked for a translator when using a segment locking workflow.
If a segment has a translation memory (TM) match, the TM match button illuminates, indicating that there are matches in translation memory. Click the button to see these matches. You can then click the copy button or manually copy and paste as needed to the target segment. You can also click the match link to open the TM entry editor and edit the entry as needed.
Click "Save and Update TM" when you want your translations to be added to translation memory. When a task is in progress, you can click "Save" instead to have your in-progress translations not populate the TM, but to be saved to the target asset.
Choose Tools>Reapply TM to have any new or changed 100% matches loaded into the appropriate segments or to cause any new lower-scoring matches to cause the TM match button to illuminate. Choose Tools>Pre-translate to automatically populate any empty target in the document with the top-scoring translation memory match. Tools>Paste from source copies and pastes the source text of the segment to the target for any selected segment. In addition, the Tools menu provides locking and unlocking options for human steps with dynamic locking.
NOTE: You can set the minimum percentage match that you want to appear in the Translation Workbench in Tools>Personal Preferences.
You can maintain your TM by removing obsolete matches, or modifying incorrect matches in Tools>Translation Memories.
An asset or task is made up of segments with translatable text and attributes and segments with non-translatable markup. Selecting the "Show Markup" check box allows you to see the segments with non-translatable markup as well as those with translatable text and attributes. You cannot edit markup segments.
NOTE: Some filters, such as MIF, Office, and RTF do not allow the markup to be viewed.
Working with Placeholders
Placeholders appear in segments that have translatable attributes. The translatable text appears as text in the segment, and the markup appears as bracketed numbers in the segment. All placeholders that are in the source of the segment must appear in the target of the segment. You translate the text that appears in the segment, placing it in the appropriate place in relation to the placeholders. To view the markup that is represented by the placeholders, click the Placeholder button for that segment.
Splitting and Merging Segments
You may want to split a segment to increase the chances of the Translation Workbench finding translation memory matches or term database entries or to make a large segment easier to translate. Likewise, you can merge segments that are better translated together for a more natural translation.
NOTE: Do not split or merge segments that you have already translated, as splitting or merging the segment deletes the translation in progress. If you do need to split or merge a segment that you have already started translating, you can copy the contents of the target, then split or merge the segment, then paste the translation into the new segment and re-arrange the translation as necessary.
Accessing the Term Database
If WorldServer detects term database entries that match your source segment, the term database button illuminates for that segment. Clicking the button will display the entry or entries that match the segment. You can click the entry link to open the term database entry editor and edit it as needed.
You can also search the entire term database by clicking the "Term Database" link.
Working with the Freeform Editor
The Freeform Editor allows you to edit a task without saving to translation memory. The Freeform Editor is well-suited to indirect translations where a segment-to-segment translation, like that in the Translation Workbench, is not ideal. WorldServer may suggest that you translate in the Freeform Editor if, for example, the asset was edited outside of WorldServer.
The Freeform Editor opens when you click the "Freeform Editor" link.
You can edit the asset in the browser or download the asset and edit it offline.
You can also access the Viewer and perform a term database search from the Freeform Editor.
Using the Viewer
The Viewer allows you to see the assets on which a task is based from the task list. This is helpful while you are working on a task and want to see a preview. With certain file types, you can also edit the asset from within the Viewer.
You can work on WorldServer translations directly in WorldServer DVX. A single mouse click in WorldServer opens a project in WorldServer DVX, and a single menu selection in WorldServer DVX uploads a project to WorldServer. There is no need to export and unzip projects, and to zip and import projects.
You can also choose to work on translations offline in Trados TagEditor or SDLX.
This chapter provides an overview of how to do the following:
Using WorldServer DVX
A single mouse click in WorldServer opens a project in WorldServer DVX, and a single menu selection in WorldServer DVX uploads a project to WorldServer. There is no need to export and unzip projects, and to zip and import projects.
Online freeform TM search provides a freeform SQL query facility. This allows WorldServer DVX users who have connectivity to their WorldServer server to query a WorldServer translation memory.
WorldServer DVX allows you to take advantage of WorldServer translation memories and term databases while translating assets or tasks offline. To use the WorldServer DVX, you download it from the WorldServer Home tab and launch WorldServer DVX from Explorer or the Task list.
Installing WorldServer DVX
The WorldServer Home tab provides a link to download WorldServer DVX installer. This download link is located in the Useful Links section.
To download WorldServer DVX, click the link and follow the prompts.
To install WorldServer DVX, double-click the install executable and follow the prompts. When installing, you have three install choices:
Creating a WorldServer DVX Project
Before you can begin translating your WorldServer assets or tasks in WorldServer DVX, you need to create a project that contains the following:
NOTE: Each time you create a project and translate assets, you will generate several different types of files. You may want to devise a file structure to organize your work.
To create a new project, choose File>New>Project. The project creation wizard steps you through the process, where you specify which content will be in the project, and create or select a new translation memory and a term database.
There are two major sections of the WorldServer DVX main window: the project navigator and the translation window. When you create or open a project, the project navigator appears. The translation window does not appear until you open an asset to translate. The next two sections explain these windows.
About the Project Navigator
The project navigator is the panel at the right side of WorldServer DVX that displays the names of the assets in the current project. Double-click an asset to display its contents in the translation window.
NOTE: If you have closed the project navigator, you can re-open it by choosing View > Project Navigator.
Working with the Translation Window
The translation window displays the source and target segments of the selected asset. The translation window is where you translate the asset.
When you first open an asset in the translation window (by double-clicking it in the project navigator), any 100% matches from WorldServer translation memory automatically populate the appropriate target segments. To make use of fuzzy matches or term database entries, you can use any of the following options:
The target segments use color coding to indicate their translation status.
About the Options Dialog Box
The Options dialog box provides general options, including settings for AutoAssemble, AutoSearch, AutoPropagate, and AutoSend as well as spelling options. Choose Tools > Options to open the Options dialog box.
You can use the pretranslate feature to get the most out of your translation memory matches, term database matches, and lexicon. Depending on what options you choose in the pretranslate dialog box, and how many entries you have in your translation memory and term database, pretranslating can make translating your task or asset easier. Pretranslate can involve assembling a translation from portions.Choose Translation > Pretranslate to access the pretranslate options.
Using Translation Lookup
Translation lookup allows you to search the translation memory for matches. It displays all matches found for the currently selected segment as well as the score for the match.
Click the segment for which you want to find matches and choose Translation > Translation Lookup or press Ctrl+S to search the translation memory for matches to the current segment. If there are any matches, the translation memory match results window appears. Translation lookup is done on a segment-by-segment basis. If you want to search the translation memory for all segments in the file, or in the project, use pretranslate instead.
Using Term Lookup
Term lookup allows you to search the term database for matches to the selected word or phrase. Select the word or phrase for which you want to find term database entries and choose Translation > Term Lookup or press Ctrl+Shift+S. If any entries match the selected word or phrase, the term database lookup results window appears, delineating the matches. Select the entry to see the score (fuzziness) and the date that the term was entered into the term database. You can insert the selected entry or cancel.
Term lookup is done on a segment-by-segment basis. If you want to search the term database for all segments in the file, or in the project, use pretranslate instead.
Using the Populate Feature
Populate copies the source text to the target segment for any segments that are empty and do not have embedded codes (placeholders). Choose Insert > Populate > Current Sentence to populate the currently selected segment. Choose Insert > Populate > Current Language to populate all empty segments in the project.
Propagate finds segments that have source text that matches the selected segment and populates the matching target with the target text of the selected segment. Choose Translation > Propagate in Current File or Translation > Propagate to All Files to search for and populate matching segments in the current asset or in all assets in the WorldServer DVX project.
If you want to always propagate matching segments, turn on AutoPropagation. When enabled, AutoPropagate fills in the target of any segments that have an identical source to the current source when you press Ctrl+DownArrow (to move to the next segment) or Alt+DownArrow (to move to the next untranslated segment).
Enable AutoPropagate in the Options dialog box (Tools > Options) or by clicking the APr button in the lower right of the Translation Window.
Assemble looks for translation memory matches, term database entries, and lexicon matches at the word level. WorldServer DVX then assembles the segment from the translation memory, term database, and lexicon. Target segments that are populated by an assemble process have a blue label.
You can pretranslate with assemble enabled or choose Translation>Assemble.
When AutoAssemble is enabled, WorldServer DVX automatically assembles the next untranslated row when you press Alt+DownArrow.
Enable AutoAssemble in the Options dialog box (Tools > Options) or by clicking AAs in the bottom right corner of the translation window.
Finding and Replacing
You can find words or phrases in the source or target of the asset loaded into the translation window. In addition, you can find and replace words or phrases in the target. Choose Edit > Find or click Ctrl+F.
You can change the capitalization of a segment. The change case feature changes all words in the segment to all caps the first time, then sentence capitalization, then all lowercase. Choose Edit > Change Case or click Shift+F3.
Joining and Splitting Sentences
Joining and splitting sentences in WorldServer DVX is similar to splitting and merging sentences in the Translation Workbench in the browser.
You may want to split a segment to increase the chances of finding translation memory matches or term database entries or to make a large segment easier to translate. Likewise, you can merge segments that are better translated together.
Clicking "Join" (or choosing Edit > Join Sentences) merges the currently selected segment with the segment directly under it. Clicking "Split" (or choosing Edit > Split Sentences) breaks the selected segment where the cursor is currently positioned.
Using the Translation Memory
When you open an asset or task in WorldServer DVX, it contains any translation memory (TM) matches that were found. When you create a WorldServer DVX project and open the asset in the translation window, these WorldServer translation memory matches are inserted into the WorldServer DVX translation memory. 100% WorldServer matches automatically appear in the appropriate target segments. Throughout the translation process, you can search the WorldServer DVX TM for fuzzy matches, and can browse and edit the TM. However, when you import translated assets back into WorldServer, changes or entries that you have made to the offline TM do not get inserted into the WorldServer TM. Only matched segments that are in the actual assets are inserted into the WorldServer TM (only if you select that option upon import).
Maintaining the WorldServer DVX TM will make it easier for you to translate using features such as assemble and AutoSearch. There are several ways to search the TM, send translations to the TM, and to maintain the TM.
Searching the Translation Memory
Adding, Editing, and Deleting Translation Memory Matches
To add, edit, or delete TM matches, open the translation memory file *.dvmdb), then do one of the following:
Sending Translations to the Translation Memory
Using the Terminology Database
When you import WorldServer assets or tasks into WorldServer DVX, applicable terms from the WorldServer term database are inserted into the WorldServer DVX term database. These terms will be useful when using the WorldServer DVX assemble feature as well as the AutoSearch feature. You can also perform term database lookups as you translate your files.
You can add to and edit the term database to make it more useful while working in WorldServer DVX, however, the term database is not imported back into WorldServer with the assets or tasks.
Using the Lexicon
The lexicon is a list of all the source language words or phrases in the project. AutoAssemble and AutoSearch use the lexicon to help you translate untranslated segments.
You can build a lexicon to your specifications by using Project > Lexicon > Build. You can also resolve the lexicon to your term database and translation memory. This means that the lexicon will be searched for any TM matches or term database entries. Any matches will be inserted into the lexicon. Choose Project > Lexicon > Resolve with Translation Memory or Project > Lexicon > Resolve with Term Database.
Once the lexicon is built and translated, it will become very useful in AutoAssemble and AutoSearch operations.
You can check the translation for term database usage. Choose Translation > Check Terminology (Ctrl+Shift+F7) to check for term database entries that are not being used in the target.
Example: If there is a term database entry that specifies that "pen" should be translated as "stylo" in French, if the word "pen" appears in the source side of a segment, and the word "stylo" does not appear in the target side of that segment, when you check terminology, the word "pen" will turn red, indicating that the term database entry is not being used properly.
When this happens, choose Translation > Term Lookup to see the entry, and make corrections as necessary. This command checks for the first misuse. Choose the command again to see the next instance of a missing term.
Checking Numerals in Text
You can check the numerals in your translation to make sure that the numbers that appear on the source side also appear on the target side. Choose Translation > Check Numerals to check your numerals. You can also automatically check for numerals while checking terminology; this is an option that you can select from the Options dialog box (Tools>Options).
Checking Embedded Codes (Placeholders)
You can check if your embedded codes are correct before exporting a finished translation. You cannot import assets whose placeholders are incorrect into WorldServer.
WorldServer DVX checks to make sure that the placeholders that appear on the source side also appear on the target side. If there are any missing, extra, or incorrect placeholders on the target side, WorldServer DVX marks the segment with a red "x". Make sure you resolve incorrect placeholders before importing back into WorldServer.
Using the Spell-Checking Tool
Choose Tools>Spelling (F7) to check your target spelling. The spell check dictionaries you have available depend on the install option you chose ("Typical" includes all spell check dictionaries, "Custom" includes only those dictionaries that you specify, and "Compact" does not include any dictionaries).
The WorldServer DVX Spell Check tool works the same way as most word processor spell check tools.
NOTE: You can change your spell check options in the Spelling tab of the Options dialog box (Tools > Options).
Using the Word Count Tool
The word count tool provides a detailed account of the words in the document, listing different types of matches separately. To find the word count of a file, choose Tools > Word Count. Choose the files, languages, and row types and then click "Calculate".
Exporting Finished Translations
When you are finished translating your assets or tasks in WorldServer DVX and are ready to upload back into WorldServer, choose File > Export > Upload Project to WorldServer.
NOTE: For the best results, you should have a separate folder for your finished translations than the folder into which the IDZ files were exported from WorldServer. This facilitates troubleshooting problems that may arise.
Exporting Assets and Tasks
To translate assets or tasks offline in Trados or SDLX, you export them in the appropriate format. You export assets from Explorer, and tasks from the task list.
Using Trados TagEditor
When you export tasks or assets to be translated offline in Trados, WorldServer exports the following files into a ZIP file:
The only files that you should open and/or edit are the Items index.html, which contains a list of all the assets or tasks exported, and the SGM files in the "translate" folder, which are the translatable assets or tasks.
To translate assets or tasks in Trados
The source and target segments from the imported files will populate the translation memory if you select the "Update the translation memory using imported assets" check box upon import.
When you export tasks or assets to be translated offline in SDLX version 3.5 or version 4.2, WorldServer exports the files into a ZIP file.
After translating your tasks or assets in SDLX, you import the translations back into WorldServer.
Importing Assets or Tasks into WorldServer
You import tasks or assets that have been translated offline in WorldServer DVX or in Trados.
NOTE: Translation memory from offline translation tools is not imported - instead, the source and target segments are aligned and inserted into the translation memory, if that option is selected. You can load an external translation memory by importing a TMX file from Tools > Translation Memories.
Issues are problems that arise when globalizing content. Issues can be associated with a particular task (task issues), or can be assigned to a user or workflow role (independent issues).
There is a typo in one task. Since this issue only involves one task, and is not related to any particular user, you should log a task issue from the task list. In addition, the marketing manager reports that there is a missing graphic on one of the Spanish Web site's pages. Since there is no current project or task associated with this problem, you should log an independent issue from the issues list.
This chapter explains how to view, log, and modify task and independent issues.
Where and how you log an issue depends on whether you are logging a task issue or an independent issue. See one of the following sections for an overview.
You log a task issue in the task list (Assignments>Projects>Project). Locate the task with an issue and click the issues link. A task issue remains with the task while it progresses through the workflow steps. The issues link is updated when you log a new task issue to reflect the number of open issues that task has associated with it. When logging a task issue, you specify the name, severity, and a description of the issue.
You log independent issues in the issues list (Assignments>Issues). When logging an independent issue, you specify the name, severity, locale, workgroup, assignee (user or workflow role), and description of the issue. After you log the issue, an email message is sent to the assignee(s), provided that email notification is set up in their personal preferences (Tools > Personal Preferences).
Where and how you view an issue depends on whether the issue is a task issue or an independent issue. See one of the following sections for an overview.
You can view task issues from the task list by clicking the issue link for the appropriate task, or you can view task issues from the issues list.
To view task issues from the issues list, select one of the following from the "View" drop-down menu then click the issue title link:
View independent issues in the issues list. Select one of the following from the "View" drop-down menu then click the issue title link:
Tracking and Modifying Issues
Regardless of whether an issue is a task issue or an independent issue, you track and modify issues in the issues list. Click the issue link to modify an issue. You can view the general information about the issue as well as its history. When modifying an issue, you can change the status, assignee (for independent issues only), and notes.
Notifications inform you of changes to assets. You may want to be informed of changes to your source assets so you know when projects need to be created, or to be informed of changes to a localized version to monitor progress. The Notifications list allows you to view the changes that may have been made to the asset, informs you of when the notification was generated, and allows you to review the rule that generated the notification. You set up notifications in Management > Business Rule Linkage > Rules. You review and delete notifications in the notifications list (Assignments > Notifications).
Setting up Notifications
To set up notifications, you need to create rules that govern when and why you are notified. When you create a rule, you can choose to create a project, send notifications to a particular user, and/or send email to a particular user. To set up notifications, you should select the "Send notifications to a particular user" check box. There are other rule parameters to configure.
In addition to setting up rules, you need to set up the following for email notifications to work:
Review your notifications to determine whether or not to create a project or to work in Explorer. When you click a notification link, the Viewer appears and shows you the difference between the current version and the last version. In addition, you can review the rule that generated the notification.
After reviewing notifications and taking the necessary action, delete them.
Maintaining your linguistic tools will make them work more effectively for you as you translate assets in your globalization process. You can search, export, import, and modify a translation memory or term database as needed. This chapter explains how to maintain these linguistic tools.
Translation memories make it easier to translate the same files as they change multiple times, ensuring consistency and reducing the time and cost of translation.
Searching Translation Memory
You can search a translation memory for a particular term or phrase, or can perform a search and replace. In addition, you can use attribute filters to conduct an advanced search.
NOTE: Placeholders affect the match scoring. In addition, searches in the translation memory may yield matches that are slightly different from those seen in the Translation Workbench, since repairing may occur.
Exporting and Importing Translation Memory
You can export a translation memory as a Translation Memory eXchange (TMX) file, and can import a TMX file into a WorldServer translation memory.
A term database allows you to manage commonly used terms and phrases.
Searching a Term Database
You can search a term database, including wildcard searches, to manage its entries and terms. In addition, you can use attribute filters to conduct an advanced search. You can also add entries to a term database.
Exporting and Importing a Term Database
You can export a term database as a comma-separated values (CSV) file or a MultiTerm file. You can use the CSV file to add or modify entries offline, and then later import the file back into WorldServer Global Electronic Publishing. Use this technique to add terms offline or to import an existing glossary or term database.
To import a term database:
To export a term database:
Creating a Term Database Manually
Ordinarily, you create a term database from within WorldServer. However, to create a term database manually (or to create part of a term database), follow these guidelines: