Re: [sane-devel] Pixma future

2020-11-25 Thread m. allan noah
On Wed, Nov 25, 2020 at 2:01 AM Alexander Pevzner  wrote:
>
> Obviously, this is better not to implement emulation of missed (in
> hardware) features in the drivers, to avoid code duplication and having
> an assortment of independent, often incompatible implementations of the
> similar features.
>

Nonsense. You can have every driver implement a consistent level of
features, and only have a single implementation of emulated functions.
You just need a library like sanei_magic, which is already used by a
number of existing backends to provide software deskew and autocrop
functions. It would be pretty easy to do something similar for
binarization.

allan
-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"



Re: [sane-devel] Pixma future

2020-11-25 Thread Olaf Meeuwissen
Hi Andrea,

Andrea Croci writes:

> [...] I have always wondered why the Windows programs make a 180 kB
> pdf of the same page for which xsane made a 7MB file (don't know if it
> has changed in the last few years since I'm scanning from command
> line).

That's probably because those Windows programs embed the images as JPEGs
and xsane embeds PNMs.  Needless to say, JPEGs suck for text documents.

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join