X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2003" "Wed" "3" "November" "93" "15:06:05" "EST" "Werenfried Spit" "SPIT@VM.CI.UV.ES" nil "32" "" "^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 AA17123; Wed, 3 Nov 93 15:21:07 +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 AA23950; Wed, 3 Nov 93 15:21:03 +0100 Message-Id: <9311031421.AA23950@sc.ZIB-Berlin.DE> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 1573; Wed, 03 Nov 93 15:19:50 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 6328; Wed, 03 Nov 93 15:19:39 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 6326; Wed, 03 Nov 93 15:19:35 CET Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Message of 03 Nov 1993 13:51:49 +0100 (CET) from Date: Wed, 3 Nov 93 15:06:05 EST From: Werenfried Spit Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Status: R X-Status: X-Keywords: X-UID: 1084 On 03 Nov 1993 13:51:49 +0100 (CET) said: >When you come to sysadmins and the like: >>It also makes not so (La)TeX fluent users and system administrators much more >>reluctant to upgrade their systems" >i think, sysadmins will usually install a new LaTeX while leaving the old >one where it has been (and it will linger there for a long time, probably). >And if the changes in the documents can be done with an awk-script once >and for all, i don't see a problem. As long as there is a well functioning awk and as long as someone takes the trouble to write a good script for it and as long as the users get to know precisely what script they should run on their old files. So, yes, I do think there is a problem. First of all I think that upgrading should be done completely within TeX; we should not rely on awk, patch or any other external tool (because there is almost no tool that can be used on all systems). Secondly, as Frank Poppe already mentioned: upgrades should be transparent to the users as much as possible. (I'm not a sysop, but I do a lot of TeX related installing for the department. When I install a new version of something I try to make sure that the users can continue to work just as they were used to when they don`t use new functionality; in the announcement of the new verion I usually try to provide something like 'if an old document suddenly causes strange error messages try to process it with 'oldxxx' instead of 'xxx''-- having the old software renamed to oldxxx; in case of new styles even this should be completely unnecessary; the users should not note it if they don't need to. If I'd demand everyone to run some conversion script before they can continue their work they don't want any upgrades -- and rightly so.) ------------------------------------------------ Werenfried Spit email: spit@vm.ci.uv.es tel: +34-6-386 4550 Dep. de Fisica Teorica, Universitat de Valencia