Procedure for Exporting Translation Kits - Step 1

  1. In the WorldServer Explorer, select the source folders or assets to export.
  2. Select Tools > Export/Import > Export Translation Kit.
  3. In the Create Translation Kit for Assets (Step 1 of 2) dialog box, select a target locale. The source folders or assets you selected must be linked to this target locale.
  4. Determine the translation memory scoping mode to use.
    Your choices are either Studio-aligned or WorldServer 9.x scoping mode. The selected default should be appropriate to your translation environment.
  5. Click Next.
  6. Complete the subsequent export steps in Procedure for Exporting Translation Kit - Step 212.
    Important: When you export a translation kit that contains the tasks in a project, WorldServer automatically adds certain information (the project ID and the target locale) to the name of the kit. On the other hand, SDL Trados Studio has a 50-character limitation on project names. Therefore, if you export a translation kit whose name exceeds 50 characters and import it into SDL Trados Studio, Studio will truncate its name and add other characters, according to the following example:
    • Name of the project in WorldServer: Trados_Studio_PhaseII_Test_DITA
    • Name of the translation kit exported from WorldServer: tasks_Trados_Studio_PhaseII_Test_DITA_43012_ru_RU_xliff.wsxz
    • Name of the project in SDL Trados Studio: Trados_Studio_PhaseII_Test_D_ru_RU_20150212_110347
Parent topic: Exporting Translation Kits
1 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.
Note: In WorldServer 11.3.0, the tasks that you want to export also need to be in the Review step or in another step that has the Review step type configured in the workflow. This requirement has been removed starting with WorldServer11.3.1.
2 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 a translation kit from WorldServer 11.1 or later, 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"/>