A translated paragraph can read perfectly while its footnote points to the wrong source. That mismatch is easy to miss when the notes sit outside the main text, and it can make an otherwise polished report hard to verify.
Footnotes and endnotes are linked parts of a document, not loose lines of small print. A sound translation workflow protects both sides of each link: the reference mark in the body and the note text it identifies.
This guide explains how to translate notes in Word, what to do with citations, how different workflows compare, and how to check the finished file. The same checks help with reports, contracts, manuals, articles, and other documents where a reader needs to trace a claim to its source.
What footnotes and endnotes contain, and why their links matter¶
A footnote is a note connected to a reference mark in the body and displayed at the bottom of a page; an endnote is connected to a reference mark and displayed at the end of a document or section. Both can carry explanations or references, as Microsoft Support describes.
In Word, the reference mark and note text form a linked pair. The mark appears in the document body, while the associated footnote text appears at the page bottom. An endnote uses the same basic relationship, with its text placed at the document end. The editor manages that connection, so a note is not simply a paragraph typed beneath the main text.
That distinction matters when a file goes through translation or editing. If someone removes a reference mark, the connected note may be removed too. If someone deletes note text instead, Word can renumber notes in a new order. Microsoft’s instructions for deleting notes explain why the safest cleanup starts with understanding which part of the structure is being changed.
A note can contain more than one kind of language. An explanatory sentence may need translation, while a book title, journal name, identifier, or page reference may need to remain unchanged. Those elements can sit side by side in a single note, so translating the entire line without distinguishing its parts risks changing bibliographic information that the reader needs to find.
Microsoft Support says: “Use footnotes and endnotes to explain, comment on, or provide references to something in a document.”
That description covers the two main jobs of a note, but it doesn’t tell you to treat every note as ordinary prose. First identify whether each part explains an idea, identifies a source, or does both.
A useful way to think about the task is as two connected checks:
- Language check: Does the translated note say what the original note says?
- Structure check: Does the body marker still point to that note, and does the note still appear in the intended place?
A translator can pass the language check and still leave a broken document. A reader may see a familiar note number in the text but find a different citation at the bottom of the page. The translated wording won’t reveal that structural error on its own.
For a team translating files rather than copied text, keep the original document available throughout review. The guide to translating Word and DOCX files explains why formatting and document structure can change when content is handled outside its original file.
Decide what to translate inside each note¶
A footnote translation workflow starts with classification, not rewriting. Mark the note’s explanatory prose separately from its citation details, then apply the client’s or publication’s rules to each part.
There is no universal instruction in the available source material that says every citation title must always be translated or always left in its source language. Treat the following as an editorial workflow, not a binding citation standard: translate explanatory language, then preserve and verify bibliographic fields, identifiers, locators, and source titles according to the relevant style guide or client instructions. The XLIFF 2.0 standard offers a useful model for separating translatable content from non-linguistic elements such as formatting codes and placeholders.
| Note element | Typical action | What to check |
|---|---|---|
| Explanatory prose | Translate | Keep the meaning, references, and qualifications intact. |
| Source title | Follow the required citation style or client brief | Check whether the cited work has an established translated title and whether the original title must also appear. |
| Author or organization name | Preserve the identifying name; follow project rules for transliteration | Compare spelling with the source and the project’s approved names. |
| Publication details | Preserve and verify | Check dates, edition details, publisher, volume, and issue against the source note. |
| Page or section locator | Preserve the reference and its relationship to the source | Check that digits, ranges, and labels haven’t changed accidentally. |
| DOI, URL, or other identifier | Preserve exactly unless project instructions say otherwise | Make sure the identifier still resolves to the same source. |
| Quoted text | Follow the project’s quotation policy | Check whether the translated quotation needs an indication that it is a translation. |
The table gives you a review checklist, not permission to override a style guide. A publisher may set its own rules for translated titles, transliterated names, or quotations. When the client has supplied instructions, those instructions take precedence over a translator’s general preference.
A mixed note illustrates why the distinction matters:
For the concept, see Title of Work, 2nd ed., p. 43. The author uses this term in a narrower sense.
The final sentence is explanatory prose. The title, edition, and page locator are citation details. A translator may need to translate the explanation while leaving the title as published, translating it in brackets, or following another style rule. The choice depends on the brief. The translator should not quietly invent a new title or alter a page reference.
Before starting, ask the client or project lead:
- Which citation style applies?
- Should source titles stay in their original language?
- Are published translations of cited works preferred?
- Should quotations be translated, kept in the source language, or shown in both?
- Are author names to remain as printed, or should an approved transliteration be used?
- Should URLs and identifiers be checked, or only preserved?
Clear answers reduce avoidable back-and-forth and give reviewers a basis for checking decisions. A short translation brief can also record preferred terms and naming conventions, so separate notes don’t handle the same person or concept differently.
Take extra care with a note that combines a citation with commentary. Moving punctuation or changing the boundary between the two can make it unclear whether a translated phrase belongs to the source title or to the note writer. Preserve the structure of the original where possible, and check ambiguous cases against the surrounding paragraph.
Choose a workflow that fits the file and review needs¶
Three practical options cover most document translation projects: a translation bureau, a freelance translator, or an online document workflow. The right choice depends on the file, the amount of human review required, and how much formatting work the team can do.
A bureau can be a good fit when the document needs a managed process, specialist review, or coordination across several people. Ask how the team will handle note structure, citation conventions, and the editable output. A promise to translate the text alone doesn’t answer whether the delivered document will preserve the references.
A freelancer may suit a project with a clear brief and one accountable translator. Before assigning the work, confirm that the translator can edit the source format and will check the final note sequence, rather than delivering only translated text for someone else to paste into the file.
An online document translator can help when the project needs a first draft or a reviewable file without manually copying every note into a separate text box. Tools still differ in supported formats and in how they handle document structure, so inspect the returned file instead of assuming that a translated note remains linked correctly.
In ChatsControl, a team uploads a DOCX or PDF and receives a translated Word file with document formatting preserved. A bilingual side-by-side review view shows the source beside the translation, which helps a reviewer compare wording in notes as well as in the main text. ChatsControl is a document-translation tool, not a full CAT tool or TMS, so teams that require translation memory or segment-level project management should account for that limitation. See ChatsControl for the workflow.
| Option | Useful when | Questions to settle | Main limitation |
|---|---|---|---|
| Translation bureau | The project needs a managed handoff or specialist coordination | Who checks note links, citation style, and the final editable file? | The project still needs clear instructions and a defined review scope. |
| Freelance translator | One translator can own the language work and document review | Will the translator return an edited file and check every marker-note pair? | The client may need to coordinate additional reviewers or formatting work. |
| Online document workflow | A team wants a translated document to review in its original layout | Which formats are supported, and how will reviewers inspect the notes? | Automated output still needs human review, especially for citations and document structure. |
Choose based on the actual handoff, not just on the translation interface. A workflow that returns plain text may require someone to rebuild every note manually. A workflow that returns a Word file can save that step, but it doesn’t remove the need to verify the result.
Google Docs offers a built-in document translation feature. Its Help page says the feature creates a translated copy in a new window and places that copy in Google Drive; if the option isn’t visible, the document may be in Microsoft Office editing and need conversion to Google Docs first (Google Docs Help). That page doesn’t specify how Translate document handles note anchors, so check the copy rather than assuming the links survived.
The editor itself also affects what you see. Google Docs supports footnotes in page-format documents, while in pageless format it displays them together at the end of the document (Google’s footnote guidance). A change in display position can look like a lost footnote even when the note remains in the file. Check the document’s format before deciding that the translation workflow dropped the notes.
LibreOffice Writer automatically numbers footnotes and endnotes, and its Writer Help explains how to edit note text and numbering properties. Different applications may present the controls in different places, but the review questions stay the same: does each marker point to the intended note, and does the note appear where the document expects it?
LibreOffice Help states: “LibreOffice automatically numbers the footnotes and endnotes.”
Automatic numbering helps maintain a sequence, but it doesn’t prove that the translation preserved the original relationship. A correctly numbered set of notes can still contain the wrong citation under a marker. Check both the sequence and the content-to-anchor pairing.
A step-by-step workflow for translating notes in Word¶
Use the same order for a short DOCX and a longer report: establish the source structure, translate with a clear brief, then compare the finished file against the original. The steps below keep language decisions separate from document checks.
- Save a clean source copy. Keep an untouched copy of the original file and work on a separate version. If the document contains tracked changes, resolve them according to the project instructions before translation; don’t assume deleted or pending text is irrelevant to the delivered document.
- Inventory the notes. Identify whether the document uses footnotes, endnotes, or both. Note the existing sequence and count, and flag any notes that combine prose with citations, URLs, identifiers, or quotations.
- Agree on citation rules. Record how the project handles source titles, names, quotations, locators, and identifiers. Ask the client about ambiguous entries instead of silently choosing a convention.
- Translate the document in its working format. Keep the body markers and note structure intact. If you use an online workflow, confirm the supported input and output formats and retain the source file for comparison.
- Review the language in context. Compare each note with its source and the sentence that calls it. Check that references such as “see above” or “as defined here” still make sense after translation and any change in pagination.
- Check structure and formatting. Compare source and output note counts, follow the body markers to their notes, and inspect numbering, placement, separators, indentation, and page breaks.
- Deliver the checked file with open questions recorded. Don’t hide unresolved title or citation decisions. List them for the client or editor, and make sure the final handoff identifies which file is the reviewed version.
A note inventory can be as simple as a review sheet:
| Check | Source file | Translated file | Pass condition |
|---|---|---|---|
| Note type | Footnote, endnote, or both | Same intended type | Note placement matches the document’s purpose. |
| Number of notes | Record the source count | Record the output count | Counts match, or every difference has an explanation. |
| Body references | Follow each marker | Follow each translated marker | Each marker points to the intended note. |
| Citation content | Record titles and identifiers | Compare the corresponding fields | Required details remain accurate and traceable. |
| Layout | Check note position and breaks | Inspect the output pages | Notes remain readable and attached to the intended pages or section. |
The pass condition isn’t simply “the numbers look sequential.” The sequence can be neat while a note has been paired with the wrong paragraph. Follow each reference mark to the note it identifies, especially after edits that add or remove notes.
Word provides note formatting controls for size, font, and indentation through its footnote and endnote views (Microsoft’s formatting guidance). Use those controls when a translated note wraps differently or no longer reads well. Don’t shrink note text automatically just because the target language takes more space; check whether the change harms legibility or conflicts with the document’s style.
ChatsControl’s DOCX workflow reads text paragraph by paragraph and cell by cell, along with formatting, and writes translated text back into the same paragraphs and runs. That mechanism matters when a note sits inside a structured file: content isn’t treated simply as a plain text dump. The result still needs a note-specific review, because preserving general formatting doesn’t certify that every citation decision or reference is correct.
Pitfalls that break footnote formatting or meaning¶
A note can fail in several distinct ways: the text can be wrong, the citation can be altered, the anchor can be disconnected, or the layout can make the note difficult to read. Review each failure type directly instead of relying on a quick visual scan of the main text.
Deleting the note instead of its marker. Word’s deletion guidance explains that removing a reference mark in the document body removes its note, while deleting the note text itself can make Word renumber notes in a new order (Microsoft Support). During translation cleanup, don’t delete unfamiliar note content just to clear a formatting problem. Identify the corresponding body marker first and confirm that deletion is intended.
Using Replace All on note markers. Word’s Find and Replace can locate footnotes with ^f and endnotes with ^e. Microsoft warns that replacing all instances with an empty replacement removes all notes of the selected type, making that a destructive action rather than a routine cleanup method (Microsoft’s note deletion guidance). Avoid broad replacement commands unless removing every note is genuinely the task.
Treating the number as the entire reference. A superscript marker is only a pointer. Translators and reviewers need to check the note text that the pointer reaches, not just whether a number appears in the body. A count comparison can reveal a missing note, but only following the marker can reveal a mismatched citation.
Translating citation details as ordinary prose. A translated book title can become hard to locate if the project expects the source title. An altered identifier can point to the wrong item. Separate explanatory language from bibliographic details and follow the supplied rules; if the brief is silent, ask before making a project-wide choice.
Assuming note separators never change. Word lets users change or remove footnote and endnote separator lines through the Footnotes pane (Microsoft Support). Inspect the separator in the delivered file instead of treating it as an unchangeable part of the source. A missing line may be a formatting choice, a conversion change, or an accidental edit.
Ignoring pagination and target-language expansion. A translated note may take more or less space than the original. A footnote that moves because the body text or note text reflows isn’t necessarily lost, but the reviewer should check that it remains associated with the intended page and body marker. Endnotes may also shift the length of the final section.
Assuming an editor’s display tells the whole story. Google Docs pageless format places footnotes together at the document end, unlike the page-based display described in its Help guidance (Google Docs). Confirm the document’s format before diagnosing a placement change as a translation error.
Relying on tabs to align note details. Some document translation workflows may treat repeated tabs differently from normal paragraph text. If a note uses tabs to align a source title, page number, or other field, inspect the translated file and use deliberate formatting rather than assuming that spacing will survive.
Overlooking font coverage. Characters outside the fonts available in the document may not render as expected. Check translated note text for missing glyphs or substitution, especially when the target script differs from the source script. A technically present note can still be unreadable.
Microsoft’s note guidance describes a reference mark in the body and related note text at the page bottom or document end.
That linked structure explains why both content and formatting checks are necessary. A note can remain visible while its relationship to the marker changes, and layout changes can make a sound relationship look broken. Compare the actual pairs in the editor.
Regional, format, and delivery differences¶
The note itself doesn’t follow one universal layout across every editor and file format. A translator should know which format the client expects, which application will be used for review, and whether the delivered version must remain editable.
Microsoft Word distinguishes footnotes, generally shown at the page bottom, from endnotes, generally shown at the end of a document or section (Word Help). Google Docs can show footnotes at page bottoms in page format or together at the end in pageless format (Google Docs Help). LibreOffice Writer describes footnotes as information at the page bottom and endnotes as information at the document end, and automatically numbers both (LibreOffice Help).
The display differences don’t establish different translation rules. They do mean the team should agree on the file that counts as the final deliverable. If the client will review in Word, don’t sign off only on a pageless preview in another editor. If the client expects an editable DOCX, check the DOCX rather than a PDF export alone.
Word for the web’s support guidance directs users to open a document in Word to convert footnotes to endnotes or endnotes to footnotes (Microsoft Support). A conversion can change where notes appear, so record whether the translated file should preserve the original note type or convert it as part of the assignment.
For localization teams exchanging content between systems, XLIFF provides another useful distinction. The XLIFF 2.0 standard describes a lossless interchange format for exchanging localizable content and distinguishes translatable source and target content from non-linguistic inline content such as formatting codes and placeholders. That model helps explain why a translator should change the words while protecting structural markers.
An exchange format doesn’t remove the need to inspect the final file. A segment can carry the right translated words while the exported document still needs a check for note placement, numbering, and formatting. Keep the source document as the reference for that final check.
A final QA checklist before you deliver¶
A short, repeatable check catches more than a last read of the main text. Run the checklist on the actual deliverable, not on a draft or a temporary preview.
- Compare note counts. Record the source count and output count for footnotes and endnotes separately. Explain every difference before delivery.
- Trace every body marker. Start at each reference mark and confirm that it points to the intended note. Don’t rely on numbering alone.
- Check the sequence. Look for duplicate, skipped, or unexpectedly changed numbers after edits. Word’s renumbering behavior makes this check useful after note changes.
- Review the note text against the source. Confirm that explanatory meaning is intact and that citation fields follow the project’s rules.
- Verify identifiers and locators. Compare names, titles, page references, dates, and other identifying details against the source note or citation instructions.
- Inspect page and section placement. Check footnote position, endnote location, page breaks, and whether a note has become separated from the passage that calls it.
- Review formatting. Check font, size, indentation, separators, and readability. Word provides formatting options for footnotes and endnotes, so repair a visible layout issue in the editor rather than masking it with ad hoc spacing.
- Open the final file in the expected application. Confirm that the client can see the notes in the intended layout and that the delivered format matches the project agreement.
A bilingual review view can help with the language check by placing source and translation side by side, but structure still needs a separate pass in the document editor. The guide to translating scanned PDFs and photos with AI and OCR covers a related problem: when the source is a scan, first confirm what text and layout were recognized before judging the translation.
Keep a record of unresolved items. If a source title has no agreed translation or a citation is incomplete in the original, flag the issue rather than quietly “fixing” it. The client can then decide whether to supply a reference, approve a convention, or leave the source detail as it stands.
FAQ¶
How do you translate footnotes in Word without losing the references?¶
Translate the note text without deleting its reference mark, then compare each marker in the body with its corresponding note. Check the sequence, note count, and formatting in the output DOCX.
Should bibliographic citations and source titles be translated in footnotes?¶
Translate explanatory prose, but verify titles, identifiers, publication details, and page locators against the required citation style or client instructions. There isn’t one universal rule for every publication.
How can you check footnote numbering and anchors after translating a DOCX?¶
Compare the source and target note counts, then follow each body marker to its note and check the numbering sequence. Inspect placement and pagination too, since note text can reflow.
Does Google Docs translate footnotes when translating a document?¶
Google Docs can create a translated copy with its Translate document feature, but the Help page doesn’t specify how that feature handles footnotes and their anchors. Check the resulting copy manually.
Can I translate footnotes with an online document translator?¶
Some document translators can process note text, but supported formats and preservation behavior differ. Check the output in Word and don’t assume that a translated note still points to the right marker.
Can I use an automated translation for a document with citations?¶
An automated draft can help with explanatory prose, but citation metadata and the marker-to-note relationship need review. Follow the publisher’s or client’s requirements for source titles and bibliographic fields.
What should I do if a footnote disappears during translation?¶
Compare the output with the source and check whether the body reference mark was removed or the note text was lost. Restore the note structure in the editor, then verify the sequence and every anchor-to-note pairing.