ManYue EPUB image order: separate the manifest, spine and image occurrences

The first image file listed inside an EPUB need not be the first read. Check an image-based EPUB in ManYue by tracing manifest resources through the spine to images in content documents. Published import support does not guarantee preservation of every text-book layout. Record known images and actual presentation without assuming an in-app package editor.

Prepare three small images with content identities

Make three small images with A, B, C corner marks and different short text, retaining originals and the small EPUB. Record authoring tool, name, edition and source rather than beginning with restricted material. Marks identify content independently of directory position. Observe the intended sequence in an already trusted reader, explicitly as another tool’s result rather than ManYue’s. Inspect package structure only after obtaining the complete file; a cloud placeholder or cover does not establish all three images are present. Work on a copy and retain the original.

Locate the package document instead of guessing from ZIP order

With an existing trusted desktop tool, inspect the EPUB read-only. Use container information to locate the actual OPF before reading manifest and spine; no extra installation or phone-side editing is required. Keep ZIP entry order, filename order and publication order separate. An image named first page still needs reference checks. If the tool cannot expose structure, mark it unchecked instead of inferring OPF from the shelf cover. Multiple package documents require the container’s declaration and edition context, not an arbitrary familiar-looking choice. Leave unclear structure unresolved.

The manifest identifies resources rather than their sequence

Our original sample uses part01.xhtml, part02.xhtml, part03.xhtml, referring respectively to images A, B, C. Map resource identifiers to document paths, then documents to image paths, preserving relative locations. Listing the second document first in the manifest does not itself put B first, nor should identifiers be sorted numerically. Styles, fonts and navigation resources do not each become comic pages. Record types and references, distinguishing resource presence from participation in the main reading chain.

Trace the spine into images within each document

The sample spine explicitly references the second, first and third documents, all ordinary primary content, giving intended main sequence B, A, C. This follows reference mapping, not ZIP placement. A document with several images needs further checks of occurrences within it; one spine item does not necessarily equal one comic page. Record non-linear supplementary content separately rather than inserting it automatically. The independent three-image sample avoids complex layout, while the specification’s spine definition still does not guarantee unlimited app compatibility with every EPUB.

Separate image files from image occurrences

In a separate control, supplementary content references A again. The image-resource count can remain three while occurrences increase. Reuse may be a deliberate recap rather than an organisation error. Whether ManYue retains that occurrence requires current results, not an accusation of missing pages based on deduplicated resources. Record main chain, supplementary chain, image identity and occurrence locations separately. CSS backgrounds, SVG-contained images and complex compositions are not promised independent pages; mark them outside this sample’s coverage and use simple references to isolate the issue first.

Check actual import order through corner marks

Import the working copy into ManYue and record app version, work identity, chapter/position and mark order. Check whether B, A, C matches this sample’s expectation. For disagreement, verify the OPF and file mapping before batch-renaming images. Published order improvements describe release scope, not proof that every current page is correct. Text, navigation and image order need separate results; three correct images do not certify every text feature. Retain neighbouring anchors as well as total count, leaving missing observations unresolved.

Change only one ordering condition in a control

For an owned control, change only manifest listing order while preserving spine and content references: the specified main chain remains unchanged. In another copy change the spine, explicitly changing that chain. Do not rename files, recode images and restructure together, then attribute a result to one factor. Use an existing trusted authoring tool, not app-database edits or overwriting a published work. Name and record each reimport clearly. If the tool rewrites other structures automatically, disclose them rather than calling it a single-variable control.

Exit and return to check the reference-to-image chain

Exit the reader and return to the original and controls, relocating B, A, C and neighbours without confusing editions. Save six fields: original identity, package location, resource mapping, spine, image occurrences and app result, marking inaccessible fields unknown. Completion means sequence conclusions trace back through references, not merely tidy filenames or a successful import. For a complex EPUB beyond image extraction, retain it and separately use an appropriate text-reading workflow rather than treating image output as an equivalent complete publication.

Related guides and sources

ManYue file formats: choose CBZ, CBR, CB7 or PDF and check page order; ManYue: Build a minimal three-page import reproduction package.

Checked on November 11, 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 specific controls in the installed version.

Method reference: W3C EPUB3.3: Manifest and Spine. Samples, passages and controls are original exercises. Sources establish definitions and checking methods rather than new automatic analysis in the app. Manual records may be kept externally, and unknown fields should remain explicit. This article does not claim step-by-step testing on a physical device, private server or every output environment.