Skip to content
Prev 3662 / 63421 Next

xfig device (was [Rd] Re: [R] MetaPost device?)

On Sat, 8 Apr 2000, Ross Ihaka wrote:

            
AFAIR no problem: many dvixx drivers such as dvips compute string widths at
least.  In dvips bbox.c computes the bounding box for a dvi file, and
thereby computes BB info for each string. In doing so it computes from the
tfm the llx,lly,urx,ury for each character.

However, I would be inclined to go the other way, and just use the
PostScript fonts and their metrics.  For a start, the X11 metrics are I
believe device-specific, and I would view xfig screen output as an
approximation to the final printed form. And it is that final form I want
to be accurate.
Are we not just discussing a xfig driver for R, and R's driver model only
writes single text strings at specified (x,y) locations?  So test output
from an R xfig driver would not be richly structured?  Yes, there is
kerning but there is using postscript fonts directly, surely?
By the time a dvixx driver is reading the dvi file the kerning has been
done, but the information is all there in the tfm, and the format is
readily available (e.g. in tftopl).

Brian