Boast Post: Protectors

Thomas Pluck contacted me, asking for a price quote on a formatting job. I told the old man, “If it’s for one of his charity projects, I’ll do it for free.” Sure enough, it’s an anthology to benefit PROTECT, an organization devoted to wiping out child abuse. (a few of you know about my adopted daughters, so it’s no surprise I didn’t hesitate to say I’d do the project)

What good is a boast post without some boasting and patting myself on the back? If you don’t want to indulge my smugness, jump to the bottom and check out the line-up of writers who have contributed to the Protectors anthology. If you’re still here, let me tell you what I’m most proud to have accomplished in this project:


Here’s the thing. I used to think I was disorganized, that I lacked the organizing-gene. As I get older I realize that I am capable of tremendous organization. Unfortunately, it’s rarely the type of organization anyone else can understand. “Creative” organization looks a lot like chaos to some folks. (Namely Darling Daughter #1 who dreads my demise because she will inherit my many, many file cabinets.) But this is what I’ve learned about organizing: Pick a few rules and stick to them.

One of my biggest gripes with story anthologies in ebooks is a lack of consistency. Layouts shift from story to story. A sense of unity is lacking. Sometimes the stories don’t look as if they belong together. It’s a cobbled together, higglety-pigglety effect that can be downright jarring to readers. If there is too much disorganization and disregard for unity and flow, the overall effect looks amateurish and it’s not very comfortable  to read.

I understand how that happens. There are 41 stories and a foreword in the Protectors anthology. That meant 42 source files, plus the author bios. Each of those source files was… unique. Not just the stories themselves, that goes without saying.  I’m talking about the way the manuscripts were formatted. How they appeared on the “page.” You see, writers know that how their words look, how they flow on the page, affects how the words are read. Text placement affects pacing and emphasis. The use of punctuation and italics and bolding and line breaks can guide readers in directions the writer wants them to go and affect emotional impact. Sometimes, too, while they are creating, writers need for their words to look a certain way on the screen (or in the notebook or on the walls or however they compose) because that is how their minds work and the visual quirks aid creativity.

As a formatter there are two temptations: One, cobble the stories together just the way the writers formatted them; Two, disregard everything the writers have done and make every story look exactly the same. The first way is disrespectful to readers, and the second is disrespectful to the writers.

Given that middle-grounds rarely make anybody happy, I wasn’t looking for compromises. I wanted a way to draw the stories into a unified whole while at the same time using as much of the writers’ visuals as possible in an ebook.

This project required some serious organization.

Step Number One was to establish some RULES.

Creating an overall look for the ebook was fairly easy. I made up a simple graphic to use as titles.


Each story began with non-indented text, first three words bolded (with one or two exceptions). I wanted to make up a little graphic to use for scene breaks, but given the sheer size of the ebook and how many scene breaks there were I felt so many images would have made the ebook file too big. So I used bullets and white diamonds which stood out without being obnoxious. (The point of little touches like that is NOT to draw attention to itself, but to serve as a visual head’s up for readers and as a repeating pattern that helps to draw everything together—think of it as the rule book in a sporting event. As long as the rules are consistent, everybody can focus on the action.)

So, with those rules established, time for the stories themselves. No matter how unique or creative a writer’s formatting may be, there will be an underlying logic. There will be patterns. It’s the ebook producer’s job to find those patterns and figure out how to either make them work in an ebook format or how to approximate them to create them same effect.

I made some cheat sheets to help me stay focused. I’d reproduce them here, but just looking at them won’t make much sense and it would take several blog posts to explain them. The important point is that by taking notes and comparing one story’s special requirement to another’s I could SEE the common denominators so I could figure out the least number of paragraph styles necessary.

Paragraph styles are the key to ebook formatting, whether you’re using a word processor or html. By keeping the number of styles to a minimum, you insure consistency and an overall unified book. What I came up with were three paragraph styles: One with an indent, one block style, and one block quote style. I made the indented paragraph style the default. So while I was cleaning up the original files, if a paragraph required block style or block quote, I tagged it as such. Tagging the styles during clean-up makes it very easy to use Find and Replace in Notepad++.

Then there were a few places that required some special touches. That’s where the cheat sheets come in really handy. Instead of flipping back and forth to the original files, I made copious notes to tell me where and how certain things were supposed to look. For instance, one story had some interesting bits of staggered text. If you’ve formatted ebooks you know that staggered text is rarely a good idea. It can look fine on one device, then go totally haywire on another. That’s because of the way devices justify and flow text—-words can get pulled out of shape.

There wasn’t much (three instances) and I thought the effect the author (Ken Bruen, “Spectre in the Galway Wind”) was going for was interesting enough to give it a try. What you don’t want to use are regular spaces. Those can get distorted when the ereader tries to justify text. What I used are no-break spaces (html entity  ) which lock the spaces into place (perfect for bulleted lists, by the way).

Anyhow, the project was HUGE, over 140,000 words, but by establishing some rules and taking the time to organize the paragraph styles, I think it came out very nicely. I’m proud of my part in the project and honored to be able to do it for such a worthy cause.

But don’t take my word for it. Check it out yourself. The line-up of authors in incredible and the stories are fabulous.

From Thomas Pluck’s PROTECT website:

41 stories.
One cause: PROTECT
100% of proceeds go to PROTECT and the National Association to Protect Children – the army fighting what Andrew Vachss calls “the only holy war worthy of the name,” the protection of children.

We’ve rallied a platoon of crime, western, thriller, fantasy, noir, horror and transgressive authors to support PROTECT’s important work: lobbying for legislation that protects children from physical, sexual, and emotional abuse.

Powerful stories from George Pelecanos, Andrew Vachss, Joe R. Lansdale, Charles de Lint, Ken Bruen, Chet Williamson, James Reasoner, Charlie Stella, Michael A. Black, Wayne Dundee, Roxane Gay, Ray Banks, Tony Black, Les Edgerton and 16 more, with 100% of proceeds going to PROTECT.

PROTECTORS includes a foreword by rock critic Dave Marsh, and fiction by Patti Abbott, Ian Ayris, Ray Banks, Nigel Bird, Michael A. Black, Tony Black, R. Thomas Brown, Ken Bruen, Bill Cameron, Jen Conley, Charles de Lint, Wayne D. Dundee, Chad Eagleton, Les Edgerton, Andrew Fader, Matthew C. Funk, Roxane Gay, Edward A. Grainger, Glenn G. Gray, Jane Hammons, Amber Keller, Joe R. Lansdale, Frank Larnerd, Gary Lovisi, Mike Miner, Zak Mucha, Dan O’Shea, George Pelecanos, Thomas Pluck, Richard Prosch, Keith Rawson, James Reasoner, Todd Robinson, Johnny Shaw, Gerald So, Josh Stallings, Charlie Stella, Andrew Vachss, Steve Weddle, Dave White, and Chet Williamson.

Among PROTECT’s victories are the Protect Our Children Act of 2008, which mandated that the Justice Department change course and design a new national nerve center for law enforcement to wage a war on child exploitation, the Hero to Hero program, which employs disabled veterans in the battle against child abuse, and Alicia’s Law.

Join the fight, with 41 stories by top writers. Be a Protector!



13 thoughts on “Boast Post: Protectors

  1. I love this boast post! And your graphics? Genius! I think you’ve entered the Zen of formatting – you seem to see all the way through to it’s building blocks, the molecules of a word.

    • Thank you, dear. I love the way the ebook turned out and I’m still drooling over being able to rub shoulders (so to speak) with some of my literary heroes. And all for such a good cause.

  2. I remember when I stuck a few symbols into my first ebook for scene breaks. I tested it on my desktop kindle program, looked fine, tested on my android app, looked fine, tested on my e-ink kindle… 😦

    If they would expand the kindle to handle a few more characters, that would be nice. Seems they’re getting ready to phase out everything but the touch, though.

    • You have hit on the ebook formatter’s personal hell, Jim. The Kindle is perfectly capable of accepting all sorts of fonts and graphics and symbols–but which ones will work at any particular time depends on the program used to create the ebook. In xml I can use any named entities, ( ) In Word, my choices are very limited. Even if the symbols or characters show up on the document, it is no guarantee it will translate. I test things out by creating an ebook and loading it onto my Kindle. I prefer making a prc file through Mobipocket for Kindle files, then I’ll convert it to epub on Calibre to see how looks in that format. If a ? , number or odd little box character shows up, then no go.

      As for how things will change, all I know is that they will change. I hope they stay with eink technology–it’s a blessing for my aging eyes. And to play optimist, maybe the device makers will suddenly decide on one platform and one format so we can quit having to fret about what will work and what won’t, and concentrate of making ebooks better.

  3. Thanks, all. Now I have time to actually READ all the stories (as opposed to getting distracted and sneaking a read when I’m supposed to be working!) they’re wonderful. I hope this anthology sells a million copies.

  4. Jaye,

    For staggered text, try this CSS as an alternative to &nbsp HTML entities.

    text-indent: 0;
    text-align: left;
    margin: 0;

    text-indent: 1.5em;
    text-align: left;
    margin: 0;

    text-indent: 3.0em;
    text-align: left;
    margin: 0;

    Your HTML markup would have a class=”level0″ attribute for the first paragraph, class=”level1″ for the second, and so on.

    I use this for Table of Contents. Older Kindles tend to screw up margin declarations, but the text-indent property seems to be rendered okay. Good luck with the doorstopper (140K, ouch).

    Paul in Bangkok

    • You’re absolutely right, Paul. Using p class styles would be easier. I had a “word processor moment” and worked harder than I should have. 😛

      That said, the &nbsp (no-break space) has some nifty uses. For instance, in making bulleted and numbered lists. Not used much in fiction, but I’m running into them a lot in non-fiction. I’ve been experimenting (for instance, Word’s bulleted and numbered list commands almost convert into mobi and epub) and will write a blog post about it soon.

      As for 140k–shoot, I had the easy part. The editor, Thomas Pluck, had the tough job!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s