Skip to content
Learn / Encyclopedia / Translation Studio
Continuity Encyclopedia · Term

Translation Studio

StoryHelm Term Translation Canon

Translation Studio is StoryHelm's entity-aware translation: it carries your manuscript into another language with character names and coined names from your Canon locked and other recurring terms tracked in a series glossary.

Part of: Translation (separate add-on, priced per book and language)  ·  Powered by: Claude  ·  Scope: Per-book, anchored to that book's Canon and your series glossary

What it does

A general translation tool renders each sentence on its own, which works until the sentence contains a word a dictionary has never seen: the name you invented for your protagonist, the city she rules, the order of knights she belongs to, the curse word her people use. A plain translator treats each of those the way it treats any other noun. It guesses, and it guesses differently every time it meets them.

Translation Studio is the part of StoryHelm that knows those words are yours. Before it renders a single line, it reads your Canon: the characters, places, factions, and items StoryHelm has already cataloged from your manuscript. Then it produces the translation with character names locked to one consistent form, the form you chose, every time they appear. Invented names that are not ordinary words or real places are locked the same way; other recurring terms are tracked in a glossary, and the finished translation is audited against it. Helen stays Helen in chapter two and chapter forty, and so does Eldermoor; if the Silver Vow comes out differently than an earlier book rendered it, the audit names the chapter.

It keeps three kinds of detail stable that ordinary translation lets drift:

  • Character names: Helen is Helen across the whole book, not Helene in one chapter and Elena in the next; her recorded aliases are locked too before the model sees the text.
  • Place names and invented terms: the harbor town, the name of a spell, a coin, a god, or a guild, locked when the name is coined rather than made of ordinary words or a real place name, otherwise tracked in a glossary that carries across your series, with a drift audit that checks each rendering against the one an earlier book used.
  • Series consistency: because each book's translation glossary is saved to the series, Book Four's German edition can carry the same glossary as Book One's.

You decide how each name should read

Some authors want a name left exactly as written. Others want it adapted so it reads naturally to a Spanish or Japanese reader. Translation Studio surfaces the choice instead of deciding silently: you can pin a name to its original form or give it a preferred rendering in the target language; that decision then holds for every appearance in the manuscript, whether the name belongs to a character, a place or a term. The Canon it reads from is the same one the Story Bible is built on, so the names it works from are the ones you can already review there.

A translation, not a rewrite of your story

Translation Studio carries your existing prose into another language. It does not draft the original, invent new scenes, or "improve" your sentences. It reads your manuscript and your Canon and produces a machine-translated edition in the target language with your names intact. The story stays yours; only the language changes.

A translated edition is machine generated, and it is marked as such: Anthropic watermarks the text Claude produces. The mark identifies Claude as the translator rather than the author, and says nothing about the original manuscript. Retailers that ask about AI content expect an AI translation to be declared.

An example

Here is the drift Translation Studio is built to prevent: an invented place name rendered three different ways by a translator that never learned it was a proper noun.

Casebook excerpt: "The town with three names"
General translator · the same town, three chapters
Chapter 2 calls it Puerto Sombra. Chapter 9 calls it Puerto de la Sombra. Chapter 24 drops back to the literal Shadowport. Three names, one harbor, and nothing in the file says they are the same place.
Translation Studio · anchored to your Canon
The harbor is entered in Canon once, as Shadowport, and you pin its Spanish rendering as Puerto Sombra. From then on, every mention of Shadowport comes out as Puerto Sombra, in chapter 2, chapter 9 and chapter 24 alike, instead of changing from one chapter to the next.
! Why the difference. The general translator has no memory of the harbor between sentences. Translation Studio reads the Canon first, matches the harbor to a known place, and uses your one chosen rendering wherever the harbor appears.

See the full walkthrough for translating an established series, with the name-pinning step and a chapter-by-chapter review. Open the translating-a-series guide →

Related terms

Translation Studio leans on the rest of StoryHelm's continuity vocabulary, starting with the Canon it reads from.

One name, every chapter, every language

Carry your series into a new language with every name you pin held to one form.

Pin Eldermoor, the Silver Vow, and every name you made up to one form, and watch it hold from chapter two to chapter forty. A foreign reader who meets your harbor town under three different spellings stops trusting the world before they finish book one. StoryHelm reads your manuscript and your Canon and names the chapter where a name's rendering drifts from an earlier book's. It never touches your source manuscript; the translated edition is machine generated from the book you wrote, scored for publishability, and delivered for your review before release.

Get the free Self-Audit
Free 12-check PDF with your welcome email · Founding seat included · It never writes your prose