Hello,
On Feb 22 11:29 m. allan noah wrote (shortened):
> > At the moment it is simply ignored when particular models require
> > special settings in .conf
>
> unfortunately, this can be difficult to deal with, since what
> each model needs can vary drastically. cheaper models that require
> firm
Hello,
On Feb 22 17:23 Gerhard Jaeger wrote (shortened):
> On Tuesday 22 February 2005 16:21, Johannes Meixner wrote:
> > Perhaps it is possible to "misuse" the PPD file syntax for scanner
> > setup as well.
>
> You are right, but I don't like the idea to "misuse" something,
> especially it has a
On Tuesday 22 February 2005 16:21, Johannes Meixner wrote:
[SNIPSNAP]
> Therefore it is normally not possible to determine the matching
> backend from the autodetected model string.
>
> I think we should discuss about an enhanced *.desc file format
> to specify autodetected model strings and model
Hello,
On Feb 22 09:16 m. allan noah wrote (shortened):
> i would like to see a few things done in the sane2 standard:
...
> 3. more consistent config file interface for all backends
I would appreciate this very much.
At the moment all what the Suse scanner config tool does is:
a) show a list of
On Tuesday 22 February 2005 11:54, gerard klaver wrote:
> On Tue, 2005-02-22 at 09:26 +0100, Rene Rebe wrote:
> > Hi,
> >
> > Gerhard Jaeger wrote:
> >
> > > the problem is our SANE 1 standard, which defines the image format.
> > > We have currently only the possibility to pass RGB data to a fron
>>> i would like to see a few things done in the sane2 standard:
>>> 3. more consistent config file interface for all backends
>>
>> I would appreciate this very much.
>>
>> At the moment all what the Suse scanner config tool does is:
>> a) show a list of model names made from the *.desc files
>>
On Tue, 2005-02-22 at 09:26 +0100, Rene Rebe wrote:
> Hi,
>=20
> Gerhard Jaeger wrote:
>=20
> > the problem is our SANE 1 standard, which defines the image format.
> > We have currently only the possibility to pass RGB data to a frontend=
.
> >=20
> > The solution (whenever we can start) is SANE 2
On Tue, Feb 22, 2005 at 08:28:18AM +0100, Gerhard Jaeger wrote:
> On Monday 21 February 2005 00:09, Michal Jaegermann wrote:
> >
> > But does somebody at least have some idea how to read an infrared
> > channel?
>
> the problem is our SANE 1 standard, which defines the image format.
> We have cur
> On Feb 22 09:16 m. allan noah wrote (shortened):
>> i would like to see a few things done in the sane2 standard:
> ...
>> 3. more consistent config file interface for all backends
>
> I would appreciate this very much.
>
> At the moment all what the Suse scanner config tool does is:
> a) show a l
Hi,
Major A wrote:
>>- starting SANE 2 with, let's say 2 or three backends (in the end your Avision
>> stuff, my Plustek backends (plustek, plustek_pp and u12, maybe some other
>> VOLUNTEERS - hell lot of work to do ;)
>
>
> I've been suggesting that for months. As soon as a simple S
On Tuesday 22 February 2005 09:26, Rene Rebe wrote:
> Hi,
>
> Gerhard Jaeger wrote:
>
> > the problem is our SANE 1 standard, which defines the image format.
> > We have currently only the possibility to pass RGB data to a frontend.
> >
> > The solution (whenever we can start) is SANE 2 where we
Hi,
Gerhard Jaeger wrote:
> the problem is our SANE 1 standard, which defines the image format.
> We have currently only the possibility to pass RGB data to a frontend.
>
> The solution (whenever we can start) is SANE 2 where we have a more flexible
> approach for transmitting image data to a fr
> - starting SANE 2 with, let's say 2 or three backends (in the end your Avision
> stuff, my Plustek backends (plustek, plustek_pp and u12, maybe some other
> VOLUNTEERS - hell lot of work to do ;)
I've been suggesting that for months. As soon as a simple SANE2
front-end (scanimage) i
the problem is our SANE 1 standard, which defines the image format.
We have currently only the possibility to pass RGB data to a frontend.
The solution (whenever we can start) is SANE 2 where we have a more
flexible
approach for transmitting image data to a frontend.
Hi,
On Monday 21 February 2005 00:09, Michal Jaegermann wrote:
>
> Yes, I have seen a rather short "Sane does not support the dust
> removal with the Perfection 4870" here:
>
> http://lists.alioth.debian.org/pipermail/sane-devel/2004-September/012111.html
>
> But does somebody at least have som
15 matches
Mail list logo
