About a WorldServer translation workflow for a Regulated industry
WorldServer Translation workflow scenario
Assume you are a translator. You receive an assignment from a project manager to localize several MS Word *.docx files that contain information about the use of certain medications. Previous versions of these documents 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:
- the file-based TMs assigned to the 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 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 WorldServer credentials to the server where the project is located.
The WorldServer package also gives access to the WorldServer termbase associated with the project, shows the WorldServer File Attributes and Project Attributes and automatically sets the QA Checker Profile configurations ** and the TM Penalties ** defined by the WorldServer project manager.
The bilingual documents that the package contains have tracked changes in the source segments to indicate what updates need to be made for the current project.
Follow the workflow for WorldServer packages in a regulated industry to translate the documents and send them for review.
Why use this workflow?
You would use this workflow if you received a project package from WorldServer that is for translation for a regulated industry.
* For packages created in WorldServer 10.3 and higher.
** For packages created in WorldSever 10.4 and higher.