Hi,

Because coolscan2 doesn't work with my Coolscan 5000 ED film scanner I
more or less rewrote coolscan2 as ls5000. During the cleanup I removed
support for all other scanners, it shouldn't be too hard to add back in.

Things I changed:
 * use C99 constructs for easier command packing
 * clean up coding style to conform to something I can work with
 * remove LS-40/4000/... support
 * add LS-5000 support (the coolscan2 package claims to support it but
   it doesn't work)
 * add grayscale support
 * clean up options
 * rip out the sane_read implementation and replace with something
   sane (excuse the pun)
 * add lots of comments about what the backend is doing
 * possibly lots more

I don't plan to submit any patches to coolscan2.c because that code is
in my eyes horrible to work with. I also don't plan to submit ls5000.c
to SANE because apparently SANE still requires that the backend builds
with ancient compilers.

The project has a tiny website at
http://johannes.sipsolutions.net/Projects/ls5000, code is available via

   git clone http://git.sipsolutions.net/ls5000.git

(and that URL also works as a gitweb URL)

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070511/71b4025c/attachment.pgp
From r...@exactcode.de  Fri May 11 14:03:14 2007
From: r...@exactcode.de (=?iso-8859-1?q?Ren=E9_Rebe?=)
Date: Fri May 11 14:04:18 2007
Subject: [sane-devel] [FYI] new ls5000 backend
In-Reply-To: <1178888306.8896.22.ca...@johannes.berg>
References: <1178888306.8896.22.ca...@johannes.berg>
Message-ID: <200705111603.15150.r...@exactcode.de>

Hi Johannes :-)

On Friday 11 May 2007 14:58:26 you wrote:

> Because coolscan2 doesn't work with my Coolscan 5000 ED film scanner I
> more or less rewrote coolscan2 as ls5000. During the cleanup I removed
> support for all other scanners, it shouldn't be too hard to add back in.
> 
> Things I changed:
>  * use C99 constructs for easier command packing
...
> I don't plan to submit any patches to coolscan2.c because that code is
> in my eyes horrible to work with. I also don't plan to submit ls5000.c
> to SANE because apparently SANE still requires that the backend builds
> with ancient compilers.

Indeed SANE is suppost to build on various other, aging Un*x flavours
and this is why so far no backend does use C99 features (at least as
far as I know and I also avoided it in my Avision backend as well).

Yours,

-- 
  Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name

Reply via email to