# Check EPUB navigation in ManYue: landmarks are entry points rather than another spine
Language: en
Canonical: [Check EPUB navigation in ManYue: landmarks are entry points rather than another spine]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-11-15T00:00:00+08:00
Modified: 2026-11-15T10:03:44+08:00
Author: Bison
Use an original chapter package and report to distinguish contents, landmarks, fragment targets and default reading order.
English translation of the [Chinese original](), translated on 2026-11-15. Original publication dates, attribution, code and version notes are retained.
A body-start landmark does not delete the preface or make landmark order the reading order for every chapter. Inspect an original EPUB’s navigation and spine externally, then read a supported PDF report in ManYue. Focus on entry semantics, referenced resources and reading positions, without promising native exposure of every EPUB navigation type on a given path.
## Fix three documents and their reading order
Externally prepare original preface.xhtml, chapter.xhtml and glossary.xhtml documents. Declare spine order preface, chapter, glossary and record package and navigation paths instead of substituting filename order. Without an editable EPUB, use labelled structure cards and state no container was generated. Name the later PDF report separately rather than claim a reader fully parsed the original package. ManYue’s task is legible report reading and return.
## Give contents and landmarks separate purposes
Contents can list browsable chapter links, while landmarks identify key entries such as body start, contents or glossary; they are not meant to repeat the entire contents list. Record purposes and actual items separately rather than demand equal counts. Human-readable labels and semantic types have different roles: a label saying body does not prove bodymatter markup. Missing landmarks do not mean missing documents, and a landmark alone does not establish spine membership.
## Follow the body landmark to its fragment
The body entry targets `chapter.xhtml#start`, with an actual start identifier in that chapter. Resolve the file against the navigation base, then verify the fragment; text after the hash is not a new extension. A document-only target does not establish a specific paragraph landing. A body-start entry leaves the preface in the spine: one navigation jump is not deletion or editing. A listed link also does not guarantee every reader chooses the same initial-reading strategy.
## Change landmark order without changing the spine
Make control B changing only landmark display order to glossary then body start, while retaining preface/chapter/glossary spine order. Verify resources and spine unchanged, so first landmark does not make glossary the default first chapter. Interfaces may expose some landmarks or present them differently; record observations, not assumed compatibility. Change only landmark order rather than also reorder the spine or rename files, which would obscure the responsible layer.
## Check semantic type and target identity together
The specification restricts repeated identical landmark types targeting the same resource or fragment; duplicating bodymatter is not a way to pad navigation. Audit type, file, fragment and readable label together. A glossary label targeting the preface is a mismatch, not a colour problem. Entries may address different positions in a resource subject to actual rules; do not impose one link per file universally. Inspect original structure and edit copies externally, without assuming an in-app navigation editor.
## Read a four-column PDF report
Externally make a short PDF covering documents, spine, A/B landmarks and target checks, with original markers and date. Open through an available ManYue PDF path and enlarge filenames, hashes, fragments and arrows, returning to each row. Report links or visible labels do not demonstrate native EPUB navigation. Printed or rasterised reports can change text selectability, so record their representation separately. Visible text does not prove XML structure, and untested original-package paths remain unperformed.
## Check missing fragments and deletion assumptions
Opening a file without the intended landing calls for checking fragment existence, case and edition, not treating resource access as precise-location success. If starting at body hides the preface, inspect spine and source before alleging deletion. A report omitting landmarks may reflect tool scope, not absence. Share original documents and minimal structure without private-library credentials. Preserve packages and reports rather than run an unknown bulk navigation repairer.
## Reopen and verify both orders
Reopen the report at the same marker and reconstruct spine and A/B landmark orders without conclusions. Trace the body fragment, glossary label and four-field identities, explaining why entry changes do not rewrite the spine or delete a preface. Recheck added documents, fragments and order after package changes rather than edit only a report title. Deliver an auditable navigation record with unperformed reader paths explicit, not claims of automatic EPUB repair, uniform landmark display or exhaustive device interaction testing.
## Related guides and sources
[ManYue EPUB image order: separate the manifest, spine and image occurrences](); [Check EPUB root paths in ManYue: container full-path starts at the container root]().
Checked on November 15, 2026: [Apple public information]() lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the [official App Store]() for published capabilities; verify controls in the installed version.
Method reference: [W3C: EPUB landmarks navigation](). Materials and numbers are original exercises. Record external reports, paper reasoning and actual reading observations separately, without inventing missing conditions. Sources do not establish new automatic analysis by the app. No step-by-step physical-device, private-server or all-output-environment testing is claimed.