X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["4653" "Wed" "26" "January" "1994" "16:49:23" "CST" "George D. Greenwade" "bed_gdg@SHSU.EDU" "<199401262316.AA18264@mail.cs.tu-berlin.de>" "82" "Re: Changing default preloads" "^Date:" nil nil "1" "1994012622:49:23" "Changing default preloads" (number " " mark " George D. Greenwa Jan 26 82/4653 " thread-indent "\"Re: Changing default preloads\"\n") nil]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA10424; Thu, 27 Jan 94 00:16:25 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA29900; Thu, 27 Jan 94 00:16:24 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA18264 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Thu, 27 Jan 1994 00:16:19 +0100 Message-Id: <199401262316.AA18264@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 6754; Thu, 27 Jan 94 00:16:10 +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 6749; Thu, 27 Jan 1994 00:16:09 +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 3268; Thu, 27 Jan 1994 00:15:06 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Wed, 26 Jan 1994 16:49:23 CST From: "George D. Greenwade" Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Changing default preloads Status: R X-Status: X-Keywords: X-UID: 1318 On Wed, 26 Jan 1994 16:35:21 LCL, Mike Piff posted: > Most likely everyone will object to using anything *other* than > \documentstyle, and it seems to me that there are going to be an endlessly > growing list of parameter declarations (call them classes if you like) that > everyone will need to use at their site. This is getting like Ada and > Modula- 2 programming, where you need to declare packages and identifiers > from packages all over the place to make things work. Agreed. The more things are changed, the more likely people will be alienated. Over time, they may become concordant with the new designs, but I feel sure that more than a few people will object to what they believe they've learned to be "standard" LaTeX. Why? Mainly because the learning curve begins anew. > Is there no mechansism to allow options to be pre-loaded at iniTeX stage, > and then to get these options to announce themselves to you whenever you > LaTeX something? Most users wouldn't need to worry about these details > then. Their paper would be A4, language English, date day/month/year, time > 12hr clock, font encoding OT1, currency symbol pounds, etc. > > I am now in favour of a more open approach to LaTeX. Make everything > general enough to do almost anything, ban @ in control words, and let > anyone redefine any ``internal'' control word he likes if it makes things > work. This is the funny edge all of TeX is -- or at least seems to me to be -- walking on. Can any package be everything to everyone? No; indeed most products attempting to meet this goal end up being nothing to anyone. The easier it is for an everyday user to type in: \i-wanna-begin-my-text [text deleted] \done--print-this-darn-thing for the majority of their documents, the better. After all, LaTeX is merely a product which creates very nice output {\em without} having to "do TeX" in the eyes of many, if not most, users. Certainly, this is not the case in the sense of the developers and most of the people who will eventually read this, but it has to be admitted that the developers and readers of this post are in the significant minority among LaTeX users. If any product gets too complex or changes too radically too quickly, people will switch to something else. The idea of extensibility is great -- so long as you only have to deal with the pains of extensibility when you want to extend something. Should the ideas going into LaTeX3 be dropped? {\em NO,} good lord, there are too many good ideas already under works! Should all of the ideas going into LaTeX3 be something all users have to deal with everytime they want to create a document? {\em NO!} That is, unless the goal is to create a less user-friendly atmosphere or to create a product used by technocrats -- very likely the minority of all present LaTeX users -- who are seeking to amaze and amuse their colleagues with how neat it is, or if the goal is for the developers to "gee whiz" each other with their elegant approaches which, in reality, cause nothing but headaches for end users who have no use for their wizardry. In the alternative, should there be good, readily available, supported, documented, easily interfacable, and official extensions allowing for the varied typographical needs of users in different fields and languages which may optionally be used when needed (note that this means some users will be enabled to view the quirks of English as the optional language) -- and not otherwise addressed, nor necessarily even learned by users -- to improve the product? {\em PRECISELY!} I sincerely hope that this is the general direction this is headed. The fewer the keystrokes between: \I-have-to-type-in-all-of-this-preamble-garbage and whatever equivalent to: \bye are required, the more welcomed this upgrade of LaTeX will be received. The reception by users, moreso than the wizardry of what can be imposed upon everyone, is what ought to be addressed, IMO. Enough normativism from a naive everyday LaTeX user. Regards, George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Bitnet: BED_GDG@SHSU Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 P. O. Box 2118 FAX: (409) 294-3612 Sam Houston State University Internet: bed_gdg@SHSU.edu Huntsville, TX 77341 bed_gdg%SHSU.decnet@relay.the.net %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%