Xref: utzoo comp.sys.mac.wanted:3843 comp.sys.mac.misc:12505 comp.sys.mac.apps:6355 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uunet!stanford.edu!neon.Stanford.EDU!pescadero.Stanford.EDU!philip From: philip@pescadero.Stanford.EDU (Philip Machanick) Newsgroups: comp.sys.mac.wanted,comp.sys.mac.misc,comp.sys.mac.apps Subject: Re: Why does Mac output not look as good as LaTex? Message-ID: <1991May24.181851.27245@neon.Stanford.EDU> Date: 24 May 91 18:18:51 GMT References: <20081@cs.utexas.edu> <1991May20.223955.22343@midway.uchicago.edu> <26376@ttidca.TTI.COM> <1445@mephisto.edu> <76668@brunix.UUCP> Sender: news@neon.Stanford.EDU (USENET News System) Reply-To: philip@pescadero.stanford.edu Organization: Stanford University Lines: 19 In article <76668@brunix.UUCP>, man@cs.brown.edu (Mark H. Nodine) writes: |> I was actually thinking about what this would be like in a WYSIWYG editor, |> and I came to the conclusion that you wouldn't want to do the recomputations |> _very_ often, because it would be very disconcerting as a user to be say |> typing in the middle of the paragraph and have your cursor jumping all over |> the place because the whole paragraph (including the part above the cursor) |> is jiggling with every character you type. You'd have to apply the paragraph- |> wise heuristics after you leave the paragraph and settle for only line-at-a- |> time heuristics while you're editing. I'm not so sure this is such a big problem. Latex (tex with a popular set of macros) takes about 1.5s per page on a DECstation 3100. A 68040 machine should be at least this fast - they should be affordable by the time the necessary programming is done (some are affordable right now - I won't mention names). Anyone keen to implement a real-time WYSIWYG TeX? (I would be if I had more spare time...) -- Philip Machanick philip@pescadero.stanford.edu