ManYue: Distinguish PDF page content from annotation visibility

A red line on a PDF may be page content or a separate annotation, and viewers need not display it identically. ManYue’s published PDF-comic support does not make it a full annotation editor. Compare original page content with annotations using your own short file and record actual visibility. Annotation creation, inspection or processing belongs explicitly to an existing trusted external tool.

Make a sample with distinguishable content and annotations

Create a two-page PDF in a familiar document tool with Body A and Body B on its pages. In an existing trusted PDF tool, add Annotation test to page one without private data. Retain unannotated and annotated versions with distinct names and dates. If no annotation function exists, do not install software: use a file you already own or perform reading observations with the sample limitation stated. Record which wording is page content and which is an added object. Colour in a screenshot does not establish the distinction because page content itself can be coloured.

Confirm annotation identity in the external viewer

In the tool that created the annotation, use an available annotation list or object information to confirm its identity. Record tool version, annotation type, page and presentation, such as popup text or a visible page overlay. If the tool merely draws text into the page without a confirmable annotation object, record page content instead; it cannot test annotation support. Highlights, text boxes and handwriting need not be the same object type. Retain the original as a read-only reference and establish identity and scope before comparison, rather than diagnosing features with an uncertain sample.

Inspect body content and annotations separately after import

Import the annotated version normally, recording app version and local-entry identity. Check both body pages first, then whether page-one annotation text, position or only an icon appears. If body content is intact but the annotation absent, record readable body, annotation not shown, not page one missing. Popup-only text in the external tool is not missing source wording merely because no popup appears in ManYue. Do not seek unpublished annotation panels or editing buttons, or equate visibility with editability, export or synchronization.

Use the unannotated version to bound the difference

Open the unannotated version separately and verify the same Body A/B and page count, avoiding comparison of unrelated exports. Record three environments: unannotated externally, annotated externally and annotated in ManYue, with body, annotation and page-count fields for each. An issue limited to the annotated copy narrows the relationship to that processing step without diagnosing an internal cause. If both lose words, inspect the source document and export. Change only the annotation condition, not font, compression, page dimensions and colour simultaneously, so the comparison has a defined scope.

Do not infer deletion from absent display

After leaving ManYue, reopen the same annotated file in the original external viewer and check whether its annotation object remains. If it does, the observed paths display differently; do not claim import deleted it. For a separately saved file, confirm path and revision rather than assuming a reader entry and external original are one storage object. This exercise does not verify preservation of every PDF feature through app export, and opening success is no lossless-format guarantee. Retain the annotated original and normally available annotation records separately for long-term preservation, not only the comic entry.

Identify processing in any visible reading copy

If your reading purpose requires annotation material visible on pages, make a clearly named reading copy with an existing trusted tool, without overwriting the annotated original. Printing, flattening or export may change interaction, text layers and image quality. Follow that tool’s guidance; no universally lossless procedure is promised here. Check page count, body, small text, annotation position and transparency before importing. Describe the actual processing, such as annotation material incorporated into visible pages, rather than claiming full equivalence to the original PDF. Without that need, retain the original and external viewing method.

Report a minimal shareable example

For unexpected display, provide the self-made two-page sample, tool version, annotation type, page and three-environment results, not a private review document. Check whether public scope promises the needed feature; an unpromised capability differs from failure of a promised one. If only colour differs, use a separate colour-reference check instead of combining annotation identity and page colour into one defect. Preserve unconfirmed results when reproduction fails. Do not alter app internals to force display, and identify external reading as an alternative method rather than a repair in ManYue.

Check the reading-scope statement after returning

Leave the app and return to pages one and two of the same annotated entry. Recheck body and annotation display, then confirm identity against the original. Separate page content, independent annotations, externally processed copies and unconfirmed capabilities, recording where each is retained. Reopen any shareable version externally so annotations cannot be mistaken for the original author’s body text. Completion does not require identical viewers. It establishes what is visible in each environment, which inferences are unsupported and where original and annotation evidence remain retrievable.

Related guides and sources

Read PDF comics in ManYue: covers, wide pages and reading position; ManYue: Check PDF page colours with a self-made reference sheet.

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 annotation objects and external-tool concepts, see Adobe: Add comments. This describes Adobe tools, not equivalent annotation-editing capabilities in ManYue.