Johannes Meixner jsm...@suse.de writes:
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
Hello,
On Feb 23 10:34 Olaf Meeuwissen wrote (shortened):
What you are suggesting here sounds quite a bit to the way foomatic
handles printers.
- an XML database
- a few utilities to crank out PPD files
- one utility to glue the PPDs, the spooler and the printer drivers
together
Hello all,
hello Till,
I don't know if you followed the Infrared channel thread.
Now I include you explicitely because I think we have come
to a point where I would like to have you informed.
I don't know who is the scanner-stuff maintainer at Red Hat.
The Infrared channel thread has changed to
Le lundi 21 F=E9vrier 2005 22:05, Julien BLACHE a =E9crit=A0:
Gerhard Jaeger gerh...@gjaeger.de wrote:
Hi,
I'm going to play with this next week, and this will probably make it
into the next revision of the Debian package, and to the CVS :)
Hmmm, go ahead, but it should remain somewhat
On Wed, 23 Feb 2005, Till Kamppeter wrote:
I think, the best is if the backend can spit out this data. Then there can
never happen that the database and the actually installed backends differ
from each other.
unfortunately, scanners often work in a fashion similar to printers, the
model
Hello,
On Feb 23 15:14 Till Kamppeter wrote (shortened):
I think, the best is if the backend can spit out this data. Then there can
never happen that the database and the actually installed backends differ from
each other.
Yes, this would be best.
In SANE one has at least only one driver
Hello,
On Feb 23 10:05 m. allan noah wrote (shortened):
On Wed, 23 Feb 2005, Till Kamppeter wrote:
I think, the best is if the backend can spit out this data. Then there can
never happen that the database and the actually installed backends differ
from each other.
unfortunately,
Hello.
I do not understand the discussion about the sane config file format.
In a usual/normal case the config file of a backend should not be
touched by a user or configuration program:
- We do not need to enter any device files because the sanei_* routines
search the devices and passes them to
Hello.
I do not understand the discussion about the sane config file format.
In a usual/normal case the config file of a backend should not be
touched by a user or configuration program:
- We do not need to enter any device files because the sanei_* routines
search the devices and passes them to
This scanner *was* working normally, but now it makes scans that look
like this:
http://home.comcast.net/~hbbs/images/out.tiff
This is a 300x300 scan of a color print, full color range. This was
working fine but I can't imagine what may have changed. Perhaps someone
can tell me what
Hello.
I do not understand the discussion about the sane config file format.
In a usual/normal case the config file of a backend should not be
touched by a user or configuration program:
- We do not need to enter any device files because the sanei_* routines
search the devices and passes them to
most respectfully oliver, i disagree. perhaps your points about scanner
damage, etc are true in your backend because of models of scanners that
you support, but for my backend, it is far more likely that there is an
odd variation on the scanner that the backend does not know about, but
works
Am Mit, 2005-02-23 um 20.59 schrieb m. allan noah:
most respectfully oliver, i disagree. perhaps your points about scanner
damage, etc are true in your backend because of models of scanners that
you support, but for my backend, it is far more likely that there is an
odd variation on the
On Wed, 23 Feb 2005, Oliver Rauch wrote:
Am Mit, 2005-02-23 um 20.59 schrieb m. allan noah:
most respectfully oliver, i disagree. perhaps your points about scanner
damage, etc are true in your backend because of models of scanners that
you support, but for my backend, it is far more likely
but you give no reasons why! you just repeatedly say we are doing wrong.
that is not constructive.
yes, what the vendors do is odd and divergent from the normal sane
installation (suse's insistence on resmgr comes to mind) but if you admit
that there is a 'bad situation', the how about
--SUOF0GtieIMvvwua
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Feb 23, 2005 at 08:36:44PM +0100, Oliver Rauch wrote:
It is dangerous when a setup program or an unexperienced user is
changing the config file. For
16 matches
Mail list logo
