(Continued from earlier post)
4. Create a table of contents, again.
Wait, didn’t we already do that? Yes, but that was a HUMAN table of contents. We made it “by hand” and it both looks good and works well. However, most E-readers won’t specifically recognize that ToC as a ToC. So now, we need to make what’s called a “logical” ToC.
Aesthetic disclaimer: This technique kind of sucks. It comes into play because there are three (3!) different kinds of Tables of Contents for E-books.
- Traditional Table of Contents: The thing you think we’re talking about? That’s what we’re talking about. This is a list of sections, or chapters, or poem titles, typed up by a human and positioned in the first few pages of a book (let’s not argue, now) so that people browsing the book can find out where to go.
- A Logical or Metadata Table of Contents: This is a list in outline format that lists the contents of your book by header <hx> elements. It usually is not styled, typed, or formatted so much as it is generated by an E-book editor. This list is where people will go when they click on the “Table of Contents” button or menu option in their E-reader. It should go at the end of your E-book so it doesn’t clog up your frontmatter (which already has a ToC).
- An NCX file. The NCX file is a series of bookmarks or milestones (EPUB 2.1 and Kindle .mobi) in an E-book that helps some readers on some devices jump around inside the book. For example, a proper NCX file will allow a reader to jump around in the E-book in exact, one-chapter increments. The NCX file is created automatically by an E-book editor.
Fortunately, our E-book editor Sigil will handle most of this for us. Continue reading
Use Sigil to assemble the files for the E-book anthology.
Our files are back together like peas in a pod.
You can, if you wish, use a text editor and a compression utility to make the EPUB .zip file. You can, that is; I sure can’t. And I see no clear reason why anyone would want to, not when Sigil is back in active development.
As Sigil is (kind of) an HTML editor, I could have used it all along for making the HTML/CSS markup in Steps 3 and 4. That wouldn’t have been a particularly awesome idea, though. As of this writing, Sigil hasn’t fully transitioned to HTML5. I feel it’s better to code in an HTML5 setting such as Dreamweaver, then step backwards a little bit closer to the end, rather than to do a whole project soup-to-nuts in an older specification and have more to re-code if you ever update the book to modern standards.
The first move is to download and install Sigil. If you need an older/more compatible version, those are still available, too, although they have been deprecated. I’ll wait…got it up and running? Great! Here’s what we’ll do next:
- Dump our files into a new Sigil document.
- Put the files in the proper order.
- Input some metadata (I’ll explain).
- Create a table of contents, again.
- Validate the files with FlightCrew.
- Rinse and repeat.
This post will cover 1-3. It’ll be fun. Ready? Continue reading
Sigil’s Icon for OS X
Editing EPUBs in the Post-Post-Sigil World?
I wrote the first drafts of these tutorials in April and May 2014, and I’ve been dribbling them out ever since. But almost since the day I started, there has been an uncomfortable reckoning on the horizon: Step 5 of my workflow uses Sigil, an open-source HTML/EPUB editor that ceased development right as The Yellow Buick Review project got underway.
Computers, E-books, the Web, life in general—we understand these things to be dynamic and shifting. Anyone reading this blog in 2022 (hi!) will find outdated information. The best I can do is offer honest advice in good faith. But when Sigil went quiet in Spring 2014, I felt as if I were leading people down a path I knew to be a dead end. It was hard to be enthusiastic about documenting Step 5:
5. Place the HTML and CSS files into an EPUB. We’ve been using Sigil, a free, open-source EPUB editor. Sigil wrangles together our HTML/CSS files, plus any images or media files we’ll be using. Sigil also helps us make a Table of Contents…
But I got excited this week reading this post over on the development blog of Sigil:
Now that all changed about a month ago when Kevin Hendricks decided to invest his time in some bug fixes. Then he decided to start working on a plugin framework for Sigil. He’s been spearheading the effort to get this feature implemented. It’s not ready yet but it’s coming a long (sic) nicely.
Everything Bicycle Comics has learned about formatting poetry anthologies for Kindle and Kobo.
From MS Word to Kindle in six steps!
There it is. Depending on where you are in your publishing journey, that workflow looks beautifully simple or laughably Byzantine. Don’t worry; I’ll walk you through each of these steps in future blog posts. But big-picture, here is how we move an anthology from manuscript into Kindle and Kobo.
- Paste and proofread all the poems as plain text. We remove nearly all formatting from the poems. The document should look like (or actually be) a text file. Here we can check spelling and discuss proofreading/editorial changes with poets via E-mail. The entire interior of the book is in one whopping-huge Word document.
- Lightly format the book in Microsoft Word. We add basic structure to the book. If it can’t be done via the Style menu, then we probably won’t do it. We try to have all of our content debates now, because after this step, our book “forks” into two paths: one set of files goes to InDesign for our paperback edition, and one set of files goes to Dreamweaver for our E-book. If we make a change now, we make it one time. If we make a change later, we’ll need to make it twice.
- Save the document as HTML + CSS. We tell MS Word to export our document as HTML, and then we use Adobe Dreamweaver to tidy up the resulting code. We also pull all styling of the document into an external style sheet. If you’re coming from a traditional publishing background (QuarkXPress, InDesign, PageMaker), this step will seem the most foreign and tedious. I’ll talk you through it!
- Separate the HTML into chapters. We split our one huge interior HTML file into several smaller HTML files. For the most part, we split at chapters; each month of our Tandem anthologies is one chapter. Our table of contents, foreword, and contributor biographies become additional “chapters.” For the most part, we try to have all our chapters use the same, external cascading style sheet, but we’re open to adding one or two mini .css files if we really need them.
- Place the HTML and CSS files into an EPUB. We’ve been using Sigil, a free, open-source EPUB editor. Sigil wrangles together our HTML/CSS files, plus any images or media files we’ll be using. Sigil also helps us make a Table of Contents. Once we’re happy with our Sigil EPUB, we’re ready to publish on Kobo, Nook, and Google Play Books!
- Create a MOBI and/or KF8 book with Amazon Kindle Previewer. We use the free Kindle Previewer program to translate our EPUB into Amazon’s specialized Kindle format(s).
On a tight budget? Bicycle Comics uses both commercial and free software to make our poetry E-books. In subsequent posts, I’ll offer advice on how to work through each step using low-cost substitutes for some of the expensive programs.