Find and Replace: Do It Once, Do It Twice

Ol' Lew has taken quite nicely to the digital age.

Ol’ Lew has taken quite nicely to the digital age.

Out of all the small jobs that make up the big job of getting a book ready for publication, proofreading is the job nobody wants. It is NO FUN.

It’s exacting, it’s painstaking, it reduces an otherwise interesting piece of writing into boring little components that must be examined individually. If your attention wanders or if you get caught up in the story (it’s harder to proofread a rousing good story than a so-so one), you can miss errors. Ideally, any project should have at least two proofreaders. This isn’t an ideal world, however, and not everybody has the funds or the qualified (and indulgent) friends to get two reads.

When I build an ebook, I either proofread it myself or send a proof copy to the writer to proofread. Sometimes we both proofread it. All in the hopes of rooting out the boo-boos and gremlins before a paying customer does.

I have, of course, learned a few tricks (of course) along the way. One of the most valuable tools in my arsenal (second only to Webster’s 9th) is the Find/Replace function. This is especially true since I have found that most writers have a tendency to repeat mistakes. One does need to be careful, though, about global FIND/REPLACE. Or you might end up with something like this:

Barnes & Noble was briefly suspected of employing an outrageous anti-Amazon marketing strategy in May after blogger Philip Howard noticed that a version of Tolstoy’s “War and Peace” sold by the chain store had substituted “nook” for every instance of the word “kindle” throughout the text, resulting in sentences like, “It was as if a light had been Nookd in a carved and painted lantern….” The e-book turned out to have been published by a third-party company, Superior Formatting Publishing, who issued an apology (still posted on the company’s Web home page) explaining that it had accidentally applied the “find and replace” function to the entire text when reformatting the Kindle version of the book for the Nook platform.

The stuff of a proofreader’s nightmares.

Every text handling program has its own set of rules and functions. I can’t possibly cover them all here. I suggest you play with your program’s FIND/REPLACE function and figure out what it can and cannot do. The one thing that every program has in common is that it searches for a unique string of characters. That unique string can include spaces and punctuation.

There are some F/R searches I do as a matter of course. The first is for extra spaces. Extra spaces are the bane of ebooks. They all need to be rooted out. I run searches for double spaces between sentences within paragraphs, and for extra spaces at the beginnings and ends of paragraphs. I also run searches for extra paragraph returns.

The second routine search I do is for backward quote marks and apostrophes. MS Word, especially, has a bad habit of turning quote marks the wrong way, especially when the quote marks are connected to em or en dashes or at the beginning of truncated words. Here the basic rules of grammar are useful. For instance, the left double quote belongs at the beginning of a quoted passage. I will search for a space right double quote or a paragraph return or new line right double quote. I run the opposite search for wrong-way right double quotes by looking for left double quotes at the end of sentences.

Another routine search is for proper names and place names. When I proofread I make a list of preferred spellings. Flying fingers or attention lapses trip up writers. Sometimes the misspellings look right and are easily missed. Take my name for instance. “Jay” looks right, but I spell it “Jaye.” I’ll do a search for “Jay” and “Jay’s” to catch any instances where the “e” was dropped.

The same thing goes for preferred spellings. A word such as “judgment” is also correctly spelled as “judgement.” It doesn’t matter to me what the writer prefers–consistency is my fallback. If the writer prefers the former, I will do a search for the latter and change any instances I find.

I’ve worked on quite a few backlist books that have been scanned and run through OCR. Do enough of them and you start recognizing common OCR errors. For instance, misreading the letter “e” as a “c”. Spell check will catch the most egregious errors, but if the text is supposed to be “eat” and the OCR reads it as “cat” then spell check is useless. It doesn’t take much time to run a search for the word “cat” to make sure each usage is what the writer intended. Another common problem with scanned books is that typesetters often use hyphens and en dashes to space text on a line. Finding those is a bear, but F/R is a big help in rooting out the many permutations that end up as errors in an ebook.

I can’t possibly cover every F/R trick. If you, while you are proofreading your own work, get into the habit of assuming you have a tendency to repeat certain errors, you can use F/R to help you create a cleaner ebook. If you find a goof, run a quick search to see if you repeated it elsewhere.

Check List of Common Errors That Can Be Found with FIND/REPLACE:

  • Extra Spaces
  • Extra Paragraph Returns
  • Proper Names
  • Place Names
  • Quote Marks (single and double)
  • Hyphenated Words
  • Preferred Spellings
  • Italicized Foreign Words (yes or no, but be consistent)
  • Em and en dashes, and hyphens