Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Proofreading
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Professional== ===Traditional method=== [[File:Historical sketch of Posey County, Indiana - DPLA - 195d919570db0bda5f26f016757a9014 (page 14).jpg|thumb|A galley proof]] A "galley proof" (familiarly, "a proof") is a [[Typesetting|typeset]] version of [[Copy (publishing)|copy]] or a [[Manuscript (publishing)|manuscript]] [[document]]. It may contain [[typographical error]]s ("printer's errors"), as a result of human error during typesetting. Traditionally, a proofreader looks at a portion of text on the copy, compares it to the corresponding typeset portion, and then marks any errors (sometimes called "line edits") using [[List of proofreader's marks|standard proofreaders' marks]].<ref>{{Cite web |url=http://www.merriam-webster.com/mw/table/proofrea.htm |title=Proofreaders' Marks |access-date=2009-06-16 |archive-date=2010-08-16 |archive-url=https://web.archive.org/web/20100816210104/http://www.merriam-webster.com/mw/table/proofrea.htm |url-status=dead }} from [[Merriam Webster]]</ref> Unlike [[copy editing]], the defining procedure of a proofreading service is to work directly with two sets of information at the same time. Proofs are then returned to the typesetter for correction. Correction-cycle proofs will typically have one descriptive term, such as "bounce", "bump", or "revise" unique to the department or organization and used for clarity to the strict exclusion of any other.{{cn|date=April 2025}} ===Alternative methods=== "Copy holding" or "copy reading" employs two readers per proof. The first reads the text aloud literally as it appears, usually at a comparatively fast but uniform rate. The second reader follows along and marks any pertinent differences between what is read and what was typeset. This method is appropriate for large quantities of [[boilerplate text]] where it is assumed that there will be comparatively few mistakes. Experienced copy holders employ various [[code]]s and verbal shortcuts that accompany their reading. The spoken word "digits", for example, means that the numbers about to be read are not words spelled out; and "in a hole" can mean that the upcoming segment of text is within [[parentheses]]. "Bang" means an [[exclamation point]]. A "thump" or "screamer" made with a finger on the table represents the [[List of typographic features|initial cap]], [[comma]], [[Full stop|period]], or similar obvious attribute being read simultaneously. Thus the line of text "''(He said the address was 1234 Central Blvd., and to hurry!)''" would be read aloud as "''in a hole'' [thump] ''he said the address was digits 1 2 3 4'' [thump] ''central'' [thump] ''buluhvuhd'' [thump] ''comma and to hurry bang''". Mutual understanding is the only guiding principle, so codes evolve as opportunity permits. In the above example, two thumps after ''buluhvuhd'' might be acceptable to proofreaders familiar with the text. "Double reading" is when a single proofreader checks a proof in the traditional manner and then another reader repeats the process. Both initial the proof. With both copy holding and double reading, responsibility for a given proof is necessarily shared by the two proofreaders. "Scanning" is used to check a proof without reading it word for word, has become common with computerization of typesetting and the popularization of [[Word processor|word processing]]. Many publishers have their own proprietary typesetting systems,<ref>See 1983 {{cite web |title=Company timeline |url=http://www.bowne.com/about/timeline.asp |url-status=dead |archive-url=https://web.archive.org/web/20100429014855/http://www.bowne.com/about/timeline.asp |archive-date=April 29, 2010 }}</ref> while their customers use more common commercial programs. Before the original data can be published, it must be converted into a format used by the publisher. The end product is usually called a ''conversion''. If a customer has already proofread the contents of a file before submitting it to a publisher, there will be no reason for another proofreader to re-read it from the copy (although this additional service may be requested and paid for). Instead, the publisher is held responsible only for formatting errors, such as typeface, page width, and alignment of [[Column (typography)|columns]] in [[Table (database)|tables]]; and production errors such as text inadvertently deleted. To simplify matters further, a given conversion will usually be assigned a specific [[Template (file format)|template]]. ===Checklists=== Proofreaders are expected to be consistently accurate by default because they occupy the last stage of typographic production before [[publication]]. Checklists are common in proof-rooms where there is sufficient uniformity of product to distil some or all of its components into a list. They may also act as a training tool for new hires. Checklists are never comprehensive, however: proofreaders still have to find all mistakes that are ''not'' mentioned or described, thus limiting their usefulness.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)