X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1949" "Thu" "10" "February" "1994" "20:47:03" "+1100" "Kristoffer H. Rose" "kris@DIKU.DK" "<199402100949.AA14581@mail.cs.tu-berlin.de>" "48" "keyed options lists (Was: RE: A philosophical....)" "^Date:" nil nil "2" "1994021009:47:03" "keyed options lists (Was: RE: A philosophical....)" nil "<199402100925.AA09573@odin.diku.dk>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA12210; Thu, 10 Feb 94 10:49:13 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA29072; Thu, 10 Feb 94 10:49:12 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA14581 (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 10:49:08 +0100 Message-Id: <199402100949.AA14581@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 2552; Thu, 10 Feb 94 10:48:57 +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 2551; Thu, 10 Feb 1994 10:48:54 +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 9192; Thu, 10 Feb 1994 10:48:18 +0000 Reply-To: Mailing list for the LaTeX3 project Comments: Warning -- original Sender: tag was kris@ZEUS.MPCE.MQ.EDU.AU In-Reply-To: <199402100925.AA09573@odin.diku.dk> Date: Thu, 10 Feb 1994 20:47:03 +1100 From: "Kristoffer H. Rose" Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: keyed options lists (Was: RE: A philosophical....) Status: R X-Status: X-Keywords: X-UID: 1507 Frank Poppe writes: > I suggested a way out of this as reaction to the "new features" > discussion. I did not get any reaction so I fear something went wrong > with my mail. If this suggestion is a foolish one, please point it out > (people generally don't seem to hesitate pointing out the inadequateness > of reactions on this list..:-). I agree with David: this is not for LaTeX2e because LaTeX2e should be stable. Thus new features -- even simple ones -- should be left out. (IMO even the \documentclass thing should have been left out until LaTeX3 or at least it should explicitly have been an `experimental feature' such that its merits could have been discussed in depth here...). > Anyway, I'd suggest > \documentclass[[key1]value[key2]value]{article} .... > as well as >... > The syntax key=value is of course more natural, but is seems very > difficult to distinghuish that from the current syntax. IMO, no, since it just means you can't use `=' in option names where your suggestion means you can't use `[' in option names! In fact it is not particularly complicated to implement the option=value syntax. I still prefer that *for LaTeX3* because it is so nicely intuitive (in fact the notation is not only used in programming languages (teh first was PL/I, I think), but also SGML allows a similar syntax). I would prefer the `official' use of \section to be \section{full} \section[mark=short]{full} \section[mark=short, toc={longer, may contain =}]{full} *always* giving all options used, and allow \section[short]{full} as a default for backwards compatibility and/or convenience. -- Kristoffer Hxgsbro ROSE Internet: kris@diku.dk DIKU, U of Copenhagen, Universitetsparken 1, 2100 Kxbenhavn X, DANMARK phone: +45 35321400 direct: +45 35321420 fax: +45 35321401 -- World Wide Web URL: file://ftp.diku.dk/diku/users/kris/WWW/home.html