ManYue: Read in-story calendars by separating date cells, weekdays and story time

A calendar in a comic may establish a date or merely furnish a room. Which day a circle covers, which weekday starts the columns and whether the month is visible all affect its use as plot evidence. Read a calendar in context using a self-made positioning sample, without searching for plot answers or assuming that ManYue recognizes dates, computes weekdays or generates a story timeline.

Choose a calendar with headings and context

Choose a panel showing the month, at least one weekday header row and several date numbers. Record work, edition, chapter, page position and panel number. If no complete sample is available, make a fictional June calendar, explicitly placing day one in the Monday column and labelling Monday through Sunday. Do not claim it matches a real year. Circle day twelve and add a note arrow beside thirteen as two different marks. Retain nearby dialogue and neighbouring panels so an old wall calendar, flashback image or decoration is not automatically treated as the story’s current date.

Copy the month and weekday-column order

First record the visible year, month and weekday headings. If the year is absent, write not shown rather than borrowing the publication year. Weeks may start on Sunday or Monday, and columns may be arranged vertically, so copy the original order before locating numbers. A red date is not necessarily Sunday or a holiday without a heading or legend. If the top is cropped, record only relative positions of visible numbers, not an invented complete month. In the fictional sample, twelve belongs in the second row’s Friday column because of the stated layout rule, not a real-calendar lookup.

Check numbers and neighbouring cells

When locating a target date, check preceding and following numbers and the rows above and below. This prevents a blurred twelve becoming seventeen or a small note becoming a date. Record row, column and readable content in two neighbouring cells; that is easier to trace than a number alone. If small dates from the following month appear at month-end, note their style and month rather than assigning them to the current month. Where one cell includes lunar dates, activity numbers or small notes, distinguish levels first. Do not assume every smaller number is irrelevant, and preserve alternative readings for blurred areas instead of choosing the best plot fit.

Distinguish circles, arrows and spanning marks

On the second pass, record mark type and coverage. In the practice sample, the circle clearly encloses twelve while the note arrow points to thirteen; both must not become an activity on twelve. In a real image, a large circle may span two cells, a line may indicate a date range and handwriting may sit between cells. Separate definite enclosure, arrow target and uncertain scope. If needed, describe the mark’s left end, right end and crossed grid lines. Do not guess the artist’s intention or treat every conspicuous mark as an event already completed; it could indicate a plan, deadline or anniversary.

Separate prop dates from the present story time

Read context again, separately recording what the calendar says, what characters say the present time is and whether the panel belongs to present action, memory or imagination. A circle around twelve does not establish that today is twelve, and tomorrow requires an established speaking date. Without a year, do not validate weekdays across years. With a fictional calendar system, do not impose real-world month rules. Add a mark to a story-time note only when narration or action supplies a connection, and record that connection. Unlike listing every flashback, this limits what date claims one prop can support.

Exclude changed references before declaring inconsistency

If the next panel seems to change the date, first check room, month, calendar identity and viewpoint. A turned calendar page, another room or a memory may change the object. If it is the same object, specify whether number, mark or weekday heading differs rather than immediately declaring a timeline error. Published editions may also correct a calendar, so record the edition instead of substituting an online screenshot for yours. Without year and month, report at most a local positional difference; do not invent a precise Gregorian date to explain it.

Keep the smallest usable fact when details are unclear

If zoom still does not resolve details, inspect the whole panel for text orientation and scan cropping so a rotated page does not reverse rows and columns. Look for a clearer close-up nearby, but do not generate missing date details. If you can establish only that a circle lies in the latter half of the month, preserve that limited fact rather than supplying a day. In plot discussion, label directly visible information, contextual inference and unconfirmed claims separately, omitting calendar inferences entirely if necessary. Dropping an attractive explanation is sounder than turning a blurred digit into a decisive clue.

Return to the panel and audit the date wording

Leave the reader and return, relocating month, weekday headings, target number and mark. Check that every row/column description matches. Finish with a bounded sentence such as the calendar circles twelve, but narration has not established today’s date, rather than the story occurs on twelve. For the fictional sample, verify Friday for twelve, Saturday for thirteen and the different targets of arrow and circle. Preserve the unread year and unconfirmed purpose. The result is a prop-date evidence record, not an automatically generated schedule or guidance for real appointments or deadlines.

Related guides and sources

ManYue flashback timeline: separate presentation from event order; Referencing a panel in ManYue: create a verifiable address within a page.

Checked on November 7, 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 records, external tools and actually visible controls are identified separately, and personal analysis or code observations are not presented as verified automatic capabilities.