Procedure for Exporting Translation Kit

Complete the previous export steps.

In the Create Translation Kit for Assets (Step 2 of 2) dialog, select an export format, optionally select whether to allow split and merge, select a scoping configuration, specify segments to exclude, select attribute filters, and click Export. Exported files are packaged into a ZIP file. See below for a description of the options.

Note: You also can add translation memory and terminology database filters from this page.

The corresponding target assets are automatically locked. They must remain so for you to import the translated assets back into WorldServer. If the target asset does not yet exist, you will not see it in Explorer, but it will still be locked to prevent another user from creating it.

After translating the asset off-line, import it back into WorldServer. When importing, you will select the Update the translation memory using imported assets check box to insert the source and target segments into the translation memory as matches.

Note: Before translating assets exported to TRADOS, see the WorldServer User Guide for important information.

Allow Split and Merge

To preserve the highest level of translation memory leverage, it may be advantageous to prevent translators from performing split and merge operations on segments.

In general, the split and merge technology can be effectively used when significant segmentation differences exist between the asset and the translation memory. For instance, consider using the split technology when the translation memory mostly contains sentence-level entries and the asset filter produces paragraph-level segments. The split process can potentially break up the asset segments to make better matches against the TM entries.

Similarly, the merge process can be effectively used when the asset segments are produced at the sentence-level, but the TM entries were created at the paragraph-level. The merge process can progressively merge successive asset segments to match against a larger TM entry.

Both technologies can be used in tandem to leverage against a TM that may contain both sentence and paragraph-level entries. It is worth restating that this technology is only employed in the event that a qualifying match cannot be found for the original segment.

For an in-depth explanation of the split and merge processes, 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.

Select Scoping Configuration

A scoping configuration is a collection of ranges that describes the quality of a match. When scoping is applied to an asset, all translation memory matches are divided among the available ranges, as appropriate. When you export an asset, you can select which scoping configuration to use.

Note: This drop-down does not appear in the case where only one scoping configuration is available. In this case, the WorldServer default scoping configuration is used.

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 doesn’t include segments for which there are ICE or 100% matches in the translation memory. This is one of two ways you can avoid having translators touch ICE and 100% segments. The other 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.

Formats for which each option is enabled:

	XLZ	TRADOS TTX	XLIFF
Allow split and merge	X		X
Select Scoping Configuration	X		X
Segments to exclude	X	X	X

Note: Whether these formats display is controlled by property settings in exchange.properties. See your WorldServer administrator.