Exporting a Task for Offline Work

Click the check boxes next to the task or tasks to export.
Click Create Translation Kit for Tasks.
In the Create Translation Kit for Tasks dialog box, select the format to use, optionally select whether to allow split and merge, specify segments to exclude, and select attribute filters, and click OK.

Choose a location where the downloaded file will be saved.

Exported files can be packaged into one of several formats:

A .wsxz file for use with SDL Studio 2009 or later

Note: An exported WSXZ kit will not contain project or task level attachments. Any attachments for the project or task must be added into the WSXZ manually before the kit is sent to the translators.

An .xliff ZIP file containing a file in XML Localization Interchange File Format

The tasks are automatically claimed, and the corresponding target assets are locked. They must remain so for you to import the translations back into WorldServer.

The task status icon changes to exported when the export is complete.

After translating the task, import it back into WorldServer.

Allow Split and Merge

Enable this capability for translators who can be trusted to change the presented segmentation into more logical groupings when necessary. To preserve the highest level of translation memory leverage, however, you may want to prevent translators from splitting and merging segments.

For futher explanations of the split and merge processes, both manual and automatic, see the WorldServer Translation Memory Administration Guide.

Note: The Allow split and merge check box does not appear on export dialog if the Can split and merge segments box is not checked in the User Type privileges screen.

Segments to exclude

You can choose to exclude ICE or ICE and 100% matches when you export an asset. If, for example, you select ICE and 100% matches, your exported translation kit does not include segments for which there are ICE or 100% matches in the translation memory. This is one of three ways you can avoid having translators touch ICE and 100% segments. The second way is to lock them from the workflow using an automatic action. However, not all third-party tools respect WorldServer locks, so this filter is the surest way of not allowing translators to modify them. The third way applies only to ICE matches in XLIFF files. It requires your WorldServer administrator to turn on the property xliff.markICEMatchesAsTranslated in the exchange.properties file. When this property is enabled, ICE matches are marked as translate=no in the translation-unit element. This causes smart XLIFF editors to ignore the translation unit altogether, so it is not editable by translators and does not show up in word counts.