sane-project-website/old-archive/1999-08/0179.html

70 wiersze
3.1 KiB
HTML

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

<!-- received="Sun Aug 15 15:05:50 1999 PDT" -->
<!-- sent="Sun, 15 Aug 1999 17:22:25 -0400" -->
<!-- name="Tom Martone" -->
<!-- email="tom@martoneconsulting.com" -->
<!-- subject="Re: SANE V2" -->
<!-- id="" -->
<!-- inreplyto="SANE V2" -->
<title>sane-devel: Re: SANE V2</title>
<h1>Re: SANE V2</h1>
<b>Tom Martone</b> (<a href="mailto:tom@martoneconsulting.com"><i>tom@martoneconsulting.com</i></a>)<br>
<i>Sun, 15 Aug 1999 17:22:25 -0400</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#179">[ date ]</a><a href="index.html#179">[ thread ]</a><a href="subject.html#179">[ subject ]</a><a href="author.html#179">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0180.html">Nick Lamb: "Re: SANE frames"</a>
<li> <b>Previous message:</b> <a href="0178.html">Tom Martone: "Re: SANE frames"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Nick Lamb wrote:<br>
<i>&gt; </i><br>
<i>&gt; On Sun, 15 Aug 1999, Andreas Beck wrote:</i><br>
<i>&gt; </i><br>
<i>&gt; &gt; With more intelligence being moved into the scanners, we might get</i><br>
<i>&gt; &gt; text/plain or text/rtf in the future. TWAIN has provisions to read barcodes,</i><br>
<i>&gt; &gt; so their translation is probably also directly provided by some scanners.</i><br>
<i>&gt; </i><br>
<i>&gt; If the scanner wants to speak text, it's probably beyond the territory</i><br>
<i>&gt; we should sensibly stake out for SANE. At that point you're looking at a</i><br>
<i>&gt; whole new class of device IMHO.</i><br>
I'd have to disagree with you on this on, Nick. If you have a scanner<br>
that has an integral barcode/patchcode decoding feature that works on the<br>
surrently scanned image data in the firmware of the scanner, do we want to<br>
use SANE just to get the image data? Then do we get an OCR package to<br>
decode in software, the barcodes out of the saved image data? I've<br>
observed that the scanner firmware does it more quickly and more reliably, <br>
than an OCR approach and it does it at scan time rather than a separate<br>
pass.<br>
<p>
Although this is an obscure feature when you consider the types of scanners <br>
that individuals own, it's quite common with production level document <br>
scanners. It's not new. These capabilities have existed for several <br>
years.<br>
<p>
TWAIN 1.7 and ISIS support this data exchange, and SANE should as well,<br>
I think. I don't see why high-speed production document scanning with<br>
barcode/patchcode support is out of the scope of SANE.<br>
<p>
Scanners from Bell+Howell, Kodak, Ricoh, and others have barcode/patchcode<br>
support.<br>
<p>
Tom Martone<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">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0180.html">Nick Lamb: "Re: SANE frames"</a>
<li> <b>Previous message:</b> <a href="0178.html">Tom Martone: "Re: SANE frames"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>