Translate a book without losing the voice

The literary translator’s workflow

Books are where generic translation tools fail most visibly — by page 30 the protagonist has three names, the dialogue voice has flattened, and the recurring metaphor has shifted. This workflow is built to hold all of that.

1. I.

   Import the chapter

   Upload DOCX or paste the chapter. Or pull from Scrivener’s Markdown export. The chapter becomes editable blocks with the original structure intact.

2. II.

   Build the character glossary

   Add character names, place names, recurring objects, invented words. Pin each to a target-language rendering. The glossary travels with every chapter — page 1 to page 500.

3. III.

   Build the styleguide from a sample

   Paste in the opening pages translated by hand, or by an editor you trust. Transept reads them and proposes a styleguide — sentence rhythm, register, dialogue tone — that captures the voice. Refine, save, reuse across chapters.

4. IV.

   Translate, with alternatives where dialogue lives

   Premium mode for the prose. For dialogue, walk through the alternatives view — three to five renderings per line, picking the one that sounds like the character.

5. V.

   Polish for literary rhythm

   A polish pass smoothes the rhythm without touching the choices you made. Read it through. Make the last manual edits.

6. VI.

   Export to DOCX or Markdown

   For your editor, your typesetter, or your KDP upload. Formatting intact, footnotes preserved, chapter breaks where they belong.

Why books are different

Questions, answered without the fluff

• Can it handle a full novel?+
  Yes — chapter by chapter, or batched. A 90,000-word novel in Premium mode runs about 270K credits — comfortably inside a few months of the Starter plan, or a top-up pack.
• How does it handle dialogue tags and stage directions?+
  Dialogue tags ("she said", "he murmured") translate naturally. Stage directions and beats stay as prose. The styleguide can include rules for how to handle each.
• What about translator notes?+
  Add them as comments on the translated sentence. They stay in the workspace; they don’t show up in the exported manuscript.
• Can I co-translate with another person?+
  Yes — team review supports two translators on the same document with sentence-level locking. Or use client review links for a beta reader’s pass.
• Is this used for serious literary translation?+
  Yes — indie authors translating their own books, small literary publishers translating acquisitions, and freelance literary translators using AI as the first-draft layer. The output is meant to be reviewed and refined by a human, not shipped as-is — but it cuts the first-draft time by 70–80%.
• Can it preserve verse, rhyme, or rhythm?+
  Partial. For prose with rhythm and rhetorical figures, Premium mode plus a careful styleguide usually preserves the feel. For metered verse and tight rhyme schemes, AI translation is currently a starting point — significant human craft is still required.
• What about translating from a less-common source language?+
  Transept supports any language Claude, Gemini, GPT, or Groq handle. For minor European languages and many Asian languages, quality is strong. For very rare or extinct languages, the major models are limited and human translation remains the better path.
• How do I handle translator’s notes?+
  Add them as comments on the translated sentence (visible only in the workspace) or as footnotes that export with the document (visible to the reader). Both are supported.
• Can I co-translate a book with another person?+
  Yes — team review supports two translators on the same manuscript with sentence-level locking, real-time presence, and shared glossary/styleguide. Common pattern: one translator does the first pass, one does the literary review.

Keep reading around this workflow

• FeatureA styleguide that steers every regeneration→Tone, register, rules, formatting conventions. Build a styleguide manually or have Transept generate one from a sample page of finished…
• FeatureA glossary the AI actually follows→Character names, product terms, branded phrases, client-specific vocabulary. Build a glossary once — manually, by upload, or seeded from a…
• FeatureSentence-level alternatives→Translation isn’t one right answer. Every sentence has three or five reasonable choices, and the best one depends on the page around it.…
• FeaturePublish-Ready Mode in one run→The whole workflow, one button. Translate. Enforce the glossary. Apply the styleguide. Proofread for drift. Polish for readability. Run QA.…
• Use caseTranslate the next post without losing your voice→Long-form content lives or dies on voice. Run your post through Transept with a styleguide built from your own writing, choose from…