The opening piece in a Gurugo Labs field series on multilingual publishing — the craft of turning a manuscript into a real book.
About this series. These are field notes from a Gurugo Labs consulting engagement: producing a traditional trilingual (Sanskrit · Tamil · English) devotional book for a client, from a raw manuscript through to print-ready and digital editions. The work paired software engineering — custom text-conversion tooling, a Unicode normalization and QA pipeline, and professional typesetting — with traditional scholarship, including a Sanskrit scholar engaged to verify readings and pitch accents. The client is anonymized, but the problems were real; each article generalizes one of them — what we saw, why it happens, and how we solved it — so any team doing similar work can follow the same path.
The assumption almost every project starts with
When a client brings us a text to publish, it tends to arrive the same way: a scholarly work, a liturgical collection, a family's devotional compilation, already typed up in a word processor. It looks fine on screen. Hit Print or Export to PDF, and — surely — that's a book?
It isn't, quite. And the gap between "a document that looks fine" and "a published book" is where every surprise, every cost, and every late night lives. This article is about that gap, so nothing in it catches you off guard.
A document is content. A book is content, deliberately presented and produced.
Here's the single most useful idea to hold onto:
A Word document is your content in a default presentation. A book is your content in a chosen presentation, produced for a specific way of being read.
When you type in Word, the software makes a hundred silent decisions for you — the font, the margins, the line spacing, where pages break, how images sit. That's fine for a letter or a report. A book is different: those decisions are the craft, and leaving them on autopilot is exactly what makes a home-made book look home-made. Publishing is the act of taking those decisions back on purpose.
Publishing is a chain of distinct crafts — not one step
"Writing a book" is really several different jobs, often owned by different specialists (and, on a lean engagement, carried by one small team):
- Writing / compiling — producing the actual words. This is the manuscript. It's what most people mean by "the book," and it's genuinely only the first link.
- Editing — correcting, verifying, and deciding what's right. For a scholarly or sacred text this includes which reading is authoritative — often a job for an expert, not the compiler.
- Typesetting & layout — arranging the words and images on pages: choosing fonts, sizes, spacing, margins, headers, a table of contents, how facing pages relate. This is where a document becomes a book to the eye. It's usually done in dedicated layout software, not a word processor, because the control a word processor gives you isn't enough.
- Design — the cover, the visual identity, the ornaments and illustrations. The cover is its own small world of technical rules (bleed, colour for print, spine width).
- Production — turning the finished layout into a deliverable: a print-ready file for a printer, and/or an ebook. Print and digital are two separate productions with different rules, not one file that serves both.
- Distribution — getting it into hands: a printer and shops, an ebook store, or — as with many devotional works — given away freely.
Each link has its own vocabulary, its own tools, and its own pitfalls. A document skips all of them by default. A book earns each one.
Why the gap matters: the surprises live at the boundaries
Almost every hard problem in book-making appears precisely when you cross from "document" to "book":
- The moment you care about fonts, you discover that one font can't draw every script, that fonts can render marks as mysterious circles, and that you can't always legally embed a font you own.
- The moment you care about layout, you meet facing pages, master templates, running headers, and the fact that inserting one page can shift every page after it.
- The moment you make a cover, you meet bleed, print colour that looks nothing like your screen, and files that balloon to enormous sizes.
- The moment you make an ebook, you discover there are several kinds, that they trade your design for adaptability, and that the "right" one depends on what device your readers use.
None of these exist in a Word document. All of them are unavoidable in a book. That's not a warning to scare you off — it's a map, so each one is a small task instead of a nasty surprise.
Content vs. presentation: the mental shift that unlocks everything
If you take one habit from this article, take this: keep your content and its presentation separate in your mind.
- The content is the words and images and their meaning — the thing that must be correct.
- The presentation is how they look and behave on a page or screen — the thing that must be deliberate.
The same content can wear many presentations: a print layout, a fixed digital page, a reflowing ebook that adapts to any screen. When you understand that these are different productions of the same content, decisions get simpler. You stop asking "how do I turn my Word file into a book?" (there's no one answer) and start asking "which presentation am I making right now, and for whom?"
A special word for multi-script and traditional texts
If your book is in more than one script — Sanskrit, Tamil, Arabic, and English together, say — or carries something precise like Vedic pitch accents, add a few more links to the chain:
- Getting the text into modern, portable form (often rescuing it from an old font that only worked on one computer).
- Handling each script's fonts and special marks correctly, so nothing renders as boxes or circles.
- Adding faithful transliteration so readers of one script can read another.
- Verifying readings with a scholar, because a "correction" can accidentally change a sacred text.
These are real, learnable steps — and they're the subject of the rest of this series. They're also the reason a devotional or scholarly book is more than a document by an even wider margin than usual.
So, where does that leave you?
You don't need to become a professional publisher. You do need to know that publishing is a chain of deliberate choices, not a single Export button — and to meet each link with eyes open. The rest of these articles walk that chain one problem at a time: what you'll see, why it happens, and exactly how to fix it.
A Word document is a fine place to start. It's just not a book yet. The distance between them is entirely crossable — this series is the bridge.