Oliver,
Oliver Rauch wrote:
>
> 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 a f/e doesn't support a particular encoding then it would not request
it.
> 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
Sorry my understanding of the discussion was that we were talking about
additions 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 - 15:13:48 PDT