Microsoft Word

Learn how you can localize Microsoft Word (.docx) documents with Transifex.

Nina avatar
Written by Nina
Updated yesterday

File Extension(s)

.docx

i18n type(s)

MS_DOCX (for Microsoft Word)

DOCX (for Microsoft Word (Alpha))

Transifex supports Microsoft Word files (with the extension .docx). These files can be uploaded as either resource files or translation files.


Uploading a resource file

When such files are uploaded in Transifex, their formatting (styles, images, tables, hyperlinks, headers/footers, etc.) is preserved.

The following screen appears when a .docx file is uploaded:

ms_docx_upload.png#asset:8331

It is essential to select the Microsoft Word (.docx) NEW option in the dropdown list for the formatting of the file to be preserved.


Translating a Microsoft Word resource in the editor

When the source strings are formatted, this is depicted by using <tx> placeholders. If the project maintainer has activated translation checks for the project and the translator does not respect the number and position of these placeholders, a warning or an error will be shown.

ms_docx_warning.png#asset:8332

💡Tip: Please refer to this article on how to manage translation checks. The file format you need to select is the "Microsoft Word files (.docx) checks", and the translation check you need to enable for either to show a warning or an error message is the “HTML tags are preserved in the translation”.

📝Note: The order of the source formatting tags is preserved in the translations upon export. For RTL languages, the translations are returned in RTL.


Duplicate strings

If your document contains duplicate strings, Transifex will display only one instance of that string in the editor. Once the translations are done, the generated translation files will have all the duplicate instances translated accordingly.


Downloading a resource file for translation

There are two options to download the resource file to translate it offline:

Screenshot-2021-02-19-at-7.35.35-PM.png#asset:8333
  1. Select “Download file to translate” from the popup menu. This action will download the resource as a .docx file.

  2. Select “Download file for translation as XLIFF” from the popup menu (for the Growth plan and up). This is the preferred option since the translators can focus only on the strings that need to be translated, no matter the formatting.


Parser behavior

The following table outlines what occurs to strings when using the API, CLI, or UI to manipulate translation files depending on download mode.


Upload a translation file

You can either upload the .docx file containing the translations or the translated XLIFF file (if you have downloaded the resource as an XLIFF file).

For the first option, it is advisable to maintain the structure of the resource file while translating offline. An error message will appear if the number of paragraphs in the uploaded translation file does not match the number of paragraphs in the resource file.


Microsoft Word (Alpha)

The .docx files were already supported in Transifex with the Microsoft Word (Alpha) file format. We decided to build a new DOCX parser to parse DOCX documents more efficiently and keep any inline formatting the text might have.


Migrating an existing Microsoft Word resource

To take advantage of the benefits of the improved Microsoft Word file parser, you must upload the same resource file as the new one. Since the file parsing is done differently, there may be a chance that existing translations will not be filled in automatically; in this case, you must copy and paste the translation based on the available TM suggestions in the editor.


💡Tip

Looking for more help? Get support from our Transifex Community Forum!

Find answers or post to get help from Transifex Support and our Community.

Did this answer your question?