A contract arrives with underlined additions, struck-through clauses, comments in the margin, and a translation deadline. The first question isn’t which translation tool to open. It’s what the recipient expects the translated file to show: approved wording only, the editor’s proposals, or a review trail that mirrors the source.
A Word file with tracked changes isn’t simply a clean document with visible marks drawn over it. The marks represent structured revision data, and accepting or rejecting them changes which wording belongs in the final text. A translation workflow that ignores that distinction can produce a polished target file with the wrong content or no useful review history.
This guide helps you choose what to translate, decide whether to preserve markup, compare the result, and avoid turning a reviewer’s unresolved choices into an accidental editorial decision. The short version: settle the deliverable first, test the exact Word or translation workflow on a copy, and inspect the result before sending it onward.
Start with the deliverable, not the translation tool¶
The right workflow depends on what the receiving person needs to do with the translated file. A client who wants a readable final document needs something different from a lawyer who needs to review every proposed clause.
Write down the deliverable in plain language before you process the DOCX. Useful descriptions include:
- “Translate the approved text only. Resolve all revisions before delivery.”
- “Translate insertions and retain deletions as visible review markup.”
- “Provide a clean target document and a separate change log.”
- “Translate the document, but keep source comments available for the reviewer.”
- “Create a target-language review copy in which translated wording appears as tracked changes.”
Those instructions separate three jobs that people often bundle together: deciding which source wording is authoritative, translating that wording, and showing the review history. A translator can do the translation, but shouldn’t decide whether a contested clause is approved unless the project brief gives that authority.
A practical default follows from Word’s accept-and-reject mechanics. Resolve revisions first when the recipient needs a final approved text. Preserve or extract revision content when the recipient needs to assess proposals. Ask the document owner to decide when tracked changes conflict or leave the intended wording unclear.
Microsoft explains that accepting or rejecting a revision changes the document: acceptance keeps inserted content and removes deleted content, while rejection reverses those choices. See Microsoft’s instructions for accepting or rejecting tracked changes. A visual display setting is not the same as a decision.
For example, imagine a clause that originally says “the supplier may terminate” and contains an insertion changing “may” to “must.” If the translation begins before anyone confirms whether the insertion is approved, the translator faces two possible meanings. Choosing one silently doesn’t solve the source ambiguity; it hides it in the target.
A translation brief should name the treatment of insertions, deletions, comments, and final output separately. If the brief says only “keep Track Changes,” ask what that means in the target file. It could mean retaining the source document’s history, showing translated wording as a new revision, or simply delivering a document with Word’s tracking feature switched on. Those are not interchangeable outcomes.
Microsoft Support says: “To remove tracked changes, you must accept or reject them. Choosing the No Markup view only temporarily hides changes. They will be visible again the next time someone opens the document.” Read the full guidance.
That distinction matters when someone sends a file that looks clean on screen. A No Markup view can hide unresolved edits without removing them. Before translation, check whether the file contains pending revisions rather than relying on how it happens to look when opened.
What Word tracks, and why appearance isn’t enough¶
Word marks insertions and deletions so reviewers can see how text changed. In the usual display, additions appear underlined and deletions appear struck through; edits by different authors can use different colors, according to Microsoft’s Track Changes guidance.
The DOCX format stores revision information as structured content. The WordprocessingML elements w:ins and w:del represent inserted and deleted text, respectively. An insertion can include details such as its author and date, and deleted wording is held within a deletion wrapper rather than treated as ordinary visible text. The OOXML reference for inserted content describes the insertion element and its metadata; the reference for deleted content describes the deletion element.
That structure explains a common surprise: turning Track Changes off doesn’t resolve existing revisions. The setting stops Word from marking new edits, but old revision data remains until someone accepts or rejects it. Likewise, choosing No Markup changes how the file is displayed, not what the file contains.
A DOCX can therefore present several different layers that need separate attention:
| Layer | What it means | Translation question |
|---|---|---|
| Accepted body text | Wording currently present as ordinary document content | Is this the agreed source text? |
| Inserted text | Proposed wording stored as a revision | Should the insertion be translated as part of the main text, or shown as a proposal? |
| Deleted text | Wording marked for removal but still available in the revision data | Does the recipient need to review the deleted wording in the target language? |
| Comments | Reviewer notes attached to document content | Should comments be translated, retained in the source language, or omitted? |
| Author and date details | Metadata associated with revision activity | Should the target file retain this history, or should a clean copy remove it? |
| Display settings | The view Word uses to show or hide markup | Does the file merely look clean, or have revisions actually been resolved? |
Word’s visual conventions make revisions easier to scan, but they don’t settle editorial meaning. A red insertion may be an approved change, a suggestion that still needs discussion, or an edit from one reviewer that another reviewer disputes. Color and formatting identify a revision; they don’t establish approval.
Comments add another layer. A note like “confirm with legal” isn’t necessarily text to translate into the body. The project owner should say whether comments are in scope, whether they need translation, and whether their positions should stay attached to the same passages. Treating comments as ordinary paragraphs can make the translated file harder to review.
A useful intake check is to ask the sender for a copy with the intended review display and then inspect its revision state in Word. Don’t ask them to hide markup as a substitute for resolving it. If the final target needs to preserve review history, save an untouched source copy before accepting, rejecting, extracting, or comparing anything.
Choose a workflow for the review state¶
No single method suits every DOCX with tracked changes. The options below depend on whether revisions are settled, whether a review trail matters, and how much control the recipient needs over the target file.
| Workflow | Best fit | Main trade-off |
|---|---|---|
| Accept or reject revisions, then translate | The recipient needs approved final text | Resolving revisions removes the unresolved alternatives from that working copy |
| Translate a clean copy and keep the marked source separately | The review history matters, but the target can be a clean document | The target won’t automatically show translated text as matching source revisions |
| Extract revision text for translation | Only specific insertions, deletions, or comments need translation | Extraction makes a separate translation task; it doesn’t preserve the original revision history by itself |
| Translate first, then create tracked target edits | The recipient explicitly needs translated wording displayed as revisions | Requires a deliberate review and markup step; a simple export may not create the intended history |
| Compare source and target with Word Compare | A reviewer needs to inspect differences in a new document | A same-language comparison and a translation comparison answer different questions |
Resolve the source before translating¶
When the source document contains proposals that have already been decided, ask the owner to accept or reject them. Word lets a reviewer move through revisions one at a time or resolve them in bulk. Bulk actions are appropriate only when the reviewer has already chosen which version is authoritative. Microsoft’s accept-or-reject instructions describe both approaches.
After resolution, save a distinct clean source file and retain the marked original if the review record matters. The clean file gives the translator a stable text to work from. The marked original lets the owner return to the discussion if a question arises.
Don’t use Accept All as a shortcut when reviewers have made competing changes. The operation is a content decision, not a formatting clean-up. If two proposals conflict, the document owner should select the intended wording or consolidate the reviewer input before translation.
Preserve the history outside the target¶
A recipient may need the original revision history for audit or legal review without needing that history reproduced in the target language. In that case, retain the source DOCX as a separate record, and translate the agreed text into a clean target copy. Name the files so the distinction is unmistakable, such as “source-review” and “target-approved,” following the team’s file-naming conventions.
A separate source copy avoids implying that translated revisions are an exact continuation of the original authors’ edits. The translator can make target-language decisions that don’t map neatly to individual source words, and a source insertion may require restructuring a whole sentence in the target.
Extract revision content when only part needs translation¶
Extraction can help when the document owner wants the translator to focus on inserted wording, comments, or selected revisions instead of translating the entire file again. A practitioner describes a macro-based approach that places tracked-change content into a separate Word document, then removes deleted text before translating insertions in a CAT tool. The method is an extraction strategy, not preservation of the source’s original revision history. See the practitioner article on extracting track changes.
Extraction needs a careful scope check. A macro may count or extract some revision types while leaving out others; the cited article specifically warns that its counting macro counts inserted words while ignoring deletions and other revision types. Test any macro on a duplicate, inspect the extracted table against the source, and follow your organization’s macro-security policy.
A short extracted table also needs context. A proposed phrase can depend on surrounding text, definitions, references, or a comment elsewhere in the file. Give the translator enough adjacent wording to understand what the revision changes, then check that the translation can be reinserted in the correct place.
Create tracked changes in the target as a separate task¶
A request to “export the translation with tracked changes” can mean the translated target should display its wording as new revisions. That output isn’t the same as retaining the source file’s revision metadata. The translator may need to create the target text first, then place it into a copy of the source or another agreed base document with tracking enabled.
An RWS Community discussion highlights that distinction. One participant describes wanting to translate a standard Word file and export the translation with Track Changes. A community reply suggests copying the source to a target, enabling tracking, and then translating, but notes that the proposed workflow wasn’t tested in the initial reply. Another post describes translating and checking first, then copying the translations into a source-to-target copy with tracking enabled. Read the discussion of exporting translation as tracked changes.
A participant in the RWS Community forum describes the goal as: “Import untranslated document (standard word document; some fields, text, headings; no tracked changes). Translate document in Trados Studio. Export document to MS Word with Tracked Changes.” See the forum thread.
The forum exchange isn’t a universal guarantee for a particular CAT tool or Word version. Treat target-side markup as a production requirement that needs a sample test. Agree what the initial text is, which target edits should be tracked, who should appear as the author, and whether the final file should include comments or only revisions.
Compare the available translation options¶
Translation tools differ in how they handle files and review data. A translation route that produces readable target text may still fail the separate requirement to preserve tracked revisions or comments.
Word’s whole-document Translator¶
Word’s whole-document Translator is available through Review > Translate > Translate Document. Microsoft’s instructions say the feature opens a separate translated copy rather than replacing the original. The same support page lists a Microsoft 365 subscription or Office 2021, internet access, and enabled Office connected experiences as requirements; check the current Microsoft instructions for your Word build.
The instructions describe creating a translated copy, but they don’t promise that tracked revisions or comments survive the translation. That doesn’t prove the feature always removes them; it means preservation isn’t documented as a guaranteed result. Test a duplicate in the exact Word version and account environment you plan to use.
A good test file should contain at least one insertion, one deletion, a comment, and a passage with ordinary text. After translation, reopen the output and inspect each element. Check what happens to the revision text and metadata, not only whether the translated paragraphs appear.
CAT tool or translator workflow¶
CAT tools can help translators handle repeat terminology, segments, and review tasks, but the target document’s revision display still needs to be specified and tested. “Translate the DOCX” and “deliver a DOCX that presents the translation as tracked changes” are separate requirements. The latter can involve a deliberate second pass after the translation is checked.
When several reviewers have contributed to the source, use Word’s Combine process if the aim is to consolidate those reviewers’ edits. Microsoft says Combine creates a new document with revisions and can merge further copies successively. The Combine document revisions guidance explains that workflow. Combine is for bringing reviewer edits together, not for turning translated text into a faithful copy of the source’s revision history.
Document translation with a bilingual review view¶
For a DOCX where formatting and review of the translation both matter, a document-translation tool can handle file structure while a person checks the language. For example, ChatsControl reads a DOCX paragraph by paragraph and cell by cell, then writes the translation back into the same paragraphs and runs. The tool also provides a bilingual side-by-side review view, with the translated text highlighted and the source available on hover.
That view can help a translator or reviewer check meaning without constantly switching between separate files. It doesn’t mean source tracked changes are automatically preserved or converted into equivalent target-language revisions. Confirm the revision requirement separately, and don’t treat a bilingual review screen as a substitute for a Word deliverable containing the requested markup.
The tool is a document-translation option, not a full CAT tool or TMS. It doesn’t provide translation-memory leverage, segment-level project management, or team vendor workflows. If the project depends on those functions or strict on-premise handling, choose a workflow that meets those requirements instead.
| Option | What it can help with | What to verify |
|---|---|---|
| Word Translator | Producing a separate translated copy from Word | Whether revisions and comments survive in the exact Word environment |
| CAT tool workflow | Translating and reviewing document content in a structured workflow | Whether the export creates the requested target-side revisions |
| Document translation tool | Translating the DOCX while retaining its document structure | Whether Word’s revision history is preserved, translated, or replaced |
| Manual extraction and reinsertion | Translating selected revision text with context | Whether every relevant revision type and comment was captured |
| Word Compare or Combine | Comparing two files or consolidating reviewer edits | Whether the chosen command matches the actual task |
A practical workflow from intake to delivery¶
A repeatable process reduces the chance of translating the wrong version or sending a file that only looks ready. Use the following checklist for a DOCX with revisions.
- Confirm the requested output. Ask whether the recipient expects approved text, visible translated proposals, translated comments, or a clean translation plus the source review record. Record the answer in the job instructions.
- Save an untouched source copy. Keep the original marked file before accepting, rejecting, extracting, or comparing revisions. Work on a duplicate so you can return to the source state.
- Inspect revision and comment content. Turn on a view that exposes markup, then check insertions, deletions, comments, and reviewer conflicts. Don’t infer approval from the color or age of an edit.
- Resolve or preserve revisions according to the brief. Ask the owner to decide competing proposals. Accept or reject only when the intended final text is clear; otherwise, preserve the marked source and agree on an extraction or review workflow.
- Translate the agreed content. Use the chosen translation route, with instructions for terminology and treatment of names, comments, and deleted wording. Keep the unresolved source material available when it affects meaning.
- Check the translated document. Compare the target against the agreed source text, verify that headings and tables remain readable, and review every passage that depended on a revision or comment.
- Test the review markup and reopen the file. If the target is meant to show tracked changes, inspect insertions and deletions in Word and reopen the saved file to confirm the markup is still present. If the target should be clean, verify that unresolved revisions haven’t merely been hidden by a display setting.
- Run the final document check. Use Word’s Document Inspector as a final check for tracked changes and comments, along with hidden text and personal names in document properties. Make sure inspection doesn’t remove information the recipient asked to retain.
Word’s Compare feature can create a third document showing differences between two files without changing the source documents. Microsoft’s legal blackline comparison guidance describes that output. A comparison can help locate changes, but a translated target isn’t a same-language edited copy: normal translation differences may appear throughout, so a reviewer still needs to assess meaning and agreed revision status.
When files already contain tracked changes, Word may prompt the reviewer to accept changes before comparison. Microsoft’s legal-blackline guidance says the output accepts changes in the original and presents differences from the revised document as tracked changes. Read the prompt carefully and work from copies, because the result may not represent the unresolved revision state the sender intended.
A typical decision looks like this: a reviewer has proposed a new limitation in a contract clause, and the document owner has not approved it. The translator shouldn’t turn the proposal into definitive target wording. The owner can decide whether to accept the insertion, reject it, or ask for a translated version of both alternatives. The translator can then deliver the agreed text and, if needed, a separately labelled review copy.
For projects that use ChatsControl as a translation step, the DOCX is uploaded and translated while its paragraphs, runs, and cells are read and written back in place. A reviewer can then use the bilingual view to compare source and target text. Keep a separate Word review step for the original revisions: formatting preservation and bilingual checking don’t establish whether source changes were accepted.
Common pitfalls and how to avoid them¶
Most errors come from confusing display with document state, or treating a revision as a formatting mark rather than a change in meaning.
Turning off Track Changes doesn’t clean up old revisions¶
Track Changes off means Word won’t mark new edits in the same way. Existing tracked revisions can remain in the file. Accept or reject them when the recipient needs final text, or preserve them deliberately when review history is part of the deliverable.
A document can therefore look ordinary after someone switches off the feature while still containing unresolved edits. Inspect the revision state before translation and verify the saved output after processing.
No Markup is a view, not a finalization step¶
No Markup can make the document easier to read, but it hides the marks temporarily rather than resolving the underlying revisions. Microsoft warns that those changes can reappear when the document is reopened in its guidance on accepting or rejecting tracked changes.
Don’t send a No Markup view as proof that a file has been finalized. If the deliverable needs clean text, resolve the revisions. If the deliverable needs a review trail, make sure the trail is retained intentionally.
Accept All can choose the wrong text¶
Bulk acceptance can remove the very alternatives the document owner still needs to consider. A document with competing edits from different people isn’t ready for a mechanical accept-all step. Ask the owner to decide, or use Combine to consolidate reviewer edits where that is the goal.
Word’s Combine guidance is relevant when merging contributions. A combined document still needs human review: consolidation doesn’t make conflicting proposals agree or identify which version is authoritative.
Deleted wording can still matter to the translator¶
Deleted text may affect the meaning of a comment, a cross-reference, or an unresolved choice. Translating every deleted passage into the main target text would be misleading, but ignoring all deletions can remove information the reviewer needs. Decide whether deletions should be translated as review notes, retained in a separate change log, or excluded after the owner approves the final wording.
The document format stores deleted text in revision data, using w:del and w:delText, as described by the OOXML reference. The visible strikethrough is only one way Word displays that structured information.
Comments can drift away from their context¶
A comment may refer to a phrase that changes position or disappears in the target. If comments are in scope, check that each one remains understandable and attached to the intended passage. A translator shouldn’t silently turn a reviewer note into body text or discard a note that contains a required decision.
Agree whether comments should be translated, kept in their original language, or removed from the target. The same decision applies to author names and dates if the recipient wants a clean file rather than a review record.
A translated copy doesn’t prove revision preservation¶
Microsoft’s whole-document translation instructions describe a separate translated copy, not guaranteed preservation of tracked changes. Test the exact file and Word environment before making the method part of a production workflow. Include a comment, insertion, and deletion in the sample so the test covers more than visible body text.
Macros and extraction can miss data¶
A macro that collects insertions may not capture deletions, comments, formatting changes, or every revision type. The practitioner article on track-change macros documents limitations in its particular method; it shouldn’t be treated as a guarantee about all macros.
Use an approved macro only on a copy, inspect the output against the source, and follow internal security rules. If the extraction cannot be verified, use a controlled manual process or ask the document owner for a settled source.
Microsoft describes legal blackline as a comparison that “displays what changed between them in a third new document” while leaving the compared documents unchanged. Read Microsoft’s Compare guidance.
That feature is useful when you need a separate comparison record, but it doesn’t resolve the question of which source edits should be translated. Choose Compare for differences between documents and Combine for consolidating reviewer edits; choose acceptance or rejection when the owner has decided the final wording.
FAQ¶
Should I accept tracked changes before translating a Word document?¶
Accept or reject revisions first if the target should contain only approved final wording. Keep the marked source or extract the revision content if reviewers still need to assess proposals.
How can I translate a DOCX and keep tracked changes visible?¶
Agree what the target markup should represent, then test the complete workflow on a copy. Check insertions, deletions, comments, author details, and revision history after saving and reopening the output.
Does Word’s Translate Document feature preserve tracked changes?¶
Microsoft describes Translate Document as opening a separate translated copy, but its instructions don’t promise preservation of tracked revisions or comments. Test a sample in the exact Word version and environment before relying on it for a review deliverable.
How do I compare a translated Word file with the original?¶
Use Word Compare to create a separate document showing differences between two files, and review source and target together for meaning. Translation changes wording throughout, so a comparison alone can’t decide whether a source proposal was approved.
How should deleted text and insertions be handled in a translation?¶
Translate approved insertions as part of the agreed text. Treat deleted wording according to the brief: preserve it for review, extract it as an alternative, or leave it out after the owner confirms the final wording.
Can I merge tracked changes from several Word reviewers?¶
Use Word’s Combine process when the purpose is to consolidate reviewer edits into a new document. Ask the document owner to resolve competing proposals before translation if the intended final wording remains unclear.
Is turning off Track Changes enough to remove existing markup?¶
No. Turning off tracking stops Word from marking new edits, but it doesn’t resolve existing tracked changes. Accept or reject revisions to remove them permanently from the working copy.
Does No Markup remove tracked changes from the DOCX?¶
No. No Markup changes the display, not the underlying revision state. The changes may appear again when the document is reopened, so resolve them if the recipient needs a genuinely clean file.