[QUOTE=Bosstone]
(Links go to Wiki)
Proofreading is simply checking a document for factual errors in spelling, punctuation, and a couple other things depending on the job. Depending on the job, it might entail looking for grammatical errors as well.
Editing is a bit broader, and involves manipulating content such that it’s presentable. Editors make decisions about what does or doesn’t see print, arrange text and graphics in particular fashions, and the like.
[/QUOTE]
Not necessarily. In my world (book publishing, and these are general observations; YMMV):
Editing (or, more specifically, copyediting) involves the hands-on mechanical correction of grammar/usage/spelling/consistency and so on. It involves working directly with the manuscript, either on paper or in the electronic (usually Word) file. Some minor fact-checking may be involved. You ensure consistent treatment of references/bibliography, art numbering/labeling, styles of heads and other elements, number style, actual text content against the TOC/chapter objectives/summary, etc. etc. If author says we are going to discuss X, Y, and Z, you make sure he does so in that order (unless there’s a compelling reason not to) and doesn’t leave out Y, and you query if he goes into X and Y in detail but only touches on Z, or if perhaps he might like to talk about W as well. Does Figure 13 show what he says it does? Does this column of numbers sum correctly? Are list items in parallel construction (all questions, sentences, or fragments/initial cap or lowercase/closing period or not)? And on and on.
The edited file goes to typesetting/composition, and then . . .
Proofreading involves comparing the typeset pages to the original edited manuscript to see that the compositor set the text according to the instructions on manuscript. This generally involves a word-for-word read of Ms. against proofs as well as checking the pages visually against sample design pages or written specs: are the fonts correct, do things align as they should, are the dingbats correct, is art placed properly, are running heads correct, etc. A good proofreader also wears the copyeditor hat while reading, but the object here is to keep editorial changes to a minimum, generally correcting/querying only outright errors. The proofreader’s job is not to second-guess the copyeditor’s overall decisions, but only to catch goofs.
I know I’ve gone into this in more detail elsewhere, but I’m on deadline today (
) and don’t have time to search. If you search on my handle and “copyediting” you should find a bunch of stuff.
Recommended books for newbies:
The Copyeditor’s Handbook, by Amy Einsohn
Copyediting: A Practical Guide, by Karen Judd
You might also consider joining the Copyediting-L mailing list. Googling should turn up the link.
The USDA (yes, Department of Agriculture) correspondence course in copyediting has a good rep. (I’ve never taken it.)