# Re: SANE API & file format

From: Nick Lamb (njl98r@ecs.soton.ac.uk)
Date: Thu May 03 2001 - 14:35:13 PDT

- Next message: Oliver Rauch: "Re: SANE API & file format"
  - Previous message: Henning Meier-Geinitz: "Re: Canon backend"
  - In reply to: Stephen Williams: "Re: SANE API & file format"
  - Next in thread: Oliver Rauch: "Re: SANE API & file format"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  On Thu, May 03, 2001 at 01:42:38PM -0700, Stephen Williams wrote:
  > Most formats will be variable size streams. To account for that, the
  > application should always read to the EOF to get everything that is
  > the format.

  Yes.

  In your experience, do the fast hardware scanners ever leave anything
  "out-of-band" which a user might need in order to reconstruct the image
  but which isn't included in the stream, such as image dimensions or
  color type /depth info ?

  You said JFIF in your example, does that mean that the data coming out
  of the scanners is a true JFIF compliant file, or just that it would
  be easy in the frontend or backend to prepend the appropriate APPn
  markers and data?

  Nick.

      --
      Source code, list archive, and docs: http://www.mostang.com/sane/
      To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

  - Next message: Oliver Rauch: "Re: SANE API & file format"
  - Previous message: Henning Meier-Geinitz: "Re: Canon backend"
  - In reply to: Stephen Williams: "Re: SANE API & file format"
  - Next in thread: Oliver Rauch: "Re: SANE API & file format"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Thu May 03 2001 - 14:26:30 PDT