ManYue PDF page labels: separate printed numbers, logical labels and physical positions

A printed page 1 appearing at physical position three does not alone show missing or misordered pages. Use an owned six-page PDF in ManYue to separate printed markings, logical PDF labels and position from the beginning. This task does not reorder pages or promise label display/jumps in the app; check each available interface separately.

Fix a six-page file and its visible anchors

Make six small pages with distinct content and nonnumeric anchors such as mountain, door, boat, tree, bridge and lamp, retaining the original. Record source, name, edition and total pages rather than substituting a revision. Count from the beginning to six, explicitly using positions one through six rather than author numbering. Resolve incomplete-file access before assuming that six outline headings mean six pages. Anchors should remain identifiable when zoomed; one numeric sequence must not be the sole identity evidence.

Define all three numbering systems

Printed numbering is text actually on the image. Logical labels are optional PDF page-identification metadata. Physical position counts pages in file order. They may agree or differ. If an existing trusted desktop tool exposes labels, record its actual interface and settings as an external check, not an assumed ManYue panel. Missing labels remain unprovided rather than inferred from printed Roman numerals. Programming documentation may index the first page as zero, unlike this article’s one-based positions; record the base instead of treating that difference as an error.

Build six label-to-position mappings

The example assigns labels i,ii to positions one/two, 1,2 to three/four, and A-1,A-2 to five/six. Pair each with its anchor and physical position. Label 1 maps to the third page and appendix 1 to the fifth; removing the prefix would confuse identities. Labels do not increase page count to their numeric values. If an existing authoring tool writes them into the sample, record that output. If the scheme exists only in your notes, call it expected metadata rather than claiming it already exists in the PDF.

Compare printed text with labels on every page

Even with labels written, printed numbers can retain older content. Inspect every anchor and printed marking, then compare in a label-capable tool, recording agreement rather than calling a label edit a page-text correction. An unnumbered page is recorded as unprinted, not filled with its logical label. Preserve prefixes, Roman case and body numbering instead of standardising them first. If an author’s contents use printed numbering, identify that system in your notes; replacing it with physical positions does not preserve the author’s original reference.

Test return navigation through actual ManYue controls

After importing, verify all six anchors from the start and record the numbering actually displayed. Use physical position to locate the boat if only positions are shown. For an input control, record the input and destination instead of assuming label 1 automatically reaches page three. Rejected Roman input does not prove a missing page; the control may accept numbers only. Verify destination and neighbours through anchors rather than trusting a displayed 1. Without a suitable control, return manually using the mapping instead of inventing a logical-label switch.

Rebuild positions when adding a preliminary page

In an owned control, insert one cover before the unchanged six pages. The file now has seven pages and the boat moves to position four, while its printed body 1 does not automatically become 2. Label changes depend on the authoring tool’s output; do not guarantee preservation or renumbering. Map inserted and original pages explicitly rather than using old position three for the revised edition. Retain the six-page original. Identical labels across editions can map to different positions, and the control does not promise automatic migration of old bookmarks.

Troubleshoot apparent omissions through numbering systems

If body 1 seems followed by appendix 1, first check actual page objects, then label restarts or prefixes before reimporting. Cropped prefixes, confusing i with 1 and zero-based tool indices can create different appearances; each needs evidence. A printed-number mistake differs from incorrect metadata, so changing one must not conceal the other. Compare the identical file in an existing trusted reader when necessary, not a different edition. Leave unverified labels unresolved while independently retaining page count and anchors instead of completing the mapping by guesswork.

Exit and return to verify three destinations

Exit the reader and return to the six-page original. Locate preface ii, body 1 and appendix 1, checking door, boat and bridge anchors with their positions. Locate the boat again in the seven-page control and verify the edition mapping. Save six fields: file identity, physical indexing base, logical label, printed text, anchor and control result. Completion means different numbering references reach the same image evidence, not forced equality between a reader box and author numbering, or a guarantee that every PDF supplies labels and every reader interprets input identically. Date mappings for new editions separately.

Related guides and sources

Read PDF comics in ManYue: covers, wide pages and reading position; ManYue: Distinguish PDF reopening delays from missing pages.

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 PDF17: Consistent Page Numbering. 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.