[sane-devel] infrared, SANE_FRAME_RGBA

Giuseppe Sacco giuseppe at eppesuigoccas.homedns.org
Thu Dec 14 20:14:41 CET 2006

Hi Gerard and all SANE developers,

Il giorno gio, 14/12/2006 alle 13.40 +0100, Gerhard Jaeger ha scritto:
> But I think you are right, we are moving into a dead-end. We have 
> devices that are able to do much more than we are able to support
> with the SANE 1 standard AND we have a not yet finished (if finished
> ever) SANE 2 standard.
> I'd like to hear/read some more opinions on that.
> Any?

I am not an active SANE developer, but I follow the list since some
year; I tested SANE on many scanners and on a few operating system
versions; I worked at the italian translation. Lately I decided to work
more on coolscan2 driver in order to work with Coolscan V LS-50 ED, so I
requested all documentation to Nikon and I am actually waiting for it.
Moreover I develop an application that uses scanners on Windows (via
TWAIN), and MacOSX and Linux (via SANE).

So take my opinion as the less important among SANE developers opinions.

My impression is that SANE is nice peace of software, but there are some
incompatibilities among the backends. As an exemple: a common user
interface (arguments) would be useful to applications that invoke SANE.

I have to re-read the SANE2 specification. I think it could be useful in
making it easy to develop backends and to interface with them. I don't
remember what were pro and cons in previous threads, but I am in favour
of starting sane2 implementation now since nothing will change in the
next months.

Some backends will be "ported" to sane2 earlier than other; maybe others
will never be ported. But I think that sane does not require a complete
compatibility with sane1. It may be a "different application".


More information about the sane-devel mailing list