Translation is where a series quietly fractures. The invented capital you named in book one gets rendered three different ways across three volumes, the honorific that carried a character's deference gets flattened to a plain name, and a coined term for your magic drifts from book to book. The fix is the same one that holds the original together: a single entity canon of names, places, and invented terms, agreed once and applied to every volume, so the translator works from a glossary instead of guessing each time.
A single novel can be translated by one person in one pass, and the invented words inside it stay consistent because they live in one translator's head for the few months of the job. A series breaks that arrangement. Books come out years apart, the translator who did book one may not be available for book four, and even the same translator does not remember exactly how they handled a coined term three volumes ago. The result is drift: the same invented place, person, or term rendered slightly differently each time, in a language the author often cannot read to check.
The author is the one person who knows the original is consistent and the one person least able to verify the translation is. You wrote the same spelling of the kingdom's name in all four English books, but you have no way to confirm the German edition did the same, because you do not read German. The series fractures precisely where you cannot watch, and a reader who bought every volume in that edition can see it when you cannot. The defense is not to read the translation. It is to hand the translator a fixed list of how every name, place, and invented term should be rendered, agreed once and reused for every volume.
The damage in a translated series is rarely a mistranslated sentence. It is the small, repeated elements that recur across hundreds of pages and have to match every time, and they go wrong at the boundary between volumes, the one place a single-pass proofreader of book three would never think to look. Four categories cause most of the trouble.
The names you made up have no dictionary entry, so the translator has to decide whether to transliterate, adapt, or keep them in the original script. Whatever the decision, it has to be the same in every book. A coined capital can be transliterated in one volume and left untouched in the next, and a reader who bought all four notices immediately. Invented names need a fixed rendering, recorded once.
Many languages carry social distance in the words for "you" and in the titles characters use for each other. When a character who always addresses the queen with the formal form suddenly uses the familiar one, that is a character change the author never wrote. These choices encode relationships, so they need a stated rule per character pair, not a fresh decision each scene.
The word you invented for a kind of magic, a faction, a currency, or a creature is part of the world's texture. If it is translated as one thing in book one and a near-synonym in book three, the world loses the solidity that repetition built. Coined terms belong in the glossary with their agreed equivalent, flagged as fixed.
Translation can reintroduce continuity errors that the original did not have. A translator who renders a number, a color, or a relationship loosely can contradict a fact the author set carefully. The eye color, the count of siblings, the order of events: these survive translation only if the translator knows what the canon says they are.
The work that protects the original series also protects every translation of it. The entity canon you already keep becomes the brief you hand the translator. Three steps turn it into a translation glossary.
Pull the proper nouns and coined words out of the manuscript into one list, with the source spelling and a short note on what each one is (a city, a faction, a kind of magic). This is the same canon that holds the original consistent, read here as a checklist of everything that must be rendered the same way every time. A name that never makes the list is a name the translator will improvise.
For each entry, agree how it should appear in the target language: transliterated, adapted, or kept in the original, plus any rule for honorifics tied to it. Do this with the translator, who knows what reads naturally in their language, and write the decision down. The point is that the choice is made deliberately and recorded, not remade from scratch in book four.
Carry the same glossary into each book, including any new entities a later volume introduces, and check the finished translation against it. When the German edition of book three renders the capital differently from books one and two, that is a finding, the same kind of cross-book diff you would run on the original. Fix it in the translation, update nothing in the canon, and re-check.
Drift in a translation looks exactly like drift in an original: two lines that are each fine alone but conflict when set side by side across volumes. Here a single invented place name has been rendered two ways:
Book 1, Ch. 2: The road climbed for three days before the towers of Ravenhold broke the horizon.
Book 3, Ch. 7: She had not seen Rabenhalt since the siege, and the walls looked smaller now.
A reader of the original would never see this, because the author spelled the name the same way every time. It appears only in translation, only across two volumes, and only if no one is checking the later book against a fixed rendering of the name. A glossary catches it before the reader does.
StoryHelm reads and analyzes your series and builds your Canon: the single source of truth for characters, places, factions, items, and events. Translation Studio is an entity-aware translation add-on that works from that canon, so once you and your translator agree how Ravenhold should read, that rendering is what every volume gets, instead of being re-decided book by book. You still own the prose; the author writes the story, and StoryHelm only keeps the entity list steady underneath it. For how the underlying continuity check works, see what an AI continuity check actually does.
An entity canon solves the consistency problem, the part where the same name or term should match across every volume. It does not make a translation good. Whether a joke still lands, whether a threat still chills, whether a formal register reads as stiff or as dignified: those are judgment calls a glossary cannot make, and a skilled human has to read the result to make them. Translation Studio handles the mechanical consistency that machines are well suited to and the entity awareness that a canon makes possible. It does not pretend to be a literary translator, which is why it is sold as a separate add-on.
So the division of labor is clean: the canon guarantees the queen is always addressed the way you intended, while the translator, with you, decides what reads beautifully in their language.
No. It is built to work alongside one, not instead of one, and it is a separate add-on. The glossary it enforces is only as good as the renderings your translator agreed to in the first place; the tool holds those choices steady across volumes, it does not invent them.
Yes. Import the finished books, let the canon build from the earliest volume, and you have a ready glossary of every name, place, and invented term to hand a translator. This is the same starting point as a backlist audit before a box set: one canon, applied across the whole series.
No. StoryHelm reads and analyzes; it never drafts your prose. Its job here is to hold the entity canon and flag where a finished translation drifts from it, so the wording choices stay entirely yours and your translator's. The author writes the story; StoryHelm makes sure it holds together.
Where translation, box sets, and a backlist strategy fit in the wider business of publishing a series.
ReadRun one canon across a finished series before you relaunch it, the same groundwork a translation needs.
ReadHand your translator one fixed glossary of every name, place, and invented term, then diff each finished edition against it. StoryHelm reads your series, builds the canon, and points to the exact book and chapter where a rendering drifts, in the language you cannot read to check. Catch it before the reader who bought all six volumes spots it for you.
Request a founding seat