Normally, initial typesetting of your book will not take too long, especially if no attempt is made to finalize the pagination of the book (for instance, no illustrations yet placed in the document).
As we have seen earlier, the result of the initial typesetting is a set of first proofs delivered to the production editor. These proofs will be quickly checked then your production editor will send you a copy for proof-reading. At the same time, chances are that someone at the press or an outside professional proof-reader will check this first proof as well.
About the first proof
The proof received will almost certainly be typeset text output on ordinary pages (described and illustrated here) rather than the galleys of yesteryear. In all probability, these page proofs will not have been finally paginated (essentially because the illustrations are missing and some changes to the text are expected). In addition, as pointed out in Leena’s mail above, much else about the proof indicates that it is a preliminary version of your book. For example:
- The running heads are incorrect or non-existent.
- The text will likely be loose in places (any hyphenation or massaging of the character spacing yet to be done).
- Text may not completely fill the page so that page bottoms in a two-page spread are not lined up.
- Tables may straddle two pages.
- Figures and illustrations may be missing (though, as illustrated in my previous post, space may have been reserved for these).
- Any ‘hard’ cross-references (like ‘see overleaf’, ‘see page 43’, etc.) should be flagged as provisional.
On the other hand, you should expect something more than a picture of the typesetting in its raw, newly converted state. In particular:
- The book/page design should be apparent in the page layout (e.g. trimmed page size and fonts are correct).
- Paragraph (and character) styles should have been implemented in the text.
Your primary task
What your production editor will be expecting you to do in quite a short time is carefully to go through the proofs, marking up any changes required. (My next post describes marking up in greater detail while the subsequent post lists the common proofing marks used in printing and publishing.)
Mainly, you should look for problems in the text, examples being:
- Corruptions in the text (perhaps caused by the text conversion problems described a month ago and again more recently).
- Missing text.
- Incorrectly formatted text (e.g. missing italics).
- Paragraph appearance is inappropriate (possibly due to incorrect assignment of paragraph style).
Of course, you may wish to request other changes that have nothing to do with errors in the text. This is a problematic issue that I shall discuss in a separate post later this week.
Proofing with the other side of the brain
In addition – although the lack of illustrations, final formatting, etc. may force you to stretch your imagination somewhat – now is probably the last moment when you can comment on the page design and request changes. (Unfortunately, for most authors it is also the first time that they have seen how the publisher intends to layout their book – so this is a last-gasp thing I am foisting upon you. Indeed, it is probably too late for you to make a similar ‘right-brain’ assessment with the final proofs that I suggest in an upcoming post.)
While it is unlikely that you can get your publisher to completely change the page design presented to you, there is a chance that you can convince your production editor to make some changes. For instance, if you can demonstrate that the fonts used evoke a mood/approach at odds with (your treatment of) the subject, then it need not be too late for such a systematic change to be implemented.
Be smart, however, in what you request. You’ll have a greater chance of agreement to global changes that can be implemented relatively easily rather than to custom changes that must be made on a case-by-case basis.
There are different ways of noting your proofing changes/corrections; these I describe in my next post. If you choose to mark up the proofs received from your publisher, then make sure that you save a copy of what you send back. This will be your reference at the final-proof stage, ensuring it is quick to check that the changes you requested have been implemented.