If you want to work on one or more tasks offline, in a tool such as
Trados Studio, you can export those tasks from
WorldServer in the form of a translation kit.
Before you begin
You need to set up linkage for the folders or assets that you want to export.
Procedure
-
Open
WorldServer Explorer and select the source folders or assets that you want to export.
-
Select
-
On the
Create Translation Kit for Assets (Step 1 of 2) page, select a target locale, and then select
Next.
The source folders or assets you selected must be linked to this target locale.
-
On the
Create Translation Kit for Asets (Step 2 of 2) page, do the following:
-
Select the format of your translation kit. You can choose between formats such as:
| Name
|
Description
|
| Regulator Bundle1
|
A
.zip archive that contains a number of
.docx files that need to be reviewed2.
|
| WSXZ3
4
|
A
WorldServer
.wsxz file that you can use with
Trados Studio 2020 or other supported versions.
|
| Bilingual DOCX
|
An external review document in Bilingual DOCX format.
|
| XLIFF
|
A
.zip archive that contains a file in XML Localization Interchange File Format.
|
-
Next to
TM Information, select whether you want to export the content of the previously configured project TMs, a link to them, or both. The
TM Information section is available only if you choose the WSXZ format for your translation kit.
-
Select the
Allow split and merge check box if you want to be able to split and merge segments in the translation kit.
-
Next to
Segments to exclude, select whether or not you want to exclude certain types of segments from your translation kit, such as segments with ICE matches.
-
If necessary, next to
TM Filter and
TD Filter, select an existing translation memory or terminology database attribute filter or select
Add Filter to configure and add such filters5.
-
Select
Export.
The corresponding target assets are automatically locked until you import the translated assets back into
WorldServer. If the target asset does not exist, you will not see it in Explorer, but it will still be locked to prevent another user from creating it.
2 In a Regulator Bundle kit, you can only export
.docx files segmented with the Microsoft Word 2007-2016 File Type. This feature does not support Microsoft Word 2003 (or earlier) files, even if they were created with the Microsoft Office Compatibility Pack installed. Reviewers have to use Microsoft Word 2007 or higher.
3 When you export an updated
.wsxz translation kit from WorldServer 11.1 or later and open it again in 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.
4 Translation quality assessments from
Online Editor and
Browser Workbench are included in
.wsxz translation kits starting with WorldServer 11.3. Therefore, the error types and severities configured in your project's quality model in
WorldServer are converted automatically to categories and severities when you open the translation kit in
Trados Studio. The errors reported in
Online Editor and in
Browser Workbench are also displayed in
Trados Studio. For TQA profiles to be included in translation kits, make sure that the project type has a corresponding quality model.
In WorldServer 11.3.0, the tasks that you want to export also need to be in the Review step or in another step type configured in the workflow. This requirement has been removed starting with WorldServer 11.3.1.