Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.text
Subject: Re: cminch and imagens
Message-ID: <13686@mimsy.UUCP>
Date: 22 Sep 88 05:01:34 GMT
References: <3616@boulder.Colorado.EDU>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 26

In article <3616@boulder.Colorado.EDU> hartzell@boulder.Colorado.EDU
(George Hartzell) writes:
>I am having problems using the cminch font that comes on the Unix TeX
>distribution. ... won't work on the imagen.  Beebe's imagen driver just
>gives a blank page, while Chris Torek's (?) iptex program prints a mess
>(it looks like some of the scan lines are vertically displaced by about
>1.25 inches).  Is this something that I am going to have to live with, or
>is it fixable?

Check the revision of the software on the Imagen itself.  Anything
older than about three years has some serious bugs in the rasterising
code.  More recent revisions have less serious bugs or no bugs (I had a
sample page, printed on, I think, rev 2.0) that mysteriously began
duplicating output lines about two-thirds of the way down the page,
with increasing density of duplication towards the end.  The last few
lines were almost solid black.  Printing the same file a second time
(after power cycling the Imagen, which had wedged) produced perfect
output.  One reliable way to crash old software was to define a glyph
with zero pixels (height=width=0, adv.width>0).

(Of course, it is possible that the latest software has some interesting
bugs too.  I think we are running version 2.6 of Imagen's software, but
this is from memory: the machines are at the University and I am at home.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris