This question has been asked a number of times before (by me, among
others), and usual answer is that the SCSI-II specs for scanners is
far too vague (and open to mfg-to-mfg variation) to make a common
library useful.
>This helps in adding new SCSI-II scanners by changing only the
>specifications file (provided you get your hand on the Scanner SPECs).
>This truly helps when we have latest scanners from the same manufacturer.
If you have a new model from an old manufacturer, chances are the
command set is about the same, and the old backend just needs some
tweaks. Much easier to do. (And, I think, what gets done implicitly
by many backends --- adjusting what they send to the scanner depending
on what particular model is used.)
-matt m.
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com