Word Comments and Tracked Changes Lost After Translation
EqualangIn brief
How to check whether Word comments, tracked changes, and page layout survived translation, plus manual ways to preserve review markup in a DOCX file.
Keywords: word comments lost after translation; tracked changes lost after translation; check translated docx markup; translate reviewed word document; preserve word layout
Whether Word comments and tracked changes survive document translation depends on how the file is processed, so you must inspect the returned .docx in the Review tab before sending it to a client or colleague. If your review markup is missing or detached from the right words, you can either resolve revisions onto a copy before translating or re-link notes manually from your original file.
How to verify your returned DOCX before sending it on
Open both the source .docx and the translated .docx side by side in desktop Word. Rather than scrolling through pages by eye, run three quick checks in the Review tab:
- Switch Display for Review to All Markup: Look at the right-hand margin balloons and inline insertions or deletions. Confirm whether markup is present at all or if the document was flattened into plain body text.
- Open the Reviewing Pane: Click Reviewing Pane (vertical or horizontal) to see the total count of revisions and comments at the top of the panel. Compare that number directly against your source file.
- Click Next through each comment anchor: Jump from comment to comment using Next in the Comments group. Because word order shifts between languages, check that each highlight still wraps the intended phrase rather than an adjacent sentence or an empty space.
If you only have a legacy .doc file, save it as .docx first and verify that all comments and tracked insertions still appear in the Reviewing Pane before you run any translation workflow.
Manual ways to handle a reviewed Word file
When you cannot afford to lose a single revision record during translation, separate the body text from the review history before you start:
- Keep an untouched archive and translate an accepted copy: Save a duplicate of the
.docx, accept the settled tracked changes in the duplicate, and translate that clean copy so redlines do not break sentences in half. Keep the original file open beside it to re-enter remaining open questions as fresh comments on the translated text. - Compare two clean versions after editing: If two reviewers are working in the same target language, translate a clean baseline first and use Word's Review → Compare → Compare Documents tool afterward to generate a fresh set of tracked changes between the baseline translation and the edited draft.
- Copy comment text into a two-column reference table: When comments contain long explanations that the recipient also needs to read in the target language, copy the comment author, anchor phrase, and comment body into a separate
.docxtable, translate that table alongside the main file, and paste the translated notes back onto the corresponding passages.
Translating the DOCX layout with Equalang
We built Equalang to translate .docx files while keeping the surrounding document structure editable. On our two-way Word sample, the translated .docx stayed on one page and kept its three sections, product tables, numbered and bulleted lists, headers and footers, and inline bold, italic, color, and underline formatting, ready for further editing in Word.
We do not have verified test records for how Word comments or tracked changes behave after translation in Equalang. Do not assume review balloons or redlines will carry over intact—if you upload a .docx that contains active markup, run the Reviewing Pane and anchor checks above on the downloaded file before sharing it.
A few other practical boundaries apply when you use Equalang for Word documents:
- File format and queue: The web uploader accepts
.docx(not legacy.doc) one file at a time, runs up to three documents simultaneously per account, and queues additional uploads automatically. - Side-by-side workspace: Once a job finishes, the translation workspace displays the source on the left and the translation on the right so you can compare paragraphs before downloading the
.docx. - Layout details to inspect: Font size and line wraps shift when the target language is longer or shorter, footers and small details still need a visual pass, and in Arabic
.docxoutputs paragraphs switch to right-to-left while tables keep their first column on the left.
Document translation in Equalang currently covers Chinese, English, Japanese, Korean, Spanish, French and other languages with automatic source language detection, and signing up includes 200 credits so you can test a sample file first. After downloading the translated .docx, run the three-step Review tab check above to confirm both the layout and any review notes meet your team's handoff standard.
Sources
- Equalang Document Translator
- Equalang Overview
- Microsoft Word Review Tab Documentation (Track Changes, Comments, Reviewing Pane, and Compare Documents)