You can export projects and tasks to work on their associated assets offline in SDL Trados Studio 2019 or earlier or other desktop translation tools that support XLIFF files. When you export a task, it is automatically claimed, and the corresponding target asset is locked. The relevant portions of both the translation memory and terminology database are exported with it. After translating the task offline, you import the asset pair back into WorldServer.
Exporting projects is the same as exporting tasks, except that the translation kit contains one or more zip files, each of which represents a translation kit containing tasks, and the TMs which are displayed individually. You must extract the zip files and presented each one separately to the translation tool in the same manner as would be done for task export.
Note: To make your package fully compatible with SDL Trados Studio 2019 (recommended) select WSXZ in the Create Translation Kit for Projects window. To make your package compatible with previous SDL Trados Studio versions, select the Backward compatible package check box.
Note: When you export an updated WSXZ translation kit from
WorldServer 11.1 or later and open it again in SDL Trados Studio 2017
Cumulative Update 5 or later, the existing project is updated in Studio. In previous versions, Studio would create a new project each time you imported the same translation kit. This improvement aligns better the concepts of
project group in
WorldServer and
project in Studio.
Moreover, subsequent downloads from the same WorldServer project group with new or updated task files are merged or added to the existing Studio project. Translation memories, terminology databases, and project and task attributes are also updated or added to the same Studio project, while attribute names are prefixed with their corresponding target locale for clarity.
Before you export the WSXZ project, make sure your administrator adds the following configuration to the
Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config file, under
appSettings:
<add key="StudioGuidGeneration" value="true"/>
After you finish a translation session offline, you import the translation kit and, optionally, update the translation memory.
If you have permissions to update the translation memory during the import process, the WorldServer translation memory will be updated based on the new translations.
Note: The import process does not actually import your local translation memory; it updates the WorldServer translation memory based on the translated segments in the kit. The only changes that are inserted into the WorldServer translation memory are those that come directly from the translations themselves.
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 is not imported into WorldServer translation memory, because it may contain irrelevant or incorrect matches.
Note: Not all users have permissions to update the translation memory. Translators often do not have this ability. Instead, their translations could be passed to a reviewer to approve the translations before the translation memory is updated.
For more information about exporting and importing projects and tasks, see the
Export and Import Formats topics.