[sane-devel] XSane not showing full list of resolutions for Epson V500

2008-07-22 Thread Olaf Meeuwissen
Olaf Meeuwissen olaf.meeuwissen at avasys.jp writes: [snip] Apparently, something went wrong when initiating the scan but from the log I can't really tell what. Please try previewing in colour with scanimage as follows: SANE_DEBUG_EPKOWA=127 SANE_DEBUG_SANEI_USB=127 scanimage --mode

[sane-devel] [lsb-discuss] Scanning interfaces and LSB 4.0

2008-07-22 Thread Olaf Meeuwissen
Till Kamppeter till.kamppeter at gmail.com writes: Theodore Ts'o wrote: The simple solution would be add the necessary Scanner interfaces to the LSB. Unfortunately, we have many other high priority items on our work queue, and the SANE interfaces need to be documented before they could be

[sane-devel] [lsb-discuss] Scanning interfaces and LSB 4.0

2008-07-22 Thread m. allan noah
On Mon, Jul 21, 2008 at 4:36 AM, Till Kamppeter till.kamppeter at gmail.com wrote: Theodore Ts'o wrote: The simple solution would be add the necessary Scanner interfaces to the LSB. Unfortunately, we have many other high priority items on our work queue, and the SANE interfaces need to be

[sane-devel] [BUG] Duplicate SANE_NAME in saneopts.h

2008-07-22 Thread m. allan noah
Several backends use SANE_NAME_SCAN_X_RESOLUTION: abaton, artec, canon, epjitsu, fujitsu, microtek2, sp15c, and umax. I propose to change those backends to use SANE_NAME_SCAN_RESOLUTION, so that their UI does not change if we separate those options. comments? allan On Wed, Jul 9, 2008 at 11:57