kopia lustrzana https://gitlab.com/sane-project/website
65 wiersze
3.1 KiB
HTML
65 wiersze
3.1 KiB
HTML
|
<!-- received="Tue Aug 3 21:50:05 1999 PDT" -->
|
|||
|
|
<!-- sent="Wed, 4 Aug 1999 05:51:33 +0100 (GMT)" -->
|
|||
|
|
<!-- name="Nick Lamb" -->
|
|||
|
|
<!-- email="njl98r@ecs.soton.ac.uk" -->
|
|||
|
|
<!-- subject="Re: SANE_FRAME Formats (was Re: xsane-0.31 available)" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="37A7A8E4.D6014E0@martoneconsulting.com" -->
|
|||
|
|
<title>sane-devel: Re: SANE_FRAME Formats (was Re: xsane-0.31 available)</title>
|
|||
|
|
<h1>Re: SANE_FRAME Formats (was Re: xsane-0.31 available)</h1>
|
|||
|
|
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
|
|||
|
|
<i>Wed, 4 Aug 1999 05:51:33 +0100 (GMT)</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#44">[ date ]</a><a href="index.html#44">[ thread ]</a><a href="subject.html#44">[ subject ]</a><a href="author.html#44">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0045.html">Stephen Williams: "Re: SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0043.html">Nick Lamb: "Re: SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
On Tue, 3 Aug 1999, Tom Martone wrote:<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> Document scanners such as the Bell+Howell scanners can produce CCITT-G3,</i><br>
|
|||
|
|
<i>> CCITT-G3-2D, and CCITT-G4 compressed image streams. I'm not sure if it</i><br>
|
|||
|
|
<i>> would be appropriate to classify these formats as proprietary although</i><br>
|
|||
|
|
<i>> they are certainly not specifically supported by SANE. </i><br>
|
|||
|
|
<p>
|
|||
|
|
Unless I'm sorely mistaken, this algorithm is so cheap that you can<br>
|
|||
|
|
trivially do it inline. Is there a problem with doing this in your<br>
|
|||
|
|
backend? If it turns out to be too expensive, we should probably add<br>
|
|||
|
|
one or more frame types as necessary to SANE.<br>
|
|||
|
|
<p>
|
|||
|
|
The barcode stuff is a separate issue, and I suspect there's more to it<br>
|
|||
|
|
than meets the eye -- can you really just scan barcode string data off<br>
|
|||
|
|
A4 pages as you're going along? Or is it meant for indentifying the<br>
|
|||
|
|
documents somehow?<br>
|
|||
|
|
<p>
|
|||
|
|
If the barcodes aren't really "image data" as such you can expose them<br>
|
|||
|
|
as an option text string which is changed by the backend only and<br>
|
|||
|
|
updates for each new page. Then a custom frontend can read the codes<br>
|
|||
|
|
before/during/after each page is scanned. No magic needed :)<br>
|
|||
|
|
<p>
|
|||
|
|
NB There is NO NEED for each and every frontend to support each and every<br>
|
|||
|
|
possible FRAME format. A bulk-scanning app needn't support stuff used<br>
|
|||
|
|
only in desktop scanners, and a photo-oriented app needn't do CCITT.<br>
|
|||
|
|
<p>
|
|||
|
|
Nick.<br>
|
|||
|
|
<p>
|
|||
|
|
<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">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0045.html">Stephen Williams: "Re: SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0043.html">Nick Lamb: "Re: SANE_FRAME Formats (was Re: xsane-0.31 available)"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|