X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2527" "Fri" "11" "February" "1994" "09:27:43" "LCL" "Mike Piff" "M.Piff@sheffield.ac.uk" "<199402110936.AA17610@mail.cs.tu-berlin.de>" "59" "Re: On compatibility in LaTeX2e [was: Re: keyed options lis" "^Date:" nil nil "2" "1994021109:27:43" "On compatibility in LaTeX2e [was: Re: keyed options lis" nil nil]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA20128; Fri, 11 Feb 94 10:37:11 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA06592; Fri, 11 Feb 94 10:36:21 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA17610 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Fri, 11 Feb 1994 10:36:19 +0100 Message-Id: <199402110936.AA17610@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 1693; Fri, 11 Feb 94 10:36:06 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 1692; Fri, 11 Feb 1994 10:36:05 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 2916; Fri, 11 Feb 1994 10:35:28 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Fri, 11 Feb 1994 09:27:43 LCL From: Mike Piff Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: On compatibility in LaTeX2e [was: Re: keyed options lis Status: R X-Status: X-Keywords: X-UID: 1534 From: David Carlisle %> %>Mike, I seem to remember in some earlier messages you commenting on %>lack of compatibility in certain areas, then in your last message you %>say: %> %>> What I had expected was that you would keep the interface constant, %>> but include your nice verbatim, array, theorem, etc, extensions as %>> standard. %> %>The Mainz packages are incompatible with original LaTeX. If we had %>just put them in the core then old documents would break. Producing %>errors where before there was no error (verbatim) producing different %>spacing (array). %> The problem I know about with verbatim is that you can't say \end{verbatim} more text... and I am pretty sure that few people would have anyway. A problem I used to have with 209 was that I *had* to write vvvvvv\end{verbatim} to stop an ugly gap after the verbatim. Perhaps you know of other problems. I was not aware of spacing problems with array.sty. My users were happily using it until it conflicted with someone's publisher's style file, so I had to remove it. Were the spacing problems insurmountable? %>The ONLY point to the new \documentclass command is that it leaves %>\documentstyle to run old documents. We have spent hours trying to %>ensure that as far as possible a document starting with \documentstyle %>works as before. %> Hours probably wasted, in that the problem would never have arisen if this decision about clopages had not been taken? Was there much consultation on this list about this one? I am afraid I may have missed it if there was. %>So you are quite free to use \documentstyle, but be aware that as far %>as possible we will try to ensure that those documents will also work %>at a site that is still running 2.09. So most of the new features are %>disabled. %> But the implication is that you are actively encouraging users to convert their styles to clopages. Is there a guarantee that any pyle will work unadulterated with \documentstyle? I certainly haven't seen one; quite the opposite, in fact. The implication is that \documentclass will take over from \documentstyle, and that new styles will have to conform to the clockage format. With hard-wired limited options? %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Dr M J Piff, School of Mathematics and Statistics, University of %% %% Sheffield, UK. e-mail: M.Piff@sheffield.ac.uk %% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%