How to translate novel titles and hundreds of chapter headings without breaking character names or your EPUB table of contents
Tri Thu知秋
On this page
- Why does translating book and chapter titles before building your character name table cause mismatches?
- How should you translate the three most common web novel book and chapter title patterns?
- When does the interface display a bilingual "Original | Translated" book title and clean up "index_split" chapter labels?
- How do chapter titles flow differently into TXT exports, newly built EPUBs, and format-preserving EPUB write-back?
Novel titles and chapter headings pack character names, locations, realms, or plot tropes, so they only translate accurately after locking your Names & terms dictionary first. On NovelVerba, the book title displays bilingually as Original title | Translated title when the opening chapter verifies the book-title line, while each chapter heading translates automatically with the chapter body when placed on line one of the source.

| Component | Condition for detection and translation | Display and exported file result |
|---|---|---|
| Book title | Novel has at least 2 chapters; chapter 0 title matches the project title; first non-empty source line of chapter 0 is at most 60 characters, matches the project title, and is not a chapter label (第1章, Chapter 1) | Displays bilingually as Original title | Translated title on the interface (up to 160 characters for the translated title); if ambiguous, keeps the project title you set |
| Chapter headings on the reading list | First line of the chapter's source text matches the chapter title exactly; raw Calibre labels like index_split_000 are recognized automatically | Takes the first line of the chapter translation as the translated chapter title (up to 160 characters); normalizes index_split_000 into Chương 1, Chương 2 on the reading screen |
| Table of contents in TXT, Markdown, SRT, and newly built EPUB (from TXT) | First source line matches the chapter title and chapter source text has not been cleaned up after completing the novel | Splits the translated first line as the chapter heading and rebuilds toc.ncx completely; if unverified or after source cleanup, uses the clean label Chapter N so untranslated source titles never leak |
| Table of contents in format-preserving EPUB (write-back from original EPUB) | Chapter headings sit inside h1 or h2 text nodes within each XHTML chapter file of the original EPUB package | Translates h1 and h2 headings inside the chapter page content, while keeping original navigation TOC files (toc.ncx, nav.xhtml) untouched so chapter links never break |
Why does translating book and chapter titles before building your character name table cause mismatches?
Anyone who has read a long translated web novel knows this jarring moment: the chapter list says Chapter 15: Foundation Building Pill or Chapter 42: Visitors from Azure Cloud Sect, yet two paragraphs into the chapter the exact same pill or sect is called by raw pinyin or a different name altogether. It gets worse when a chapter title is just a three-character personal name or alias: if you translate the table of contents separately before reading the opening chapters, the AI has no context to tell whether those characters name the male lead, a sword technique, or a border city.
Chinese, Japanese, and Korean web novel chapter headings rarely form full sentences; instead, they pack proper nouns tightly: a newly introduced character, a title, a cultivation realm, a sect, or an artifact. When you scan the first 5 to 10 chapters and lock the Names & terms table (the per-novel dictionary) before running translation, every character name, place name, and technique inside a chapter heading automatically follows that locked dictionary. What the heading calls the sect or protagonist matches the dialogue inside the chapter.
That is why I never pull a table of contents out to translate in isolation beforehand. My workflow always begins by setting up the proper-noun table as covered in Build a character name table before translating a novel with AI, and locking two-way interpersonal address pairs as explained in Choose address terms by character relationship when translating Chinese novels. Once those two layers are fixed in the per-novel dictionary, every chapter title translated alongside its chapter body stays faithful to the cast list.
How should you translate the three most common web novel book and chapter title patterns?
Across hundreds of cultivation, fantasy, and modern romance web novels, almost every book title and chapter heading falls into one of three structural patterns. The first combines a Proper Name with a Title, Location, or Cultivation Term, such as 第15章 筑基丹 (Chapter 15: Foundation Establishment Pill) or 第42章 青云宗来人 (Chapter 42: Arrivals from Qingyun Sect). Accuracy here depends on scanning the first 5 to 10 chapters first so the per-novel dictionary holds the exact entry for 筑基丹 and 青云宗 before the batch runs.
The second pattern is the concise four-character idiom or classical parallel phrase used as chapter headings in historical and xianxia fiction. Out of context in a bare table of contents, four classical characters can mean five different things and often come out stiff or guessed backwards. When that heading stays on the very first line of the chapter source text, the AI translates it together with the full chapter narrative underneath, picking phrasing that fits the actual scene.
The third pattern is the long sentence-style or trope-packed book title common in modern web novels and romance, stringing together community shorthand like rebirth, book transmigration, system, white moonlight (白月光), wife-chasing crematorium (追妻火葬场), or marry first, fall in love later (先婚后爱). Translating these word for word turns a genre hook into baffling literal English; to render romance tropes and slang naturally, see the reference table in Chinese romance novel slang in translation: avoiding literal traps like eating vinegar and green hat.
| Title pattern and source example | What goes wrong when translated in isolation | Natural translation with locked dictionary and chapter context |
|---|---|---|
| Proper Noun + Location / Pill / Realm: 第15章 筑基丹, 第42章 青云宗来人 | Heading renders as Base Building Medicine or Green Cloud Mountain Guests while the chapter body says Foundation Establishment Pill and Qingyun Sect | Scan the first 5 to 10 chapters to lock Foundation Establishment Pill and Qingyun Sect in Names & terms; headings align as Chapter 15: Foundation Establishment Pill and Chapter 42: Arrivals from Qingyun Sect |
| Concise four-character idiom or classical parallel heading in historical and xianxia chapters | Guessed blind from 4 isolated characters in a TOC list, producing stiff literal words that miss who acts in the scene | Keep the heading on line 1 of the chapter source so AI translates it alongside the full chapter events underneath |
| Long trope-packed novel title: combining 白月光 (white moonlight), 追妻火葬场 (wife-chasing crematorium), 先婚后爱 (marry first, fall in love later), rebirth, or system | Word-for-word rendering turns genre shorthand into awkward literal phrases that hide the story premise | Use natural English web novel trope phrasing and keep the book title on line 1 of chapter 0 so the bookshelf displays Original title | Translated title |
When does the interface display a bilingual "Original | Translated" book title and clean up "index_split" chapter labels?
On the NovelVerba bookshelf, the display helper never guesses randomly from an opening paragraph. The system only infers a translated book title from the opening chapter (chapter 0) when all 4 positive evidence conditions are met: (1) the novel has at least 2 chapters; (2) the title of chapter 0 matches the project title; (3) the first non-empty line of chapter 0's source text is at most 60 characters long and matches the project title; and (4) that first line is not a chapter-number heading such as 第1章 or Chapter 1.
Only when all 4 conditions hold does the system take the translated line at that exact first-line position (capped at 160 characters) and pair it into Original title | Translated title on the interface. If your opening chapter jumps straight into narrative prose or starts with a line over 60 characters, the system keeps your project title as-is, never mistaking the first sentence of the story for the book title.
The same safeguard protects chapter headings on the reading list. A translated chapter title (up to 160 characters) is taken from the first line of the chapter's translation only when the first line of that chapter's source text matches the chapter title exactly. If a chapter begins directly with story prose without repeating the heading on line 1, the app never pulls the opening prose sentence up as a fake title. Meanwhile, Calibre-split EPUBs with raw technical chapter labels like index_split_000 and index_split_001 are automatically normalized to Chương 1, Chương 2 on the reading view.
How do chapter titles flow differently into TXT exports, newly built EPUBs, and format-preserving EPUB write-back?
When exporting plain text files (TXT, Markdown, SRT) or a newly built EPUB from TXT, the exporter separates the translated first line as the chapter heading (heading) and the remaining lines as the chapter body (body) whenever the first source line matched the chapter title, and rebuilds the new EPUB's toc.ncx table of contents from those translated headings. If the first line cannot be verified (or if the source text of completed chapters was already cleaned up after finishing the novel), the exporter assigns the target-language label Chapter N (or Chương N, Bab N, Capítulo N, ตอนที่ N), ensuring untranslated source headings never leak into a newly built book.
When your project started from an EPUB file and you export a format-preserving EPUB (write-back), the writer translates text nodes inside each chapter XHTML file (including h1 and h2 chapter headings on the chapter page), but does not overwrite the separate navigation table-of-contents files (toc.ncx or nav.xhtml) in order to preserve the original internal link structure. On your e-reader, every chapter page shows its translated heading and every TOC link jumps to the right chapter, while navigation menu labels on the device may remain in the source language.
Walk through the full EPUB translation and export steps in How to translate an EPUB novel into English and export a file you can read, compare e-reader screen layouts and export modes in Reading translated novels on an e-reader: choosing the right EPUB export, checking errors, and fitting your screen, and check your file's toc.ncx, nav.xhtml, and XHTML chapter links in the browser with EPUB Validator: Check EPUB Files Before Reading or Translating.
- Run your EPUB file through the browser-based EPUB Validator before uploading to verify that its spine, toc.ncx, and nav.xhtml links are clean.
- Keep the book title on line 1 of chapter 0 (at most 60 characters, matching the project title) and keep each chapter's heading on line 1 of its source text to enable Original | Translated book titles and translated chapter headings.
- Scan Names & terms across the first 5 to 10 chapters and lock the per-novel dictionary before translating batches so proper nouns in chapter headings match the chapter body 100%.
- Choose format-preserving EPUB write-back to keep original illustrations and TOC link structure, or choose TXT, Markdown, and newly built EPUB when you want toc.ncx rebuilt with translated headings or clean Chapter N labels.