Tag Archives: editing

Can Your Reformat and Revise at the Same Time?

I am about a third of the way through the next set of revisions for Bottom of the World. I started this process right after finishing the Kindle formatting process for Shaking the Tree and I wondered if I couldn’t combine the two so that I was revising and reformatting the manuscript in the same pass. Was it possible? Would it save time? Check out my six lessons learned.

The short answer is no. I gave up after the first chapter. Revising and rewriting, at least the way I do it, need a flow. I like to read each scene out loud, then rewrite or revise, read again, hunt down typos and then make any necessary notes or continuity checks. Lather, rinse, repeat with the next chapter. Reformatting and layout threw a wrench in there. The whole process engages the old systems analyst side of my brain and just clogs up the creative narrative engine. So I chucked the idea. Mostly. Given the Kindle requirements I learned and the tips laid out in the Smashwords style guide, there are a number of things you can do while you’re in the manuscript to streamline the epub process later.

  1. Use Microsoft Word – While it does not throw out great HTML code for the Kindle, the .doc extension does play best with the Smashwords engine. With a few simple tweaks and a little arm twisting you can get Word to heel and behave.
  2. Use a clean template – It’s hard to get Word to stop sticking its nose into your document. Most of the time you won’t notice what it’s doing till you try to output it and you find Word has been messing with things under the hood. The best thing you can do is try to manage these tendencies.  Use a blank, fresh document. Use one font (see #3). Use two styles: normal for all text and heading 1 for chapter titles. Use only bold and italics. That’s it. Don’t touch anything else. Don’t insert header or footers. Don’t use drop caps. Just keep it simple.
  3. Stick with one simple font – The truth is you have little control over how the text will be displayed in any given e-reader. Why worry about it. Stick with one of the tried and trued fonts (Times, Courier, serif, etc). It may not look pretty. It may be boring. But it won’t cause you headaches later.
  4. Forget pages – This one was surprisingly hard for me. I liked to write in page preview mode. Watching the pages pile up in my rearview gave me some sense of accomplishment and kept the writing momentum going. Switching to Web Layout felt awkward, but if you’re joining the brave world of self-epub, then it’s best to get completely out of legacy page mode.
  5. Pull the tab key off your keyboard – Tabs are like termites, they worm their way into the wood of your manuscript and are a royal pain to get rid of later. When you set up your Normal style (see #2), set the left line indent to .5″ and let the style handle it. Resist the urge to hit the tab key for indents. This is actually the part you can do while you are revising/rewriting. Once you’ve completed a scene, before you move on, turn on Word’s Show/Hide function (CTRL + *) and look for any stray tabs.
  6. Be wary of carriage returns – While you are looking for stray tabs, cull any extra carriage returns you may have thrown into your manuscript to try to fudge spacing. Remember in this brave new world, layout is less a priority. Smashwords recommends not more than four consecutive carriage returns to be on the same side. Otherwise you may find certain e-readers throwing in blank pages. I insert a page break where necessary (personal preference), then 4 returns, then the next chapter (styled with headline 1).

Following those steps during the revision process will help any e-format conversion you undertake to go a lot smoother. It’s rarely seamless and each format carries some additional specific headaches (I’m looking at your NCX file) but these simple switches can cut down your turnaround time.

Blatant self-promotion: Don’t want to try formatting it yourself? I offer affordable conversion services at picolibro.com


Flickr CC attribution for photos used in this post: John Blyberg & Corsairstw