We're copyediting! It occurs to me that we (by which I mostly mean, *ahem* my coauthor) would benefit from an overview of copyediting marks. So I searched the web and found a couple of references. (Okay, I admit I'd actually forgotten some of them myself. It's been a very long time.)
http://bfa.sdsu.edu/editorial/copyediting.htm has most of the common ones that we're likely to use.
http://www.wiley.com/legacy/authors/guidelines/stmguides/4-fig1.htm is a more complete, less friendly reference.
In addition to these, I tend to indicate that I want to move a block by bracketing it [ ] and drawing an arrow. Circled words most often mean "tt format", for command or file names. Transposition is indicated with an s-curve between and around the items to switch.
We don't have to be precise, since all the paper markup we're doing is just for scratch. But there's no reason not to use a standard system. It's like terminating your UTP cables with the correct scheme, rather than just taking any two pairs.
http://bfa.sdsu.edu/editorial/copyediting.htm has most of the common ones that we're likely to use.
http://www.wiley.com/legacy/authors/guidelines/stmguides/4-fig1.htm is a more complete, less friendly reference.
In addition to these, I tend to indicate that I want to move a block by bracketing it [ ] and drawing an arrow. Circled words most often mean "tt format", for command or file names. Transposition is indicated with an s-curve between and around the items to switch.
We don't have to be precise, since all the paper markup we're doing is just for scratch. But there's no reason not to use a standard system. It's like terminating your UTP cables with the correct scheme, rather than just taking any two pairs.
Leave a comment