Re: [Gimp-print-devel] unprint bugs fixed

[<sh...@al...>]

>    BTW, I notice that that image file that my friend gave me came out
>    twice as tall as it should have

Maybe it's just a photo of an entire family of Tall Clubs International
members?

>    (or half as wide, I don't know).

I think it's half as wide.  If you enable the secret unprint error detection
codes, you'll get a warning message if the unprinter ever puts ink of the
same color on the same spot on the page more than once.  The reason this
is not enabled by default is that it occurs so often (in this file) that
you have to wait 30 minutes for all the warning messages to scroll across
your terminal.  Pixels are being put on top of one another.  That would
happen if it's half as wide as it should be, but not if it's twice as tall.

> I took a closer look at the output files my friend sent me.  It looks
> like the one printed at 720 dpi advances on average 24 rows per pass,
> while the one printed at 1440 dpi advances on average 12 rows per
> pass.  So I think that my theory about double spacing (effectively 360
> dpi rather than 720 with ESCi) is probably correct.

So, do you think that ESCi is permanently fixed at 360 DPI, or is the
mystery ESC ( D command putting the machine into "double space" mode?

Can someone with a real printer grab this file, and use a binary editor
like beav to remove/alter the ESC(D command and send the output to the
printer and see what happens?

Eric