Xref: utzoo comp.text.tex:4701 comp.windows.x:31307 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!uwm.edu!bionet!agate!ICSI.Berkeley.EDU!stolcke From: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke) Newsgroups: comp.text.tex,comp.windows.x Subject: Re: Where are "texsun" and "texx"? Message-ID: <1991Jan8.202751.1966@agate.berkeley.edu> Date: 8 Jan 91 20:27:51 GMT References: <2783DB48.24C4@deneva.sdd.trw.com> Sender: usenet@agate.berkeley.edu (USENET Administrator) Reply-To: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke) Organization: International Computer Science Institute, Berkeley, CA Lines: 22 In article , fischer@iesd.auc.dk (Lars P. Fischer) writes: |> Hmm. xtex does not use pk or gf fonts. Instead, you transform the |> 85dpi fonts into native X fonts (bdf format). There a script to do |> that. When you have the X fonts, you store them somewhere and use xset |> to tell the X server where to look, i.e.: |> When you have done as above, xtex provides a good quality as any other |> previewer I know of, and as a bonus it *fast*. I'm surprised nobody in this thread has mentioned xdvi. we also have xtex, but IMHO the necessity of maintaining a second set of fonts just for xtex is a real inconvenience, especially if you have a lot of non-standard local fonts being used with TeX. xdvi uses pk fonts directly, and as far as I can tell without any penalty in display quality and speed. I doesn't have any fancy widget interface but a lot of functionality activated by simple one-key command, which makes it very efficient to use. [xdvi is available from expo.lcs.mit.edu in directory contrib.] -- Andreas Stolcke stolcke@icsi.berkeley.edu International Computer Science Institute stolcke@ucbicsi.bitnet 1957 Center St., Suite 600, Berkeley, CA 94704 (415) 642-4274 ext. 126