X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2999" "Tue" "4" "May" "93" "13:19:22" "BST" "Mike Piff" "M.Piff@SHEFFIELD.AC.UK" nil "61" "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 AA27332; Tue, 4 May 93 16:09:29 +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 AA22466; Tue, 4 May 93 16:09:23 +0200 Message-Id: <9305041409.AA22466@sc.zib-berlin.dbp.de> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 4504; Tue, 04 May 93 14:47:39 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 3584; Tue, 04 May 93 14:47:37 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 3581; Tue, 04 May 93 14:47:34 CET Reply-To: Mailing list for the LaTeX3 project Date: Tue, 4 May 93 13:19:22 BST From: Mike Piff Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Subject: Re: documentstyle option versions Status: R X-Status: X-Keywords: X-UID: 1035 %>From: Cameron Smith %>Subject: Re: documentstyle option versions %> %> %>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. %> I think that you have just denied one of the main reasons for using TeX rather than its lesser cousins. If you produce a conference proceedings in LaTeX, you don't expect your publisher to print the bible instead. I think there is an important distinction between form=spacing and content=actual printing symbols to be made here. LaTeX can have a free- for-all over form, but certainly not over content. %>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. %> There are possibly several different things going on here: (a) Publisher's macros change spacing, chapter startup, etc. Acceptable. (b) Publisher changes text style, but always substitutes like characters for like. Less acceptable, eg, in quotations which no longer stand out. Possibly the publisher has not thought long and hard enough about all the possibilities that could occur when he \let\it=\rm. (c) Publisher incompetently substitutes Times roman, say, for computer modern roman, and does not substitute like characters for like. Totally unacceptable, you should't need to have to proof read for this sort of bungling. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Dr M J Piff %% e-mail: %% Department of Pure Mathematics %% %% University of Sheffield %% M.Piff@sheffield.ac.uk %% Hicks Building %% PM1MJP@derwent.shef.ac.uk %% Hounsfield Road %% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% SHEFFIELD S3 7RH %% Telephone: (0742) 824431 %% England %% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%