# Book Isle rare-character display: distinguish source characters, glyphs and available copy actions

Language: en
Canonical: [Book Isle rare-character display: distinguish source characters, glyphs and available copy actions](<https://allluckly.cn/en/guides/nasbook-rare-han-display-source-identity-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-rare-han-display-source-identity-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-rare-han-display-source-identity-check/>)
Published: 2026-11-20T00:00:00+08:00
Modified: 2026-11-20T11:38:32+08:00
Author: Bison

Use a short original text to check common and extension characters, source identity, appearance and optional copying.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-rare-han-display-source-identity-check/>), translated on 2026-11-20. Original publication dates, attribution, code and version notes are retained.

Use a short original text to check common and extension characters, source identity, appearance and optional copying.

## Preserve the original and an identifiable sample

Choose an authorized book containing an apparent box or uncommon character. Record title, edition, format, chapter and context, and retain the unchanged original and notes. Separately make a short practice TXT containing common 吉 and extension character 𠮷 with A and B labels, so similar-looking forms are not treated as the same character. Use ordinary self-written phrases, not real names, identity documents or private information. If the editor cannot confirm the second character, record unknown rather than substituting another and claiming the issue vanished.

## Confirm character identity at the source

In an existing trusted code-point inspection tool, check the practice text: 吉 is U+5409 and 𠮷 is U+20BB7, different code points. Similar strokes or an empty box on a screen cannot establish which character is stored; one character may also appear with different glyph designs under different fonts or regional conventions. Unicode charts and FAQs identify characters but are not a font-coverage report for the user’s device. Without a code-point tool, retain the source text and note that identity remains unverified rather than installing an unknown font or diagnostic app.

## Check the same file through a system entry

Save the practice TXT as UTF-8 and record filename, location and modification time. Open it through an existing Files or text-viewing entry on the device and observe the characters beside A and B. The system entry may itself fail to display a glyph, so this is a same-device reference, not an infallible judge. If its content differs, check for an old copy, editor rewriting or an incomplete cloud download before drawing conclusions. Do not overwrite the source before saving evidence; version and file identity make comparison possible.

## Import into Book Isle and locate both positions

Use an actually visible local import entry in Book Isle to select the TXT, confirm the practice book and find A and B. Record the actual characters, boxes, blanks or other appearance with device, system and confirmable app version; do not assume a particular glyph must display. If a same-named old shelf entry exists, distinguish it using context and actual source; do not assume reimport necessarily overwrites or creates a new book. If import fails or the line itself is missing, keep the message and stage rather than labeling it immediately as a missing glyph.

## Compare appearance one condition at a time

If the current reader actually offers text-size or appearance controls, record the original state and adjust one setting, redisplaying the same line at a comparable position. Observe whether the whole character is a box, only the glyph design differs, or neighboring text is clipped: these are distinct results. Without that control, skip it; do not assume a font selector or fallback toggle exists. Restore the original preference after testing. Better visibility at a larger size does not prove the source character data changed.

## Check copied text only when available

If the current format and interface actually provide text selection and copying, select a short sentence containing the character, paste it into an existing trusted plain-text tool and inspect context and confirmable code points. Copying U+20BB7 while Book Isle shows a box is a useful layered observation, but does not identify a specific font, renderer or root cause. A different copied result can also involve selection range, paste destination or source copy. Without selection or copying, mark untested; do not require an absent button or treat text recognized from a screenshot as the original.

## Troubleshoot file, display and scope separately

If neither the system nor Book Isle displays the character, recheck source identity and available device display conditions. If the system displays it but Book Isle differs, reconfirm the same file, device and character, then preserve the observation. If the same passage appears in another owned edition, record the two sources and editions separately and inspect each character; copying older wording over the newer file does not make the originals identical. A printed image, screenshot and selectable text provide different evidence: a screenshot alone cannot reveal the stored code point. If the source no longer contains U+20BB7, investigate original acquisition and editing; changing font size cannot recover a missing character. Do not bulk-replace characters in a real book or generalize one sample to every EPUB, TXT or device. Change one condition per round and retain unresolved uncertainty.

## Reopen and deliver the smallest reproducible record

Exit and reopen the practice book, locate A and B, record whether appearance repeats and confirm the real book and notes remain locatable. Deliver the authorized sample source, whether code points were verified, system and Book Isle appearances, settings actually used and copy availability and result; mark unperformed actions untested. For feedback, prefer a self-written test sentence and a redacted screenshot over a private book. This task checks display and optional copying; full-text search matching requires a separate search exercise.

## Related guides and sources

[TXT encoding and chapters](<https://allluckly.cn/en/guides/nasbook-txt-encoding-chapters/>); [Full-text search](<https://allluckly.cn/en/guides/nasbook-full-text-search/>).

Checked on 20 November 2026: [Apple lookup](<https://itunes.apple.com/lookup?id=6766198898&country=cn&entity=software>) lists Book Isle 1.1.4 and iOS / iPadOS 15.6 or later; the [App Store](<https://apps.apple.com/cn/app/id6766198898>) describes TXT and EPUB reading. Character and glyph references: [Unicode CJK FAQ](<https://www.unicode.org/faq/han_cjk.html>) and [CJK Extension B chart](<https://www.unicode.org/charts/PDF/U20000.pdf>). No device display or copying test is claimed.

