# Book Isle FB2 spot audit: nested sections and multi-paragraph notes

Language: en
Canonical: [Book Isle FB2 spot audit: nested sections and multi-paragraph notes](<https://allluckly.cn/en/guides/nasbook-fb2-nested-section-note-audit/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-fb2-nested-section-note-audit/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-fb2-nested-section-note-audit/>)
Published: 2026-11-04T00:00:00+08:00
Modified: 2026-11-04T09:36:55+08:00
Author: Bison

Use known headings and note anchors to inspect complex FB2 structures, distinguishing readable main text, flattened hierarchy, inaccessible notes and absent content.

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

Reading the first FB2 chapter does not establish access to nested sections or endnotes in their original relationships. After basic import checks, audit known locations in an authorised complex sample for heading hierarchy, multi-paragraph notes and return paths. Published FB2 support does not guarantee every popup, link or rich structure. Identifying an unsuitable reading path is a valid outcome.

## Prepare an authorised reference with known structure

Choose an FB2 fully inspectable in a trusted external tool, noting one parent heading, two child headings and a note with at least two paragraphs. A self-made sample is acceptable if checked in a familiar tool, without claiming casually edited XML satisfies every rule. Import a copy and preserve the original. Record the reference tool, callout location and each note paragraph’s opening. Audit this one group rather than guaranteeing the whole book, and resolve unrelated encoding or archive problems separately.

## Create a heading-and-paragraph checklist

List parent and child headings with each section’s first and final sentences, not only navigation labels. Some reading paths may flatten nesting; check order and identity without requiring identical indentation. Distinguish repeated child titles through context or topic words. Mark an empty parent container so it is not mistaken for a missing chapter. Personal checklist numbers and generated display numbers are not evidence that the original file contains those numbers.

## Read through the main-text group continuously

Read continuously from the parent region, checking child order, title/first-sentence pairing and boundaries for repetition, omission or merging. Navigation failure alone does not establish absent text. Merged headings with intact content are a hierarchy-presentation change; missing boundary sentences require a wider search. Before confirming a loss against the original, avoid cycling through imports at random and preserve the reproducible location and file identity.

## Check callout and note body separately

Locate the main-text callout and surrounding phrase, then test actual note access through available controls. A visible numeral does not guarantee a link, and an inactive tap does not establish that the source lacks a note. If there is no usable access path, record that limitation rather than inventing a popup action. Verify the source note externally and consider an authorised alternative suited to notes. Readable main text does not compensate for inaccessible notes when close reading depends on them.

## Check the entire note paragraph by paragraph

If a note is accessible, inspect both paragraphs and its ending, including paragraph boundaries. A definition followed by a counterexample cannot be considered intact when only the definition is visible. Check a cross-reference if present without assuming unlimited nested-link navigation. Record the original identifier and visible content, not screen-page counts that change with font size. Compare uncertain limits externally and retain an unverified status until the evidence is sufficient.

## Verify the return after reading the note

Where the interface provides a return action, test it and read the surrounding sentences to confirm the original callout, not merely its chapter. Without linked return, use a supported main-text bookmark or an external chapter/phrase locator; that helps you navigate but does not repair FB2 relationships. Complete one round trip before opening many notes. Interpret progress changes through actual content rather than assuming an advancing percentage means all notes are included in the text.

## Preserve mappings when changing reading copies

If critical structure is unsuitable on this path, make an authorised EPUB or PDF derivative with a trusted external tool. Reuse the same heading/note checklist rather than assuming conversion solves everything. For EPUB inspect links and return; for PDF inspect complete note text and layout. Both can change positions. Retain the FB2, conversion record and chosen reading copy, mapping old notes through short phrases instead of expecting page numbers, percentages or bookmarks to transfer automatically.

## Finish with a task-specific suitability result

Report main-text completeness, hierarchy, note access, paragraph completeness and return separately. A note label in navigation needs actual opening and ending checks. Flattened headings require first/last-sentence checks before alleging loss. A useful result may be suitable for continuous main-text reading but unsuitable for this note-heavy task, rather than declaring the format wholly unsupported. Keep a minimal authorised sample for reporting, not a private library, and reuse the checklist after updates to identify specific changes.

## Related guides and sources

[Book Isle FB2 reading: verify chapters, text and converted copies](<https://allluckly.cn/en/guides/nasbook-fb2-reading-check/>); [Book Isle annotation attribution: distinguish author, editor and translator within one edition](<https://allluckly.cn/en/guides/nasbook-author-editor-translator-voices/>).

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 structure concepts, see the [original FictionBook schema](<https://github.com/gribuser/fb2/blob/master/FictionBook.xsd>). Definitions of main and additional note bodies do not establish identical access in every reader.