Publishing Technical Documents with ePub

Prerelease Version

Introduction

Perhaps, this book should be titled Everything You Wanted to Know About ePubs (But Were Too Afraid to Ask).

My original intent was to write a small bundle of articles about the format to help users who need to publish technical ePub documents. Creating this kind of document can be a chore as most existing software solutions cater to trade publishers first, educational publishers second, and academic or technical publishers last, if at all.

As I’ve delved into the topic, my goal has expanded a little. To begin with, I’ve included more details about the internals of the ePub format. I believe this background is necessary to help you understand the tradeoffs that developers make when designing ePub-related software. This understanding should help you if you need to craft your own software solutions (and you likely will).

This book will also show you what you need to do to create complex ePub documents using nothing but a text editor and some command line tools. While this is not an efficient workflow for most users, it will allow you to thoroughly understand what makes this technology work and to fix problems that may crop up when using other tools. More importantly, it will give you a foundation to create your own tools that can be tailored to fit your needs.

Finally, this book will discuss existing ePub software solutions and offer suggestions on different tools and approaches to help you make better use of this technology.

This book is intended for people who are already familiar with XML, HTML and CSS, but may not know how all of these technologies work together to create an ePub document. Readers who are not familiar with the underlying technologies may feel lost in places. I’ve tried to include links and references to the relevant documentation, but remember The Internet is your Friend here.

Important Resources

All of these technologies have standards documents out on the web. These documents are carefully crafted and their goal is to reduce areas of ambiguity as much as possible. This (perversely) tends to make the documentation difficult to follow on an initial reading.

 

Next

Table of Contents