Translation Resources

Bilingual DOCX

MXLIFF files can be exported into a bilingual DOCX file and back. This is typically used to make edits before re-importing the file back to Memsource. It is not recommended for translation. Changes in locked segments of a bilingual DOCX are ignored when the file is uploaded back to Memsource.

Bilingual DOCX files can be generated and uploaded from the Jobs Table or from the Editor.

Use Cases:

  • Running a spellcheck in a text editor rather than in Memsource Editor.

  • Passing a bilingual DOCX file to a customer or another user who prefers working in text editors (as an unclean document).

Restrictions:

  • The text is exported in a wide and long table and is not suitable for printing.

  • Only the translation for the first instance of a repetition is displayed. Notification is given at the top of the bilingual DOCX file: When a segment gets repeated, the font is light grey, and you do NOT have to translate it.

  • Tags are not protected.

  • In RTL languages (Arabic, Hebrew), tags such as {2> will be inverted to <2{ In order to get correct tags in Memsource, the tags in RTL Word must be <2{ word }2>

  • TM, TB, and MT are not available for bilingual DOCX files.

  • Segments cannot be sorted or filtered.

  • Segments cannot be confirmed (They can only be uploaded and then confirmed in Memsource Editor).

  • Comments are read-only. Changes will not be imported back into Memsource.

  • When using multilingual DOCX files to move contents across jobs, bilingual tables may have up to 1000 lines. Copying large parts of text may need to be done in parts.

  • Download an MXLIFF version of a document as a local backup before uploading large or heavily modified bilingual DOCX files. Job updates from DOCX or MXLIFF files cannot be undone.

Bilingual DOCX can also be re-formatted into a Trados unclean DOCX using Word macros from third-party PlusToyz.

Tip

Uploading part of a bilingual DOCX is not directly supported, but there is a workaround:

In the bilingual DOCX, delete the unwanted lines. Ensure that the table header is kept at the beginning of the file. The bilingual DOCX can then be uploaded.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question you can leave a public comment below or Submit a request to our Support team.
Thank you for your feedback.

Comments

0 comments

Article is closed for comments.