Importing Assets

To Import a Translation Kit from the Project or Task List

In Assignments > Projects or in the Task List, click Import. You do not need to select a project or task when you click Import because the project information is contained in the translation kit that you will import.
The Import Offline Work dialog displays.
Click Browse and select the file to import. The file you choose must be a valid completed translation kit that originally was exported from WorldServer and that has been translated off-line.
If you have the appropriate permissions, you may also choose whether to update the translation memory based on the contents of the translation kit. To insert matches, check the Update the translation memory using imported assets check box. You may not want to insert the matches into translation memory if updating the translation memory is the responsibility of the reviewer, who can update the translation memory after reviewing the translation.
If you have the appropriate permissions, you can choose to run the import in the background. If you choose to run a job in the background, you can freely disconnect from WorldServer while waiting for the job to run, and you will be notified when the job completes. If you choose not to run the job in the background, you must stay connected to WorldServer until the job finishes.

Click Import.

If the tasks that you exported are no longer claimed by you, the tasks will not be imported. There may be other reasons that a task is not imported. Import errors are listed in the Import dialog box.

Note: If an error message appears regarding duplicate or missing placeholders, either open the task in the WorldServer Browser Workbench and re-translate the offending target segments, or fix the placeholders in the off-line tool and re-import the task.

The task status changes to the imported icon when the import is complete.

How WorldServer Handles Task Import Errors

When you import assets, WorldServer generally only imports error-free segments of the asset rather than halting the import operation. Segments with errors are not imported.

Import errors are reported in two places:

The import error summary at the end of the import dialog box, if you are running in foreground mode.
The WorldServer log.

The translated content for these failed segments is not imported, leaving the previous content. You can either fix the failed segments in your offline tool and reimport or you can work on them directly in the Browser Workbench.

Note: In some cases imports will fail, such as for invalid XML files.

The default behavior for import is set in the exchange.properties file. The property catasset.failOnError is now set to false as the default. If you would prefer to have the entire import fail when WorldServer encounters errors, change the setting to catasset.failOnError=true.

To Import a Translation Kit from the Explorer

In WorldServer Explorer, choose Tools > Export/Import > Import Translation Kit .
The Import Offline Work dialog displays.
Click Browse and select the file to import. The file you choose must be a valid completed translation kit that originally was exported from WorldServer and that has been translated off-line.
If you have the appropriate permissions, you may also choose whether to update the translation memory based on the contents of the translation kit. To insert matches, check the Update the translation memory using imported assets check box. You may not want to insert the matches into translation memory if updating the translation memory is the responsibility of the reviewer, who can update the translation memory after reviewing the translation.
If you have the appropriate permissions, you can choose to run the import in the background. If you choose to run a job in the background, you can freely disconnect from WorldServer while waiting for the job to run, and you will be notified when the job completes. If you choose not to run the job in the background, you must stay connected to WorldServer until the job finishes.

Click Import.

If the assets that you exported are no longer locked by you, the assets will not be imported. There may be other reasons that an asset is not imported. Import errors are listed in the Import dialog box.

Note: If an error message appears regarding duplicate or missing placeholders, you need to either open the asset in the Translation Workbench in the browser and re-translate the offending target segments, or fix the placeholders in the off-line tool and re-import the asset.

Note: Translation memory from off-line 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 .