Check OPDS indirect acquisition in ManYue: distinguish entry media from final publication formats

An OPDS acquisition link typed as HTML does not require the final book to be a web page. Nested indirect-acquisition information can describe subsequent media types. Read an original excerpt externally, map its levels and use a supported sample or report in ManYue. Paper metadata is not a live download service or proof that the app automatically handles every fulfilment, login or packaging flow.

Make a catalogue excerpt without accounts

Write an original excerpt externally with relation http://opds-spec.org/acquisition, address https://example.com/get/sample and type text/html. The address is a teaching placeholder, not a file service; do not click or provide credentials. Add an original title and exercise identifier and preserve the text. This is field-reading material, not a claim of a complete deployable OPDS document with every required element. No server means no alleged successful connection.

Read the link’s own three fields first

Separate relation, href and type: relation identifies an acquisition entry, href its target and type the target media. Here text/html describes the entry resource; appending a PDF suffix would not create a direct download. “get” in a path does not establish full-book delivery, so actual response remains unknown. Do not copy a cover or preview type into acquisition: distinguish multiple links by relation before analysing indirect types.

Read the first indirect packaging level

Place <opds:indirectAcquisition type="application/zip"> inside the link as the first indirect level. A complete XML context must bind the opds prefix to its namespace; this field excerpt is not a validated standalone XML document. ZIP describes an expected packaging level, not HTTP Content-Encoding or page streaming. Retain HTML followed by ZIP rather than discard the entry and any legitimate acquisition steps simply because ZIP appears.

Distinguish final types from sibling items

Inside ZIP add <opds:indirectAcquisition type="application/pdf" /> and a sibling for application/epub+zip. This can describe multiple representations expected within a package. Nesting expresses levels; siblings do not mean read PDF and then automatically convert it to EPUB. Draw HTML to ZIP to two leaf types, not three comic chapters. For other catalogues use actual parent-child elements, not indentation alone, since whitespace alignment does not establish XML hierarchy.

Check permissions separately from media types

A final-PDF declaration supports only what the catalogue says is expected, not authorisation, successful downloading or complete bytes. A real source may require its normal authorised login or purchase flow; this exercise supplies no account and performs no transaction. Indirect acquisition is not an OPDS-PSE page template and does not make ordinary whole-file OPDS directly readable. Separate discoverable, authorised, acquired and page-decodable states, leaving unperformed checks unperformed rather than ticking all from one type.

Check actual reading with your own PDF

Make a separate original three-page numbered PDF externally, without claiming it came from the placeholder HTML or ZIP. Import through an existing ManYue PDF path and inspect all page numbers, centres and return positions, with an optional report PDF beside it. Reading a report is not passing an acquisition protocol. A legitimately acquired real file may be recorded separately by identity and actual type. Without a server, stop at the local sample rather than invent responses, download times or logins.

Check mixed levels and mistaken links

If text/html is taken as proof that the final PDF is unsupported, restore entry-versus-leaf columns. If sibling types become sequential conversion, redraw nesting. A downloaded web page may be the entry, not the final file; renaming it cbz is insufficient. Displaying a catalogue does not establish every later authentication flow, so record the stopping level. Share original excerpts and redacted types, not signed private links. Editing a type declaration alone cannot repair absent files or permissions.

Reopen and reconstruct acquisition levels

Reopen the report and the local three-page sample, checking structure and pages separately so a same-title cover is not mistaken for content. Retain link fields, indirect-type tree, permission status, acquired-file identity and actual reading outcomes, each sourced or explicitly unknown. Explain how an HTML entry can declare a later PDF without guaranteeing automatic handling of intermediates. Reassess catalogue, packaging or login changes instead of treating this paper example as a real-service compatibility promise.

Related guides and sources

ManYue: Distinguish OPDS artwork, sample and acquisition links; ManYue OPDS connections: why a catalogue may not support page streaming.

Checked on November 14, 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: OPDS 1.2: indirect acquisition and nested media types. 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.