Notes on the Bilingual DOCX Format

The project package that WorldServer provides for external review consists of one or more DOCX files. The files consist of the assets segmented by SDL file types.

If the WorldServer administrator has specified the bilingual DOCX format as one of your system options, you can create a DOCX file for your reviewers in one of two ways. See other WorldServer online help topics for more information on importing and exporting assets.

WorldServer Explorer
Select the source folders or assets to export and select Tools > Export/Import > Export Translation Kit from the WorldServer Explorer menu bar. The bilingual DOCX format will be one of the export and import options.
Workflow Automatic Actions
Use export and import AAs inside a workflow to specify the bilingual DOCX format for a translation kit. When you run the workflow, the review file will be produced at the appropriate step. When your reviewers are done, you provide the file back to WorldServer to pick up in the import step.

Export

When you plan to export assets for external review in a DOCX format, note the following.

  • For assets originally in DOCX format, use the track changes setting option for the Microsoft Word 2007-2010 File Type in WorldServer. This lets you see tracked changes in Studio when you work with the translated asset.
  • The export process creates a bilingual DOCX file whose filename consists of the WorldServer folder name and a long numerical "fingerprint" to identify it.
  • The only export option available is Segments to Exclude, which means that the file won't include segments for which there are ICE or 100% matches in the translation memory. See the WorldServer online help for more information.
  • New properties in the exchange.properties file govern the style of the exported file. See the appendix to the WorldServer Administrator Guide for details.

Import

When you import assets back into WorldServer from a bilingual DOCX file, note the following.

  • The filename must be the same as when you exported it (as for all translation kits).
  • The import will only change the existing target translations for the assets.
  • A second import of the same file will be ignored and have no effect on the assets.
  • Sub-segment comments are elevated to the segment level comments upon import, just as for any Studio kit import.
  • The status of updated segments will be changed to No Status.
  • If segments with track changes are saved in translation memory, the REVISIONMARKER placeholders and deleted strings are removed. In other words, the TM segment is stored as if all track changes are accepted.
  • If some segments contain track changes, and if the original asset format is DOCX, the target asset contains track changes. For any other asset format, track changes may result in illegible text.