Skip to main content

How good is AI novel translation, and what still needs a quick check?

Tri Thu知秋

On this page

When translating a long novel with AI on NovelVerba, roughly 80 to 90% of the narrative flow and recurring terminology is held in frame by genre packs and two automated checks: the Needs review badge for 4 surface script issues and the free Check by line tool for entries in Names & terms. Because automated checks inspect surface characters rather than scene meaning, a chapter with zero warnings can still hide 4 semantic blind spots that I spot-check in Bilingual view.

On a mountain-peak library observatory pavilion at warm golden sunset, a scholar in bronze-brown and celadon-jade robes stands beside a dark-wood table where an antique round bronze mirror on a stand casts a warm golden beam across an open cream manuscript scroll, revealing glowing celadon-jade crystal nodes as the scholar's hand holds a bamboo calligraphy brush dipped in cinnabar-red ink touching one glowing node.
Two automated checks guard surface script and locked names, while human eyes check four semantic blind spots in pivotal scenes.
Issue category in a translated chapterCaught by the app or checked by my own eyesHow I verify and handle it
4 surface signs: empty translated line when source has text, leftover Chinese/Japanese/Korean script, long Vietnamese line missing tone marks, long Thai line missing Thai scriptThe app attaches the Needs review badge next to the chapter in the Chapters tab and highlights the specific passageScroll the Chapters tab to open the Needs review chapter; each highlighted passage shows Fix this passage or Accept this translation (clears that passage only)
Drift on a character name or term already in the Names & terms tableClick Check by line in the Names & terms tab for a free read-only comparison (zero AI calls)Click the Fix line link in the report to jump straight to that line in the reader and retranslate the drifted passage
Blind spot 1: Fluent, complete sentences that drop a negation word (not, never) or swap who struck the blow and who took the woundNot flagged by Needs review because the sentence is complete and has no leftover source script; requires human eyesTurn on Bilingual view during key fight scenes and plot twists; since clean lines have no Fix this passage button, use Retranslate this chapter at the top of the chapter
Blind spot 2: Character names match the table, but pronouns shift across scenes or sarcastic honorifics get flattened into polite speechCheck by line reports clean as long as the character name appears; requires human ear for dialogue registerAdd character notes during Scan names & terms or in My dictionary, pin dialogue samples via Add pair in the Style tab (first 8 pairs used), then click Retranslate this chapter
Blind spot 3: Context-dependent polysemous words in a genre pack applied to an everyday literal scene (such as 夺舍 -> body possession, 出绿 -> showing green, or 潜规则 -> hidden rules)Not flagged because the source characters match the dictionary entry; requires human eyes when a literal scene sounds oddEdit the entry's translation in Names & terms or add a rule in My dictionary, then click Retranslate this chapter
Blind spot 4: Chapters where source and translation line counts do not matchCheck by line skips the misaligned chapters and only reports the total count of skipped chapters without naming which onesOpen suspected chapters in Bilingual view to inspect the opening and closing paragraphs, then click Retranslate this chapter if paragraphs merged or dropped

The first time I ran a batch of several dozen chapters and saw the chapter list finish clean with zero warning badges, I assumed every line was ready and opened straight to a climax chapter. Halfway through the duel, I froze: the English sentence read smoothly, but it had dropped the word "not", turning the protagonist from someone refusing to betray his sect into a traitor, and two lines later a master and disciple in a life-or-death standoff started talking like polite coworkers.

To see why a sentence with zero technical warnings can still flatten a dramatic scene, look at this Chinese line I put together as an illustration (an original example built for comparison, not quoted from any specific work):

沈师兄看着跪在殿外的昔日挚友,冷声道:“从今日起,你我恩断义绝,再见便是死敌!”

If a translation reads: "Senior Brother Shen looked at his old friend kneeling outside the hall and said coldly: Starting today, you and I are breaking up our friendship, and next time we meet we'll be enemies!", the line is non-empty, leaves zero Chinese characters behind, and contains the locked title Senior Brother Shen, so neither automated check raises a flag. Yet turning a solemn martial-sect severance oath into casual modern talk ruins the tension compared to: "From this day forth, all ties of grace and brotherhood between us are severed; when next we meet, we meet as mortal enemies!". Before spending credits on a multi-hundred-chapter novel, knowing what the app catches on its own and which 4 places still need my own eyes keeps me from both blind trust and exhausting line-by-line proofreading.

What do the Needs review badge and Check by line catch automatically?

In NovelVerba, mechanical checking is handled by two automated gatekeepers. The first is the Needs review badge: when I open the Chapters tab, there is no separate filter for flagged chapters, so I scroll the chapter list to spot the Needs review badge next to a chapter title and click to open it (or use the Auto-fix flagged lines · N chapters button on the batch progress bar). The Needs review badge triggers on exactly 4 surface signs: (1) an empty translated line when the source line has text, (2) leftover Chinese, Japanese, or Korean characters in a target language that does not use those scripts, (3) a long Vietnamese sentence stripped of all tone marks, and (4) a long Thai sentence with no Thai script.

When I open a chapter with Needs review inside the reader, only the individual passages highlighted with a warning display the inline buttons Fix this passage and Accept this translation. Clicking Accept this translation on a highlighted passage only clears the warning for that specific passage (useful when the author intentionally included a foreign quote), and it does not sit in the top chapter banner or clear the badge for the whole chapter. For the full walkthrough on handling highlighted passages, see How to find untranslated or odd lines in a translated novel.

The second gatekeeper lives in the Names & terms tab under Check the name table against translated lines, triggered by the Check by line button. For every entry already in the table, Check by line compares each source line containing that source term against the matching translated line, completely free (read-only, zero AI calls). Any line missing the standard rendering is listed with a Fix line link that jumps straight to that line inside the reader. To see where this check fits into the complete five-step workflow for a long book, read How to translate a whole web novel with AI: a 5-step workflow.

Which four blind spots in a chapter still need your own eyes?

The first blind spot is a smooth, grammatically complete sentence that drops a negation word or inverts who performed an action. In fast-paced combat scenes where Chinese, Japanese, or Korean originals frequently omit the subject, a translated line can be completely free of foreign script so Needs review stays silent, yet dropping a single "never" or swapping who swung the sword and who took the wound flips the plot upside down.

The second blind spot happens when character names match your table so Check by line reports zero drift, yet pronouns shift across scene cuts or biting, sarcastic honorifics get flattened into polite dialogue. Because Check by line only verifies whether the locked name string is present on that line, it will not warn you when a master and disciple suddenly sound like casual acquaintances. To lock down speaker hierarchy before translating, I set up two-way relationship notes following Choose address terms by character relationship when translating Chinese novels.

The third blind spot involves polysemous words in genre packs that appear in everyday literal scenes. Dictionary matching checks whether the source word appears in the text, not whether the author meant the genre mechanic or a literal description. In the built-in packs, for example, 夺舍 is mapped to body possession, 出绿 to showing green (when cutting raw jadeite in stone-gambling scenes), and 潜规则 to hidden rules (in entertainment-industry scandals). If a quiet countryside scene uses 出绿 simply to describe spring branches turning green, the automated checker sees no error; only a human reader notices the mismatch.

The fourth blind spot is a chapter where the source line count and translation line count do not match. If a paragraph merges or drops during translation, Check by line cannot align lines one-to-one and skips that chapter. Keep in mind that the warning message only states the total number of skipped chapters (for instance, reporting that 2 chapters have mismatched line counts) without listing which specific chapters they are, so I open suspected chapters in Bilingual view to check.

How do I check these four spots and fix unflagged lines?

I never proofread all 500 chapters line by line. Instead, I turn on Bilingual view for the first 2 or 3 chapters of a novel to verify narrator voice and dialogue cadence, and I glance at pivotal confrontations in later batches. After each batch finishes, I also run Check by line once: if any locked name drifted, clicking the Fix line link jumps me straight to that line in the reader. For the complete workflow on finding and retranslating passages that still use old names or terms, see Changed a name or a term: how to retranslate passages that still use the old wording.

When I spot an inverted meaning, a polysemous word trap, or flat dialogue on a sentence that has no surface script error, that line is unflagged, which means it has no warning highlight and no Fix this passage button in the reader. To fix it, I update my guidance first: the novel's Names & terms tab only lets you edit the translation or delete existing entries (it has no note input field and no button to add new entries), so I enter character notes while reviewing Scan names & terms results or add the term with a note into My dictionary on the Shared dictionary page. To sharpen dialogue cadence, I open the Style tab and click Add pair (the system includes at most the first 8 pairs, with pinned pairs ordered first), then return to the chapter and click Retranslate this chapter.

One data-lifecycle rule is worth remembering: once a novel is completely finished or after 30 days of inactivity with no translating or editing, the chapter's source text is deleted under the data policy, so Check by line and Retranslate this chapter can no longer run. Once my spot-check on the opening chapters looks solid, I translate the batch and export the book following How to translate an EPUB novel into English and export a file you can read.

Upload your novel file and test the opening chapters on NovelVerba