ManYue PDF missing-glyph checks: separate appearance, font metadata and searchable text

A square in place of a PDF character may involve fonts or rendering, but the square alone does not identify the cause. Start with one known character, record its appearance in ManYue and inspect font information with an already trusted desktop tool. This differs from enlarging small lettering or proofreading scans; it does not promise automatic font installation, document repair or universal missing-glyph detection.

Fix one file and three character locations

Choose an owned short PDF and record name, source, edition, size and page position. Do not compare different downloads as if they were one file. You may make a page containing ABC, 漫画 and Ω, retaining the source text to establish expected characters; this does not guarantee every font contains them. For Latin letters, Han text and a symbol, note a neighbouring phrase and a descriptive page location rather than treating screen coordinates as internal PDF coordinates. If source text is unknown, keep the missing-glyph suspicion provisional. A character guessed from context is not evidence of what the original contained.

Record ManYue display before changing anything

Open the working copy, inspect the complete line at normal size, then enlarge the target. Record whether it is blank, a box, a wrong-looking glyph or a displaced whole line. Check nearby occurrences of the same character; one blurry crop does not show the entire font is damaged. Retain version, reading mode, position and exact character sequence, noting changes before/after zoom when relevant. Zoom cannot create strokes missing from low-resolution image pixels. If a scan is an image, embedded-font metadata may not explain lettering inside it. First identify the content layer being observed.

Inspect font information in an existing desktop tool

Only if a trusted desktop PDF tool with font information is already available, inspect the same file’s document properties or font panel for name, type and embedding status. This is an external step, not a ManYue menu. If unavailable, mark font information unchecked; purchasing or installing software is not required. Adobe’s official documentation explains embedding and substitution conceptually but does not prove every missing glyph in this PDF results from an unembedded font. Record the tool, version and fields actually shown. An ambiguous font name does not establish that the device has a complete matching font installed.

Subset embedding is not automatically missing text

“Embedded subset” means embedding a selection of glyphs needed by the document; it does not mean half the page’s text is inherently missing or that all fonts must be reinstalled. Both full and subset embedding require checking actual page appearance; a status label does not certify correct document production. Conversely, an unembedded font may require substitution, but that does not guarantee a visible error. Keep font status and appearance separate for each target character. A subset may display normally, while an embedded font may still accompany an unresolved anomaly. Do not turn an association into a confirmed cause.

Record copying and search beside visible glyphs

When the file and available reading interface permit it, search for or copy the target phrase and record the exact resulting characters, not merely “search works.” Correct appearance with garbled copying differs from a visible box whose word is found in search; character mapping and glyph appearance are separate checks. Scans may be image-only or have recognised text too. Record observations without guessing the full internal structure. A failed search does not prove visible prose is absent, while correct copying does not certify every glyph. Do not silently replace an uncertain quoted glyph with a search result; retain both evidence streams.

Keep the original identical across tool comparisons

Open the same working copy in another already available trusted reader and compare all three positions, recording normal, identical anomalies or different anomalies. Normal display elsewhere does not prove a flawless file, and a ManYue-only anomaly does not identify a particular rendering library. List unisolated differences such as operating system, font environment and rendering approach. If the author provides a newly exported embedded-font edition, retain it as a separate file with edition changes recorded; do not redistribute restricted fonts for them. State the change scope: a new export is not a pure display comparison of identical bytes.

Give exact character scope and conditions in a report

A report should retain file identity, position, evidence for the expected text, actual appearance, font fields and the other reader’s result. Share only a permitted small sample. If the original character is unknown, say so instead of supplying guessed repaired prose. Include a normal occurrence elsewhere as a control when the same symbol works there. Without a conclusion, do not compress images, remove fonts or overwrite the original as trial repairs: they change several variables and may lose evidence. You may read unaffected parts, but mark this location unresolved in excerpts rather than treating uncertain content as a reliable quotation.

Exit and return to check display against the record

Exit the reader and return to the same PDF. Relocate all three positions and compare initial results, ensuring you did not open the author’s new export by mistake. Keep four evidence groups: visible glyphs, searchable text, font information and tool environment; mark every unchecked group explicitly. Completion means the anomalous character and evidence locations are clear and reviewable, not that one square identifies a font root cause or guarantees every symbol is restored. Date later results from an official revision while retaining earlier observations rather than silently rewriting a historical problem as always normal.

Related guides and sources

ManYue small lettering: separate zoom level, source detail and display processing; Read PDF comics in ManYue: covers, wide pages and reading position.

Checked on November 10, 2026: Apple public version information lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the official App Store for feature descriptions; specific controls must still be checked in the installed version.

Method reference: Adobe: font embedding and substitution in PDFs. Numbers, short passages and controls are original exercises. Sources explain concepts rather than prove automatic recognition or grading in the app. Manual notes may be kept externally. This article does not claim step-by-step testing on a physical device or private server; unresolved content should remain marked for review.