X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1805" "Tue" "9" "November" "93" "10:34:03" "+1100" "Richard Walker" "Richard.Walker@CS.ANU.EDU.AU" nil "45" "Administrator's nightmare" "^Date:" nil nil "11"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA07690; Tue, 9 Nov 93 00:36:32 +0100 Received: from vm.urz.Uni-Heidelberg.de (vm.hd-net.uni-heidelberg.de) by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA08865; Tue, 9 Nov 93 00:36:30 +0100 Message-Id: <9311082336.AA08865@sc.ZIB-Berlin.DE> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 1706; Tue, 09 Nov 93 00:35:10 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 6187; Tue, 09 Nov 93 00:35:03 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 6185; Tue, 09 Nov 93 00:35:01 CET Reply-To: Mailing list for the LaTeX3 project Date: Tue, 9 Nov 93 10:34:03 +1100 From: Richard Walker Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Subject: Administrator's nightmare Status: R X-Status: X-Keywords: X-UID: 1116 Hi all. My five cents (we got rid of our one and two cent coins a while back :-) ) As TeX expert for my department, I have to cope with an attitude of resistance towards all upgrades. So much so, that I now give two weeks notice of an upgrade (during which time the new software is available for trial), and the old version is provided for another two weeks after that. It would be quite impossible to force my users to start using LaTeX2e, or even just NFSS2, right away. They demand that critical software (such as LaTeX) must not be `interfered' with. But the issue for me is: how can I provide the functionality of 2.09 for those who don't want to move, and 2e for those that are willing? (And then there's the problem that if I provide both, no one will move to 2e.) There are files e.g. amsart.sty that are different for 2.09 and 2.09+NFSS2 (and 2e). As I see it, a solution would be to put the 2e-specific files in a separate directory (outside the normal TEXINPUTS hierarchy), and to make latex2e a shell script which sets TEXINPUTS such that the 2e-specific directory is searched before the normal inputs area. I am a bit concerned about the nf prefix too. Despite attempts to re-invent the meaning of the `nf' acronym, it seems like a hack (which it is). My users will not be impressed. I am trying to sell them the future of LaTeX, and they have to stick `nf' on the front of all their style options. Why? (My suggestion in the previous paragraph makes all this unnecessary, even in a multiple-LaTeX environment.) As an aside, in the light of the completely different structure of NFSS2, I am extremely relieved that I did not force NFSS1 on my users. I made it available (for AmS-LaTeX) but I kept it basically a secret. Richard. PS When will we see `The LaTeX companion'?