sane-project-website/old-archive/2000-09/0233.html

162 wiersze
6.0 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: image data format polarity</TITLE>
<META NAME="Author" CONTENT="Henning Meier-Geinitz (hmg-ml@gmx.de)">
<META NAME="Subject" CONTENT="Re: image data format polarity">
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Re: image data format polarity</H1>
<!-- received="Sat Sep 23 21:59:38 2000" -->
<!-- isoreceived="20000924045938" -->
<!-- sent="Fri, 22 Sep 2000 20:43:57 +0200" -->
<!-- isosent="20000922184357" -->
<!-- name="Henning Meier-Geinitz" -->
<!-- email="hmg-ml@gmx.de" -->
<!-- subject="Re: image data format polarity" -->
<!-- id="20000922204357.B2476@hmg1.vortex.swb.de" -->
<!-- inreplyto="20000921225014.B522@ecs.soton.ac.uk" -->
<STRONG>From:</STRONG> Henning Meier-Geinitz (<A HREF="mailto:hmg-ml@gmx.de?Subject=Re:%20image%20data%20format%20polarity&In-Reply-To=&lt;20000922204357.B2476@hmg1.vortex.swb.de&gt;"><EM>hmg-ml@gmx.de</EM></A>)<BR>
<STRONG>Date:</STRONG> Fri Sep 22 2000 - 11:43:57 PDT
<P>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0234.html">Henning Meier-Geinitz: "Re: will my scanner work"</A>
<UL>
<LI><STRONG>Previous message:</STRONG> <A HREF="0232.html">Oliver Rauch: "Re: Error msg on startup"</A>
<LI><STRONG>In reply to:</STRONG> <A HREF="0223.html">Nick Lamb: "Re: image data format polarity"</A>
<!-- nextthread="start" -->
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#233">[ date ]</A>
<A HREF="index.html#233">[ thread ]</A>
<A HREF="subject.html#233">[ subject ]</A>
<A HREF="author.html#233">[ author ]</A>
</UL>
<HR NOSHADE><P>
<!-- body="start" -->
<P>
Hi,
<BR>
<P>On Thu, Sep 21, 2000 at 10:50:14PM +0100, Nick Lamb wrote:
<BR>
<EM>&gt; &gt; Does anyone really think it would be a good idea to change an existing
</EM><BR>
<EM>&gt; &gt; standard in such a point? I don`t think so.
</EM><BR>
<EM>&gt;
</EM><BR>
<EM>&gt; Chaper, section, subsection reference to the STANDARD please Oliver,
</EM><BR>
<P>I don't think it's defined anywhere in the SANE standard.
<BR>
<P><EM>&gt; or do you mean &quot;I don't want to change XSane at this point&quot; ?
</EM><BR>
<P>I'm not Oliver but I don't think it's a problem of changing a single
<BR>
frontend. This change would probabaly involve updating more than 30 backends
<BR>
and a lot of them are unsupported. Please, let's not do global changes that
<BR>
are not absolutely necessary. I had some experiences with changing all the
<BR>
backends concerning simple things like DBG instead of fprintf, includes and
<BR>
sanei_config_read() instead of fgets. It's a nightmare. Further more,
<BR>
changing the backend and frontends would result in a total mess if a user
<BR>
mixes old backends an new frontends or vice versa.
<BR>
<P><EM>&gt; Well, it looks broken and is definitely inconsistent. &quot;We always did
</EM><BR>
<EM>&gt; the wrong thing&quot; is not a good excuse for doing the wrong thing,
</EM><BR>
<EM>&gt; especially when we're so early in the life of SANE.
</EM><BR>
<P>That's right. But if &quot;the wrong thing&quot; works properly and just doesn't look
<BR>
nice we shouldn't break it during major releases.
<BR>
<P><EM>&gt; This will catch
</EM><BR>
<EM>&gt; out everyone who tries to implement the spec from scratch (not by
</EM><BR>
<EM>&gt; cutting and pasting code as most have so far)
</EM><BR>
<P>The behaviour of the SANE API is not defined concerning the meaning of color
<BR>
values as it is not defined concerning some other points in SANE. The
<BR>
developer has to decide what to do and will probably decide to look at other
<BR>
implementations.
<BR>
<P><EM>&gt; I would prefer that it be corrected in the implementations and
</EM><BR>
<EM>&gt; clarified in the spec. If not, the spec must be changed to indicate
</EM><BR>
<EM>&gt; how existing implementations do it, with a footnote explaining that
</EM><BR>
<EM>&gt; this is a result of a ridiculous historical artifact.
</EM><BR>
<P>I propose to just add a description of the current behaviour to the
<BR>
standard. I don't think comments about opinions about the sense of the
<BR>
definition will help any developer.
<BR>
<P>Proposal (section{Image Data Format}, after second paragraph):
<BR>
<P>&quot;For bit depths of 8 and 16, 0 means the lowest intensity of color (or black
<BR>
for gray frames) and 255 repectively 65535 means the highest intensity of
<BR>
color (or white for gray frames). For a bit depth of 1, a value of 0 means
<BR>
white and a value of 1 means black.&quot;
<BR>
<P>Please correct errors and language (I'm not a native speaker).
<BR>
<P>On the other hand we may think about a change in SANE 2.0 because all
<BR>
backends and frontends will have to be updated in any case.
<BR>
<P>I will add this as a point of discussion in LEVEL2.
<BR>
<P>Bye,
<BR>
&nbsp;&nbsp;Henning
<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:%20image%20data%20format%20polarity&In-Reply-To=&lt;20000922204357.B2476@hmg1.vortex.swb.de&gt;">majordomo@mostang.com</A>
</PRE>
<P><!-- body="end" -->
<HR NOSHADE>
<UL>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0234.html">Henning Meier-Geinitz: "Re: will my scanner work"</A>
<LI><STRONG>Previous message:</STRONG> <A HREF="0232.html">Oliver Rauch: "Re: Error msg on startup"</A>
<LI><STRONG>In reply to:</STRONG> <A HREF="0223.html">Nick Lamb: "Re: image data format polarity"</A>
<!-- nextthread="start" -->
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#233">[ date ]</A>
<A HREF="index.html#233">[ thread ]</A>
<A HREF="subject.html#233">[ subject ]</A>
<A HREF="author.html#233">[ 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>Sat Sep 23 2000 - 22:05:42 PDT</EM>
</EM>
</SMALL>
</BODY>
</HTML>