Racing with Deadlines

I prepare to buckle down and finish up a book.

After a nice, relaxing weekend at Howard Mesa, I’m back home looking at a calendar that has a deadline on it. It’s not a “drop-dead” deadline, but it is one tied in with additional financial reward. In other words, if I meet it, I’ll see more money than if I don’t. Since I’m on the downhill slide of a less-than-perfect writing year, having a few extra bucks between royalty statements would be very nice.

What makes this deadline extra important is the stuff scheduled right after it: a bunch of extremely lucrative flights for Flying M Air. In fact, I have every single weekend in October booked for an event. I also have three photo flights in northern Arizona — one of which will last 6 days.

So if I don’t finish the book on time, I won’t have much time to work on it after the deadline.

Why am I telling you this? Just so that you understand when the number of new posts drops significantly over the next two weeks. Although I’m hoping to continue to post at least one short entry a day, I might not have time to. I work best in the morning and may have to give up my coffee/blogging time to work on the book.

And, if you haven’t figured it out yet, the book in question is my Mac OS X book revision, Mac OS X 10.5 Leopard: Visual QuickStart Guide. I’m about 1/3 finished with the 744-page book. I’m extremely pleased with what I’ve done so far, but I’ll be even more pleased when it’s done.

Wish me luck!

Copy Editing – Part III: Editing for the Sake of Editing?

That’s what it sometimes looks like to me.

In the first two parts of this series, I told you what I think copy editing should be and told you about my experiences, over a period of 10 years, working with copy editors for the annual revision of one of my books.

In this part of the series, I’ll sum up with a few of my conclusions and observations.

Stet!Editing for the Sake of Editing

I don’t think a copy editor should make a change unless there’s an error in the text he’s editing. Error means something wrong. Not something that’s equally correct his way or the author’s. If an editor’s change does not make an improvement, it should not be made at all. Period.

This is my opinion, but I think that most people in the publishing industry — especially the authors, of course — would agree. In fact, it seems like a no-brainer.

But it does not explain the commas that have come and go with each edition of this particular book. Or numerous other changes that have not improved the book’s content. Those, I think, are edits for the sake of editing — the editor’s way of proving that he’s on the job, doing what he’s being paid to do. Almost as if he’s being paid by the edit and wants to maximize his revenue or worth.

Unfortunately for these copy editors, it’s the copy editor who understands his job and does it as instructed who will be called for the next job. My recent copy editor certainly won’t be working on any of my books again. (Most likely because the PE doesn’t want to have to deal with my complaints.)

A publisher has no need for an editor who pisses off all the authors — even if some of them are prima donnas. Who wants headaches when you’re putting together a book? Why make changes when the changes aren’t needed?

Frustrated Writers?

A lot of writers (note that I didn’t say authors here) believe that editors are just frustrated writers. The thought goes something like this: If you can’t do, teach. If you can’t write, edit.

Double-ouch!

In general, I don’t think this is true. I think some people just like to edit. They might have the skill set or patience for it. They might enjoy reading an author’s work and fine-tuning it to make it better for the reader. They might simply lack the desire to do what’s required to write a book: organize, research, compose, etc. for 300+ pages of text. That doesn’t mean they can’t do it. Just that they’ve chosen not to.

[In my case, the reverse might be true: If you can’t edit, write. My editing often comes down to rewriting. That’s not a crime if my name is on the book cover, but it is unforgivable if my only mention is fine print on the copyright page. So there’s no career as an editor in my future.]

But like other writers, I also suspect that some editors are frustrated writers. They just haven’t had the break they need to get their own work published — for whatever reason.

After all, it isn’t exactly easy for a writer to become a published author. (Again, I think there’s a big distinction here.) Sure, in the era of Web 2.0, anyone can write and be published. But it’s still a more traditional publishing process — one that involves acquisition, project, copy, and technical editors — that turns a writer into an author. And that process isn’t as easy as writing your thoughts in a form and clicking a button to publish it on a blog.

Got Something to Add?

If you’ve got something to add to this discussion, don’t be shy. Use the comments link or form to add your comment to this post so others can take advantage of your insight on this matter, too!

Why I Use a Test Mule

One good reason not to load beta operating system software on a computer with real data on it.

Today, while working with a certain beta operating system, I managed to lock myself out of my user account.

Well, I didn’t do the locking. The computer did. An error occurred as I was logging in, right after disabling its heavy-duty file security feature. It decided it didn’t like my password, and although it liked the master password I entered for the computer, it didn’t like the idea of me changing mine to one that would work.

Result: I couldn’t log in as an administrator, so I couldn’t do much of anything with the operating system — including accessing my files.

This brought my entire workday grinding to a halt. Thank heaven I pulled those screenshots off before I clicked that button. They’d be goners.

Now if this were my main production machine, I’d be going bonkers right about now. I’d be freaking out. I’d be so glad I’ve been faithfully backing up all my important files all over the place. But I’d be really POed that I had to reinstall everything from scratch.

But it isn’t so bad when you’re dealing with a test mule. That’s a computer that exists solely to run software in a test environment.

Like beta operating system software.

The computer has hardly anything on it, so losing the hard disk contents isn’t a big deal. Just reformat and reinstall. I’ve already installed betas three times for this book and I’m sure I’ll be doing it again before the software is finalized. Not a big deal.

As I write this, the installation DVD is starting up the computer. I had to fool it into booting from that disc, since I’d normally need to enter my password to restart with the boot disk inserted. (I got to use that Option key trick I wrote about earlier today in an emergency situation.) I figure that just before bedtime, the installation will be complete.

Tomorrow, I’ll pick up where I left off.

Copy Editing – Part II: My Experience with Copy Editors

My experiences with copy editors.

This is the second installment of my series about copy editing. As I discuss in Part I, part of this series is a rant based on 15 years of accumulated frustration. This Part is where I blow steam.

Stet!Copy Editors and My Work

I have to start out by saying that my work is usually not very heavily edited. I take that to mean that one or more of the following are true (or is that is true? I never said my grammar was perfect.):

  • I know how to write. Seems funny to even make that statement. It’s pretty obvious that I know how to write when I’ve been doing it for a living for so long.
  • My publishers have a limited budget for copy editing. This might be true with my “packaged” books — those are the ones I write, lay out, and submit as InDesign files, TIFFs, and PDFs. But I don’t think that’s the case with my more traditionally produced books.
  • The copy editors I get don’t know what they’re doing. For the most part, I don’t believe this is true. How can they be copy editors when they don’t know what they’re doing?

So I tend to believe it’s the first reason more than the others.

But the reason doesn’t really matter. Any writer can tell you that they’d rather see their work lightly copy edited than heavily copy edited. The reason: the percentage of original words, sentences, and paragraphs that “survive” the editing process. Light editing means more of the author’s original work remains intact. Heavy editing means that less of the author’s original work remains intact. It’s as simple as that.

[I need to make a disclosure here. I am guilty of being a heavy-handed editor. I’ve worked with co-authors on three occasions. On two of them, I had final say over the text that would become the content. In both cases, I tried to change the co-author’s “voice” to match mine. Voice is a sort of writing style that comes across in sentence construction, etc. In one case, the co-author didn’t give a hoot; he was just glad that someone was going through the text and making the style consistent. In the other case, the co-author was rather upset and offended. In both cases, I did what I did to make the book better. Or at least better in my opinion. Whether I made it better or worse is something we’ll never know. In any case, I’ve decided that it’s probably best if I stay away from the co-author role.]

Ten Editions, Ten Experiences

I just completed the tenth edition of one of my books. Each revision begins with the previous edition’s text and edits it so it covers the current software product. Some years, less than 5% of the book’s content changes. Yet for the first few years, the book was sprinkled with copy edits — I could see them because we use Microsoft Word to prepare the manuscript and the revision feature is turned on throughout.

Every year’s editor — because there have been 8 of them over 10 editions — had a different “pet change.” For example, one editor didn’t like where I put words like “only” and would invariably move them to another part of the sentence. I’d read the sentence both ways and either way worked for me — although it obviously sounded more natural to me the way I’d originally written it. Another editor liked to add commas. That didn’t matter much, because the next year’s editor liked to remove commas. One year’s editor decided that all the names of menu commands, dialogs, and options within the software should be in title case, no matter how it was presented in the software. So the Show color for Background image check box would become the Show Color For Background Image check box. One editor rolled up her sleeves and rewrote a bunch sentences that the previous editions’ editors had either fiddled with themselves or left as is. The most recent editor decided to introduce italics to some text that had never had it before.

How I Felt about It

Each year — the book is revised annually, every summer — my attitude toward the copy edits changed.

At first I didn’t mind so much, although I got seriously peeved when the production editor for the first edition started making changes to content that we’d all already agreed on. (That’s another story and not a happy one, although I did get the last laugh.)

Then, as I saw the current year editor change things that the previous year’s editor had changed so it was what I’d originally written (or pretty close to it), I started complaining. I could do that since the book’s very first edition had become a bestseller and the publisher wanted to keep me happy. (Don’t try this for your first book, kids.) The copy editor on that edition tuned things down a notch.

But the following year it was back to what I consider “changes for the sake of making changes.” I got fed up, blew a gasket, and decided that I didn’t care about the changes. I’d just rubber-stamp everything. And I did for two or three years.

But then I started caring again, right around the time I got a good editor two years in a row. (Where is she now? Come back!)

Last year’s editor wasn’t bad, although he did ask a lot of questions that seemed designed to point out errors in my text rather than just fix them. For example, “The art shows that the dialog is called Colors, not Color as you have indicated here. You also called it Colors in five other places. Should I make the change here?” Uh, yeah. Isn’t that what you’re here for? Of course, I didn’t say that. I just thought it. Loudly, in my head. If he would have just made the change, I would have seen it with the revision marks and would have checked it and would have realized his edit was correct.

This Year

This year’s copy editor absolutely wigged me out. Her orders were supposed to be to edit the text that has changed. Remember, the majority of the book is exactly the same as it was the previous year. This year, about 20% of the text changed. That means she only had to look at 20% of the manuscript — the part with all the colored revision marks. Yet she insisted on copy editing the whole thing. She inserted a bunch of commas, which I really don’t care about. (Next year’s editor will pull them back out and I won’t care about that, either.)

But she also decided that all occurrences of Web should be web and that some terms, menu commands, feature names, and dialog options should be italicized. The problem with this is consistency — there wasn’t any. A command name on one page would be in normal type and the same command name on the next page might be in italics.

I freaked and I complained to the project editor. The formatting was wrong and inconsistent, I’d have to undo every wrong change she’d made while reviewing the edits. It was annoying and time-consuming and I had another (dare I say it?) more important book lined up after this one to write.

The PE clarified the instructions to the CE. The CE continued to make the same changes. I freaked again. I couldn’t get the PE on the phone, so I wrote a nasty e-mail to the CE. (I’d thrown my back out the day before and was in incredible pain, but still had to work on the book to meet the deadline, so I was pretty cranky. I wrote the e-mail just before heading out to the chiropractor.) I got scolded by the PE. I defended my complaints. The PE talked to the CE again. And then the CE stopped reviewing anything except the edits (as she should have been from the start). And guess what? In three of the remaining 12 chapters, she had absolutely no changes.

Now tell me, what does that say to you?

More to Come…

In Part III of this series, I’ll tell you what that said to me. Until then, if you want to share copy editor horror stories, the Comments link or form is a good place to do it.

Copy Editing – Part I: What Is Copy Editing?

Copy editing — an important part of the publishing process.

Prepare yourself for the usual author rant — but with a difference. This one is coming from an author who just completed her 69th book. An author who has worked with about eight different publishers and dozens of copy editors over the course of 15 years.

So no, this isn’t a newbie writer griping about a heavy-handed editor on her first or second book. It’s coming from someone who has been doing this for a long time and feels as if she’s “seen it all.”

I’ve taken this topic and split it into three parts. In this part, I’ll start off with an introduction to the topic of copy editing and tell you what I believe it should be.

Stet!What is Copy Editing?

The purpose of copy editing should be to ensure that the original text is:

  • Free of spelling, grammar, and punctuation errors. Note the use of the word “error” here; that’ll be important later in this discussion.
  • Consistent with a publisher style guide. A style guide, in the world of publishing, is a document that sets forth usage in those gray areas. I’m talking about capitalization issues such as web vs. Web, hyphenation issues such as email vs. e-mail, and design issues such as boldfacing figure references.
  • Clear and easy to understand. This usually involves breaking up long or complex sentences or possibly rearranging sentence components.
  • Unlikely to be misinterpreted. For example, when you say the “Color in pop-up menu,” do you mean a pop-up menu named “Color in” or are you talking about color in a pop-up menu?
  • Consistent with the writing style of the established book or series. This only comes into play when you’re writing for a series that has a predefined format and style. For example, Visual QuickStart Guides (VQSes) tend to be short and to the point, so I don’t have room for personal stories, as I do in other books. VQSes also have level 2 headings that begin with the word “To” and are followed by numbered steps, each of which presents a single task. (I could list about a dozen style issues specific to a VQS, but you get the idea.)

Flowers for AlgernonOf course, what you’re writing should determine how much of the above is required. If you’re writing a novel much of this may not apply at all. Consider the book, Flowers for Algernon by Daniel Keyes. The book’s first person narrator is a retarded man. The book is in journal format and the first few chapters are so full of spelling and punctuation errors (or omissions) that the book is difficult to read. But that’s because of the author’s choices and the method he uses to communicate. Would you expect a retarded man to have perfect spelling, grammar, and punctuation? Of course not. The author is using the character’s shortcomings as a writer to make his character more real — as well a to drive home the changes in the character as the story progresses. This technique was used again more recently in The Curious Incident of the Dog in the Night-Time, which featured an autistic first-person narrator. If a copy editor had done a thorough job on the grammar or punctuation in either of these two books, he would have altered the characters. The same can be said for dialog in most novels, since few people speak using perfect grammar.

So copy editing of fiction is a different subject — one I’m not addressing here. I’m discussing copy editing of non-fiction, primarily technical or how-to books, since that’s where my experience is.

More to Come…

This is the first part of my discussion of copy editing. There are at least two more parts to go. In the next part, I’ll rant a bit about my experiences with one particular book over the ten-year course of its life (so far). You’d think that after 10 years, the process would be trouble-free…

Why not take a moment to tell us what you think copy editing should be. How do you expect it to change or improve your writing? Use the comments link or form to share your thoughts.