Reading precision
ManYue rereading notes: organise clues with chapters and scene anchors
Build concise character, foreshadowing and composition anchors, revisit them with bookmarks and personal notes, and preserve edition and page-reference boundaries.
On this page
Rereading can focus on character development, recurring clues or composition rather than simply starting over. Use ManYue bookmarks as return points and brief personal notes to explain their purpose. Practise on one chapter with a few deliberate anchors; this workflow does not require a research database or automatic cross-book analysis.
Choose one rereading question
Choose a question small enough to investigate in one chapter, such as how a character’s attitude changes or how a repeated object is used. Write it in one sentence and select three to five candidate scenes that help answer it. Attractive pages unrelated to the question can wait. A limited scope makes each conclusion traceable to a specific scene.
Identify the work and edition
Record the work, volume or chapter, language, edition and local or server source. Page sequences can differ across versions. Pair a chapter reference with a brief scene description rather than relying on a number alone or copying long dialogue. These contextual anchors remain useful when a later edition changes pagination.
Save a small number of clear bookmarks
At the first candidate scene, confirm the page identity and save a bookmark using the visible controls. Add a short question-related remark if supported, or use your own note tool. Leave the page and test the return before adding more anchors. Bookmarks locate evidence; they do not automatically preserve your interpretation or surrounding context.
Separate observation from interpretation
Write the visible observation first, followed by your interpretation and uncertainties. A character stepping backwards is observable; its motivation may remain a hypothesis. Recheck nearby pages to confirm sequence and dialogue context. Two or three precise sentences are more useful than “important scene” and easier to revisit than a copied chapter.
Revisit anchors around the question
Review the anchors in story order, then compare the two most relevant to the same question in your notes. Switching between bookmarks is sufficient; simultaneous two-book display is not assumed. Record one similarity and one change in posture, viewpoint or objects. Preserve counterexamples and corrected interpretations rather than editing the evidence to fit an early theory.
Condense the session into a reusable note
At the end of the chapter, collect the question, two or three strongest anchors and your current conclusion. Retain location information when removing irrelevant temporary ideas. Keep only useful bookmarks if desired, with other candidates in your external list. Write one follow-up question for the next chapter and test that a retained reference still returns you to the evidence.
Preserve anchors when changing files
When changing editions or servers, keep the old references until you find the matching scene and context in the new version. Create a new bookmark with its edition identity. Pagination, spreads and extras can shift positions. Successful data sync does not establish that a different file shares the same page mapping; verify the actual artwork.
Questions and completion criteria
What if bookmarks become excessive? Return to the session question and retain the useful evidence. Can an interpretation be presented as a plot fact? Distinguish observation from inference and check the original context. Completion means one clear question, a few working return points, a short evidence-based conclusion and an edition record.
Related guides and sources
ManYue bookmarks and notes: save a page and return to the right place; ManYue edition comparison: distinguish monochrome, colour and revised copies.
Checked on October 26, 2026: ManYue public version 2.0.3, requiring iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. This guide describes a checking workflow; controls and permissions depend on the installed version. It does not claim that every step was tested on a physical device.