So I’m chatting with a friend and she asks, “What you doing?” I sez, “Nuking tabs. Bwahaha! All gone.”
I was, of course, prepping a manuscript for ebook formatting. That means going through the manuscript and getting rid of everything that will screw up the ebook.
My learning processes are always convoluted, in the beginning overly complicated and then as I figure out what’s important and what is not, I streamline and pare down to the essentials. If you are a regular follower of this blog, you’ve seen my process regarding source files for writers. I’ve gone from suggesting writers set up and use style sheets (they should) to what I’m going to suggest today.
When creating a source file with the end goal of turning it into an ebook, all the writer needs to do, formatting-wise, are three things:
- Indicate page breaks
- Indicate scene or section breaks
- Italics, bolding and underlining
When it comes to page breaks, “indicate” means exactly that. Don’t actually break pages either with inserted page breaks or multiple paragraph returns. Why? Because when you’re ready to format, you or the person you hire has to take them out.
The more formatting you put into your source file, the more formatting that has to be removed. The more that has to be removed, the greater the chances of something that might be missed (screwing up the ebook) and the more it costs in time and money.
When I get a manuscript to format, it’s generally been created with a word processor. Whether I’m going to format it for Smashwords (a Word file) or for everything else (html files), the very first thing I have to do is–
- Remove extra spaces
- Remove extra paragraph returns
- Remove page and section breaks
- Remove headers, footers and page numbers
- Tag page breaks
- Tag scene or section breaks
- Tag special formatting
I don’t actually have to remove tabs because those are going to disappear when I transfer the text to a text editor, but it’s easy (one Find/Replace operation) and it gives me a clearer picture of the dangerous stuff.
Now, seriously, I’m a writer. I fully understand the NEED to make the manuscript look RIGHT. But writers, you have to understand that every effort you make to that end is going to have to be undone. Because of the nature of word processors, some of the fancy touches you include can actually corrupt the ebook.
The less you do–Honestly! Truly! I’m not lying about this!–the better the ebook will be.
So what’s a poor writer to do? Not much, actually. Use whatever font and font size you like. That’s not what will end up in the ebook, but use whatever is comfortable for you while composing. Line space however you like. It makes no difference in the end. Get out of the habit of using tabs. If you can’t stand not having indented paragraphs, set up a simple style sheet that indents the paragraphs with every hard paragraph return. Get out of the habit of two spaces between sentences. Get out of the habit of adding extra hard paragraph returns to space the text. Get out of the habit of making pages. There are no pages in ebooks.
How does one indicate a page break?
I use a code. -PB- It’s unique, the dashes keep it from melding with text, and thus it is easy to find. What my clean file looks like before I take it to the text editor is this:
Final line in chapter one.
First line in chapter two and so it goes.
Use whatever makes sense to you. If you want to make extra sure you or your formatter don’t miss it, spell it out. -PAGE BREAK- That’s it. That’s all you have to do. When you do the actual formatting, that’s when you center, bold, add graphics, extra spacing, etc.
Scene breaks are another place you should get in the habit of tagging–especially if your habit is to use extra paragraph returns to make a blank line. Those can be easy to miss. My little code is -SB-. The text looks like
Last line of scene or section.
First line of new scene or section.
It doesn’t matter much what you use as long as you use something. Asterisks, a pound sign, plus signs, or spell it out -SCENE BREAK-. Use something so the scene break doesn’t get lost.
As for special formatting–italics, bolding and underlining–at some point, whether you do the job yourself or hire it out, you are going to have to tag the special formatting. I’ve gotten into the habit with my own writing to tag as I write rather than highlighting the text and italicizing (or whatever). It’s easier in the long run and I’m used to how it looks. Most writers are not going to want to do that. No biggie. If you are going to tag your special formatting, a few things I have learned–
- If you’re going to format in html, you know to tag the special formatting with open/close codes.< i > and < /i >
- If you are going to format your ebook in Word and are tagging for the purpose of stripping extra coding out of the document, do NOT use html tags. Using < i > TEXT or Wild Card < /i > in the Find box of a word processor can have… interesting results. Not the fun kind of interesting either.
- For Word files I use -I- and -ENDI- to open and close italics. Easy to find and doesn’t give Find/Replace fits.
- Make sure your special formatting is paragraph specific. In other words, don’t just highlight big blocks of text and toggle on italics. Highlight the necessary text within each paragraph, italicize it, then do the same in the next paragraph. Fewer chances for conversion programs to argue about what you really mean.
That’s pretty much it. To get the best results in your ebook, no matter who does the formatting, copy the following, print it out, and tape it to your computer monitor as a reminder:
This is a FILE not a document. Less is more. Less is good. The less you do now, the less you have to do later.