[sane-devel] Perl Bindings

2008-09-02 Thread Jeffrey Ratcliffe
2008/9/1 abel deuring adeuring at gmx.net: The test backend is a invaluably useful tool for testing: You get more or less any sort of device options; you can see if your bindings properly handle things like enabling/disabling of options, if you get the type conversion between Sane and Perl

[sane-devel] Perl Bindings

2008-09-02 Thread abel deuring
On 02.09.2008 07:25, Jeffrey Ratcliffe wrote: 2008/9/1 abel deuring adeuring at gmx.net: The test backend is a invaluably useful tool for testing: You get more or less any sort of device options; you can see if your bindings properly handle things like enabling/disabling of options, if you get

[sane-devel] Perl Bindings

2008-09-02 Thread Jeffrey Ratcliffe
2008/9/2 abel deuring adeuring at gmx.net: I would not mind seeing Perl bindings included. But other Sane folks should give their opinion too. I could imagine that CPAN might be a better place for the bindings, since Perl developers might look for Perl modules there, I'd guess. (disclaimer: I

[sane-devel] Fujitsu FI-5220C and no Option for threshold possible?

2008-09-02 Thread Markus Haberkorn
Hello, I use scanner Fujitsu FI-5220C and it works fine. /usr/bin/scanadf --mode Gray --resolution 150 --source Flatbed -e 1 -s 1 -o foo.pnm -v scanadf: scanning image of size 1275x1650 pixels at 8 bits/pixel scanadf: acquiring gray frame scanadf: min/max graylevel value = 13/255 Scanned

[sane-devel] Fujitsu FI-5220C and no Option for threshold possible?

2008-09-02 Thread m. allan noah
On Tue, Sep 2, 2008 at 7:56 AM, Markus Haberkorn Markus_Haberkorn at genua.de wrote: Hello, I use scanner Fujitsu FI-5220C and it works fine. /usr/bin/scanadf --mode Gray --resolution 150 --source Flatbed -e 1 -s 1 -o foo.pnm -v scanadf: scanning image of size 1275x1650 pixels at 8

[sane-devel] Perl Bindings

2008-09-02 Thread m. allan noah
we have found that previous bindings that are included with sane are often not kept up-to-date by their authors, not installed by the distro vendors, and reimplemented by folks in their respective communities. I think outside hosting makes more sense. a patch for pkg-config would be accepted, if

[sane-devel] libusb-dev for Mac Leopard?

2008-09-02 Thread Bob Dronski
I'm still trying to get the Canon MP4150 working. In an attempt to debug, Nicolas recommended I use libusb-dev. Unfortunately, all I can find are packages and source for libusb. Does anyone have any experience creating a version of libusb-dev for mac? Even a location of source? Thanks,

[sane-devel] pixma MP810 working with sane

2008-09-02 Thread Nicolas
Hi, Concerning the vertical lines at 4800/2400 dpi for MP810, I'm wondering whether: - this is a normal behavior of the scanner (which would mean that it has to be compensated by the backend), - or if it's an alignment problem of the sensor, the lines corresponding each one to a particular

[sane-devel] libusb-dev for Mac Leopard?

2008-09-02 Thread Bob Dronski
your_password to sane-devel-request at lists.alioth.debian.org -- Dale -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080902/52663fd4/attachment-0001.htm

[sane-devel] libusb-dev for Mac Leopard?

2008-09-02 Thread Bob Dronski
your_password to sane-devel-request at lists.alioth.debian.org -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080902/c3e8691d/attachment.htm

[sane-devel] Canon MP4150 - WORKS!!! (basically)

2008-09-02 Thread Bob Dronski
Dennis, Nicolas, and the rest of the list, Thanks so much for all your help. I'm thrilled to say that the scanner works after a new build of both libusb and Sane! There are a couple of issues that still occur, but basically, it works. I've done both flatbed and adf scanning. The only

[sane-devel] pixma MP810 working with sane

2008-09-02 Thread m. allan noah
On Tue, Sep 2, 2008 at 4:59 PM, Nicolas nicolas.martin at freesurf.fr wrote: Hi, Concerning the vertical lines at 4800/2400 dpi for MP810, I'm wondering whether: - this is a normal behavior of the scanner (which would mean that it has to be compensated by the backend), - or if it's an