Read TXT in Book Isle: check encoding, chapter detection and contents links

TXT files are small and simple in format but often suffer garbled text, a whole book recognized as one chapter, or headings merged into paragraphs. In Book Isle, separate whether the file's text is correct from whether its contents was identified correctly. This avoids repeated imports of the same faulty file.

Prepare an original for comparison

Keep an original TXT without overwriting it. Save a practice copy with Reading Edition in the name and record its source. For text you organize yourself, inspect beginning, middle, and end in a desktop editor for normal Chinese text. The first line alone is insufficient: an introductory note may be correct while the body uses another encoding or contains corruption.

This article does not require an encoding-selection button inside Book Isle. If the actual version lacks one, save a copy as UTF-8 in an external text editor and reimport it. Saving with an encoding differs from changing an extension. Renaming an unknown file to .txt does not guarantee plain-text content or remove encryption from the original.

Check three body-text locations after importing

Choose Local File Import in the shelf's add menu, select the copy, verify the preview, and import. Inspect the opening paragraph, navigate to the middle through contents or progress, and check the ending. Organize chapters only after all three read correctly. If the beginning has many question marks, boxes, or incoherent Chinese characters, stop adjusting reading settings first.

Missing font glyphs differ from encoding corruption. An occasional rare character shown as a box may respond to another available reader font. Entire passages becoming unintelligible more strongly suggest encoding. If the original already contains replacement question marks, switching encoding usually cannot restore it; recover an undamaged source. Keeping originals prevents losing more with each attempted repair.

Use consistent headings to help navigation recognition

Open the table of contents and compare the chapter count with the structure of the text. Chapter recognition in text files depends on heading patterns rather than a dedicated navigation file as in EPUB. If you compiled the file yourself, use a consistent format in an external editor, with each chapter heading on its own line, such as ‘Chapter One: Departure’ and ‘Chapter Two: Mountain Road.’ Keep normal line breaks before and after headings rather than attaching a heading to the end of the preceding paragraph.

This does not guarantee recognition of every heading. Essays, diaries, and papers may lack conventional chapter numbers. A short contents list does not necessarily mean missing text. Inspect body completeness before reorganizing the source. Do not turn ordinary sentences into headings just to create navigation; that fragments reading into meaningless sections.

Reimport a revised version carefully

If you need to work on encoding and headings on a computer, test the rules on a copy containing just three chapters before processing a longer work. Name the new file something like ‘山路随笔-UTF8-整理版.txt’ so you can identify it in the import preview. If you suspect a duplicate, first decide whether to keep the old record. Do not assume that text whose chapters have been reorganized still uses the same set of location data.

Adding or removing content or redefining chapters may move old progress, bookmarks, and excerpts. Export important notes, retain the old book, and import the organized version for verification before deciding on cleanup. An identical filename proves only an identical name, not matching paragraphs and positions.

Create reading markers independent of page numbers

Once navigation works, choose chapter two, note its opening sentence, read two or three screens farther, and return to the shelf. Reopen and check continuity. TXT is reflowable, so size, orientation, and font changes alter pagination. Do not use a fixed page number as the only evidence of progress.

When making reading excerpts, try to retain the chapter heading and a short phrase. For example, ‘Chapter Two, the passage about the ferry crossing’ is easier to find again in a revised edition than ‘page seventeen.’ If the text is a course handout or meeting notes, you can also add clear section headings to the source. When quoting someone else’s work, however, distinguish your edits from the original content to avoid mistaking your changes for the original wording.

Common diagnoses for encoding and contents problems

Why are there no chapters after successful import? Passing import checks does not establish recognizable chapter structure. Look for regular standalone headings first. A short unheaded piece can reasonably read as one continuous section. Repeatedly importing does not change the source structure.

What if the text remains garbled after changing to UTF-8? The source encoding may have been chosen incorrectly during saving, or corruption may already be written into the text. Return to the retained original, open it with a tool that displays it correctly, and save a new copy rather than converting an already garbled copy again. Work only on copies so the sole source remains intact.

What if the contents looks correct but jumps to the wrong place? Check duplicate headings, repeated heading quotations in the body, and extra blank paragraphs. Test a three-chapter file, then narrow the problem gradually. Very long files also take time to parse initially. Wait for import and preparation before checking; a newly visible cover does not prove parsing has finished.

Further organization and lookup

Once text and contents are stable, organize title, author, and tags using Organize book information. To find a passage whose wording you remember but chapter you forgot, use Full-text search tutorial. Keep before-and-after files so you can review the changes later instead of relying on one shelf result.

Sources and version

Information checked on October 23, 2026. The public release is Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. This guide is based on public feature descriptions and their entry points. Interface labels may change with the version. See Official App Store description and Apple release information.