# Book Isle Markdown character checks: distinguish code, tables and ordinary prose

Language: en
Canonical: [Book Isle Markdown character checks: distinguish code, tables and ordinary prose](<https://allluckly.cn/en/guides/nasbook-markdown-literal-code-table-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-markdown-literal-code-table-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-markdown-literal-code-table-check/>)
Published: 2026-11-04T00:00:00+08:00
Modified: 2026-11-04T09:36:55+08:00
Author: Bison

Inspect hashes, asterisks, backticks, pipes and column relationships in a small Markdown sample, distinguishing source markup from rendering and examples from instructions.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-markdown-literal-code-table-check/>), translated on 2026-11-04. Original publication dates, attribution, code and version notes are retained.

Markdown can be read as source text or displayed after parsing; those paths are different. Book Isle publishes Markdown support, but this exercise assumes no complete web-style renderer. Use a small self-made sample to inspect character identity, code boundaries and table relationships, judging accurate reading rather than command execution or automatic support for an extension.

## Prepare a sample with easily confused symbols

Save a UTF-8 MD file in a familiar text editor and retain it. Include ordinary prose, a hash heading, a code block and a two-row table using your own content without private configuration. The sample below is for inspection and does not ask you to execute commands. Verify every symbol, space and line break before importing a copy. Do not rely solely on material reformatted through messaging, which may already have altered the source markup.

````markdown
# Sample
Use * as a literal symbol.

```text
# This line belongs to the example.
item_a | item_b
```

| Item | Count |
| --- | --- |
| Amber | 2 |
| Blue | 7 |
````

## Identify the current viewing path

Compare visible hashes, backticks and table delimiter rows with the editor. Retained markup indicates a source-text path, not necessarily failed typesetting; parsed headings or code regions require correspondence checks. Either path may suit a task if its identity is clear. Record version and behaviour rather than inferring syntax highlighting, web preview or a clickable outline from the format name. Continue within the actual path without searching for an unverified mode switch.

## Check the identity of asterisks and backticks

Determine whether each asterisk is a literal character or emphasis markup, and whether backticked text requires literal reading. A missing star can change a wildcard or multiplication example despite readable prose. In source view, retained delimiters are expected but their span should be clear; in a rendered path, check whether literal characters were mistakenly consumed as emphasis. Consult the editor where needed rather than adding escapes to the sole original. Document any derivative edits.

## Inspect code blocks without executing them

Locate both code fences and check that an internal hash is not mistaken for a book heading and that indentation and breaks remain identifiable. Screen wrapping is not a new source newline; verify before copying. Check filenames, arguments and pipes literally, without joining explanatory prose into a command. Book Isle is used for reading here, not execution. For development, verify the source in an appropriate editor rather than copying a reading screenshot straight into use.

## Check each row against its headers

Use two distinct records and read each name and quantity against its header so narrow-screen wrapping does not pair a number with the wrong row. Source view requires reading pipes and delimiter rows yourself; a rendered grid also needs content checks. Tables are a common extension, so Markdown support does not establish identical extension behaviour. A pipe inside a cell may use special syntax; check the author’s convention before treating it as another column. Use an editor or reliable reference renderer when relationships are unclear.

## Separate links from body content

Link label, destination and resource path are separate fields and may not become clickable controls on the current path. Check whether destination text survives before declaring content absent. Relative paths depend on directory relationships; moving an MD alone can break resources without proving faulty body parsing. Open trusted external destinations separately as needed, distinguishing an address from embedded page content. An unread linked page is not assumed to be saved offline with the document.

## Choose source-preserving or layout-preserving copies

For syntax and literal examples, retain MD and use an editor as needed; for tables and figures, create an authorised PDF or suitable readable derivative with a familiar tool. Recheck both data rows, code boundaries and special characters after conversion. Attractive layout does not certify literal accuracy. Identify the source and conversion process rather than renaming an extension. Remap notes through headings and phrases when positions change. Source and convenient reading copies can coexist with explicit purposes.

## Acceptance and common misunderstandings

Finish with an identified viewing path, verifiable special characters, clear code boundaries, correct two-row relationships and an accurate understanding of link scope. Visible hashes may be source markup. A grid still needs checks for displaced or missing cells. Visual wrapping differs from source newlines. Keep the sample and observations for reporting without real passwords or servers. Use a reliable alternative for unsuitable material instead of inventing complete rendering or execution capabilities.

## Related guides and sources

[Read documents in Book Isle: organise Markdown, HTML and Office files](<https://allluckly.cn/en/guides/nasbook-document-reading/>); [Check TXT paragraphs in Book Isle: distinguish hard wraps from paragraph breaks](<https://allluckly.cn/en/guides/nasbook-txt-hard-linewraps/>).

Checked on November 4, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6766198898&country=cn>) lists Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6766198898>) 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 lists, external tools and actually visible controls are identified separately. Code observations do not establish verified behaviour across every release path.

For syntax concepts, see the [CommonMark specification](<https://spec.commonmark.org/0.31.2/>) and [GitHub table extension](<https://github.github.com/gfm/#tables-extension->). Standards describe syntax, not a promise about Book Isle’s rendering capabilities.