WHAT IS YOUR STORY WORTH?

by R.S. Mellette

The best advice I ever got on writing was from an acting teacher my freshman year.  I asked her about playwriting.  "I don't know anything about writing," she said, "but I know that a Broadway play costs $50."  (Okay, I just dated myself).  "You have to write a story worth $50 to the average working person."

That always struck me as an excellent test of quality.  Can I tell a story that is worth the audience's cold hard cash?  That's a standard that is visceral.  It's real.  It cuts through all of the literary, English major crap and gets right down to nitty-gritty.  The most important critical question I have for any reader is, "did you get your money's worth?"

That question has become top of the list in this digital day and age.  What is a story worth?  Is it $2.99?  $9.99?  $13.99?  Will amateur authors flood the market with such low-priced material that professionals can no longer make a living?  Is it better to sell ten books at $2.99 or three at $9.99?  If you do sell a lot of books at a low-price, should you then raise the price?

And there is the question of the value of a publisher's stamp.  When Harper Collins publishes a book, they are saying, "Out of the thousands of books we've screened, this one is worth your time and money."  What is that recommendation worth?  As publishers put out more books on the e-market, do they de-value the worth of their stamp?

In talking about traditional verses e-publishing, the questions of value centered around hard costs like paper, printing, art, etc.  Now, of course, we're learning that e-packaging – metadata, formatting, meeting platform requirements – come at a cost.  But the real question is harder to answer.  What is the story itself worth?  Storytellers are unique to our species.  We are not human without them, but how much are we willing to pay them?

I don't have the answers.  Do you?

R.S. Mellette is an experienced screenwriter, actor, director, and novelist. You can find him at the Dances With Films festival blog, and on Twitter, or read him in the Spring Fevers and The Fall: Tales of the Apocalypse anthologies.

Do It Like a Pro

by R.C. Lewis

I have a confession. I’m a little bit of a perfectionist. Just a little. As busy as it keeps me in my own life, it also has a side-effect of making me picky about some things.

Such as eBooks.

My mother owns a Nook (e-ink), my father owns an iPad, and I have an iPhone. I’ve perused a number of eBooks on all three, both Big-6 and indie, using a variety of apps on the Apple devices. I haven’t e-published anything myself yet, but I’ve played with the file formatting process, educating myself in case I decide to go that route.

"But it’s easy!" I hear you say. A few tweaks to your Word file, upload it to Kindle Direct Publishing and/or Smashwords, and conversion to eBook happens like magic.

Well, sometimes.

And sometimes the magic malfunctions.

With many writers new to the world of eBooks, they often think their DIY product looks just as good as the latest eBook from a major publisher, but does it really?

Here’s R.C.’s personal list of formatting red flags. (And when they show up in “pro” eBooks, I’m really annoyed.)

• No Linked Table of Contents. Yes, I know, they’re not required. But why would you not utilize one of the most basic advantages of digital literature? When I bring up the ToC, I should see either chapter numbers or the full chapter title.
• Incorrect Justification. Text should be full justified (lining up on both the right and left edges) with hyphenation to avoid the odd case of one longish word spread out to fill a whole line. This is especially important when reading on a smartphone, and annoying when not done properly. Apparently, some people prefer the ragged-right-edge look—I'm not one of them. Most e-reading apps let the reader choose (which can lead to some other issues), but if there's a "publisher default" option, I prefer that to show up justified.*
• Missing/Inconsistent Indentation. Paragraphs should be consistently indented. I can live with block paragraph formatting, which is how this blog post is set up—no indentation, and extra space between each paragraph. I have seen eBooks (for which people charge money) with a few paragraphs indented, but many others missing the indent and no space to denote a new paragraph. The only clue that a new paragraph has started is the fact that the last line may have ended a little early (which is hard to spot if the book is left-aligned). Very difficult to read.
• No Chapter Breaks. Each chapter should start on a new screen regardless of my chosen text size. You’re not saving paper by starting the chapter a “page” earlier. Some may not think this is important, but when I get the chapter heading sitting at the bottom of the page, I don't like it.
• Weird Margins. This one’s more rare, and I’m not sure what the author/publisher is doing wrong to make it happen, but I’ve occasionally seen eBooks with very wide left/right margins. Again, when reading on a smartphone, this is particularly maddening.

Can you avoid these red flags on your own? It’s been done. There are innumerable forum and blog posts containing tips for formatting your Word document just right to get perfect conversion from sites like KDP and Smashwords.

Alas, my perfectionism has spawned my inner control-freak. If I’m going to DIY, I like the idea of doing as much of it directly as I can, rather than trusting so much of the conversion to happen outside my control. The powers-that-be over at AgentQuery Connect have been experimenting on that end and have developed this helpful guide for getting a file ready for Kindle. They've also got a matching fancy-pants guide for making an ePub file. (I don't think they agree with me about the chapter breaks. Maybe not justification, either. We'll see if they forgive me.)

For my own experiments, I’ve used Apple’s Pages word processor, which will export to ePub format. After a simple tweak to insert my cover image (rather than pasting the image onto the first page of the document), it looked great on both the e-ink Nook and the iBooks app on the Apple devices. (Oh, speaking of covers, I'll get to that in a minute.) I used a free program called Calibre to convert to .mobi format for Kindle readability—a Kindle-owning friend was kind enough to check how it looks on the actual device, and it seems pretty solid. I plan to do some more careful checking of that soon.

* Here's the promised note. I've made four ePub files that I read on my iPhone. Used the exact same style settings and process for all four. With my iPhone full justification setting turned off and auto-hyphenation on, two show up with full justification (as I told it to do in Pages), and two don't, with the exception of a few random paragraphs. After digging into the gnarly code (ePubs are little more than a zipped group of HTML files), I found the difference and had some fun with find-and-replace to clean it up. Still not sure how the inconsistencies crept in there from the Pages file.

I’m sure there are a number of ways to get it done, some requiring more technical expertise than others. The important thing is that your method delivers high-quality results.

Now, a quick word on covers. Remember, on search result screens, your cover image won’t be any bigger than most postage stamps, but the title (and hopefully your name) should still be somewhat legible. On a main product page, the image will be larger, so it should also look good under that level of scrutiny. On many e-ink readers, the cover image will be displayed grayscale; you need to have enough contrast.

Don’t use artwork/images/fonts you don’t have the rights to use.

If anyone could mistake your cover for an elementary student’s very first assignment using Photoshop, consider professional help. It’s the first impression potential readers will have of your book. Don’t make it a turn-off.

Do you have any pet-peeves regarding eBook formatting? Any tips for getting it done right (and at what level of techno-prowess)?