“PS I now have a system for making Scrivener create an ebook for me that is rather fancy, but doesn’t require any hand work. There’s a post about it on my blog, if you care to look. A tiny bit of hand manipulation of the final epub + Kindlegen even gives me indented right margins for my epigraphs. I have learned so much from you and your posts – but I do have a different system which works for me with NO hand cleaning of the source code, and just a few tweaks to the templates. So I can say my Scrivener ebooks look good on the epub and mobi readers I’ve tried, and I’ll test them on everything I have access to before even uploading. You did say to tell you if people had a system that worked for them.”
It probably doesn’t make good business sense for me to encourage Do-It-Yourself ebook production. Except, I think DIY is wonderful and I not only encourage it, I highly approve of anyone who wants to give it a shot. In fact, I am of the opinion that anyone who wants to make a career out of self-publishing to at least try formatting an ebook. If you’re an independent writer, you’re ALSO a publisher. A publisher needs to know how things work. They need to know what the people they hire are doing and if they are doing a good job and earning their keep.
There are many, many resources available to the DIYer. Both Amazon and Smashwords have tons of information about how to make an ebook. It is possible to make a quality ebook using readily available tools such as MS Word or Scrivener. Here is a recommendation I made to Alicia:
“I haven’t used Scrivener since I had a computer die on me, [two plus years ago] and I haven’t reloaded it. I imagine it’s improved quite a bit. Even so, were I using it, I’d skip using their [built-in] KindleGen, run an epub then convert that using the Kindle Previewer. I’d use the resulting MOBI file for proofing and adjusting, then run a fresh epub and load that to Amazon. That will greatly lessen chances of conversion goofs.“
I’ve said it many times in many blog posts that the keys to a quality ebook are clean text going in and then careful testing/proofreading of the ebook before it is uploaded to a retailer. How exactly you go from the clean text stage to the proofread stage is up to you. I prefer html and css to build an ebook from the ground up because it’s efficient and I have a lot of control and I can do some very sophisticated styling without breaking the resulting ebook.
If you are comfortable using a word processor or Scrivener or even InDesign, here are the tips I gave Alicia:
—[This is a problem] Using multiple, but not embedded fonts. I encourage people to stick with Times New Roman, not because it’s easy to read or because it will show up in ebooks, but because its character sets are stable and every conversion program knows how to “read” it. It’s foolproof as far as conversion is concerned. When people use multiple fonts that are not properly embedded, what will happen is that sometimes during the conversion the program decides to “help” out. I don’t know if you’ve ever read an ebook where all the sudden a word is super-sized or teeny-tiny or characters are replaced by black diamonds or boxes with question marks. That is a result of inappropriate fonts.
—Justifying the text. Across the board, this will break a Kindle book.
[Justified text is the default in most Kindle devices, so even if your Word or Scrivener file is ragged right, the ebook will justify the text. If you justify the text, the program will code based on margins and print commands. They can lock. So what happens when it’s converted to an ebook is that the Kindle will not/can not override those locking codes, and users will not be able to adjust margins or line spacing. This is a bad thing.]
—Micro-managing line spacing. This can cause big problems in Kindle books. Broken paragraphs, squished text, weird blank “pages” and so on. Set your spacing at “single” and leave it alone. Problem solved.
—Hyphenating text. For the most part, Kindles ignore discretionary hyphens. Sometimes they don’t. So you end up with words in the middle of a sentence with a discretionary hyphen character (looks like a hyphen with a hook). It doesn’t break the ebook, but it does look sloppy and unprofessional. In html I [sometimes] use a soft hyphen character. Several of my clients are medical professionals and they use some extra long terms, so I manually insert soft hyphens. I don’t know if there is an equivalent in Scrivener.
Two more tips for you:
- Remember that what you SEE in your word processor or Scrivener is not necessarily what you will get in your ebook. So don’t get all worked up about spacing and widows/orphans. Let your text flow, which is what it is supposed to do in the ebook.
- Use styles. Use one style for the main body text (not tabs or hard returns or extra spaces) and another for headers and even a style for centering text. If you don’t know how to use styles, take 30 minutes and figure it out. It will save you time and headaches, and result in a much better quality ebook.
Finally, a word about Amazon’s Look Inside feature. This is a chronic headache for me because most people don’t realize they aren’t seeing the actual ebook. What Amazon is showing is a sample that is specially converted for the Look Inside. Sometimes they justify the text as the default, sometimes they default to ragged right. Sometimes they ignore margins. In other words, if you want to see what the ebook actually looks like, you have to download a sample. Why does Amazon do this? I don’t know. It’s a pain in the ass and I get tired of explaining to clients how it works, but that’s how it is. So my advice to you is if you want to see how your ebook looks “live” do NOT depend on the Look Inside. If you don’t have a Kindle, then download the Kindle Previewer and open up your book with that. You will get a much clearer picture.