# Re: Getting compressed B/W image data from Fujitsu M3096GXm scann er

From: abel deuring (adeuring@gmx.net)
Date: Mon Feb 05 2001 - 14:12:21 PST

- Next message: Karsten Festag: "Re: Microtek X6, USB and slackware problems"
  - Previous message: Heikki Kantola: "Re: SANE 1.0.4 and SnapScan library problems"
  - In reply to: Armistead, Jason: "RE: Getting compressed B/W image data from Fujitsu M3096GXm scann er"
  - Next in thread: Nick Lamb: "Re: Getting compressed B/W image data from Fujitsu M3096GXm scann er"
  - Reply: Nick Lamb: "Re: Getting compressed B/W image data from Fujitsu M3096GXm scann er"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  "Armistead, Jason" wrote:
  >
  > Hi Tom (and all on the SANE list)
  >
  > Thanks to Tom for his pointing out that his sane-bh backend DOES support
  > compression.
  >
  > Why isn't it directly integrated with SANE 1.04 and part of the standard
  > distribution ? The latest sane-bh patches are against 1.03, so I guess
  > there'll be some extra work required to make it go together with 1.04 ?
  >
  > The obvious question arises : When is "the next major version of SANE" due
  > to be released ? It would seem to me (maybe naively) that scanner-based
  > compression is something that has been overlooked in SANE up until now.
  >
  > Is there any reason that a "reference model" scanner from the SCSI II spec
  > wasn't developed as part of SANE, as a basis for all others to be modelled
  > on ? Obviously every manufacturer likes to "roll their own" feature set,
  > but we seem to be treading on each other's toes by re-inventing at least
  > some portion of the wheel for each new scanner. e.g. with sense code /
  > qualifier decoding for the various error messages such as ADF jamming.
  > Perhaps it's time to look at redesigning the backends to deal with these
  > e.g. a function called sane_scsi2_asc60_asq00 might actually handle the SCSI
  > 2 ASC60, ASQ00 response code "Lamp failure" for all scanners. Perhaps this
  > also lends itself to other (multi language support ?) also if the SANE API
  > could be extended to cover some sort of SANE_Status to text translation
  > scheme.
  >
  > Or am I just barking up the wrong tree ???
  >
  > There also seems to be a large discrepancy in the level of diagnostic given
  > in each driver e.g. the Microtek driver seems to be absolutely LOADED with
  > debugging information (over 119 printfs, plus stacks of DBG callouts), but
  > others have very few at all.
  >
  > Then again, maybe I'm just used to being pampered by pay-ware rather than
  > GPL-ware ;-)
  >
  > Is there a list of proposed features (or just a wish list by SANE users) for
  > the next version ?
  >
  > Just curious
  >
  > Jason (who is subscribed to the list and so doesn't need cc-ing)

  Jason,

  in July or August 1999 was a larger discussion on the Sane mailing list
  about a new version of the Sane standard, including the question about
  more data formats. Technically quite interesting, I think. Unfortunately
  the debate ended up in some not very polite arguments. Since this time,
  nobody dared to pick up the topic again.

  But I don't think that this outcome is a required feature of GPL
  developement, only an optional one ;-)

  Abel

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

  - Next message: Karsten Festag: "Re: Microtek X6, USB and slackware problems"
  - Previous message: Heikki Kantola: "Re: SANE 1.0.4 and SnapScan library problems"
  - In reply to: Armistead, Jason: "RE: Getting compressed B/W image data from Fujitsu M3096GXm scann er"
  - Next in thread: Nick Lamb: "Re: Getting compressed B/W image data from Fujitsu M3096GXm scann er"
  - Reply: Nick Lamb: "Re: Getting compressed B/W image data from Fujitsu M3096GXm scann er"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Mon Feb 05 2001 - 14:06:07 PST