In-story data and claims

ManYue: Establish the whole before reading a pie chart

Check percentages, sectors and legends with invented four-three-three groups without mixing overlapping categories or different wholes.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

A circular chart in a comic may look intuitive, but sector size cannot replace a missing whole, category or unit definition. Practise part-to-whole reading with ten fictional props split four-three-three, revisiting labels and character claims. ManYue does not automatically read percentages, match legends or measure angles; use visible information and manual checks.

Choose a chart with traceable title and legend

Record work, edition, chapter, file position and panel, retaining title, legend, values and nearby dialogue rather than only the coloured circle. Without a suitable work, draw a prop-box chart: ten objects, A four, B three, C three, each in exactly one category and all included. Label this invented low-stakes count, not survey data. First record whole ten and three mutually exclusive, exhaustive categories. If a real chart lacks the whole definition, mark it pending rather than turning three colours automatically into three groups of people.

Calculate proportions before measuring appearance

Four divided by ten is forty percent; each three divided by ten is thirty percent, totaling one hundred percent. Preserve counts and proportions separately: forty percent is not forty objects. Percentages without a whole count cannot recover a unique population; forty percent could be sixteen of forty or four of ten. Calculate from labels and use screen area only as a correspondence check. Retain exaggeration or non-scale limits rather than deriving purported exact source values from pixel counting.

Treat sector angle as another representation of proportion

A full circle is three hundred sixty degrees. In the sample, A corresponds to one hundred forty-four degrees and B/C to one hundred eight each, again totaling three hundred sixty. This checks explanation, not an in-app angle measurement or precision claim for hand drawing. A sector that looks larger than half does not alone establish a label above fifty percent: consider perspective, exploded slices and schematic drawing. A tilted three-dimensional chart also distorts apparent areas. Labels, definition and legend are stronger evidence than estimated sizes of projected slices.

Verify legend assignment through multiple cues

For each sector, record colour, pattern, label or leader endpoint, ensuring forty belongs to A rather than neighbouring B. Use legend and wording for similar colours rather than memory; in monochrome, patterns and positions can help, with unclear ownership retained. Follow a crossing leader to its endpoint rather than assigning it to a sector it passes through. Decorative rings and portraits do not automatically enter the total. Confirm each of the three categories appears once before stating A is largest and B/C equal. Equal percentages do not merge distinct categories.

Do not treat multiple-response categories as exclusive slices

If a survey allows multiple responses, one person can enter several categories, so counts need not sum to the number of people. Read question and notes; percentages coincidentally totaling one hundred do not establish no overlap. The prop example explicitly assigns one object to one category; do not import that premise into a real chart. For a multiple-response circle, determine whether the whole is response selections or respondents before interpreting it. Preserve an unclear denominator instead of normalizing values to one hundred and hiding the source scope.

Check changing wholes before comparing two pies

In a separate later count totaling twenty, A at forty percent contains eight objects rather than four: unchanged share does not mean unchanged count. Conversely, retaining A at four while the whole becomes twenty yields twenty percent. State each scenario’s conditions instead of changing count and whole together and merely saying share fell. For two real charts, compare period, population, unit and categories. Equal drawn circles do not establish equal totals. If a character says no growth because share stayed constant, establish whether they mean share or count instead of choosing for them.

Retain rounding and missing-category possibilities

For real labels totaling ninety-nine or one hundred one, inspect precision, other categories and notes before alleging deception or adjusting a slice. A total far above one hundred requires checking multiple-response scope and units rather than automatically blaming rounding. Restore the whole page for a clipped sector or incomplete legend; mark insufficient information if the source is incomplete. Arithmetic can identify a question, not author motive. Preserve labels, calculations and unknown conditions, revising interpretation only with source data or explanation.

Reread the finding from the whole after returning

Leave the reader and return, locating the whole definition before labels and legend. Recompute four-three-three as forty-thirty-thirty percent and one hundred forty-four/one hundred eight/one hundred eight degrees. Recheck eight objects with an unchanged share when the total is twenty, rather than remembering colours alone. Preserve whole, category exclusivity, counts, proportions, visual limits and provenance of character claims. Keep unread details unknown and the original untouched. Completion interprets a slice as a bounded part, not a claim that any circle is complete, accurate and sufficient to prove a whole passage.

ManYue: Read bar-chart baselines before comparing heights; ManYue comic infographics: distinguish icon counts, areas and legend units.

Checked on November 8, 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.

For part-to-whole chart concepts, see OpenStax: Frequency, Frequency Tables, and Levels of Measurement. The ten-prop data and checking sequence are original, not copied examples.