SDL WorldServer translation workflow for a Regulated Industry
SDL Trados Studio and SDL WorldServer continuously integrate to support your package and return package translation workflow.
Scenario for packages created in SDL WorldServer and translated in SDL Trados Studio
Assume you are a translator. You receive an assignment from a Project Manager to localize several Microsoft Word *.docx files that contain information about the use of medication. Previous versions of these files were translated last year.
The Project Manager sends the assignment in the form of a SDL WorldServer package which contains the pre-processed files that have to be translated in SDL Trados Studio using the associated translation memories (TMs):
- The file-based TMs assigned to the SDL WorldServer package. These are the offline versions of the TMs, as they were available when the project was created.
- The server-based TM assigned to the SDL WorldServer package*. This is the live version of the TM, with the most up-to-date translation data. To read and update this TM, you need SDL WorldServer credentials to the server where the project is located.
- Gives access to the SDL WorldServer termbase (TB) associated with the project
- Shows the SDL WorldServer File Attributes and Project Attributes
- Sets the QA Checker Profile configurations ** and the TM Penalties ** defined by the SDL WorldServer Project Manager, automatically
The bilingual files that the package contains have tracked changes in the source segments to indicate what updates need to be made for the current project.
Why use this workflow?
You would use this workflow if you received a project package from SDL WorldServer.
The process requires that the Project Manager in SDL WorldServer specifies certain filter settings that enable tracked changes to be viewed in the source segments in SDL Trados Studio. The steps you follow in SDL Trados Studio also indicate what settings you need to specify and the practices that you need to follow to ensure that changes to translations are tightly controlled. You can deviate from these steps. For example, the review step could be initiated from Trados Studio as opposed to WorldServer.
* For packages created in WorldServer 10.3 and higher.
** For packages created in WorldSever 10.4 and higher.