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

66 wiersze
2.8 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:16:51 1999 PDT" -->
<!-- sent="Sun, 15 Aug 1999 23:16:46 +0100 (GMT)" -->
<!-- name="Nick Lamb" -->
<!-- email="njl98r@ecs.soton.ac.uk" -->
<!-- subject="Re: SANE frames" -->
<!-- id="" -->
<!-- inreplyto="37B72B83.AB65D6C9@martoneconsulting.com" -->
<title>sane-devel: Re: SANE frames</title>
<h1>Re: SANE frames</h1>
<b>Nick Lamb</b> (<a href="mailto:njl98r@ecs.soton.ac.uk"><i>njl98r@ecs.soton.ac.uk</i></a>)<br>
<i>Sun, 15 Aug 1999 23:16:46 +0100 (GMT)</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#180">[ date ]</a><a href="index.html#180">[ thread ]</a><a href="subject.html#180">[ subject ]</a><a href="author.html#180">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0181.html">Nick Lamb: "Re: SANE frames"</a>
<li> <b>Previous message:</b> <a href="0179.html">Tom Martone: "Re: SANE V2"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
On Sun, 15 Aug 1999, Tom Martone wrote:<br>
<p>
<i>&gt; I think that number 3) would be a bug and would need to be fixed, </i><br>
<i>&gt; because by prepending the header to the unknown frame, the front-end</i><br>
<i>&gt; will have effectively corrupted the data stream.</i><br>
<p>
Yes. It's wrong behaviour to pretend you understand unknown formats --<br>
If you can't think of anything better to do: Scream and Shout and<br>
Stamp your feet so that the user knows something is wrong.<br>
<p>
<i>&gt; NOTE: This is how I understand scanimage behavior when encountering</i><br>
<i>&gt; an unexpected frame type:</i><br>
<i>&gt; </i><br>
<i>&gt; 1) if the FRAME does not need to be buffered (lines &gt;= 0)</i><br>
<i>&gt; The output will be the raw data with a PNM header prepended.</i><br>
<i>&gt; 2) if the FRAME needs buffering (lines &lt; 0, size not known a-priori)</i><br>
<i>&gt; The output will be a PNM header only.</i><br>
<i>&gt; </i><br>
<i>&gt; Niether one of these is useful behavior and would necessitate a minor</i><br>
<i>&gt; change to scanimage. I'll volunteer to make that change. </i><br>
<p>
Sounds good. Presumably you'll spit the raw data straight out onto the<br>
stdout file decriptor? That way:<br>
<p>
scanimage -d interesting:jpeg-device &gt; buttercup.jpg<br>
Gets you a JPEG in buttercup.jpg ready for further processing<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="0181.html">Nick Lamb: "Re: SANE frames"</a>
<li> <b>Previous message:</b> <a href="0179.html">Tom Martone: "Re: SANE V2"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>