kopia lustrzana https://gitlab.com/sane-project/website
196 wiersze
7.0 KiB
HTML
196 wiersze
7.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: SANE API & file format</TITLE>
|
|
<META NAME="Author" CONTENT="Mick Barry (mick@objects.com.au)">
|
|
<META NAME="Subject" CONTENT="Re: SANE API & file format">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|
<H1>Re: SANE API & file format</H1>
|
|
<!-- received="Thu May 3 20:33:43 2001" -->
|
|
<!-- isoreceived="20010504033343" -->
|
|
<!-- sent="Fri, 04 May 2001 13:43:54 +1000" -->
|
|
<!-- isosent="20010504034354" -->
|
|
<!-- name="Mick Barry" -->
|
|
<!-- email="mick@objects.com.au" -->
|
|
<!-- subject="Re: SANE API & file format" -->
|
|
<!-- id="3AF2257A.20F49649@objects.com.au" -->
|
|
<!-- inreplyto="000001c0d44a$e00d2480$0c2c7aa3@TIL" -->
|
|
<STRONG>From:</STRONG> Mick Barry (<A HREF="mailto:mick@objects.com.au?Subject=Re:%20SANE%20API%20&%20file%20format&In-Reply-To=<3AF2257A.20F49649@objects.com.au>"><EM>mick@objects.com.au</EM></A>)<BR>
|
|
<STRONG>Date:</STRONG> Thu May 03 2001 - 20:43:54 PDT
|
|
<P>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0064.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<UL>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0062.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0062.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0064.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0061.html">Stephen Williams: "Re: SANE API & file format"</A>
|
|
<LI><STRONG>Reply:</STRONG> <A HREF="0064.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#63">[ date ]</A>
|
|
<A HREF="index.html#63">[ thread ]</A>
|
|
<A HREF="subject.html#63">[ subject ]</A>
|
|
<A HREF="author.html#63">[ author ]</A>
|
|
</UL>
|
|
<HR NOSHADE><P>
|
|
<!-- body="start" -->
|
|
<P>
|
|
Sorry Shailendra ,
|
|
<BR>
|
|
<P>The answer to your question is that SANE does not support storage of
|
|
<BR>
|
|
specific file formats. The image is returned from the scanner in the
|
|
<BR>
|
|
format specified in the SANE standard. If you wish to save the image in
|
|
<BR>
|
|
another format then you are responsible for handling this.
|
|
<BR>
|
|
<P>mick
|
|
<BR>
|
|
<P>shailendra mehta wrote:
|
|
<BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Hi all
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> But sirs,
|
|
</EM><BR>
|
|
<EM>> could you please give answer to my earlier question?
|
|
</EM><BR>
|
|
<EM>> I have undergone all the mails related to this topic but
|
|
</EM><BR>
|
|
<EM>> my impression is that sane-1 doesn't support storage in
|
|
</EM><BR>
|
|
<EM>> specific file format.Is it true? If so give me some guidelines
|
|
</EM><BR>
|
|
<EM>> what to do.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Thanks & regards
|
|
</EM><BR>
|
|
<EM>> --Shailendra Mehta
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Mick Barry wrote:
|
|
</EM><BR>
|
|
<EM>> >
|
|
</EM><BR>
|
|
<EM>> > Oliver,
|
|
</EM><BR>
|
|
<EM>> >
|
|
</EM><BR>
|
|
<EM>> > But if it was compulsary for a b/e to support the current transfer
|
|
</EM><BR>
|
|
<EM>> > mechanism then couldn't the f/e simply fall back to using this method if
|
|
</EM><BR>
|
|
<EM>> > it didn't support other image encodings.
|
|
</EM><BR>
|
|
<EM>> >
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> The frontend or the backend has to be able to uncompress the compressed
|
|
</EM><BR>
|
|
<EM>> image
|
|
</EM><BR>
|
|
<EM>> format to do a preview.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> If we do the transformation in the frontend, we have to change
|
|
</EM><BR>
|
|
<EM>> - several frontends
|
|
</EM><BR>
|
|
<EM>> - the sane standard
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> If we do the transformation in the backend, only the relevant backend
|
|
</EM><BR>
|
|
<EM>> has to include a transformation. The sane standard can keep the same.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> So I think it is compulsary to
|
|
</EM><BR>
|
|
<EM>> - include the transformation (uncompression) in the backend for sane-1
|
|
</EM><BR>
|
|
<EM>> - add support for new file formats to sane-2
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Bye
|
|
</EM><BR>
|
|
<EM>> Oliver
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> --
|
|
</EM><BR>
|
|
<EM>> Homepage: <A HREF="http://www.rauch-domain.de">http://www.rauch-domain.de</A>
|
|
</EM><BR>
|
|
<EM>> sane-umax: <A HREF="http://www.rauch-domain.de/sane-umax">http://www.rauch-domain.de/sane-umax</A>
|
|
</EM><BR>
|
|
<EM>> xsane: <A HREF="http://www.xsane.org">http://www.xsane.org</A>
|
|
</EM><BR>
|
|
<EM>> E-Mail: mailto:<A HREF="mailto:Oliver.Rauch@rauch-domain.de?Subject=Re:%20SANE%20API%20&%20file%20format&In-Reply-To=<3AF2257A.20F49649@objects.com.au>">Oliver.Rauch@rauch-domain.de</A>
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> --
|
|
</EM><BR>
|
|
<EM>> Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
</EM><BR>
|
|
<EM>> To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20SANE%20API%20&%20file%20format&In-Reply-To=<3AF2257A.20F49649@objects.com.au>">majordomo@mostang.com</A>
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> --
|
|
</EM><BR>
|
|
<EM>> Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
</EM><BR>
|
|
<EM>> To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20SANE%20API%20&%20file%20format&In-Reply-To=<3AF2257A.20F49649@objects.com.au>">majordomo@mostang.com</A>
|
|
</EM><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:%20SANE%20API%20&%20file%20format&In-Reply-To=<3AF2257A.20F49649@objects.com.au>">majordomo@mostang.com</A>
|
|
</PRE>
|
|
<P><!-- body="end" -->
|
|
<HR NOSHADE>
|
|
<UL>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0064.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0062.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0062.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0064.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0061.html">Stephen Williams: "Re: SANE API & file format"</A>
|
|
<LI><STRONG>Reply:</STRONG> <A HREF="0064.html">shailendra mehta: "RE: SANE API & file format"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#63">[ date ]</A>
|
|
<A HREF="index.html#63">[ thread ]</A>
|
|
<A HREF="subject.html#63">[ subject ]</A>
|
|
<A HREF="author.html#63">[ 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 May 03 2001 - 20:34:04 PDT</EM>
|
|
</EM>
|
|
</SMALL>
|
|
</BODY>
|
|
</HTML>
|