Programs for Indie Publishers

Creativity is messy

One of the best aspects of indie publishing is that Do-It-Yourself is feasible. All you need is a computer and some decent programs–many of them free–and you can put together a professionally packaged book.

 

Many indie publishers start and end with MS Word. I suspect this has to do with comfort. They use Word, they know it (or think they do), and Amazon, Smashwords and Draft2Digital accept Word files. I also suspect fear plays a part. No matter how easy or intuitive a program is, there is still a learning curve. Easier to stay with the devil you know than to leap into the unknown. My hope is that the list of programs I use will encourage DIY indie publishers to wander into deeper waters and increase the quality of their book production.

This following programs and tools are what I use on an almost daily basis. It’s by no means a complete list of all the programs and apps that are available. A Google search for “programs for publishing” will turn up hundreds–thousands!–of programs an indie might find useful.

A word about computers. Currently I use two. A Lenovo Z70 laptop and a Mac. (I’m in the process of finding a new desktop PC, too.) I use the laptop for ebook production and the Mac for print and covers. The reason is: Adobe. I will not allow any Adobe products on my laptop. They are big and grabby and eat RAM like peanuts, especially InDesign. Adobe CC seems to behave better on the Mac, crashing less often. Plus, I have a 29″ screen that makes using Photoshop a real pleasure.

On to the list.

DROPBOX. Dropbox is a cloud storage service. You can sign up for the basic service and it’s free. If you need more storage space, you can go with a business plan that starts at $9.99 a month. Most indies don’t need the extra space. It’s a great way to back up your files. You can synch between devices. There are apps available so you can access Dropbox from your tablet or phone. You can share files and folders. It’s an easy way to share files that are too big for email attachments. I’ve been using Dropbox for years. It’s had a few hiccups, but very few. The only ongoing problem I’ve experienced is that the Kindle Previewer doesn’t like it. So to load a file into the Previewer I have to remember to drag it out of Dropbox and onto my desktop first.

---

MS WORD.  Used to be just about every PC came pre-loaded with MS Word. Everybody used it. Those days are over. Now you have to purchase it.

WHAT I USE IT FOR

• Personal correspondence and writing
• Initial file clean-up
• Basic ebook formats for Smashwords (fiction only)

PROS

• Everybody uses it (for now)
• It’ll open a huge number of file types and it will generate a large number of file types.
• Word docs are accepted by Amazon, Smashwords and Draft2Digital

CONS

• Most people have no idea how to use Word properly
• Clunky, bloated and overly-complicated
• Makes awful ebooks

---

NOTEPAD (PC) and NOTES (Mac). These text programs come pre-loaded on most PCs or Macs. When I’m working on a book I keep a file open where I can make notes to myself. Nothing special, but very very handy.

---

NOTEPAD++. This is my text editor of choice. (In the Mac I use Text Wrangler)

WHAT I USE IT FOR

• Create ebooks in html with cascading style sheets
• Text restoration
• File cleanup

PROS

• Free
• Easy to use
• No bloat since there is nothing running in the background to add a bunch of junk to a file
• Powerful search function with multiple levels
• Can encode files for different purposes, including UTF-8 for ebooks

CONS

• Learning curve (moderate)
• Must get used to the display which is nothing like a word processor

---

SIGIL. EPUB editor. I have it on both computers. If you want to step up your ebook quality, Sigil is an excellent tool for creating ebooks. And yes, with some modifications to your file, you can create ebooks for Amazon Kindle, too. Paul Salvette of bbebooks offers a very good tutorial.

WHAT I USE IT FOR

• Troubleshooting epub files

PROS

• Free
• Mostly stable
• Offers inline epub validation
• Can be used in WYSIWYG mode or in html mode

CONS

• Learning curve (moderate)

---

KINDLE PREVIEWER. Quick and easy way to preview your ebook files before you upload them to Amazon. If you want to see how your ebooks look with Amazon’s enhanced typesetting features you can download the Kindle Previewer 3.

---

CALIBRE. Quick and easy way to preview an epub file. Has an epub editor (which I don’t use and haven’t looked at it in over a year, so cannot say how good it is). Despite its many fans, Calibre is NOT the tool to use to create commercial ebooks. It causes disabled user preference controls on Kindle devices and apparently there are conflicts with Kindle enhanced typesetting.

---

MOBIPOCKET CREATOR. Will convert a Word or html file into a prc file that can be converted into a mobi file in the Kindle Previewer or loaded directly onto a Kindle device. Quick and simple. Good way to check how the formatting on a Word file will perform on a Kindle. I use it to do a quick and dirty conversion of Word files I want to read on my e-ink Kindle.

---

EPUB VALIDATOR. The idpf validator is the standard for making sure your epub files are free of errors and up to snuff. I use this tool in conjunction with Sigil. If I get an error message, I can find and fix it quickly in Sigil, then transfer the fix back to my html files.

---

UNMANIFESTED EPUB FILE CHECK. Apple iBooks is picky about unmanifested files within an epub package. Running your epub file through this checker will help ensure your ebook will make it onto the Apple site.

---

IRIS OCR. I do a lot of text restoration, recovering the text from printed books and turning it into a workable document. I have used and researched a lot of OCR programs. Quality ranges from “oh my god you have to be kidding” to excellent. IRIS is excellent. If you have an HP scanner, you can download IRIS OCR software along with the HP drivers. You can also purchase software that allows for side-by-side document editing (necessary if you’re scanning and restoring graphic/image heavy or complicated layouts in non-fiction books).

---

INDESIGN. For print on demand layouts. (Despite what many of its fans say, it’s NOT a good program for making ebooks. I can usually tell an ID generated ebook because it looks gorgeous and the user preference controls are disabled. There are apparently conflicts with Kindle enhanced typesetting, too.)

PROS

• For POD it’s easier to use than Word.
• Print is what it was made for and print is what it does best. Makes beautiful books.
• Adobe help sucks, but google “how do I…InDesign” and you’ll find answers all over the place.
• Trouble-free export into POD ready pdf files.

CONS

• Expensive! I don’t think you can buy the program new from Adobe. Instead, you have to set up a subscription. If you cancel your subscription, your .indd files are rendered useless.
• Steep learning curve.
• RAM grabby and has a tendency to crash.

---

PAINT.NET. A powerful paint program that is easy to use. Fun, too. And free! Good for resizing images and creating simple graphics. Offers many plug-ins that make it possible to create ebook covers. It does a good job of modifying and manipulating photos.

---

PHOTOSHOP. The more I use Photoshop, the more I learn about it, the more I like it. I use it to make covers and to clean up damaged images. Unlike ID, I’ve had no problems with it either slowing my computer to a sluggish crawl or crashing. Like ID, it’s not being offered for sale by Adobe, but is on a subscription plan.

==============================

There you go. My favorite book production programs. What about yours?

 

 

 

 

Advertisement

The Proof is in the Proofreading

My biggest gripe with ebooks is a lack of proofreading. (Trad pubs are the worst offenders–isn’t anybody at least giving the ebooks a quick scan before putting them up for sale? Judging by the multiple dumb errors and piss-poor formatting, I’d say the answer is no.)

When I produce an ebook I have two hard and fast rules, Number One: squeaky clean text going into production. Number Two: the ebook must be proofread post-production. I charge people to proofread their ebooks for them, and a lot of clients take me up on it, but I’m more than happy for the writer to do it him/herself or hire a third party. I even make it easy for them by providing a markup document and instructions (since they can’t make changes in the ebook itself).

Even though proofreading is essential, some would like to argue that they can skip it. They’ve already polished the manuscript to a high gloss, even had a professional editor have a crack at it, and, in some cases I’m sure, they are sick to death of that particular project and want to get on to something else. I get that. Been there. Even so, it’s part of being a publisher and it must be done.

Before I continue, let me explain what proofreading is NOT:

• It’s not copy-editing
• It’s not line-editing
• It’s not editing at all

What proofreading IS:

• Format checking
• Typo searching
• Error seeking

When I produce an ebook, I expect that the writer has edited, polished, tweaked and fine-tuned. They’ve made the text as clean as they are capable. They made their grammatical choices and established a style. When I proofread I’m just looking for goofs. I don’t change text unless it’s a patently obvious error. Double words (…he spelled the the word misspelled incorrectly…) or a mixed up homonym (…happy is the bear-foot boy…) or a missing word (…nothing finer than (a) sunny spring day…) and misspellings or incorrect contractions. For anything beyond that, I will make a note to the writer and they can decide how to fix it, or not. My main concerns are my own goofs in formatting, and little gremlins such as missing punctuation or words that aren’t fully italicized or spacing issues.

There is nothing particularly difficult about ebook proofing. That said, I recommend that writers NOT proofread their own work, but instead hire out the job or find a writer friend willing to barter or trade the chore. The reason is copy blindness. When you write something down, you know exactly what you MEAN to say. Your brain is more likely to “see” what you meant rather than what is actually on the page. It’s a very real phenomenon and it trips up the best.

What if it’s not in your budget to hire a proofreader? What if all your friends are busy? What if you HAVE to do it yourself? What if you WANT to do it yourself?

There is hope.

The Tools

• An ereading device: Kindle, Nook, iPad, your computer, etc.
• A style sheet
• A style manual
• A dictionary

The Device: Even though MOBI and EPUB are different platforms, the ebooks should look pretty much the same no matter what device the reader uses. So it doesn’t matter which version you proofread. If you do not have a dedicated ereader, then you need to use an online viewer. I recommend the Kindle Previewer, Calibre and Adobe Digital Editions. All three are free downloads. All three render well enough for proofreading purposes. All three allow you to double-check your ebook’s navigation.

A Style Sheet: This is basically a log of your preferred spellings, stylings and usages. I keep Notepad open when I proofread and jot down character names, unusual spellings, etc. to give me a quick reference. Consistency is the key to a good reading experience. The style sheet will keep you consistent. I also log product names and trademarked names, then double check to make sure they are spelled correctly and to see if there is any restriction on their use.

A Style Manual: Every publishing house and periodical publisher has an in-house style. Often it is based on a particular style manual such as the Chicago Manual of Style. Every indie publisher should do the same thing. Pick a style and stick with it. For fiction, a far simpler style reference will suffice. I recommend Strunk & White Elements of Style. Short, easy and friendly. Buy a copy (then buy extras for when your kids run off with them).

A Dictionary: Depending on spell check can lead to embarrassment. If you’re like me, you have dozens of dictionaries and thesauri on your bookshelves. Pick your main reference(s) and stick to it/them for consistency’s sake. Language changes and evolves, but it shouldn’t do so within one story. If you’d rather use an online source try the Merriam-Webster site or the Oxford Dictionaries site.

The Process

1. You must open the ebook on something. You cannot properly proofread the ebook by going back to the manuscript.
2. Have a markup document ready. I use a Word doc in which I’ve created a navigation guide, but no other formatting. Here is where Track Changes* comes in handy. Do all your mark up and changes on this document (which you will then transfer to your actual ebook file after you are done).
3. Work backward through the ebook. Truly, this is the number one best way to defeat copy blindness. It will help keep your mind out of the story and on task.
4. If you get sleepy or hungry, take a break. Sleepiness makes you dull and inattentive; hunger makes you impatient.
5. Periodically change the font, font size and line spacing. Just making the ebook look different goes a long way toward making you more efficient.
6. Get in the habit of questioning everything. Homonyms can be the bane of many writers. It’s so darned easy to mix up words that sound alike. Here’s a fun reference: Alan Cooper’s Homonym list. Product names are another danger area. Google is a wonderful resource. BUT, sometimes it is not enough to just get the spelling right. Companies can be very aggressive about protecting their trademarks. If you are using a trademarked product name, double check proper usage here.
7. Use Find/Replace wisely. I rarely use Replace All when proofreading–it can lead to strange occurrences. It is human nature to repeat errors, so if you find an oddball spelling, do a quick search to see if you’ve done it elsewhere.
8. If a passage seems off to you, read it aloud. Read it aloud to someone else. This is an excellent way to figure out if you’ve misplaced a comma or skipped a word.

And a final word of wisdom: Don’t rewrite your book. Seriously. You’re proofing the final product, the final step before releasing it. If you cannot stop rewriting, tweaking, doing “just a little bit more”–procrastinating!–then find someone else to proofread for you.

If anybody has any other handy-dandy tips to make proofreading easier or more efficient, feel free to fill up the comments.

* Never, ever use Track Changes in a Word doc that you intend to convert into an ebook. Turn it off, keep it off, protect your ebook from the nastiness that Track Changes inserts.

Calibre, Word and MOBI: A Tale of Three Programs

(Yes, I know, MOBI is not a program, but my blog, my headlines…)

Ever since I started blogging about ebooks, I’ve cautioned people against using Microsoft Word to format their ebooks. Not because Word is a bad program and not because it’s impossible to create ebooks with it. It’s because it’s the not quite right tool. Word’s strength lies in creating print documents or pdfs.

Recently, I’ve been cautioning people to not use Calibre to convert their Word files into MOBI files in order to sell them on Amazon. Not because Calibre is a bad program and not because it’s impossible to create MOBI files with it. It’s because it’s not quite the right tool. Calibre’s strength lies in managing a person’s digital library. It was not created to convert commercial ebook files.

EPUB files are not as troublesome as MOBI files. EPUB is EPUB is EPUB, and while each device has its own special way of rendering the file to fit the platform, the differences between devices aren’t big enough for most people to notice. A single EPUB file will work pretty much the same on a Nook as it does on an iPad.

Calibre is set up for optimum use with EPUB files. If a publisher converts a Word (html) file into an EPUB file using Calibre, then what they see there is pretty close to what a Nook or iPad reader will see.

This is not true with MOBI files. The reason is Amazon. You see, EPUB devices have evolved and changed and upgraded and gone the way all technology goes, ever upward and onward. But the device makers built the newer devices around the existing ebook platform. So an EPUB ebook formatted five years ago will work pretty much the same on a new iPad as it did on a first generation Nook. Amazon went bass-ackwards. They built the new devices then tinkered and recreated entirely new ebook platforms to fit the new devices. So a MOBI file being sold on Amazon isn’t just a MOBI file. It’s also a KF/8 file and an iOS file and an AZW3 file and god knows what else is there. I don’t quite get all the technical stuff. What I do get is that the same ebook can work fine on a Kindle Fire, but go to hell on a Paperwhite and look okay on a Kindle Keyboard and turn into gibberish if an iPad user gets hold of it.

The whys and wherefores don’t matter as much as the fact that a file formatted in a program which is optimal for printing documents and then converted with a program that is at its best with EPUB files, is going to have trouble meeting the very odd demands of Kindles.

(By the way, if you are using Scrivner or InDesign to create your ebooks for sale on Amazon, you will run into the same exact problems because Amazon is constantly tweaking and fiddling with the platform(s) and updating devices and they don’t necessarily share what they’ve done with the rest of the world.)

I realize that none of what I just wrote is going to dissuade people from using Calibre to convert their Word docs into MOBI files to sell on Amazon. I know this because people are using Word because that’s the program they know and love(hate) and they need a way to convert those Word files and Calibre is the shortest distance between A and B.

So instead of wagging my finger and clucking my tongue, I did some research. Question: Is it possible to format a file in Word and convert it with Calibre and create a MOBI file good enough to sell on Amazon? (Here, I make a very clear distinction. If your Nook died and you bought a Kindle, and you want to convert all your Nook books into MOBI files you can load onto your Kindle, Calibre is a great tool. That’s personal use. You expect that the ebook might not work completely right, but that’s okay, at least you have it. You can’t ask your paying customers to accept that standard.)

What I discovered is: Yes, it is possible.

I managed to fix the worst problems I see with Calibre-converted ebooks. I managed to create ebooks that respond properly to all the user preferences in three generations of Kindles (Kindle Keyboard, Paperwhite and Fire). I almost got Calibre to build a toc.ncx (what the user sees in the Go To features on Fires and Paperwhites) the way I want it to. I think with some more tinkering and fiddling around inside the opf file, I can fix that problem. I couldn’t get the cover to display on the bookshelf in my Paperwhite, but that’s kind of a non-issue, since Amazon will handle that when the book is uploaded. (It is only a big deal if a publisher is selling direct.)

Even though the ebooks I created this way aren’t up to my standards, they will respond to user preferences and they will look fine and read fine, and thus, they are good enough for uploading to Amazon.

There is a caveat. If you format your document, save it as an html file and convert it as is with Calibre, your ebook will be broken. It will be a substandard product you should not ask people to pay for. What you have to do first and foremost is format your Word file so it works within Calibre’s parameters, and secondly, you have to fix the html coding in the Word file.

Sound scary? It is, kind of. Word’s html coding is a nightmare, full of mso odd bits that give Kindles the hiccups. The good news is, all you really need to do is remove some very specific lines of code and rearrange a few others.

Since this post is running long and I don’t even have any pretty pictures to enliven it, (plus I have a buttload of Christmas gifts to wrap) I am going to explain how I did it in my next post. It’ll have pictures. In the meantime, if any of you, Dear Readers, have figured this out and feel like sharing in the comments, feel free.

Update: A Fix for the Calibre Line-Spacing Issue

A comment from Kovid Goyal of Calibre on yesterday’s blog post led me to do some experimenting this morning. I took the same files I used to demonstrate the squished line spacing and converted them into azw3 files. I loaded them onto my Kindle and the line spacing issue was no longer an issue.

So, if you are getting otherwise good results from Calibre and are comfortable with it and do not want to change, then from here on out, do NOT convert your files into MOBI format. Instead, convert them into AZW3 format.

Calibre and Kindle, Not a Good Match

UPDATE 010314: I wrote this article before I did any real research into Calibre. Considering the vast number of hits this blog post is generating, I knew there was a call for information about how to convert a Word file to MOBI in Calibre. I found a fix and I wrote a series of posts about it. Part 1 (Styling in Word), Part 2 (the HTML file) and Part 3 (Conversion in Calibre). It’s not a quick fix (or magical), but it’s not difficult either.

Don’t get me wrong. I like Calibre. It’s quick, it’s handy, and it has an attractive screen display that I far prefer over Adobe Digital Editions or the Kindle Previewer. Since I don’t have a device capable of reading EPUB files, it’s also useful for checking the formatting on files I create for others.

What it’s not good for? Converting EPUB files into MOBI files for commercial purposes.

Having seen some horrendously broken ebooks that had been converted through Calibre, I have long suspected that Calibre was the wrong tool for the job. I assumed it was user error, a problem with the source file and/or the html, and if the formatter did a really good job with the initial file, Calibre wouldn’t muck it up.

I was wrong. The problem is with Calibre.

I converted an EPUB file to a MOBI file with Calibre. I then took the exact same file and converted it with KindleGen via the Kindle Previewer. The above screenshots are the results. Same page, same settings, same device (Kindle Paperwhite).

Squished lines.

In the recent ebook formatting contest, I saw squishy line spacing in every single ebook that had been converted via Calibre.

So maybe the problem lies in the subtle differences between the html coding for EPUB and MOBI. I ran a file I had made specifically for Kindle through Calibre. Squishy lines. I took that Calibre-generated file and ran it through KindleGen. Squishy lines.

Could Amazon be taking care of the problem? I downloaded samples from the contest entries. Squishy lines.

Why does Calibre do this? I have no idea. It just does.

Why is it a problem? Because for many readers, myself included, Kindles (and other ereaders) make reading comfortable again. My eyes are old, plus I spend all day in front of a computer. My eyes are tired. With the Kindle I can change the font, adjust the font size and change the line spacing for optimal comfort. Squishy line spacing is hard on my eyes. When I try to read an ebook that I can’t adjust for my comfort, I get irked. When I’m irked, that author/publisher ends up on my Don’t Bother list. (Your future sales, folks)

There are alternatives to Calibre. If you are converting a Word or html file, use MobiPocket Creator. If you have a simply formatted file, it will generate a prc file you can upload to Amazon and it will work. If you have an EPUB or html file, you can use the Kindle Previewer (converts with KindleGen). A warning about the Kindle Previewer–what you see is not always what you get. Trust but verify and test your files on an actual device if you can.