Use caseWrite
Translate a book you need to read, without the terms drifting
A full translation in your folder, readable beside the original, where the same term is rendered the same way from the first page to the last — plus the glossary you approved, so you can defend any choice it made.
- You start with
- One long work you need to actually read — a technical book, a standard, a report, a monograph — as EPUB, PDF, Word or Markdown.
- Time
- An afternoon for the first chapter, then mostly unattended. An interrupted run resumes.
- Your part
- The brief, the glossary, and checking chapter one. Exactly one decision has to be made well, and it comes first.
What you'll end up with
- The whole work translated, aligned paragraph by paragraph with the original.
- One rendering per term, first page to last.
- A glossary you approved, and a Markdown file you can annotate, quote and link like anything else you own.
How to translate a whole book with consistent terminology, step by step
Recognise the scan first, if it is one.
YouA scanned PDF has no text to translate. Run recognition and check the per-page report — its quality is the ceiling for everything after, and a bad page becomes a confidently wrong sentence.
Start the translation and read the brief.
MindMaxBefore anything is translated, it works out what this document is — subject, register, audience — and proposes a glossary of the terms that will recur.
Fix the glossary now.
YouThe whole trick. One term corrected here propagates through three hundred pages; in chapter nine it means redoing eight. Renderings settled by translations already in your folder come forward automatically — accept or override them.
Let it run.
MindMaxEvery chapter is translated against that glossary. Sections failing the mechanical checks — dropped content, changed numbers, broken terms — get another pass before you see them. Progress is checkpointed, so closing the app resumes rather than restarts.
Read chapter one against the original.
YouSide by side, aligned. Judge it before committing to the rest of the book. If the register is wrong, the glossary or the brief is where you fix it.
Polish as you read.
You ask · MindMax answersAsk for a chapter to be tightened or its register adjusted; the change arrives as a tracked edit you accept or reject, not a silently replaced chapter.
Keep the result.
YouIt lands as Markdown next to the original, to annotate, quote and link from your notes.
Why it works here
A glossary that holds for the whole book
Terms are settled once, up front, and every chapter is translated against them — with earlier translations in your folder carried forward.
Whole-document translation →Checked and resumable
Dropped content, changed numbers and broken terms are caught mechanically and retried; a closed app picks up where it stopped.
How the run is checked →Read it beside the original
The translation is aligned paragraph by paragraph with the source, and polishing arrives as tracked edits in the editor.
Markdown editor →Also used here: Turning scanned PDFs into text · EPUB reader · Pricing: what a book-length job costs
Where it gets hard
- The glossary is doing the heavy lifting.
Skim it and you inherit its mistakes for three hundred pages. Twenty minutes here is the best-spent time in the whole workflow.
- A real book costs real money.
Translate one chapter, look at it, then commit.
- Poetry, wordplay and legal drafting are the wrong fit.
Terminology consistency is exactly the wrong instrument for text that depends on ambiguity.
- It cannot tell you the tone is off.
The checks catch dropped content and broken terms, not a sentence that is technically correct and wrong in feel. That judgement stays yours — which is why step 5 exists.
- Very long runs are worth watching once.
Check the first few chapters rather than discovering at the end that the register drifted.