Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!mcvax!hp4nl!kunivv1!eykhout
From: eykhout@kunivv1.sci.kun.nl (Victor Eijkhout)
Newsgroups: comp.text
Subject: Re: WYSIWYG = DIY (=hubris)
Message-ID: <390@kunivv1.sci.kun.nl>
Date: 11 Aug 89 11:07:45 GMT
References: <210927@<1989Jul28> <8800031@m.cs.uiuc.edu> <14903@dartvax.Dartmouth.EDU> <387@kunivv1.sci.kun.nl> <1438@hydra.gatech.EDU>
Reply-To: eykhout@wn2.UUCP (Victor Eijkhout)
Organization: University of Nijmegen, The Netherlands
Lines: 17

In article <1438@hydra.gatech.EDU> rh26@prism.gatech.EDU (Howard,Robert L) writes:
>In article <387@kunivv1.sci.kun.nl> eykhout@wn2.UUCP (Victor Eijkhout) writes:
>caps.  All you need to do is go to wherever the HEAD style is defined, delete 
>the bold and italic codes, and add the 'use all caps' code.  (Now I will 
>admit you're in trouble if there is no such code but the point is that it is 
>simple to do.)  
 
But is it that simple? I know that by now I can program most everything
a designer asks in TeX, but the wysiwyg systems I've seen look like
somebody threw together a number of mechanisms until s/he was convinced
there were sufficient special cases to cover most of what someone
would want. There is hardly any programmability.

The dividing line is becoming thinner and thinner, with wysiwyg
systems getting style sheets, I admit.

Victor