X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["3178" "Thu" "10" "February" "1994" "13:53:13" "+0100" "Rainer Schoepf" "schoepf@SC" "<199402101334.AA20866@mail.cs.tu-berlin.de>" "71" "On compatibility in LaTeX2e [was: Re: keyed options lists]" "^Date:" nil nil "2" "1994021012:53:13" "On compatibility in LaTeX2e [was: Re: keyed options lists]" nil "<199402101205.AA18275@mail.cs.tu-berlin.de>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA14155; Thu, 10 Feb 94 14:34:43 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA01637; Thu, 10 Feb 94 14:34:41 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA20866 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Thu, 10 Feb 1994 14:34:39 +0100 Message-Id: <199402101334.AA20866@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 3946; Thu, 10 Feb 94 14:34:28 +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 3945; Thu, 10 Feb 1994 14:34:28 +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 9745; Thu, 10 Feb 1994 13:54:53 +0000 Reply-To: Mailing list for the LaTeX3 project Organization: Konrad-Zuse-Zentrum fuer Informationstechnik Berlin In-Reply-To: <199402101205.AA18275@mail.cs.tu-berlin.de> Date: Thu, 10 Feb 1994 13:53:13 +0100 From: Rainer Schoepf Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: On compatibility in LaTeX2e [was: Re: keyed options lists] Status: R X-Status: X-Keywords: X-UID: 1513 Alex Stark writes: > I personally like the > \section[mark=short, ...]{full} > syntax. Apart from anything else, as commands include increasing number of > options the assignment format should make them less confusing. Yes, definitely. I think that previous messages to this mailing list have made clear that this is something for LaTeX3, not for LaTeX2e. As David Carlisle pointed out, of one the key issues for version 2e was *compatibility*, and that means, among other things, *not to introduce new syntax*. Therefore, Mike Piff's remark in reply to David's message: David> %> David> %>key=value is definitely not a standard convention of 2.09. David> %> > I don't follow this argument. \documentstyle can keep its old syntax, but > \documentclass is outside LaTeX209 and can do what it likes. Similarly > \...package... commands are entirely new. is besides the point. \documentclass, as well as any other new command, has to conform to the syntax rules laid down for LaTeX2. Anyone who likes to maintain that this decision was not correct is welcome to do so, but it is not going to be changed. LaTeX2$_{\textstyle\varepsilon}$ (which is what the logo actually looks like, and which should be immediately comprehensible to the mathematically trained) is only a minor step forward. Those of you who remember the time when the LaTeX3 project was born will also remember that we wanted to produce LaTeX 2.10 then, as an intermediate step towards LaTeX3. This idea was abandoned, since we thought that it would be better not to try to patch the holes in the existing software, but rather concentrate on writing the new system LaTeX3. However, the proliferation of mutually incompatible systems which were all called LaTeX -- a development for which some of us were partially responsible -- persuaded us that it would be vital for the survival of LaTeX and for its further development to have a unique version, upon which the whole (La)TeX world can build. So, in some sense we have been coming back to the original idea. This means that some obvious mistakes and omissions in LaTeX 2.09 were corrected for LaTeX2e, but nothing really new has been added nor will be added. It should also be noted that during the work on LaTeX2e practically no time was left for working on LaTeX3. When we decided in favour of LaTeX2e, it was rather clear to us that this would postpone completion of LaTeX3 for an extra half year. By now, this half year is over, and LaTeX2e is not yet finally released; therefore my estimate is more like a full year lost. I don't want to leave you with the impressions that we are not interested in discussions on what is bad and can be improved and how. We appreciate them. But it should be clear that this is for the future development of LaTeX3. I invite everyone to find out more, by looking into the LaTeX3 public library, which is on the ftp server niord.shsu.edu in directory [FILESERV.LTX3PUB]. For the LaTeX3 project Rainer Schoepf Konrad-Zuse-Zentrum fuer Informationstechnik Berlin Heilbronner Strasse 10 D-10711 Berlin Germany or