[sane-devel] API addition request

2009-06-22 Thread jeffrey.ratcli...@gmail.com
, then this would the problem on its own. Regards Jeff -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090622/06c00b2b/attachment-0001.htm

[sane-devel] Regarding Canon DR-2050C using sane-1.0.20 backend _ Duplex Option

2009-06-22 Thread Rajesh Shah
/attachments/20090622/d2724224/attachment.htm

[sane-devel] Canon LiDE 50 CanoScan (04a9:2213) is broken with 1.0.20

2009-06-22 Thread Ozan Çağlayan
Hi, I've just noticed that my Canon LiDE 50 is broken with sane-backends 1.0.20 (1.0.19 was OK). I've bisected it to: e026a4fa2c72f71a3a8b79755a36d32ae4cddecb is first bad commit commit e026a4fa2c72f71a3a8b79755a36d32ae4cddecb Author: Pierre Willenbrock pierre at pirsoft.dnsalias.org Date:

[sane-devel] Regarding Canon DR-2050C using sane-1.0.20 backend _ Duplex Option

2009-06-22 Thread m. allan noah
On Mon, Jun 22, 2009 at 8:39 AM, Rajesh Shahrajesh at finlogicindia.com wrote: Thank you very much for your reply . I was able to scan the page with duplex mode .. Basically my requirement is to create a multipage image with optimum size in tiff . I am using the following command to acheive

[sane-devel] Canon LiDE 50 CanoScan (04a9:2213) is broken with 1.0.20

2009-06-22 Thread Pierre Willenbrock
Ozan ?a?layan schrieb: Hi, I've just noticed that my Canon LiDE 50 is broken with sane-backends 1.0.20 (1.0.19 was OK). I've bisected it to: Thanks for bisecting, but this bug should be fixed in git master. See bug #311691. Regards, Pierre

[sane-devel] API addition request

2009-06-22 Thread Alessandro Zummo
On Sun, 21 Jun 2009 20:04:15 -0400 m. allan noah kitno455 at gmail.com wrote: Well, if we dont use params, our only choice with the current API is more well-known options. One advantage of moving maintained backends to a new package would be the possibility of regularizing/requiring such

[sane-devel] Canon LiDE 50 CanoScan (04a9:2213) is broken with 1.0.20

2009-06-22 Thread Ozan Çağlayan
Pierre Willenbrock wrote: Thanks for bisecting, but this bug should be fixed in git master. See bug #311691. Argh, I took a look at the commits after RELEASE_1_0_20 but that didn't catch my attention at all. I'll grab/try the patch tomorrow. Thanks!