Proofreaders generally get baffled via the term 'reading through from duplicate', so on this page I will attempt to clarify exactly what the expression usually means.
There are two ways in which a proofreader could be requested to operate: possibly by examining against copy, or executing a straight (blind) looking through.
When she's questioned to browse versus copy, the proofreader will probably be offered Together with the writer's initial typescript (or a replica of the) While using the editor's corrections marked on it, and a set of proofs produced by the typesetter. The proofreader then compares the proofs Using the edited typescript, dealing with the two, phrase by phrase, line by line, making sure that the creator's text (together with any editorial amendments) has actually been faithfully rendered, without having glitches released within the typesetting phase.
When accomplishing a straight or blind reading, the proofreader will be supplied with proofs only and not the original typescript. In this case, the proofreader cannot know whether or not the original typescript continues to be properly reproduced along with the editor's corrections. Her function is simply to check the proofs for content, marking up any clear errors in spelling, punctuation, and so on, that she may find.
When reading versus duplicate, most proofreaders work by scanning some words and phrases of the first typescript, then examining to find out that these look appropriately within the proofs, with any editorial corrections correctly implemented. Where there is a difference (if, such as, an apostrophe has long been omitted), the proofreader implies this with the suitable mark.
For each correction, a single mark should be produced in the textual content alone and One more while in the margin. This can be carried out in order to ensure that, in the event the typesetter will come to incorporate the proofreader's corrections, he doesn't inadvertently skip over any of these.
Glitches created by the typesetter has to be highlighted with 1 color pen, issues because of the writer/copy editor with another. It's not so as to apportion blame, but to make a decision who must pay for the amendments. The conventional process of colour coding is shown down below:
Purple: That is used to show faults that have been introduced into your textual content through the typesetter.
Blue: This really is utilized to exhibit problems made by the creator and missed from the duplicate editor, and glitches made by the duplicate editor herself.
(Observe: some publishers choose black ink to blue -- you will be encouraged of this when you start Doing the job for them).
Inexperienced: This color is reserved with the typesetter's possess queries or corrections.
The cost of 'pink' corrections is going to be borne via the typesetter, while that of 'blue' corrections will probably be met via the publisher (or, in critical situations, the writer). Having a straight reading, certainly, you won't know whose accountability any mistakes may be. In this case, you can mark up all corrections in one shade (normally crimson).
As a freelance proofreader you are very likely to be made available far more straight readings than readings towards copy. This is due to the amended typescript is Ordinarily returned towards the copy editor for her to examine versus the proofs. The proofreader's purpose is regarded a lot more as giving again-up: a clean pair of eyes which can location evident blunders ignored by an editor jaded by more than-familiarity. Although the amended typescript can be copied and despatched on the proofreader also, in practice this is commonly felt by publishers being excessive korektura textu hassle. This will not be perfect, but it points out why proofreaders are more likely to be questioned to execute a straight reading in lieu of reading through against duplicate.