The Melody of Our Manuscripts

He always arrived in a rumpled brown suit and a wide, striped 1970s-style tie. He would bustle in the door of our apartment in Germany, run his stubby fingers through his mop of gray hair, say “guten Abend,” and sit down in the chair beside the piano bench.

And I duly took my place beside him on the bench.

We opened the book.

I had one piano book when I studied under Herr Mueller. Not a book for scales or a separate book to write in and draw the little notes on the staff and practice making the G-clef. I was way more advanced than that. I’d been taking piano since I could remember.

My piano book
My piano book

So when we arrived in Bonn, Germany, in my freshman year of high school, my parents set about finding a piano teacher.

And they found Herr Mueller.

I wish I knew his whole story. He had been the pianist for the some big orchestra in the United States. Thus, in his younger days, he had played in large concert halls to crowds of appreciative symphony goers. I’m sure he’d worn a tux and, when he approached the piano bench, had deftly tossed the tails behind him. He had been applauded.

And now, he sat beside a high school girl who didn’t appreciate that she was learning piano from a genius.

I ache to think of it.

We practiced from this one book–a big red book filled with music from the great composers. The cover and spine and title page are all missing, so I can’t even give the title. But when I sit down at the piano thirty years later and open the book to page 44, I can still play Beethoven’s “Adagio ‘Moonlight’ Sonata.” I can still play parts of “Fur Elise” (page 48) from memory.

When we opened to a new song that came from an opera, Herr Muller told me the story and where, in the opera, this song appeared. He told me how to play Edward Grieg’s, “Anitra’s Dance” (from Peer Gynt) based on the action at that point in the story, and he could hum every melody from the entire opera.

I think of those days now. I remember how I’d hold my breath when he leaned in close to scribble on the piano page and his bad breath floated into my nostrils. I remember how his stubby fingers flew across the keys. I remember how he loved, loved, loved the piano.

Herr Mueller's fingering notes on my piano page
Herr Mueller’s fingering notes on my piano page

If I could just take lessons from him now. These thirty years later I would cherish every word. I’d have a notebook beside me where I would write down the context of every melody he assigned just as he told it to me.

And I’d just offer him a breath mint and be done with it.

I worked hard for him. I practiced hard. I loved the piano too, for a time, even accompanying my high school chorus for a few programs.

Herr Mueller, I wish I could thank you. I’m sure you’re long gone from this world, but I thank you for your love of the piano and great music. I’m sure that some of my love for great literature comes from hearing Herr Muller tell me the great stories of the operas with unmatched passion. And the fact that I could accompany my high school chorus as they sang Bob Dylan’s, “The Times They Are A-Changin’,” was because I had pounded away at Bach and Verdi and Grieg and Tschaikowsky and Wagner.

The same is true for writers. We’re readers first for good reason. We read great literature (past and present) because it helps us with our craft. We read because we love love love the words on the pages–and we’re amazed when, like the music notes floating on the staffs, the words come together in a way that gives us goosebumps. We want to learn to make that happen in our own writing.

We’re creating a melody in our manuscripts.

I wish I had appreciated the privilege of studying under Herr Mueller. Likewise, I wish I had appreciated the time I spent reading the classics in my literature classes both in high school and college (this summer I’m rereading many of those classics that any self-respecting English major should be conversant about!).

Because now, I understand. Now I appreciate them.

Thank you, Herr Mueller.

Me at the piano with appreciative baby sister as my audience (ca. 1970).
Me at the piano with appreciative baby sister as my audience (ca. 1970).

Midwest Writers Workshop–Day 2

It’s the middle of day two of the Midwest Writers Workshop here in beautiful Muncie, Indiana.

Writers are scurrying from pitching an agent to a social media tutoring appointment to their next session from one of our amazing faculty to a manuscript makeover appointment to finding a bathroom to grabbing a snack to checking out the book table to heading to yet another session.

And that’s what it’s all about. Learning more about the craft that we all love.

We’re all here supporting one another as writers. Some with published books. Some with dreams of publishing. All with a passion for words.

That’s why I love it.

This place reeks with people who love words and writing. We’re all geeks sort of geeking out over words and how to put them together. This place reeks of geeks.

And it’s awesome.

There are lots of writers conferences, and I’m a strong proponent of all writers attending a conference for the continued training, support, and encouragement from other writers. I’m new on the planning committee for the Midwest Writers Workshop (we’re celebrating 40 years with this conference), and I’m amazed at how this team pulls together to make a great conference happen.

This year, Cathy Day and I worked together with some savvy Ball State students. Several of the students are acting as assistants for the five agents who are taking pitches, and the others are working in the social media lab giving one-on-one tutoring advice in the art of social media (websites, Twitter, Facebook pages, etc., etc.). Here’s a photo of our social media lab:

The social media lab with one-on-one tutoring about social media for writers
The social media lab with one-on-one tutoring about social media for writers

I’m sitting in the social media lab listening to the students talk about how great the attendees are, how they feel like they’ve both been able to teach something to their clients as well as learn something from them, and how they’re enjoying connecting with other writers. We’ve built in time for the students to attend a couple of workshop sessions as well.

We’re all in this writing life together.

And we’re having a perfectly awesome time.

You ought to think about attending next year!

Teaching Editing–A Little Grammar Goes a Long Way

I’ve still got my editing cap on this week. After my tiny proofreading tantrum a couple of weeks ago and completing those two jobs for the client–who now has books way more clean than they were before–I now turn to other editing endeavors.

Namely, revising my syllabus for my editing class over at Taylor U. This year the class will be twice a week instead of once a week, which has meant major revisions to the syllabus. And since this is the fourth time teaching this class, I’m getting a good feel for what works and what doesn’t.

Over the course of the semester, I want my students to try the three main forms of editing: content editing, copyediting, and proofreading–spending roughly a month on each. (Most of them come to class not understanding the differences between these roles, the different points in the book-making process when they happen, and the different skills required to do each job well. I describe the different roles in this blog post.)

I also try to give them “real world” experience. When we edit, I obtain a real manuscript from someone who willingly allows students to give feedback. When we proofread, I show them real pages that I’ve had to work on (“This really did almost go to print, guys, until I helped save it!”).

The one difficult part is helping them realize the tools they need to sharpen in their editing toolbox–namely, grammar. When I have mentioned that part of the syllabus in previous classes, there is an ever-so-slight collective groan. Then I assure them of two things: (1) we aren’t diagramming sentences, we’re just reviewing what they probably already know instinctively or helping them be sure of things they don’t know, and (2) I will give them candy. (It’s amazing what joy mini-candy bars bring when I toss them out for getting the correct answer. And the big bags are always available in October before Halloween when I usually hit this part of the syllabus. It’s a little Pavlovian, I admit. . . .)

The students are already pretty sharp, but I still need to at least show them the rules behind some general punctuation issues. I key in on:

  • quotations marks (single vs. double–and punctuation in and around)
  • parentheses and brackets (and punctuation in and around)
  • commas, colons, semi-colons
  • hyphens, en-dashes, em-dashes
  • capitalizations

Then, I give them copyediting practice on:

  • discerning active vs. passive voice
  • omitting needless words
  • making items parallel
  • using correct tenses
  • using correct modifiers
  • smoothing awkward sentences

I’m digging through some resources in order to create some good worksheet practice for each of these categories. While I train them to work on screen, I also teach them proofreading symbols and have them do some copyediting on hard copy as well.

So you copy editors and proofreaders out there–what are the most common errors you see? Pet peeves? What do I need to make sure my budding editors have in their toolboxes before they head out into the publishing world?

10 Grammar Saves in 10 Years

I have a guest post today from a fellow laborer in the salt mines of proofreading. Good thing she made these saves before the books went to print! It’s people like Stephanie who help keep me from getting angry, because she keeps those horrendous errors from ending up in the final product. Enjoy!

Stephanie Rische's avatarStephanie Rische

I’m not quite sure how I blinked and 10 years passed, but last month I woke up and realized it had been a whole decade since I jumped into the world of editing and publishing. It has been a good decade, and in honor of the mile marker, I thought I’d share with you 10 of the errors I’ve stopped from going into print over the past 10 years.

 

{Note: I have omitted the authors and titles of these books to protect the relevant parties, but rest assured, these are all real quotes from real books.}

grammar3

 

10. My daddy was a steal worker, and my granddaddy was a steal worker.

[Sounds like a kind of shady business to me.]

 

9. Gelatins 2:16 clearly states that human deeds can never save us.

[Shockingly, the book of Gelatins made it through spell-check but not canonization.]

 

8…

View original post 280 more words

Pages in the Hands of an Angry Editor

Thanks Nathan Sturgis for the title of this week’s blog, and thanks Jonathan Edwards for the sermon that inspired it.

Let me clarify, however. I’m not angry. I tend to be on a pretty even keel most of the time. Frustration is more the word than anger. Part of it is my own obsessive compulsive desire to get things right. A printed book should not have errors. That’s a given. So forgive me for a little anger when a document gets sent to the printer who then prints a book with blatant errors.

I just spent the last week proofreading two books for a publisher. One was printed with such blatant errors that I was hired to do a full proofread quickly so they can do a reprint and send new books to everyone who got the old error-ridden books. Somewhere along the line, someone dropped the ball. The other book was a revision with updated chapters replacing old chapters. Problem is, the new author didn’t take into account any kind of style issues from the old book. While the former book had endnotes in the standard superscripted numbers, the new chapters incorporated the notations within the text. Then there were the capitalization and other stylistic issues (Oxford commas, anyone?). Someone (that would be me) had to go through and make it all consistent.

Don’t get me wrong. I get kind of gleeful when I’m catching and cleaning up errors. I’m thrilled to standardize a book that’s in process. But when a book has been published and went “out there” for all the world to see (with, among other sins, a running header that had only one word from the title instead of the full title) . . . well, that just makes me angry.

Someone should have known better. But then I remember that I’ve had my share of times when I let something slip on by.

So much can go wrong. A Word document or pdf can get lost or corrupted. Changes don’t get saved. Someone picks up the wrong version and then the dominoes just keep falling. A lack of a clean template wreaks havoc  (oh my goodness, I wish everyone knew style tags). Edits get misplaced. A single page change gets forgotten. A change randomly requested by email gets waylaid.

It’s difficult to keep everything straight as files fly back and forth. Even with Dropbox and Google docs, the possibility of error remains high.

And if a busy editor gets the bluelines (the set of pages, in blue ink, sent from the printer to show exactly how the book will look when printed–it’s the last last last chance to make a change, and if you do, it’ll probably cost money) at a time when harried by another deadline, it’s tempting to do a quick scan and send it on its way.

And miss the fact that a word from the title that is supposed to appear on every verso running head is not there.

Arrgh!

It comes down to having a good project management system in place. It comes down to being organized. There are so many steps a manuscript goes through:

  1. The manuscript comes in as a Word doc from the author.
  2. The editor saves a new version and does an edit filled with queries for the author.
  3. The editor and author go back and forth with the electronic document, new versions made and saved each time.
  4. Once the manuscript is the way the author and editor want it, it goes to a copyeditor.
  5. The copyeditor makes a new electronic version and reads for clarity, consistency, correctness, and readability. Style tags are added at this point.
  6. That manuscript goes back and forth with queries to the author and/or the editor, and the copyeditor has to collate those changes (here’s a nice place for Google docs!).
  7. A final clean manuscript goes to the typesetter.
  8. The typesetter flows the manuscript into the designer’s template and creates a pdf.
  9. The pdf goes to the proofreader who marks corrections.
  10. The typesetter makes the corrections, but, not being an editorial person, often notoriously misinterprets the proofreader’s corrections (proofreaders need to be extremely clear!).
  11. The proofreader checks all of the corrections, sends another version of the pdf for corrections still to be made, and this goes back and forth.
  12. The typesetter then creates the final pdf that gets uploaded to the printer.

See how many places things can go wrong?

It comes down to being careful, being organized, being watchful. Even a little obsessive compulsive in order to get it right.

And then, after all that organization and care and watching, the printed book comes out.

And there’s always an error somewhere.

We do our best. That’s all we can do.