Xref: utzoo comp.sys.mac.wanted:3840 comp.sys.mac.misc:12496 comp.sys.mac.apps:6353 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!brunix!cs.brown.edu!man From: man@cs.brown.edu (Mark H. Nodine) 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: <76668@brunix.UUCP> Date: 24 May 91 15:44:09 GMT References: <20081@cs.utexas.edu> <1991May20.223955.22343@midway.uchicago.edu> <26376@ttidca.TTI.COM> <1445@mephisto.edu> Sender: news@brunix.UUCP Organization: Brown Computer Science Dept. Lines: 16 In article <1445@mephisto.edu>, ashwin@gatech.edu (Ashwin Ram) writes: |> However, some subset of this optimization could (and should) be performed in |> real time by WYSIWYG word processors. (E.g., it would be fairly easy to |> optimize one paragraph at a time.) I'd be interested in hearing about |> programs that do this. 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. --Mark