Common Pitfalls of the Translation Process
Different components of WorldServer have some easily-avoided issues that you should be aware of.
Note the symptoms, causes, and solutions for common translation process issues in the listed components
Project Not Created
- The source folder has no files
- WorldServer will not start a project if there are no files in the source language folder.
- Solution:
- Copy the source files into the source language folder.
- Human action step has no user configured
- For at least one human action step, there is no assignable user configured for a target locale. WorldServer will not start a project if any human step has no eligible users. To be eligible, a user must be configured for the target locale.
- Solution:
- Ensure that the users eligible for human action steps are configured for the appropriate locales.
- Automatic error step has no user configured
- For an automatic error step, there is no assignable user configured for a target locale. The assignee for the Auto Error step of a workflow must be configured for ALL target locales.
- Solution:
- Ensure that users assigned to Auto Error steps (often "admin") are configured for all locales.
Project execution task appears to hang
The workflow is waiting for all tasks to reach a project scope step. A project scope step cannot start until all tasks reach the step. If the workflow is designed so that a step cannot reach the project scope step, then cancel the project and redesign the workflow.
- Solution:
- During workflow design, make sure that all steps are capable of reaching the project scope step. During execution, either wait for completion or cancel the project.
Browser Workbench targets pre-populated in error
The Workbench pre-populates target language segments with previous translations that are not in translation memory. WorldServer is using cached translations.
- Solution:
- Methods for clearing the cache include making a change to the source file, or using the Clear Segment automatic action in the workflow.
Workflow "Change Assignees" page must be set up for each step
Changes made in the Change Assignees To section apply only to the step currently selected in the Workflow Step choice list.
- Solution:
- Change the workflow step to view or change the assignees for a different step.
Java "serialization" error occurs
This error can occur when displaying WorldServer tools after an upgrade, in certain situations. If you upgrade WorldServer software on the server and a browser is open on the client, it prevents automatic upgrades from happening on the client.
- Solution:
- Restart your browser on the client machine to initiate the updates.
Terminology database entries show no matches
The terminology database entries have not yet been validated. If Validation was enabled when the terminology database entries were created, they must be verified before WorldServer will use them.
- Solution:
- Validate the entries, or disable Validation on the terminology database, then remove the entries, and re-create them.
Segmentation not initiated with environment change
You change the translation environment, but resegmentation does not occur. The cached segmentation is still being used. For example, if you have already segmented an asset, and then reassign the TM and create a project, the cached segmentation is used and the asset is not resegmented.
- Solution:
- To trigger resegmentation, either use the automatic action Clear Segment or change and save the asset.
Translation memory shows zero or near-zero leverage
- Translation memory attribute is wrong
- The translation memory attribute is not set correctly on the target language folder.
- Solution:
- In Explorer, select the target folder, and use Asset> Properties to assign the correct translation memory. Or, if you can use the same translation memory for all target languages, assign that translation memory as you set up the job folders.
- Source and target languages are not aligned
- The source and/or target languages are not aligned between the translation memory and the project.
- Solution:
- Check the language settings on the project’s source locale and the translation memory, and on the project’s target locales and the translation memory. Make sure they are in sync.