Test Footnote Preservation Before Changing Book Editors

Compare editors with a sample containing real footnote structures and known expected results. Import it, make a few controlled changes, export it through the intended workflow, and verify that note text and marker relationships survive without relying on a feature label alone.

Choose a sample with the note patterns you use

A manuscript with one short footnote is an easy demonstration but may not represent the actual book. Include a long note, several notes close together, notes beside punctuation, and any special formatting your project needs. Keep a separate reference copy that records the expected text and relationships.

Use nonprivate test material where possible. The purpose is to evaluate the editor's handling of structure, not to expose an entire unpublished manuscript unnecessarily. Give the sample clear internal cues so the reviewer can tell which note belongs to which passage after import, editing, and export.

Inspect the imported structure before editing

Open the sample in the candidate tool and inspect the note markers and corresponding text. Determine whether the notes remain editable as notes or have become ordinary text, images, or another structure. A visually similar page can conceal a loss of editing behavior that matters during later revision.

Check the full note text, including paragraphs, emphasis, and any links relevant to the workflow. Record the actual result instead of reducing the observation to import worked. The author needs to know whether the tool preserves the features the manuscript depends on and which elements require manual reconstruction.

Make changes that reveal the relationship

Insert a new note before an existing one, move a paragraph containing a marker, and delete a selected note in the disposable test copy. Observe what happens to numbering, order, and the associated text. These actions reveal whether the editor maintains the relationships or merely displays the imported appearance.

Keep the sequence of test edits recorded. If a note disappears or changes association, the record helps locate when the problem occurred. Do not judge the tool by a result produced through an unsupported workflow without checking its documentation, but do not accept an advertised feature as a substitute for the behavior observed in the actual test.

Export using the intended publication path

Create the kind of output the project expects to use and inspect it independently of the editor. A tool may handle notes correctly in its own interface while an export changes their placement or navigation. Compare the complete content and associations with the reference after accounting for the deliberate test edits.

KDP provides format-specific preparation guidance, so evaluate print and digital outputs according to their actual use. Printed notes need to be findable and correctly associated; digital notes may also involve navigation supported by the chosen format. Verify the real artifact rather than assuming that success in one output establishes success in another.

Test the handoff if another editor will receive the file

If the workflow includes another application or contributor, open the exported editable file in that environment and inspect the same note relationships. Make one small controlled edit and return it through the planned route. This tests the actual collaboration path rather than only a one-way export that the project will never use by itself.

Record any degradation and the work needed to repair it. A workaround may be acceptable for a small project but costly for a book with extensive notes and frequent revisions. The comparison should include that maintenance burden, not just the initial subscription price or the appearance of the tool's demonstration document.

Choose with the limitations documented

Summarize which note patterns survived, which required intervention, and which remain unsupported or uncertain. Keep the sample and outputs with the decision record so the result can be reproduced after a significant product or workflow change. Avoid a blanket claim that the editor preserves footnotes when only one narrow case was tested.

When the real manuscript moves, retain the original and inspect the imported notes before major editing continues. The successful sample reduces uncertainty but does not replace review of the full book. Choose the tool whose demonstrated behavior fits the project's note structure and whose limitations the team can manage without losing source relationships.