Christophe> 1. How can I invoke xscanimage from within gimp (btw
Christophe> could it be that gimp is kind of unstable right know? I
Christophe> somehow don't have the Gimp manpage, and in xscanimages
Christophe> manpage it says nothing...
The forthcoming xscanimage man-page has the following section. If
it's not clear or needs some other fixing, please let me know so I can
correct it before sane-0.61 comes out.
----
RUNNING UNDER THE GIMP
To run xscanimage under the gimp(1) , simply copy it to
one of the gimp(1) plug-ins directories. If you want to
conserve disk-space, you can create a symlink instead.
For example, the command
ln -s /usr/local/bin/xscanimage ~/.gimp/plug-ins/
adds a symlink for the xscanimage binary to the user's
plug-ins directory. After creating this symlink, xscanim-
age will be queried by gimp(1) the next time it's invoked.
From then on, xscanimage can be invoked through
"Xtns->Acquire Image->Device dialog..." menu entry.
You'll also find that the "Xtns->Acquire Image" menu con-
tains short-cuts to the SANE devices that were available
at the time the xscanimage was queried. For example, the
first PNM pseudo-device is typically available as the
short-cut "Xtns->Acquire Image->pnm:0". Note that gimp(1)
caches these short-cuts in ~/.gimp/pluginrc. Thus, when
the list of available devices changes (e.g., a new scanner
is installed), then it is typically desirable to rebuild
this cache. To do this, you can either touch(1) the
xscanimage binary (e.g., "touch /usr/local/bin/xscanim-
age") or delete the plug-ins cache (e.g., "rm
~/.gimp/plug-ins"). Either way, invoking gimp(1)
afterwards will cause the pluginrc to be rebuilt.
----
Christophe> 2. is that bad that whenever I scan I get this in
Christophe> messages: Jun 25 01:36:55 dumbo kernel:
Christophe> ncr53c810-0-<target 6, lun 0>: extraneous data
Christophe> discarded. Jun 25 01:36:55 dumbo kernel:
Christophe> ncr53c810-0-<target 6, lun 0>: COMMAND FAILED (9 0)
Christophe> @00ffe018.
No, that is "normal" with the ncr810 driver. The line-distance SCSI
command is causing this, but I'm not sure why. It is the reason there
NEED_MUSTEK_LINE_DISTANCE_WORKAROUND exists in the mustek backend. I
noticed that this workaround is not necessary under OpenStep. Has
anybody with a SCSI controller other than the ncr810 or on a non-Linux
platform tried configuring with option --disable-ld-fix and had
success with scanning color images? If so, I'd like to hear about it.
Christophe> oh, and I noticed that in the preview window and in GIMP
Christophe> itself aswell thw picture kind of gets broken and pieces
Christophe> move around abit, the pic gets mixed up. Is that due a
Christophe> buggy gtk ? Has anybody else experienced that ?
Not that I'm aware of. If the problem is serious, maybe you could
capture a snapshot that shows the problem and send it in (don't make
the snapshot too large, though...).
Christophe> ok thx for sane anyways - I love it
Nice to hear! ;-)
--david
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com