ManYue: Separate PDF page counts from attached files

A PDF can carry attached files whose images or documents are not necessarily body pages. ManYue’s PDF-comic support does not promise attachment listing, extraction or opening every attachment. Build separate page and attachment lists for a short file you own, checking structure externally and actual reading scope in the app instead of adding different object types into one page count.

Use a file whose attachment provenance you understand

Choose a small PDF you created or may handle, preferably a known two-page document with one self-made explanatory text attachment. Create an attachment only if an existing trusted tool supports it; install nothing unfamiliar. Otherwise audit a file you already own with its limitations stated. Record PDF name, size, source, body-page count and tool version, retaining the original. Do not open unknown executables, scripts or macro documents to study attachments. Structural checking identifies count and ownership without executing an attachment to prove its existence.

List pages and attachments separately, read-only

In a trusted PDF viewer that recognizes attachments, first record body pages from first to last, then use an actual attachment list for name, type, size and description. No list means this tool did not provide that check, not no attachments. Two body pages plus one text attachment is not a three-page PDF. Even a two-page document attached inside does not automatically add pages to the parent. Preserve parent and attachment identifiers separately without merging identical names. Listing is enough; leave unknown attachments unopened and do not infer absence from a missing icon.

Distinguish links from embedded files mentioned in the body

A body reference to an attachment might mean an embedded file, a web link or another file in the same directory. Use target information from the trusted viewer and source explanation, not a paperclip drawing alone. Record external-link type and separate acquisition needs without browsing unfamiliar sites for this exercise. Record a neighbouring file as separate from the PDF. Preserve unknown targets as unknown. Separate reference wording, actual target and availability so opening a local PDF is not mistaken for offline retention of every related resource.

Check ManYue reading against body pages

Import the parent PDF normally and record local entry and app version. Inspect titles, images and final lines on both body pages. Compare with the externally confirmed parent-page count, excluding attachment count. If body pages are intact but no attachment entry exists, record two body pages read, attachment not obtained through this path, not one page missing. Do not seek an unpromised attachment panel or infer universal extraction from an icon. Presentation of attachment-related marks follows the installed version and actual sample; this lesson supplies no universal support list.

Preserve separate identity when an attachment is needed

If an attachment is an ordinary image or document you may use and an existing trusted tool allows saving, place it in a clear directory and record parent PDF, attachment name, saved name and date. Check actual type and provenance afterwards instead of renaming every attachment CBZ. To read it as comic material, arrange it explicitly in your own organized reading copy, retaining attachment original and explanation without claiming automatic merger into the parent PDF. Record unavailable attachments as gaps. Continuing body reading does not complete the resource set; obtain supporting files from the author or an authorized source if needed.

Record offline results per object

For offline preparation, list parent PDF, separately saved attachments and external links individually. Offline first/middle/final parent pages establish body availability only. Check saved attachments in a trusted tool appropriate to their format, without demanding that ManYue open every document. Unsaved webpages still need a network; a clickable title is not local content. Do not interrupt important transfers to test: mark offline untested when conditions are unsuitable. Restore network state afterwards and record each object’s actual access method instead of a blanket pass concealing unavailable attachments.

Check object types when counts disagree

If a two-page PDF is described as three items, first ask whether that means a parent plus two attachments rather than diagnosing lost pages. For a missing list item, check revision and external-tool capability instead of combining different copies’ inventories. A genuinely missing body page needs page-by-page source investigation; attachment checking does not replace it. Report a self-made two-page-plus-text sample with viewing environments and the fact that unknown content was not opened. Retain unknown causes rather than clearing caches or reinstalling to repair something that was never a page.

Confirm resource-set scope after returning

Leave the reader and return to the parent’s two pages, confirming content identity, then verify attachment count and storage locations against the external list. Separate parent pages, embedded attachments, independent supporting files, links and unavailable items instead of placing all in one page-count field. Label any organized copy as a manual combination with explicit scope, retaining originals. Completion gives every necessary object provenance and acquisition status. Finishing body pages and completing supporting resources are different findings; unseen objects are not automatically pages lost by a comic reader.

Related guides and sources

ManYue: Distinguish PDF page content from annotation visibility; ManYue archive companion-file audit: distinguish pages, notes and system helpers.

Checked on November 8, 2026: Apple public version information lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the official App Store description 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 personal analysis or code observations are not presented as verified automatic capabilities.

For PDF attachments, see Adobe: Open attachments in PDFs. External listing and extraction do not establish an equivalent promised entry in ManYue.