How to Translate Word Cross-References and Fields Without Leaving Stale Results

A Word cross-reference is not necessarily ordinary text. The words you see can be a stored result generated from a bookmark or another document structure. Translate the source text that the field depends on, preserve its internal target, and check the result after updating the final document. Editing only the visible result can leave a translation that looks finished until the next field refresh.

This guide owns that dependency check. For styles, tables, section breaks, and general editable-file preparation, start with the Word formatting workflow.

Separate the code, target, and displayed result

Treat each reference as three things:

• Instruction: what Word should calculate or retrieve.
• Target: the bookmarked text, heading, caption, or other source used by that instruction.
• Displayed result: what the document currently shows, which may be stale.

Microsoft explains that cross-references are fields and that Word tracks referenced items through hidden bookmarks. In desktop Word for Windows, Alt+F9 switches between field instructions and displayed results. The instruction is not a sentence to send through translation. See Microsoft's cross-reference documentation.

For example, a reference may retrieve a caption's text. Translating the reference display into French while leaving the source caption in English does not establish a French dependency. Preserve the target identity and translate the appropriate source caption; then verify what regeneration produces.

Inspect a small specimen before trusting a long report

Download the synthetic English field specimen, its localized-source variant, and the reusable field inventory CSV. The specimen notes document its limits.

These are minimal structural examples, not customer files or outputs from BookTranslator. We inspected their ZIP/XML inventory, but did not test desktop Word rendering, field refresh, or a translation round-trip. They deliberately contain stale page values and a missing target. They are not finished documents.

The meaningful difference between the packages is the bookmarked caption source:

The unchanged English display in the second package makes the distinction visible: changing the source and regenerating its result are separate operations. It does not prove that Word or a translator has successfully performed regeneration.

Microsoft's OpenXML SimpleField reference describes the instruction attribute and child content of this field structure. Real DOCX files may also represent fields through separate begin, instruction, separator, and end runs. Do not assume every field can be found by searching only for one XML element.

Make a field inventory, not just a word count

Use the following distinctions when reviewing a report, thesis, or manual:

Record the region, instruction, target, expected target-language wording, and a verification decision. A field that is supposed to remain numeric needs a different check from one that reproduces a paragraph of text.

This is also where the do-not-translate decisions matter. Internal bookmark names are identifiers, not labels for readers. Renaming one casually can disconnect its references. If a template requires a structural migration, treat that as a separate editing task, not routine language replacement.

Translate, regenerate, then verify the final layout

Work on a copy and keep the original available for comparison. Our recommended sequence is:

1. Inspect the existing fields and targets before translation. Record pre-existing failures so they are not mistaken for new ones.
2. Translate the approved body text, headings, captions, and descriptive labels. Keep field instructions, sequence identities, and internal targets intact unless the document owner explicitly requests a structural change.
3. Complete target-language layout work before accepting page-based results. Longer headings or different line wrapping may change where a target appears.
4. Regenerate the applicable fields in the editing application.
5. Compare the result with the inventory, including the actual reference destination.
6. Save, reopen, and inspect the delivery version rather than relying only on an unsaved editing view.

For desktop Word on Windows, Microsoft documents selecting the body with Ctrl+A, then pressing F9. Tables containing formulas may require their own selection and refresh. If headings changed, choose the whole-table update for the table of contents rather than a page-number-only update. Check other regions separately; do not treat one body selection as proof that a header, footer, or every field has been checked. These instructions are not a universal shortcut for every platform or editor. Consult the current Microsoft field-update instructions.

Repair the relationship, not the error wording

Three failures need different responses:

• Old-language text returns after refresh. Inspect the source target. In the specimen, the caption source and stored REF display are independently inspectable; do not keep patching a result while ignoring its source.
• A page reference has the old number. Check the target's location in the final layout and regenerate the relevant field. A changed page number can be correct even though it differs from the original.
• The target no longer exists. Restore or recreate the intended target and rebuild the reference as needed. Translating an error message does not restore a bookmark.

Microsoft's bookmark troubleshooting guidance explains how bookmark edits and deletion can affect references. The specimen's MissingTarget is deliberately absent: no translation of the placeholder can make it a valid destination.

Do not convert every reference to static text just to make the document look clean. That may be acceptable for an explicitly requested static deliverable, but it removes the live dependency that an editable report needs. Preserve an editable master and document any intentionally flattened delivery copy.

Accept the file by behavior, not appearance

Before delivery, require a decision for every inventory item:

• The target still exists and represents the intended heading, caption, or passage.
• Displayed wording comes from the approved target-language source, not a stale cache.
• Sequence and page references agree with the final document.
• Table formulas agree with an independent numeric check.
• No unresolved reference errors are concealed by translated or manually replaced text.
• Any static references are intentional and recorded as such.

The specimen's table uses 2 + 3 = 5 only to make the formula dependency easy to inspect. It is not evidence of accounting accuracy, and its page placeholders are not expected pagination results.

For a usable DOCX that needs a complete-file translation draft, BookTranslator's DOCX workflow is a possible next step. This guide does not establish that BookTranslator preserves or refreshes every Word field, bookmark, table of contents, or formula. Inspect a representative file and complete the field-level checks before relying on the output. Compare tools by this acceptance requirement using the DOCX tool-selection guide, rather than treating a formatting claim as proof that dynamic references survived.