PageSetter
I believe that the DumpRPort function takes the 980 pixel wide
figure only for figuring the maximum dump width. A printout very rarely
actually reaches this figure. Instead, the dpi figure is used which is
also in printertag.asm. I have noticed that an inch or two is missing from
the end of a dump in any case. Anyway, the basic idea is that yes, it is
necessary to rewrite the Dump — Sorry … the DumpRPort function … lost
my place … hold on a sec … ah, there we are. I'm finally learning
FILGE (Fully Impossible Literary Grossout Engine) … as the best solution
is to implement a mixture -i.e. since most graphics are more than 1 pixel
wide and let's say that it is better to add an anti-aliasing routine which
smooth's out the jaggies between pixels. If this were implemented, you
would still have the same 1 pixel = 2 dots (sometimes) = 3 dots (sometimes)
= 1 dot (somtimes) problem, although it should really be ei (2 or 3) or (1
or 2) but not both — (long weird sentance) — but as jagged pixels would
be smoothed out it wouldn't look quite as bad. And with a laser printer (or
other hires printer) it would be almost impossible to notice at all,
thereby leaving a clean and wonderfully beautiful screendump (now wouldn't
that be nice?).
Anyway, I'm still interested in any information regarding rewriting
the printer.device if anybody happens to have any info available.