ManYue small lettering: separate zoom level, source detail and display processing

Unreadable corner notes can result from whole-page scaling or from missing detail in the source itself. Compare the same lettering under controlled conditions before choosing another file. The useful outcome is legible, correct text; a sharper-looking image does not guarantee that unavailable original detail has been recovered.

Choose text with a verifiable reading

Choose a small note and nearby ordinary dialogue on the same page. Record their locations and use a legitimate reference when possible to verify the actual wording. Avoid highly stylised lettering as the only sample. Keep device orientation and comfortable brightness stable. Compare the exact same text rather than substituting larger text elsewhere.

Check whether the whole-page view is too small

Zoom gradually and check whether the strokes become readable. A two-page layout can make portrait pages small, so compare a single-page view at a similar text size. Clear enlarged text suggests sufficient source detail; larger blocks or blurred edges suggest further source inspection. Extreme magnification reveals pixels in normal images too, so focus on useful reading sizes.

Inspect the corresponding original image

For your own local archive, inspect the matching original image with an external tool. Verify that it is not a thumbnail or screenshot. Record its dimensions and examine whether fine strokes are present near native scale. For a server book, obtain the original only when permitted. Compare similar displayed text sizes, and record when the service’s delivered image cannot be verified against its stored original.

Distinguish compression from absent detail

Inspect block artefacts, broken strokes and ghosting around small text, then compare larger dialogue on the same page. Compression, defocused scans and resampling can all reduce legibility, and appearance alone may not identify one cause. Preserve the comparison original. Repeated JPEG saving can lose more detail rather than solve the problem; keep experimental derivatives separate.

Compare optional processing where available

If your installed version and entitlements expose image-processing controls, record the initial value and change one option at a time on the same page. Strong processing can thicken lines or create textures without improving accuracy. Skip unavailable controls; this workflow does not require a particular enhancement model. Check ordinary dialogue again before keeping a change.

Choose a layout or a better source

When source detail is sufficient, use single-page reading, orientation changes or local zoom. When the source lacks detail, seek a higher-quality version you are entitled to obtain rather than assuming another device will repair it. Compare contents and extras before replacing editions, and transfer your position using a chapter and scene if the new import has separate records.

Keep a compact comparison record

Record the page, source dimensions, whole-page and zoomed results, and any setting changed. A self-made lettering sample or authorised crop can support a report with app version and exact steps. Screenshots introduce their own scaling and compression, so identify them as such. A reproducible source and procedure help distinguish import, transport and display issues without sharing private libraries.

Questions and completion criteria

Does visible pixelation mean the app is broken? Not necessarily; a bitmap contains finite detail. Why can darker processed text remain unreadable? Higher contrast does not guarantee restored strokes. Finish by identifying whether scale or source detail dominates and retaining either a readable layout or evidence for obtaining another file. Keep the original and your comparison notes.

Related guides and sources

ManYue reading layouts: direction, single pages, double pages and spreads; 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.