>
> As a matter of fact, I have never had shear problems with either xsane
> or xscanimage. Instead, I have had shear problems myself when I first
> tried usin PIL's[*] sanemodule. FWIR, I solved the problem by changeing
> the end of scanline logic, since AMK thought any scanner would jump to
> the next line after 3*pixels were read. If you need it, ask me, and I'll
> send you my patched version of the file, since, as of now, Andrew has
> not still axcepted and merged my changes into his module.
>
The umax scanners don`t give back any addidtional bytes. But
the scanarea is given in 1/1200 inch and the calculation of
pixels form this does not always match the pixels the scanner
sends back. This normally happens only if the resolution is greater than 600
dpi.
But it is not a rounding problem.
Bye
Oliver
-- EMAIL: Oliver.Rauch@Wolfsburg.DE WWW: http://www.wolfsburg.de/~rauch
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com