X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2057" "Thu" "10" "February" "1994" "20:49:00" "+0100" "Frank Poppe" "POPPE@swov.nl" "<199402101948.AA29755@mail.cs.tu-berlin.de>" "39" "Re: On compatibility in LaTeX2e [was: Re: keyed options lis" "^Date:" nil nil "2" "1994021019:49:00" "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 AA18408; Thu, 10 Feb 94 20:49:55 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA04196; Thu, 10 Feb 94 20:49:00 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA29755 (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 20:48:57 +0100 Message-Id: <199402101948.AA29755@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 6077; Thu, 10 Feb 94 20:48:46 +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 6076; Thu, 10 Feb 1994 20:48:46 +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 1461; Thu, 10 Feb 1994 20:48:13 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Thu, 10 Feb 1994 20:49:00 +0100 From: Frank Poppe 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: 1527 I think the discussion compatibility should focus on LaTeX3, not on (what should have been done with) LaTeX2e. I'm happy to accept that LaTeX2e will not change, but it's (Beta-)release can start new discussions on LaTeX3-issues (after all, this is called a discussion list for the LATEX3 project...). What I have been missing in some notes is the distinction between compatiblity for style designers and maintainers, and compatibility for users. It seems we'll have to accept quite some changes in the way styles (packages/options/classes...) can "hook into" the LaTeX code. That may be a point of concern in itself, but compatibility towards the users seems more important to me. In the coming years users will be forced (eg by local style designers who want to use possibilities of LaTeX2e) to switch to \documentclass syntax and other "new" commands. If LaTeX3 would force them to yet another command that would give LaTeX (and possibly TeX) a "bad name". Although using the same command with a new syntax would be even worse then a new command, a syntax that would be "upwards compatible" should be the goal. That's why my suggestion for a keyed option list was in the form \command[[key1]value1[key2]value2]{required} and not \command[key1=value1,key2=value2]{required} because the latter would mean that using a = in the "old fashioned" syntax would wreck the whole run. My suggestion makes it impossible to start an "old fashioned" optional value with [, but I don't even know if that is possible right now. But let us stop discuss what should have been done with LaTeX2e. _____________________________________________________________________________ Frank Poppe tel: +31 70 3209323 Institute for Road Safety Research SWOV fax: +31 70 3201261 ,,, ,, ,, ,, .... ,, ,, mail: PO Box 170 ||,,, || || || :: :: || || 2260 AD Leidschendam ,,,|~ ||,'|,~ :: :' ||,~ the Netherlands