If I'm going to hire a copyeditor, do I need to do any proofing myself?
For my book I'm planning to self-pub, I aim to hire a copyeditor / proofreader at some point.
The question is this: Should I do any proofreading myself, other than using a spell checker? Currently, my eyes hurt from trying to find small mistakes (things using 'their' for 'there' etc).
I'm wondering if there is any harm in just throwing the whole thing over to someone else?
Is there an advantage in me doing a typo edit pass myself? I mean, will it help reduce cost (as I've done a lot of work myself), or make the quality better (as 2 people have gone over the text)?
This post was sourced from https://writers.stackexchange.com/q/6074. It is licensed under CC BY-SA 3.0.
2 answers
Nobody is perfect, not even proofreaders. But first, let's get some terminology straight:
Copyediting is a catch-all term for editors who revise, make changes and suggestions, and so on. Of course, as editors go along, we mark up any typos they find on the proofreading level. But it's not the focus of this pass. We'll catch as many errors as we can, but at this point, we're looking to make the work read better while preserving the writer's voice.
Proofreading is done after copyediting, with the intent of catching all errors that absolutely cannot make it into print. It should be a separate pass from editing, Since a writer has to accept or reject the editor's changes, this process can actually introduce typos. This is, of course, despite the fact that editors never make mistakes.
In the world of self-publishing and small presses, these two steps are often combined. This results in more typos.
The dirty little secret of the editing world is that, in any work that's long enough, despite our very best efforts, there will be typos that weren't caught. There will be places where someone made a last-minute change in the post-galley stage, or a proofreader simply didn't catch something. This is why writers with a large following often enlist the aid of readers to catch typos, often many of them at the same time. This is also the case with writers who are working with large publishing houses. I've even seen writers who will specifically ask readers who bought the hardcover to email in any typos they found.
So, if it's important to you that your work be as close to error-free as possible, I suggest always checking a proofreader's work. It's not insulting or a slight on their professionalism. Enlist the help of some friends who will go on a typo hunt. If you have the budget, hire a second proofreader.
Even if all you do is catch one or two typos, multiple layers of editing and proofreading is a big help and makes your book look more professional.
0 comment threads
Generally speaking, this is a perfect job for a proofreader, so there's not much point in you trying to "double up" with a professional. There might be some minor cost difference if they charge by hour, but I would guess it to be negligible - the effort is less in fixing errors once found, and more in carefully going over the entire text, to find the errors.
Some provisos and qualifications, though:
- If you're not 100% certain of the proofreader, definitely look again once he's finished and make sure he's done a reasonable job.
- What shape is your ms. in, proofreading-wise? You'll only want to pay once, for one editing - on the absolutely final text. No point in paying for copyediting of something that might change entirely! However, before you get to that point, you will want outside feedback - writing groups, critique circles, feedback from friends, hiring an editor - and for them, you should have something that's not too riddled with errors. Critiquing a piece full of obvious errors is very tough; they're distracting and they give an amateur feel - even if they're sure to be corrected later in the process. So, if you've got a lot of minor errors, it's worth cleaning up on your own before any round of feedback.
- Some writers just like their writing to be pretty clean, and put effort into keeping down blatant errors even when it's not strictly necessary. Obviously, this is a matter of personal preference. It certainly doesn't hurt - and many will say that basic concern for "correctness" correlates with good command of the language.
0 comment threads