X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2848" "Tue" "4" "May" "93" "13:04:19" "BST" "K.Lyle@SHEFFIELD.AC.UK" "K.Lyle@SHEFFIELD.AC.UK" nil "65" "Re: documentstyle option versions" "^Date:" nil nil "5"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/1.9.92 ) id AA27086; Tue, 4 May 93 14:21:57 +0200 Received: from vm.urz.Uni-Heidelberg.de (vm.hd-net.uni-heidelberg.de) by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/04.05.93) id AA21785; Tue, 4 May 93 14:21:53 +0200 Message-Id: <9305041221.AA21785@sc.zib-berlin.dbp.de> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 4477; Tue, 04 May 93 14:21:26 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 3454; Tue, 04 May 93 14:21:21 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 3452; Tue, 04 May 93 14:21:18 CET Reply-To: Mailing list for the LaTeX3 project Date: Tue, 4 May 93 13:04:19 BST From: K.Lyle@SHEFFIELD.AC.UK Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Subject: Re: documentstyle option versions Status: R X-Status: X-Keywords: X-UID: 1034 > Date: Mon, 3 May 93 16:01:30 -0500 > Reply-to: Mailing list for the LaTeX3 project > From: Cameron Smith > Subject: Re: documentstyle option versions > To: Multiple Recipients of > > Michael Downes writes: > > Here's a hypothesis: If you submit a document to a publisher in .tex > > form rather than .dvi form, either the publisher must be able to > > replicate your LaTeX system exactly (TeX version, LaTeX version+date, > > versions of all documentstyle options), or the document must be > > re-proofread word for word after it has been run through the > > publisher's in-house processing. > > > The intent of my postings is not to claim that the above hypothesis is > > correct (maybe it is, maybe it isn't) but to provoke discussion of > > ways to make the interchange process more failsafe. > > Since I went on at some length yesterday, I'll be brief today. > I think the hypothesis is true. The document must be re-proofread. > (In fact, I think it must be proofread even if the publisher *can* > replicate the author's setup.) I have never thought otherwise, > and I'm surprised to learn that other people do. > > Michael's specific examples of things that might slip through include > all the \cite's being omitted, or all (somethings -- minuses?) being > changed to \Gamma's. I'm amazed that anyone might have so much > confidence in the portability of LaTeX source that their proofing > would be so cursory as to overlook this. > > Again, this is IMHO -- I don't claim to have any theorems on this subject. > --Cameron Smith Computers and computer-aided typesetting are wonderful, but no system I know of obviates the need for proofreading. The author should have read the typescript carefully before it goes to the publisher/typesetter/whoever, so that s/he has confidence in the *.tex file. Then at the final stage, someone has to check that it has come out as intended, reading against copy to check for omissions etc., cross-references, running heads, page breaks .... Ideally this last read should be undertaken by someone coming fresh to the material, which by this time will be too familiar to the authors and editors involved. The path from author's brain to printed page is a long one, and disaster can strike at any stage along the way! As a freelance copyeditor and proofreader I have a vested interest, of course, but I think that anyone with much experience of the publishing process will agree. ====================================================================== Kathleen M. Lyle Technical Editor, Applied Probability Trust, Hicks Building, The University, Sheffield S3 7RH, UK Phone +742 824269 Fax +742 729782 ======================================================================