← Back to Tool Tutorials

Translation & Post-Production

Darkling Palimpsest

What it does: Darkling Palimpsest is book translation software. It imports a manuscript, breaks it into chapters, translates chapter by chapter, preserves project context, tracks glossary terms, checks consistency, and exports the translated book.

Best used when: you want to create a translated edition while keeping names, invented terms, character relationships, tone, and formal/informal address consistent across the whole book.

Before You Begin

Do not start with Translate All on a brand-new project. Set up the language, story context, glossary, and address rules first. Translation quality depends heavily on what the tool knows before it starts.

Using Palimpsest in the Suite

  1. Open the Darkling Suite from the classroom link.
  2. Go to Translation & Post-Production and open Darkling Palimpsest.
  3. Choose the target language from the language menu.
  4. Choose the model and enter the matching API key.
  5. Click Import Manuscript.
  6. Open Story Context and fill in the book title, genre, synopsis, characters, relationships, and tone notes.
  7. Open Glossary and add important names, places, invented terms, series terms, and recurring phrases.
  8. Translate one chapter first, review it, then continue chapter by chapter or use Translate All.

The Suite version is best for larger translation projects because it includes target-language selection, project restore, validation, and book export options.

Using Palimpsest Standalone

  1. Open the standalone Palimpsest link provided in the classroom.
  2. Enter your API key and choose the model available in your version.
  3. Import the manuscript.
  4. Add story context before translating.
  5. Add glossary terms before translating major chapters.
  6. Translate one chapter, check the voice, then continue.
  7. Export the finished translation when all chapters have been reviewed.

The standalone version is best for individual translation jobs, smaller projects, or working outside the full Suite.

Supported Import Formats

  • Markdown / .md: useful for clean chapter files with headings.
  • Text / .txt: useful for plain manuscripts.
  • ePub: useful when translating a formatted ebook structure.

If the chapter list looks wrong after import, check the source file’s headings or structure before translating.

Target Languages

The current Suite version includes target-language options for Italian, Dutch, French, Brazilian Portuguese, and Polish.

Pick the target language before translating. The tool uses language-specific rules for grammar, idioms, formal address, paragraph breaks, and common AI translation errors.

Story Context

Story Context is where you tell the tool what kind of book it is translating. This context is included in translation prompts so the model does not have to guess.

  • Book Title: the title of the project.
  • Genre & Style: the shelf and tonal lane.
  • Synopsis: the core plot, setting, central conflict, and stakes.
  • Characters & Relationships: who matters, how they relate, and how they speak to each other.
  • Tone & Style Notes: POV, atmosphere, heat level, voice, register, and prose style.

Address Rules

The address/register section controls how characters speak to each other. This is especially important in languages where formality changes pronouns, verbs, or social tone.

  • Use Auto-Extract to detect relationship rules from the text.
  • Add manual rules for hierarchy, intimacy, enemies, family, teachers, royalty, employers, and formal relationships.
  • Check rules before translating dialogue-heavy chapters.

This is one of the places where Palimpsest earns its keep. A romance or fantasy translation can break fast if the register is wrong.

Glossary

The glossary keeps recurring terms consistent. Add terms before translation, then adjust as you learn what the target-language edition needs.

  • Names: characters, families, houses, schools, clans, ships, towns.
  • Invented Terms: magic systems, ranks, titles, species, artifacts, rituals.
  • Series Language: repeated phrases, slogans, branded terms, lore words.
  • Terms that should not translate: proper nouns, made-up words, or brand-specific vocabulary.

Use suggested terms if they are useful, but do not accept them blindly. Glossary choices become project rules.

Translation Controls

  • Translate Chapter: translates the selected chapter only.
  • Translate All: translates untranslated content chapters in order.
  • Autosave: saves progress as you work.
  • Word Counts: show source and target word counts for the selected chapter.
  • Projects: lets you reopen saved translation projects.

For a new book, translate and inspect the first chapter before batch translating the rest.

Validation

Validation checks translated chapters for consistency problems and likely translation errors.

  • Validate current chapter after translation to catch issues early.
  • Validate All after a batch to check the whole book.
  • Apply Fix when the suggested correction is correct.
  • Review manually when a suggestion affects voice, meaning, or character register.

Validation is a safety pass. It is not a substitute for a native-speaker review before publication.

Find & Replace

Use Find & Replace when you discover a recurring term needs to change across the translated book.

  • Fix a glossary decision after translating several chapters.
  • Standardize a name or title.
  • Repair a repeated mistranslation.

Use carefully. Replacing a common word across an entire book can create new problems if the word appears in multiple contexts.

Backup, Restore & Storage

  • Projects: stores translated progress locally by project.
  • Restore: restores a saved Palimpsest backup file.
  • Storage Warning: tells you when local browser storage is getting full.
  • Clear Storage: backs up and clears project storage when needed.

For long books, export or back up regularly. Translation projects can get large.

Export Options

  • Markdown (.md): best for clean text handoff or editing.
  • Word (.docx): best for proofing, line review, and editor/native-speaker handoff.
  • ePub (.epub): available when the original import was an ePub and the source file is available for export.

Export after saving the current chapter. Then proof the exported file before formatting or publishing.

Recommended Workflow

  1. Choose target language and model.
  2. Import the manuscript.
  3. Fill Story Context.
  4. Add glossary terms.
  5. Add address/register rules.
  6. Translate Chapter 1 only.
  7. Review the voice and register.
  8. Translate in batches.
  9. Validate all chapters.
  10. Export to Word for human review.

Common Fixes

  • Names keep changing: add them to the glossary.
  • Dialogue sounds too modern or too formal: update Story Context and address rules.
  • Invented terms are being translated literally: add them to the glossary as protected terms.
  • Chapters feel inconsistent: validate, then use Find & Replace for approved repeated fixes.
  • The export is missing ePub: re-import the original ePub source before exporting.
  • Storage warning appears: create a backup before translating more chapters.

Best Pairings

  • Series Bible Builder: use the canon names, terms, and lore to build a stronger glossary.
  • Ruthless Editor: use after translation only if you are editing translated prose intentionally.
  • EdgeWeaver: use after the translated edition is proofed and formatted if you need print-edge or interior-graphic assets.

Suggested next tool: EdgeWeaver