# Book Isle EPUB cross-references: match reference wording to its actual target

Language: en
Canonical: [Book Isle EPUB cross-references: match reference wording to its actual target](<https://allluckly.cn/en/guides/nasbook-epub-cross-reference-target-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-epub-cross-reference-target-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-epub-cross-reference-target-check/>)
Published: 2026-11-05T00:00:00+08:00
Modified: 2026-11-05T09:38:59+08:00
Author: Bison

For references to sections, figures or appendices, verify target identity, available navigation and return, distinguishing a working link from a correct destination.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-epub-cross-reference-target-check/>), translated on 2026-11-05. Original publication dates, attribution, code and version notes are retained.

“See section three” is guidance, not proof that an activated reference reaches the right section. In Book Isle, manually check a cross-reference’s wording, target and return context in an EPUB. This concerns internal correspondence rather than external bibliographic tracing. Linked file structure does not guarantee every navigation or return action on the current reading path.

## Choose three kinds of internal reference

Choose three authorised same-edition references to sections, figures or appendices, recording book, version, source heading and necessary wording. Confirm internal scope, excluding websites and bibliographic sources for this pass. Repeated figure numbers may need chapter context. Start within completed material where targets can be checked rather than auditing the whole book. Preserve the original and inspect a copy instead of unpacking and editing the sole file to erase evidence.

## Record what the reference asks you to find

Log target type, number, title and purpose, such as a definition in chapter three section two. An isolated “two” cannot match any second figure. Relative wording such as “next section” needs the current and neighbouring identities because revisions may change them. Mark ambiguous wording unresolved instead of completing it from familiarity. Retain adjacent sentences to distinguish an actual navigation request from an example of reference formatting.

## Use only actually available navigation

If an actual link is available, preserve the source before trying it and record the result. For plain wording, use contents, supported search or manual navigation without hunting for a hidden switch. No response does not prove absence, and arrival does not prove correctness. Identify whether navigation used contents or the body link. A source bookmark or external locator can substitute for unavailable return history, but does not repair links or create an assumed automatic two-way relationship.

## Verify target heading and content identity

Read heading, adjacent sentences and object to check number, chapter and topic. In an invented example, chapter one figure two may be a process while chapter three figure two is a result; matching numbers alone fails. A definition reference landing on an example’s use of the term also fails. Log field matches rather than using nearby progress percentages. Reflowed screen pages vary with font size, so structural identifiers and phrases are usually better evidence than one displayed page number.

## Check whether the destination answers the question

A correct location must also contain the promised explanation. A conditions reference may need the next paragraph or note rather than immediately indicating a wrong link. A heading with a missing figure is a presentation issue separate from number matching. Compare the same authorised source in a trusted tool if necessary and record the difference. Do not silently import a fuller revised edition’s explanation into a claim about this edition’s link.

## Test returning to the original sentence

Return through the available method and verify adjacent wording, not just the chapter. Combine a source bookmark with a distinctive phrase where the same chapter repeatedly says, for example, “see section three.” For chained references, log entry and return at each level without assuming an unlimited navigation stack. Complete one round trip before the other two. Restore through your locator rather than resetting progress or deleting notes; report a return-path limit instead of treating existing body text as lost.

## Save four distinct kinds of discrepancy

Distinguish ambiguous wording, unavailable navigation, wrong destination and invisible target content. They can coexist but need different handling rather than one broken-link label. Report edition, wording and locations with an authorised small sample, not a private book or server. Recheck all three references after any separately saved conversion, which is not a guaranteed repair. Remap old bookmarks through headings and phrases rather than expecting same-name inheritance.

## Finish the three-reference checklist

Finish with source, expected target, actual arrival, content result and return method for all three. Working links may reach same-numbered wrong chapters; nonclickable wording does not establish missing sections; correct locations still need content checks. Mark unknowns and needed evidence. Choose a usable reading method while retaining the EPUB, limiting conclusions to this file and path rather than every EPUB cross-reference.

## Related guides and sources

[Book Isle illustrated EPUB checks: images, notes and contents](<https://allluckly.cn/en/guides/nasbook-epub-image-check/>); [Book Isle reference-index checks: trace entries to text and saved notes](<https://allluckly.cn/en/guides/nasbook-reference-index-route/>).

Checked on November 5, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6766198898&country=cn>) lists Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6766198898>) and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and reading analysis is not presented as an existing automatic application feature.

For format concepts, see [W3C EPUB 3.3](<https://www.w3.org/TR/epub-33/>). The specification defines publication structure, not verified behaviour for every Book Isle control or every file link.

