> >>>>> On Tue, 20 Apr 1999 18:40:28 +0200, Petter Reinholdtsen <pere@hungry.com> said:
>
> Petter> The pnm backend is supposed to be full of bugs. Maybe you
> Petter> should try with another backend?
>
> Note that in 1.0.1 we rolled back the pnm backend to the previous
> (stable) version. That earlier version (before 1.0) should be _very_
> stable (it passes "scanimage -T" etc.).
Well, I think "fairly stable" or "somewhat less unstable" would be a better
phrase...
[njl98r@chef ~]$ scanimage -T -d pnm:0 --grayify --filename /usr/local/src/cvs-gnome/gimp/gimp_logo.ppm
scanimage: scanning image of size 310x360 pixels at 8 bits/pixel
scanimage: acquiring gray frame, 8 bits/sample
scanimage: reading one scanline, 310 bytes... PASS
scanimage: reading one byte... FAIL Overflow: 310 bytes
scanimage: stepped read, 2 bytes... FAIL Overflow: 310 bytes
scanimage: stepped read, 4 bytes... FAIL Overflow: 310 bytes
This is with SANE 1.01 as released. There were always known bugs in the PNM
backend, and someone did undertake to fix them, but it hasn't happened yet.
At least 1.01 shipped with a PNM backend which works long enough to see that
SANE is working properly, which 1.00 didn't manage :)
Actually for my purposes the PNM backend isn't very useful anyway. I'm still
working on a replacement test backend with behaviour which more closely
resembles a real scanner. This should let people fiddle about with front-end
code without needing a real scanner to hand, which the PNM backend is barely
suitable for even when it works.
Nick.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com