I didn’t publish anything last year, and for too long I was afraid that this year would be just as unproductive. I have one novel completed that I had planned to publish last year, but it didn’t happen, a victim of ebook-formatting despair. Formatting for Smashwords and Kindle was always a hassle, with my books looking completely different, depending on whether they were .mobi, .epub, or .pdf. They also displayed differently in different readers. I finally decided that I needed to give up my faith in my own formatting and turned to Scrivener’s Compile. After days of wrestling with too many details of the program, most of which were poorly explained, and failing to get the damned thing to set up a TOC the way I wanted it, I just gave up, my manuscript a worse mess than I could have managed on my own.
If that was the last book I was ever going to write and publish, it wouldn’t have mattered. But it wasn’t and I needed to find a workable solution. One well-known program for creating ebook files didn’t work at all, another was too complicated, and another worked for some people and not others.
It had become obvious that I needed to start using styles, which I hadn’t been doing. But that didn’t solve the problem of live links for the TOC, or converting the source text to the ebook formats. I can’t afford to pay someone to do any of that for me, and even if I could, I refuse to pay someone to do what I should be able to learn to do for myself.
I knew that the core of all ebooks is HTML. I also knew a few basics of HTML, so I was mildly interested whenever someone would say that the way to go was to convert your text to HTML for total control. But I’m not good at any kind of coding, and wasn’t willing to dive deep into HTML. Until now. What got me to change my mind was an excerpt from Guido Henkel’s new book, Zen of eBook Formatting, plus a somewhat confrontational discussion about his formatting methods, on Kindleboards. His much earlier blog tutorial on the subject hadn’t convinced me, but the combination of that discussion and the excerpt did. HTML was the way to end formatting frustration.
So I bought the book and started reading. By the time I reached chapter three, my fears about HTML (and CSS) being too complicated to learn were assuaged. Yes, there’s a learning curve, and the material is the kind that takes a lot of repetition for me to understand and absorb. But I could see my way clear to it for the first time. I learned that CSS isn’t the fearsome and mysterious thing I thought it was, and the number of HTML tags that ereaders will accept is actually fairly small, so I probably won’t have to go much deeper than what I already know. Best of all, once I have HTML under my belt and can use it fairly easily, my books will look exactly as I want them to, on every device, in every ebook format.
A new self-publishing adventure begins.