m. allan noah gmail.com> writes:
>
> On Mon, Feb 7, 2011 at 6:37 AM, Michael Rickmann gwdg.de>
> wrote:
> > I got a Reflecta USB film scanner to digitize my collection of old slides
> > and negatives.
>
>
>
> Some random thoughts:
>
> 1. SCSI over USB is a fairly common way for makers to up
I am really hopping that somebody can help me. I am at a loss.
I have a CanoScan Lide 110 on Ubuntu 10.10.
sane-find-scanner returns "found USB scanner (vendor=0x04a9 [Canon],
product=0x1909 [CanoScan], chip=GL124) at libusb:002:005" (which it
should) however, scanimage -L just returns the usual "N
at lists.alioth.debian.org
> >
>
>
>
> --
> "The truth is an offense, but not a sin"
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110308/a1ab837e/attachment.htm>
..
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110308/a6acc4a2/attachment.htm>
I will correct the bug.
Device string is parsed for network scanner support.
On Tue, Mar 08, 2011 at 08:23:43AM -0500, m. allan noah wrote:
> I am familiar with sanei_usb device detection, and I speak diff. The
> only thing that seems odd is just why the backend is parsing the
> device strings.
I am familiar with sanei_usb device detection, and I speak diff. The
only thing that seems odd is just why the backend is parsing the
device strings.
The author was responding to bug reports yesterday, so I think it's a
bit early for you to be pessimistic :)
allan
--
"The truth is an offense, bu
Responses below.
On Tue, Mar 8, 2011 at 1:13 AM, m. allan noah wrote:
> Thanks for the patch. I must confess I don't quite understand the
> code.
A lot of the lines of code just added debugging output so that I could
see what functions were being called as I find the code pretty
difficult to fol
You may produce whatever patches you want. It is up to the backend
author to accept the patch.
allan
On Tue, Mar 8, 2011 at 2:54 AM, Warren Turkal wrote:
> I see no consistent use of spaces and tabs in the source files that I
> am looking at. It makes it very difficult to see the flow of the cod
I see no consistent use of spaces and tabs in the source files that I
am looking at. It makes it very difficult to see the flow of the code.
Would a re-indent patch be accepted for some of these files so that
they might be easier to read be acceptable?
Thanks,
wt
