For decades, writers have been asked to finish the difficult part in one program and then watch their work become generic material in another. The manuscript arrives at the layout desk; the layout software sees frames, styles, margins and pages. It does not see a stanza crossing the wrong boundary, a line ending that carries the weight of a poem, or a repeated sound that should remain audible on the page.
That blindness is not a moral failure. InDesign was built to solve an enormous range of visual problems. The problem is that a book of poems is usually treated as a small, awkward brochure inside that range.
Fabylon Bookmaker starts from the opposite assumption: the software should first learn what kind of writing it is setting. It scans metre in Dutch, English, German, French and Spanish; maps rhyme, alliteration and assonance; keeps stanza structures intact; and gives the author typographic warnings without pretending that a warning outranks a poetic decision.
Underneath that literary layer is a real compositor's workshop. Paragraphs are broken as wholes, not line by line. Hanging punctuation, optical margins, ligatures and rivers in justified prose are handled by instruments whose results remain visible and overruleable. A finished project can produce a print PDF, an EPUB, an editable .fab and a KDP-ready Word file from the same typeset pass, so the editions do not quietly diverge.
The most radical feature may be the least technical one: Bookmaker is free. The deterministic tools run locally, and the manuscript does not leave the machine unless its author explicitly sends something. Windows opens first at the end of August 2026; macOS and Linux follow.
This is not an argument that every poet must become a professional book designer. It is an argument that the author should be allowed to see the workshop, keep the source, and decide where help is actually useful.
See how Fabylon Bookmaker reads and sets a manuscript
