Understandably, time is a key factor, but I would still strongly urge your publisher to send you color pre-prints of the article with everything in place after the layout is done. The only things that should be missing in this proof would be page numbers and spots for advertizing if the articles are not entirely full pages. In addition to catching typos, errors, and other weird things that might happen when they import your electronic text into their layout, there can sometimes be problems with colors and backgrounds to make the article unreadable (eg, using black on dark red or blue, which might look good on screen or printing in b&w, but falls apart in CMYK printing. The cost of overnighting these few sheets and the day or two turnaround to proof is more than outweighed than the embrassment to both the author and publisher for such mistakes.

(This advice isn't just for merlyn, but for anyone that is publishing articles in computer magazines).

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
It's not what you know, but knowing how to find it if you don't know that's important

In reply to Re: Re: No Proofs/Pre-prints? by Masem
in thread How to avoid being mangled in Print by dws

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.