About the Project Package
WorldServer project packages have a file extension of .wsxz and contain the information needed in order to translate or review translations of files whose translation is managed by WorldServer.
Project and task information and the associated metadata are included in the project package. Project information can be viewed in SDL Trados Studio in the Project Attributes tab on the Projects view. Task information can be viewed in SDL Trados Studio in the File Attributes tab on the Files view.
With this release, the WorldServer package has been configured to be backward compatible (that is, to work with versions of Studio prior to 2015). To make the package backward compatible, you must select this option when exporting it.
- A segmented representation of each source file
- The server-based TM assigned to the WorldServer project
This offers real-time access to the version of the TM available on the WorldServer system. The WorldServer TM is enabled by default in the list of translation memories applied to the project and it can be updated while confirming the translations in Studio. This TM is only available for WorldServer packages opened in Studio 2017 and only for Studio users with the required WorldServer credentials.
- The file-based TMs assigned to the WorldServer project
These are the offline version of the TMs assigned to the WorldServer project, as they were available when the WorldServer project was created. Studio users who do not have access to the server-based TM can use these TMs when translating the files in the WorldServer package. The changes to these TMs can be updated by the WorldServer project manager when importing the return package into WorldServer
- WorldServer terminology entries
WorldServer includes a single project TBX file that contains relevant TD entries, if they exist. When you open the WorldServer project package in Studio, this TBX file is imported into a new Studio termbase file named WorldServer.sdltb and is automatically included in the Studio project. The TD Name field in the imported TD in Studio is displayed in the Term Recognition window by default. When it is present, the termbase file includes information on individual terms:
- Term statuses such as Proposed, Approved, Preferred, Deprecated and Rejected
- Task attributes and metadata information is exported for use by the Project Manager
- System attributes such as Created On, Created By, Modified On and Modified By
- Term and entry custom attributes, which are mapped to Studio attributes
- Task information and associated metadata for each file in the package. Task information can be viewed in SDL Trados Studio in the Files Attributes tab in the Files view.
- The Studio QA Checker Profile settings
In WorldServer, the main use of Studio QA Checker profiles is to ensure consistency in terms of length, punctuation, numbers, and so on when exporting WSXZ translation kits for SDL Trados Studio. For example, if you split the files in a WorldServer project into multiple translation kits and pass them on to multiple Studio users (who may use different QA Checker settings), the Studio QA Checker profile ensures that the translation quality is consistent across all the files in the project. You cannot modify Studio QA Checker profiles in WorldServer, nor can you use them to perform QA checks. The only QA Checker that you can use in WorldServer is the default WorldServer QA Checker.
To use a Studio QA Checker profile in WorldServer, first you need to upload it from the location where SDL Trados Studio exported it. To do so, go to and then choose Studio QA Checker Profile from the Custom component type list. Select Add, and then, in the Add Custom Studio QA Checker Profile Component dialog, enter a meaningful name for your QA Checker profile and select Browse. Then, in the File Upload dialog box, browse for the Studio QA Checker profile, select it, and then select Open.
- The TM Penalties defined in WorldServer for a TM or a group of TMs. Knowing the penalty score that the WorldServer project manager defined for each TM ensures that Studio users know the real value of each translation unit in a WorldServer TM and can better assess their reliability. The TMs in a WorldServer TM Group are listed individually in Studio and ordered by the priority set in WorldServer.
- The TM Attribute mismatch Penalties are applied in Studio the same way as they are applied in WorldServer when the mapped metadata of the TM match does not match the mapped metadata of the asset being translated.