kopia lustrzana https://gitlab.com/sane-project/website
132 wiersze
5.2 KiB
HTML
132 wiersze
5.2 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>sane-devel: Re: Writing Fujitsu M3091 backend</TITLE>
|
|
<META NAME="Author" CONTENT="Tom Martone (tom@martoneconsulting.com)">
|
|
<META NAME="Subject" CONTENT="Re: Writing Fujitsu M3091 backend">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|
<H1>Re: Writing Fujitsu M3091 backend</H1>
|
|
<!-- received="Thu Mar 1 17:52:14 2001" -->
|
|
<!-- isoreceived="20010302015214" -->
|
|
<!-- sent="Thu, 01 Mar 2001 21:22:29 -0500" -->
|
|
<!-- isosent="20010302022229" -->
|
|
<!-- name="Tom Martone" -->
|
|
<!-- email="tom@martoneconsulting.com" -->
|
|
<!-- subject="Re: Writing Fujitsu M3091 backend" -->
|
|
<!-- id="3A9F03E5.5D88E87B@martoneconsulting.com" -->
|
|
<!-- inreplyto="20010301200801.A22915@aruba.remote.org" -->
|
|
<STRONG>From:</STRONG> Tom Martone (<A HREF="mailto:tom@martoneconsulting.com?Subject=Re:%20Writing%20Fujitsu%20M3091%20backend&In-Reply-To=<3A9F03E5.5D88E87B@martoneconsulting.com>"><EM>tom@martoneconsulting.com</EM></A>)<BR>
|
|
<STRONG>Date:</STRONG> Thu Mar 01 2001 - 18:22:29 PST
|
|
<P>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0025.html">Davis, Tom: "RE: Writing Fujitsu M3091 backend"</A>
|
|
<UL>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0023.html">Tom Martone: "Re: Writing Fujitsu M3091 backend"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0012.html">Frederik Ramm: "Re: Writing Fujitsu M3091 backend"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0013.html">mh: "Re: Writing Fujitsu M3091 backend"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#24">[ date ]</A>
|
|
<A HREF="index.html#24">[ thread ]</A>
|
|
<A HREF="subject.html#24">[ subject ]</A>
|
|
<A HREF="author.html#24">[ author ]</A>
|
|
</UL>
|
|
<HR NOSHADE><P>
|
|
<!-- body="start" -->
|
|
<P>
|
|
Greetings,
|
|
<BR>
|
|
<P><EM>> It does make a difference I think. If the front-end is expected to do
|
|
</EM><BR>
|
|
<EM>> something automatically - even if it's just saving the images with
|
|
</EM><BR>
|
|
<EM>> proper names - it would be good to know whether a certain image is
|
|
</EM><BR>
|
|
<EM>> "another image derived from the same sheet of paper" or "a new image
|
|
</EM><BR>
|
|
<EM>> derived from a new sheet of paper". You would probably want to assign
|
|
</EM><BR>
|
|
<EM>> different file names.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Of course it can be "guessed" - if the front-end knows that duplex
|
|
</EM><BR>
|
|
<EM>> mode is on, every other image that the scanner delivers will probably
|
|
</EM><BR>
|
|
<EM>> be a back side - but that's not exactly cool. For example I've been
|
|
</EM><BR>
|
|
<EM>> looking at the Bell+Howell driver and saw that these scanners may
|
|
</EM><BR>
|
|
<EM>> produce a multitude of images from one page - things like "front
|
|
</EM><BR>
|
|
<EM>> thumbnail", "front barcode", whatever.
|
|
</EM><BR>
|
|
<P>I agree that it's not exactly cool. The practical way of dealing with
|
|
<BR>
|
|
it in the Bell+Howell case is that the front-end is in control of
|
|
<BR>
|
|
requesting which set of possible images can be generated from a sheet
|
|
<BR>
|
|
of paper, and the driver delivers them in a predictable, documented
|
|
<BR>
|
|
order. So a front-end program can reliably know which image is it
|
|
<BR>
|
|
working on at any time.
|
|
<BR>
|
|
<P><EM>> So, in "some future version" of SANE, there ought to be a mechanism by
|
|
</EM><BR>
|
|
<EM>> which the backend can inform the front-end of the intrinsic relation-
|
|
</EM><BR>
|
|
<EM>> ships between images it delivers.
|
|
</EM><BR>
|
|
<P>Agreed. For now, non-standard, xml-encoded text frames work like a charm.
|
|
<BR>
|
|
<P>By the way, scanadf can scan only some of the documents in the hopper by
|
|
<BR>
|
|
using the --start-count and --end-count options. I think xsane has similar
|
|
<BR>
|
|
capabilities. But in my version of "real-life" these options are never
|
|
<BR>
|
|
used. The users control how many pages to scan by the size of the stack
|
|
<BR>
|
|
of sheets that they place in the hopper.
|
|
<BR>
|
|
<P>Tom
|
|
<BR>
|
|
<P><PRE>
|
|
--
|
|
Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20Writing%20Fujitsu%20M3091%20backend&In-Reply-To=<3A9F03E5.5D88E87B@martoneconsulting.com>">majordomo@mostang.com</A>
|
|
</PRE>
|
|
<P><!-- body="end" -->
|
|
<HR NOSHADE>
|
|
<UL>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0025.html">Davis, Tom: "RE: Writing Fujitsu M3091 backend"</A>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0023.html">Tom Martone: "Re: Writing Fujitsu M3091 backend"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0012.html">Frederik Ramm: "Re: Writing Fujitsu M3091 backend"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0013.html">mh: "Re: Writing Fujitsu M3091 backend"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#24">[ date ]</A>
|
|
<A HREF="index.html#24">[ thread ]</A>
|
|
<A HREF="subject.html#24">[ subject ]</A>
|
|
<A HREF="author.html#24">[ author ]</A>
|
|
</UL>
|
|
<!-- trailer="footer" -->
|
|
<HR NOSHADE>
|
|
<P>
|
|
<SMALL>
|
|
<EM>
|
|
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
|
|
: <EM>Thu Mar 01 2001 - 17:52:32 PST</EM>
|
|
</EM>
|
|
</SMALL>
|
|
</BODY>
|
|
</HTML>
|