# ManYue recurring visual motifs: compare what each appearance does Language: en Canonical: [ManYue recurring visual motifs: compare what each appearance does]() 中文：[中文 HTML]() English: [English HTML]() Published: 2026-11-04T00:00:00+08:00 Modified: 2026-11-04T09:36:55+08:00 Author: Bison Track the context and outcome of a recurring object or composition, seeking changes and counterexamples before calling resemblance a symbol. English translation of the [Chinese original](), translated on 2026-11-04. Original publication dates, attribution, code and version notes are retained. Recurring umbrellas, windows, circular compositions or gestures invite comparison, but repetition does not prove a shared symbolic meaning. While rereading in ManYue, build a small evidence log for one candidate motif and compare its role across contexts. Classification and interpretation remain the reader’s work; the app provides reading and supported return references. ## Define a recognisable candidate Choose one candidate, such as a damaged red umbrella rather than every red object. Define inclusion by shape, user, pattern or compositional relation, and state exclusions. For window framing, record the figure’s relation to the panes rather than collecting every window background. Limit the first pass to two or three completed chapters to avoid importing future plot. Rejecting the candidate is a valid result: identifying an ordinary recurring prop is more useful than assembling arbitrary images to force a theme. ## Record the complete context of each occurrence For each occurrence, record chapter, page, panel, participants and surrounding action, then its size, use and visual attention. A cropped detail may hide that it is merely shop merchandise, so retain access to the full page. Start with three to five cases, each containing an observation and context sentence. Consecutive panels showing the same umbrella belong to one scene occurrence unless there is a reason to distinguish them; panel counts should not inflate recurrence. ## Separate function from mood labels First state what it does—shelters rain, blocks sight or passes between people—then separately interpret distance or intimacy. An umbrella in a sad scene does not establish sadness as its meaning; inspect weather, action and dialogue for direct explanations. Practical and narrative functions can coexist, but give evidence for each. A character liking an object is not an authorial declaration of abstract symbolism. Where the work explicitly explains meaning, cite its location and test whether the occurrences fit. ## Find the same form serving a different role Seek an occurrence with a different outcome: a first departure behind an umbrella versus a later shared umbrella and continued conversation. Identify whether the change lies in object, holder, action or timing rather than simply calling it improvement. Retain background-only cases to test inclusion. You may narrow an overly broad category, recording why instead of silently discarding inconvenient evidence. A counterexample may refine the claim or reveal contrast rather than invalidate every observation. ## Keep compositional comparisons comparable Compare complete images before inferring distance from differently zoomed views. Use relations such as an umbrella rim obscuring eyes rather than screen centimetres. Describe landscape–portrait differences instead of forcing equivalent proportions. Return to the full page after inspecting details, and keep references rather than altering images. Cropping between editions can change the observation, so hold the source edition constant for this pass. ## Write a bounded interpretation Limit the interpretation to how this image accompanies change in the sampled scenes, giving two supporting cases and one imperfect fit. Use appropriate scope rather than promoting a small sample into the work’s sole theme. An invented example might say that two ways of holding an umbrella move the figures from separation to shared presence; that is more testable than declaring red umbrellas equal love. Keep observations beside interpretation so later rereading distinguishes what you saw from what you inferred. ## Test returning to each occurrence Bookmark three important examples where supported, or record chapter, landmark and panel externally. Leave and return in occurrence order to catch a nearby lookalike. If an image collection lacks context, attach the original location rather than treating the gallery as a complete evidence base. Recheck each case after changing sources; old coordinates may not map to a new file. Share only necessary commentary and authorised quotations instead of distributing a batch of pages to prove recurrence. ## Acceptance and common generalisation errors Finish with a clear definition, at least three contextualised cases, a handled counterexample and a bounded claim. Similar appearance requires shape and context checks before identifying the same object. Frequency may reflect ordinary scenery or continuous action rather than a motif. If evidence is insufficient, retain a candidate instead of padding with unrelated cases. Add only new evidence and revision reasons later; this log supports understanding rather than assigning a fixed symbol to every prop. ## Related guides and sources [ManYue rereading notes: organise clues with chapters and scene anchors](); [Referencing a panel in ManYue: create a verifiable address within a page](). 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.