Falling back to the famous opening line from Shoot and The Mist (which King admits he stole from Shoot), this is what happened:
Last night was Formatting Night at the casa, and it was time to play with the Table of Contents. Almost every ebook needs one, particularly if you’re hawking a novel, and you want your readers to jump to chapters quickly. I’ve done this for Kuntilanak, and I started playing with it for Her Demonic Majesty.
I discovered quickly, however, that while you can set up a text file in Scrivener for you ToC, you can’t link to things as you would in Word. That functionality simply doesn’t exist. But wait! After doing some research using this strange tool that a lot of writers seem to be unaware of called “Google”, I was reminded of something Scrivener does, and that’s compile your documents into epub and mobi formats.
For the less and tech savvy out there, epub is a common ebook standard that’s been around a few years. The other format, mobi, has been around even longer, and is what’s used by Kindle. When you compile into either of these formats, if you have things set up right, you’ll build your Table of Contents automatically.
With that being the case, why not give it a try?
I decided to try out mobi, since I could shoot this straight up to my Kindle Direct account when the time came to complete this magic. So I selected a few things to test this out, and . . .
Wait a minute. Since you need a way to see your ebook before it becomes an ebook, I needed a little tool for that. I downloaded Kindle Previewer from the Kindle Direct page, so once I had my mobi file, I could pull it up and “read” my story. Great! I get that on the machine, then I start the compile . . .
Oh, wait. In order to compile anything as a mobi, Scrivener needs to know where you store your KindleGen program. KindleGen lets you convert files that could be ebooks into mobi format, and even though I’m creating a mobi file, Scrivener wants to know where this magical program resides on my computer. Which meant I needed to go and download that–
I have all the tools in place. I selected my text, click to Compile, say I want mobi, and do it. A few seconds later–success! I have a mobi file! It was that simple.
With the mobi file in place I started Kindle Previewer, loaded by file, and–there it was! My test book, all nice and . . . well, not exactly neat. The ToC was a mess, but this was due to how I named things rather than something Scrivener did. But things were in place, and the pages looked great . . .
That was when I noticed the page count: 1,452. What? What is his insanity? It seemed that when the mobi file was created, all sorts of pages that I can’t see were created, and this led to this incredible page count, rather than the 72 pages which should have been.
Obviously, there is something I did when writing that brought about this issue. That means more investigation and research, and more testing. But when the time comes, I’ll have this book made.
Oh, yes, I will.