# Read PDF destination reports in ManYue: a name targets a location, not a page title

Language: en
Canonical: [Read PDF destination reports in ManYue: a name targets a location, not a page title](<https://allluckly.cn/en/guides/manyue-pdf-named-destination-key-target-page/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-pdf-named-destination-key-target-page/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-pdf-named-destination-key-target-page/>)
Published: 2026-11-16T00:00:00+08:00
Modified: 2026-11-16T10:38:47+08:00
Author: Bison

Use an original three-page PDF and destination map to check names, link labels, target identity and revision behavior.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-pdf-named-destination-key-target-page/>), translated on 2026-11-16. Original publication dates, attribution, code and version notes are retained.

A destination named orchard can target a page headed“果园”(“Orchard”), but matching appearance does not bind those strings automatically. Make an original three-page PDF and external destination report, verify page identities in ManYue, and assess name mapping separately from navigation. A named destination is not an app bookmark, and PDF link execution is not guaranteed across readers. Use verifiable page content and real reports.

## Prepare cover, bridge and orchard page identities

Create a three-page PDF externally: cover C1, bridge B2, orchard O3, each with a different original small drawing. List physical positions 1–3 and markers in a report and preserve the original. Titles need not share a language with destination keys; this example deliberately uses Chinese headings and Latin-letter keys. If only ordinary PDF creation is available, make the readable pages and label the mapping a paper exercise instead of claiming nonexistent interactive objects were written.

## Separate destination keys from visible wording

Set destination key `orchard` in the external report to resolve to physical page 3/O3. A visible link labelled“回果园”(“Return to orchard”) references that key. Copy name, link wording and heading into separate columns. The label is not the key, and a page saying orchard does not prove a destination exists. Tool-selected identifiers need not be translated or rewritten. Preserve spelling and case: erroneous orchad omits an r and requires checking the reference, not misspelling the target heading to match.

## Check target page identity before view parameters

A destination can include a page plus position or fit parameters. Use a normal parser to verify O3 first, then record whole-page fitting or another view. An object number is not automatically physical page 3; object identities need not follow page order. If a documented tool reports zero-based index 2, translate that to the third page rather than a two-page book. Without structural parsing, label the map as a premise only. Adobe pdfmark’s one-based Page convention must not be conflated with every parser’s zero-based indexing.

For an explicitly invented report, A’s ordered page-object list is 8, 12, 17 and the destination resolves to 17, hence page 3. With a new 23 at the front and retained identities, B’s list 23, 8, 12, 17 puts it fourth. This is no universal numbering rule: re-export can renumber objects, requiring the current report and page markers again.

## Try navigation only through an actually available control

In ManYue first manually reach O3 and verify the orchard image, then return to the linked page. If the installed version offers a usable interaction, record starting location, reached marker and zoom. No observed jump does not prove an absent destination. Do not invent a destination manager or present an external report screenshot as a native panel. Manual arrival proves content exists, not that a link executed. Check readable pages, structural mapping and successful current-control navigation separately, leaving unperformed items blank.

## Check what the name targets after a separate revision

Save revision B with a revision sheet before the cover. If original O3 retains identity, it moves to physical page 4. Use an external tool that supports destinations to update or inspect the actual map and record whether orchard still resolves to that orchard; insertion alone guarantees no universal automatic maintenance. A’s third page and B’s fourth differ in position but can share marker/content identity. If the key points to B’s third-page bridge, record a revision mapping defect, not a reading-progress error. Preserve both versions for reproduction.

Distinguish a missing key from an existing key mapped to the wrong page. One fails name resolution; the other has a wrong mapping. Neither is fully described by “page three changed.” A heading revised to“Autumn Orchard” can retain a correct unchanged key. Record the heading change without assuming identifier and visible wording must be edited together.

## Allow more than one name for one target page

Add `fruit` to the exercise map as another name for O3. Two names can target one page without adding a fourth comic page. If they target different views on that page, retain separate parameters instead of calling them identical from page number alone. Conversely, the same visible wording can occur on different pages without identical targets. App bookmarks are separate reading records; returning to the orchard does not establish synchronization with internal PDF names. Deleting a test bookmark is not a method of editing the PDF destination map.

## Diagnose spelling, indexes and version confusion

For a wrong target first identify file A/B, then key spelling and resolved page identity, and finally view offsets. A clipped top alone is not a wrong page: use O3 and its drawing to separate identity from zoom. Share the minimal original sample and nonprivate report rather than an entire personal comic. If image export loses destinations, distinguish interactive structure from visible pixels. Return to the structural PDF for checking; drawing the same name on an image does not repair navigation.

## Reopen and deliver the four-identity mapping

Reopen original and revision, inspect cover/bridge/orchard order, then compare name, visible label, target content and observed arrival in four columns. Explain how a maintained name can target revised page 4 and where conclusions stop without a tested jump. Keep PDFs, structural reports and reading notes. One successful navigation does not establish every action type or cross-file link. Recheck maps after merging, deleting pages or renaming; an old app bookmark opening does not prove every internal relationship survived.

## Related tutorials and sources

[Page labels and physical positions](<https://allluckly.cn/en/guides/manyue-pdf-page-label-physical-index-map/>); [Bookmarks and returning](<https://allluckly.cn/en/guides/manyue-page-bookmarks/>).

Sources checked on 16 November 2026: [Apple public lookup](<https://itunes.apple.com/lookup?id=6753895889&country=cn&entity=software&timestamp=20261116>) shows ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. Published reading capabilities appear in the [official App Store listing](<https://apps.apple.com/cn/app/id6753895889>). Use controls actually available in the installed version.

Method references: [Adobe actions and named destinations](<https://developer.adobe.com/acrobat-pdfl-sdk/guides/pdfmark/pdfmark-actions>). Diagrams, numbers, counterexamples and recording arrangements are original exercises. Separate external preparation, paper expectations and actual reading results. Available documentation does not substitute for device observation, and no private-server or universal file-environment test is claimed.

