Path: utzoo!utgpu!water!watmath!clyde!rutgers!iuvax!pur-ee!uiucdcs!uiucdcsm!grunwald
From: grunwald@uiucdcsm.cs.uiuc.edu
Newsgroups: comp.windows.x
Subject: Re: DVI previewers under X on Suns
Message-ID: <26900023@uiucdcsm>
Date: 27 Jan 88 00:28:00 GMT
Lines: 28
Nf-ID: #R:<8801242243.AA28913@ATHENA.MIT.E:-35:uiucdcsm:26900023:000:1128
Nf-From: uiucdcsm.cs.uiuc.edu!grunwald    Jan 26 18:28:00 1988


Although I hacked ``texx'', I didn't do the routines which it uses to find the
font files.

I'll give you some suggestions, and I'd like to know how they worked.

1) You can specify the Dots Per Inch of your the desired fonts using e.g.

	% texx -dpi 118 foo.dvi

   to use 118 DPI fonts. Thus, if you're using the 118 DPI fonts used by
   'dvisun', you should be able to try this.

2) In the 'fontdesc' file, you should be able to change the 'slop factor'
   to make it be less picky about fonts. To be honest, I have little
   intuition about how this affects the font selection or what a good
   number would be.

As for the core dumps: Sorry 'bout that, I have to admit that one late night
I generated every font I thought I'd ever need, because I was sick of the
problem. I think the best solution would be to draw a small box around
the (intended) character. If someone makes the modifications to do this,
please let me know (it's non-trivial, because it would require looking at
the .tfm file to determine the width & height -- however, I think that the
imagen driver does this already)

Dirk Grunwald.
Univ. of Illinois