# ManYue: Read in-story forms by separating ticks, blanks, deletions and additions

Language: en
Canonical: [ManYue: Read in-story forms by separating ticks, blanks, deletions and additions](<https://allluckly.cn/en/guides/manyue-in-story-form-state-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-in-story-form-state-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-in-story-form-state-check/>)
Published: 2026-11-07T00:00:00+08:00
Modified: 2026-11-07T09:41:37+08:00
Author: Bison

Treat forms as story props with authors and times, recording field states without interpreting blankness as a negative.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-in-story-form-state-check/>), translated on 2026-11-07. Original publication dates, attribution, code and version notes are retained.

Registration sheets, duty lists and check cards may appear in only one panel while carrying an important clue. Ticks, blanks, deletions and later additions are different states, and a form title does not mean every field has been completed. Practise field-by-field reading with a self-made low-stakes form. Keep the work in external notes; this assumes no table recognition, recovery of obscured text or automatic author tracking in ManYue.

## Prepare a practice form with field labels

Create a prop-loan card with fields for date, borrower, prop number, returned and remarks, using fictional names and objects. In panel one, Lin borrows paper hat number one and the returned box stays blank. In panel two, tick that box and add intact. In panel three, cross out an incorrect number and write the correct one. Number the panels one, two and three, then import them as an ordinary image comic. A real work is also suitable, but retain headings, legends and nearby dialogue, including any explanation of blank fields. The exercise concerns no real lending, legal signatures or private data.

## Record headings and field scope first

Open the first page and copy the form title, field names and legend. Establish whether each row represents a person, loan event or object. Do not assign a tick from an adjacent row to the current person, or guess ownership from horizontal alignment alone. For merged cells or notes spanning rows, record the covered rows and defer unclear scope to context. For every field, preserve page and panel, visible wording, location and state. Establishing field scope first provides the basis for deciding whether a tick actually changes this particular loan’s status.

## Preserve a blank as a blank

For the returned box in panel one, write no visible mark, not not returned or lost, unless a legend explicitly defines that meaning. A blank could reflect incomplete entry, inapplicability, occlusion or poor reproduction, each requiring different evidence. If a hand hides a corner of the box, record partial visibility rather than extending the visible white area to the whole box. The same applies to dates and names: unreadable does not mean unfilled. Distinguish not seen, clearly empty, obscured and illegible so that a later summary does not quietly turn uncertainty into a definite negative.

## Record ticks and deletions individually

When comparing panels two and three, first confirm it is the same card, then record the field gaining a tick, the wording crossed out and the location of replacement text. A deletion shows that a mark was altered; it does not automatically identify who changed it, when, or whether the replacement is final. If the old text remains readable, preserve old wording, deletion state and new wording separately. If it is fully obscured, do not guess. In the practice example, explicitly record the added returned tick, the added intact remark and the separate number correction, rather than compressing all three into card completed.

## Require evidence for author and time

Then examine hand movements, dialogue, handwriting changes and date fields for evidence of authorship. A person standing beside the form did not necessarily write every entry. Different colours do not necessarily mean different people; one writer may change pens. A date on the card may be the event date rather than the moment of writing. Separate the recorded date, panel sequence and inferred addition time. Narrow the claim only with explicit action or narration. Otherwise keep writer unknown or time uncertain instead of using the ending to assign an author to every mark.

## Check whether a conflict is real

If dialogue says returned while the box is blank, first check that both refer to the same object, loan event and time. A difference may mean the form has not been updated, not that someone is lying. Match object number, name and date, then state the scope of each piece of evidence. A later tick establishes its presence in that later panel; it does not prove the return happened between the two panels. Possible explanations include delayed recording, a mismatched object or unreliable narration, but list missing evidence for each. A form is not automatically absolute truth.

## Protect original states when legibility fails

If zoom is insufficient, return to the whole panel to inspect headings, rules and occlusion, then look for a fuller view in neighbouring panels. A short diagonal stroke is not automatically a tick: it might be deletion, a pen tip or paper texture. Do not generate an image or add strokes to recover supposed original content, or complete fields in the comic itself. If the form appears on several pages, record each version instead of keeping only the clearest, because change may itself be evidence. Mark unread fields honestly while completing the confirmed ones.

## Return to the original and check the field-level summary

Leave the reader and return. Use page and panel references to check date, borrower, number, returned box and remarks individually, ensuring the summary omits none. Attach evidence and uncertainty to each state, especially checking whether blank became no or deleted became never existed. The result is a field record updated in panel order, showing additions, removals and unknowns, not an automatically recovered form database. For recommendations or plot discussion, remove unnecessary spoilers and retain only the minimum description that supports the point.

## Related guides and sources

[ManYue documentary-comic reading: quotation, reconstruction and inference](<https://allluckly.cn/en/guides/manyue-documentary-comic-source-layers/>); [ManYue comic infographics: distinguish icon counts, areas and legend units](<https://allluckly.cn/en/guides/manyue-comic-pictogram-quantity-legend/>).

Checked on November 7, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6753895889&country=cn>) lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) 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.