Exporting translation kits from Explorer
If you want to work on one or more tasks offline, in a tool such as SDL 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
1 You can only export Regulator Bundle kits for projects that use File System AIS mounts. Also, you can only export bundles if the tasks are in the Review step.
2 In a Regulator Bundle kit, you can only export .docx files segmented with the Microsoft Word 2007-2013 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 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.
4 Translation quality assessments from SDL 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 SDL Trados Studio. The errors reported in SDL Online Editor and in Browser Workbench are also displayed in SDL 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.
5 TD attribute names are truncated if they exceed 50 characters.