# ManYue maps inside comics: read the legend before checking a route
Language: en
Canonical: [ManYue maps inside comics: read the legend before checking a route]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-11-04T00:00:00+08:00
Modified: 2026-11-04T09:36:55+08:00
Author: Bison
Match an in-world map’s legend, orientation and route to story locations while distinguishing schematic diagrams from measured maps.
English translation of the [Chinese original](), translated on 2026-11-04. Original publication dates, attribution, code and version notes are retained.
City, school and voyage maps in comics may contain plot clues or simply illustrate relationships. Save references to a map and relevant story pages in ManYue, then check one specific route against its legend. This is an interpretation of fictional information, not real-world navigation or an automatic distance-measurement or place-recognition feature.
## Choose a legible map page
Choose a complete map in an already-read work and record edition, chapter and narrative placement. Inspect title, frame, margins and dialogue outside the map before cropping attention to its centre. Identify whether it is front matter, a character’s drawing, a screen or narrator-provided information; reliability may differ. Check source detail before enlarging tiny labels, since zoom cannot restore missing letters. Start with two or three locations and one route rather than transcribing a whole fictional city.
## Read legend and orientation first
Look for north arrows, colour keys, line styles and numbered symbols, recording their stated meanings. If a legend is absent, mark it unspecified rather than assuming a dashed line is a walking path. Up is not always north, and rotating the device does not change map orientation. Record shape or text cues alongside colour. If the key is elsewhere, retain that reference and check edition correspondence; another companion book’s legend may not apply automatically.
## Check whether a usable scale exists
Check for a scale bar, distances or a schematic label. Without one, compare relations such as adjacency, river crossing and inside/outside the city; do not convert screen centimetres into kilometres. Even a scaled inset may be distorted or narratively simplified. Exact distance is usually unnecessary: the task is whether a route passes relevant locations. A character’s ten-minute estimate does not establish uniform map scale, and time spent turning pages does not measure the fictional journey.
## Match map labels to story names
Choose the start, a turning point and destination, then find their story names and landmarks. A map’s “old clock tower” and dialogue’s “north tower” need evidence of identity beyond proximity. Keep map label, story name and support in a manual three-column record rather than expecting cross-page recognition. For translation changes or duplicate names, include chapters and scene context, temporarily labelling locations A and B. Merge only verified aliases so the route does not begin with a mistaken location.
## Check the nodes of one completed route
Log where the character leaves, what they cross and where they arrive, then compare each node with the map. If a bridge is unnamed, leave an unknown bridge node instead of selecting the nearest. Omitted travel is not necessarily instantaneous movement. For an apparent detour, inspect closures, pursuit or motives before declaring a geographical error. Mark shown and inferred passage differently so map-supported sections remain distinguishable from connections you supplied.
## Check the map’s date and owner
A map may be outdated, forged or incorrectly drawn by a character. Record who owns and interprets it and whether it is later revised; a new bridge does not automatically show an omission in an old map. Separate planned and actual routes. A secret entrance known to readers may be absent from the character’s map, so avoid judging choices from an omniscient viewpoint. Establish matching time, place and available information before pursuing a route contradiction.
## Create two-way references between map and story
Bookmark the map and two decisive story pages where supported, adding the map area or surrounding labels externally. Test both directions: story to map and map to story. A small inset on a tall image also needs nearby artwork, not only a percentage. Use location codes and concise explanations in discussion, avoiding later secret-location spoilers. Recheck map and names after changing editions instead of assuming old references remain valid.
## Acceptance and common map-reading errors
Finish with legend, orientation, scale conditions, one route and at least one uncertainty. Apparent proximity cannot determine time without scale, roads and travel conditions. A different route requires checks for plan, action and map age before alleging error. Leave an illegible symbol unknown rather than imposing real-world conventions. End by explaining what the map adds to the story, not by transcribing every setting detail. Correctly identifying a schematic relationship map is a sufficient result.
## Related guides and sources
[Checking scene geography in ManYue: follow movement through visual landmarks](); [ManYue small lettering: separate zoom level, source detail and display processing]().
Checked on November 4, 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 lists, external tools and actually visible controls are identified separately. Code observations do not establish verified behaviour across every release path.