Hi all
But sirs,
could you please give answer to my earlier question?
I have undergone all the mails related to this topic but
my impression is that sane-1 doesn't support storage in
specific file format.Is it true? If so give me some guidelines
what to do.
Thanks & regards
--Shailendra Mehta
Mick Barry wrote:
>
> Oliver,
>
> But if it was compulsary for a b/e to support the current transfer
> mechanism then couldn't the f/e simply fall back to using this method if
> it didn't support other image encodings.
>
The frontend or the backend has to be able to uncompress the compressed
image
format to do a preview.
If we do the transformation in the frontend, we have to change
- several frontends
- the sane standard
If we do the transformation in the backend, only the relevant backend
has to include a transformation. The sane standard can keep the same.
So I think it is compulsary to
- include the transformation (uncompression) in the backend for sane-1
- add support for new file formats to sane-2
Bye
Oliver
-- Homepage: http://www.rauch-domain.de sane-umax: http://www.rauch-domain.de/sane-umax xsane: http://www.xsane.org E-Mail: mailto:Oliver.Rauch@rauch-domain.de-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Thu May 03 2001 - 20:25:56 PDT