mirror
/
sane-project-backends
kopia lustrzana https://gitlab.com/sane-project/backends
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

doc: final pass through the man pages. 

Mostly just tidy up, catching pages that I missed the first time round.
A small number of pages were given a bit more reformat. A bit beyond
the remit of this merge request but not too much has been changed.
merge-requests/603/head
Ralph Little 2021-02-13 12:02:54 -08:00
rodzic 0eaae38d1e
commit 85f4ef1065
99 zmienionych plików z 1569 dodań i 1184 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

3
doc/gamma4scanimage.man
Wyświetl plik

@ -72,10 +72,11 @@ scanimage \-\-custom\-gamma=yes \-\-gamma\-table
>image.pnm
.SH SEE ALSO
.BR sane (7),
.BR scanimage (1)
.SH AUTHOR
Oliver Rauch
.SH EMAIL-CONTACT
Oliver.Rauch@Rauch-Domain.DE
.I Oliver.Rauch@Rauch-Domain.DE

40
doc/sane-abaton.man
Wyświetl plik

@ -16,7 +16,8 @@ works with this backend, or if you own an Abaton scanner that does not
work with this backend, please contact
.IR sane\-devel@alioth-lists.debian.net
with the model number, so that arrangements can be made to include
support for it. Have a look at http://www.sane\-project.org/mailing\-lists.html
support for it. Have a look at
.I http://www.sane\-project.org/mailing\-lists.html
concerning subscription to sane\-devel.
.PP
Abaton is out of business, and these scanners are not supported by
@ -48,13 +49,17 @@ name takes a format such as
.I /dev/sga
or
.IR /dev/sg0 ,
for example. See sane\-scsi(5) for details.
for example. See
.BR sane\-scsi (5)
for details.
.SH CONFIGURATION
The contents of the
.I abaton.conf
file is a list of device names that correspond to Abaton scanners.
Empty lines and lines starting with a hash mark (#) are ignored. See
sane\-scsi(5) on details of what constitutes a valid device name.
.BR sane\-scsi (5)
on details of what constitutes a valid device name.
.SH FILES
.TP
@ -77,13 +82,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory separator
character, then the default directories are searched after the explicitly
specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_ABATON
If the library was compiled with debug support enabled, this
@ -119,8 +129,14 @@ confidence that it will work, as well as to fully exploit the
information returned by the INQUIRY command.
.SH "SEE ALSO"
sane(7), sane\-scsi(5), scanimage(1)
.BR sane (7),
.BR sane\-scsi (5),
.BR scanimage (1)
.SH AUTHOR
The sane\-abaton backend was partially written by David Huggins-Daines,
based on the sane\-apple backend by Milon Firikis.
The
.B sane\-abaton
backend was partially written by David Huggins-Daines,
based on the
.BR sane\-apple (5)
backend by Milon Firikis.

48
doc/sane-agfafocus.man
Wyświetl plik

@ -32,7 +32,8 @@ If you own a scanner other than the ones listed above that works with
this backend, please let us know by sending the scanner's model name,
SCSI id, and firmware revision to
.IR sane\-devel@alioth-lists.debian.net .
Have a look at http://www.sane\-project.org/mailing\-lists.html
Have a look at
.I http://www.sane\-project.org/mailing\-lists.html
concerning subscription to sane\-devel.
.PP
All of these scanners are pre-SCSI-2, and do not even report properly
@ -55,7 +56,10 @@ a device name could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See sane\-scsi(5) for details.
for example. See
.BR sane\-scsi (5)
for details.
.SH CONFIGURATION
The contents of the
.I agfafocus.conf
@ -93,19 +97,25 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in /etc/sane.d. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory separator
character, then the default directories are searched after the
explicitly specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"/etc/sane.d" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_AGFAFOCUS
If the library was compiled with debug support enabled, this environment
variable controls the debug level for this backend. E.g., a value of 128
requests all debug output to be printed. Smaller levels reduce verbosity.
SANE_DEBUG_AGFAFOCUS values:
.B SANE_DEBUG_AGFAFOCUS
values:
.sp
.ft CR
@ -138,8 +148,9 @@ these options have been disabled.
The scanners that do not support disconnect have problems with SCSI
timeouts if the SCSI bus gets loaded, eg. if you do a kernel build at
the same time as scanning. To see if your scanner supports
disconnect, run "SANE_DEBUG_AGFAFOCUS=128 scanimage \-L" in sh and look
for the "disconnect:" line)
disconnect, run
.I "SANE_DEBUG_AGFAFOCUS=128 scanimage \-L"
in a terminal and look for the "disconnect:" line.
.SH DEBUG
If you have problems with SANE not detecting your scanner, make sure the
@ -147,12 +158,14 @@ Artec backend is disabled. Somehow, this backend causes at least my scanner
not to respond correctly to SCSI inquiry commands.
.PP
If you encounter a bug please set the environment variable
SANE_DEBUG_AGFAFOCUS to 128 and try to regenerate the problem. Then
send me a report with the log attached.
.B SANE_DEBUG_AGFAFOCUS
to 128 and try to regenerate the problem. Then send me a report with the
log attached.
.PP
If you encounter a SCSI bus error or trimmed and/or displaced images please
also set the environment variable SANE_DEBUG_SANEI_SCSI to 128 before sending
me the report.
also set the environment variable
.B SANE_DEBUG_SANEI_SCSI
to 128 before sending me the report.
.SH TODO
.TP
@ -166,9 +179,10 @@ a scanner, I could be helpful in adding support for these scanners.
The AGFA HORIZON scanners are SCSI-2 scanners, and it would probably
be easier to support these scanners in a SCSI-2 compliant backend.
.SH SEE ALSO
sane(7), sane\-scsi(5)
.BR sane (7),
.BR sane\-scsi (5)
.SH AUTHOR
Ingo Schneider and Karl Anders \[/O]ygard.

64
doc/sane-apple.man
Wyświetl plik

@ -24,8 +24,9 @@ If you own a Apple scanner other than the ones listed above that
works with this backend, please let us know by sending the scanner's
model name, SCSI id, and firmware revision to
.IR sane\-devel@alioth-lists.debian.net .
See http://www.sane\-project.org/mailing\-lists.html for details on how to subscribe to
sane\-devel.
See
.I http://www.sane\-project.org/mailing\-lists.html
for details on how to subscribe to sane\-devel.
.SH "DEVICE NAMES"
This backend expects device names of the form:
@ -43,14 +44,18 @@ symlink to such a device. Under Linux, such a device name could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See sane\-scsi(5) for details.
for example. See
.BR sane\-scsi (5)
for details.
.SH CONFIGURATION
The
.I apple.conf
file is a list of options and device names that correspond to Apple
scanners. Empty lines and lines starting with a hash mark (#) are
ignored. See sane\-scsi(5) on details of what constitutes a valid
device name.
ignored. See
.BR sane\-scsi (5)
on details of what constitutes a valid device name.
.PP
Options come in two flavors: global and positional ones. Global
options apply to all devices managed by the backend, whereas positional
@ -83,13 +88,18 @@ This environment variable is list of directories where SANE looks
for the configuration file. Under UNIX directory names are
separated by a colon (`:'), under OS/2 by a semi-colon (`;').
If SANE_CONFIG_DIR is not set, SANE defaults to
searching the current working directory (".") and then /etc/sane.d.
searching the current working directory (".") and then
.IR @CONFIGDIR@ .
If the value of $SANE_CONFIG_DIR ends with the separator
character, the default directories are searched after the directory list.
For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in that order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in that order).
.TP
.B SANE_DEBUG_APPLE
Controls the debug level. A value of 255 prints
@ -100,7 +110,7 @@ library compiled with debug support.
The apple backend is now in version 0.3 (Tue Jul 21 1998). Since
I only have the AppleScanner and not the other models (OneScanner,
ColorOneScanner) I can only develop/test for the AppleScanner effectively.
However with this release I almost completed the gui part of all scanners.
However with this release I almost completed the GUI part of all scanners.
Most of the functionality is there. At least OneScanner should scan
at the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
personal belief is that with a slight touch of debugging the OneScanner
@ -167,7 +177,7 @@ bugs.
We know we have a GUI bug when a parameter is not showing up when it
should (active) or vice versa. Finding out which parameters are active
across various Apple modes and models from the documentation
.B ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripherals_Documentation/
.I ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripherals_Documentation/
is an interesting exercise. I may have missed some dependencies. For example
of the threshold parameter the Apple Scanners Programming Guide says
nothing. I had to assume it is valid only in LineArt mode.
@ -212,7 +222,8 @@ hardware, or may be bugs in your driver or in SANE itself...
.SH DEBUG
If you encounter a GUI bug please set the environmental variable
SANE_DEBUG_APPLE to 255 and rerun the exact sequence of keystrokes
.B SANE_DEBUG_APPLE
to 255 and rerun the exact sequence of keystrokes
and menu selections to reproduce it. Then send me a report with the
log attached.
.PP
@ -223,9 +234,16 @@ would be very helpful.
If you want to offer some help but you don't have a scanner, or you
don't have the model you would like to help with, or you are
a SANE developer and you just want to take a look at how the apple backend
looks like, goto to apple.h and #define the NEUTRALIZE_BACKEND
looks like, goto to
.I apple.h
and #define the
.B NEUTRALIZE_BACKEND
macro. You can select the scanner model through the APPLE_MODEL_SELECT
macro. Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
macro. Available options are
.BR APPLESCANNER ,
.BR ONESCANNER ,
and
.BR COLORONESCANNER .
.PP
If you encounter a SCSI bus error or trimmed and/or displaced images please
set the environment variable SANE_DEBUG_SANEI_SCSI to 255 before sending me
@ -234,10 +252,12 @@ the report.
.SH TODO
.TP
.B Non Blocking Support
Make sane\-apple a non blocking backend. Properly support
.B sane_set_io_mode
Make
.B sane\-apple
a non blocking backend. Properly support
.BR sane_set_io_mode ()
and
.B sane_get_select_fd
.BR sane_get_select_fd ()
.TP
.B Scan
Make scanning possible for all models in all supported modes.
@ -245,9 +265,13 @@ Make scanning possible for all models in all supported modes.
Add other missing functionality
.SH "SEE ALSO"
sane(7), sane\-scsi(5)
.BR sane (7),
.BR sane\-scsi (5)
.SH AUTHOR
The sane\-apple backend was written not entirely from scratch by
Milon Firikis. It is mostly based on the mustek backend from
David Mosberger and Andreas Czechanowski
The
.B sane\-apple
backend was written not entirely from scratch by
Milon Firikis. It is mostly based on the
.BR sane\-mustek (5)
backend from David Mosberger and Andreas Czechanowski

35
doc/sane-artec.man
Wyświetl plik

@ -32,14 +32,7 @@ the following scanners are known to work at least partially with this backend:
Although this manual page is generally updated with each release,
up-to-date information on new releases and extraneous helpful hints
are available from the backend homepage:
.br
.br
.RS
.B http://www4.infi.net/~cpinkham/sane/
.RE
.SH DOCUMENTATION
.IR http://www4.infi.net/~cpinkham/sane .
.SH CONFIGURATION
@ -48,12 +41,11 @@ The contents of the
file are a list of device names that
correspond to Artec scanners. Empty lines and lines starting with a
hash mark (#) are ignored. See
.I sane\-scsi(5)
.BR sane\-scsi (5)
on details of what constitutes a valid device name.
Sample file:
.br
.br
.nf
# artec.conf
#
@ -107,6 +99,7 @@ The static library implementing this backend.
.I @LIBDIR@/libsane\-artec.so
The shared library implementing this backend (present on systems that
support dynamic loading).
.SH ENVIRONMENT
.TP
.B SANE_CONFIG_DIR
@ -115,19 +108,26 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a semi-
colon (`;'). If this variable is not set, the configuration file is
searched in two default directories: first, the current working direc-
tory (".") and then in @CONFIGDIR@. If the value of the
tory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_ARTEC
If the library was compiled with debug support enabled, this environment
variable controls the debug level for this backend. E.g., a value of 128
requests all debug output to be printed. Smaller levels reduce verbosity:
SANE_DEBUG_ARTEC values
.B SANE_DEBUG_ARTEC
values:
.ft CR
.nf
@ -170,9 +170,10 @@ the SCSI bus (and/or machine) by not having patience enough when scanning.
correction is not totally working on models other than the AT3.
.SH "SEE ALSO"
sane(7), sane\-scsi(5)
.BR sane (7) ,
.BR sane\-scsi (5)
.SH AUTHOR
Chris Pinkham (cpinkham@corp.infi.net)
Chris Pinkham
.I <cpinkham@corp.infi.net>

55
doc/sane-artec_eplus48u.man
Wyświetl plik

@ -17,14 +17,19 @@ the scan area.
.PP
If you own a scanner other than the ones mentioned on the list that works with this
backend, please let us know this by sending the scanner's exact model name and
the USB vendor and product ids (e.g. from /proc/bus/usb/devices,
sane\-find\-scanner or syslog) to me. Even if the scanner's name is only
the USB vendor and product ids (e.g. from
.IR /proc/bus/usb/devices ,
.BR sane\-find\-scanner (1)
or syslog) to me. Even if the scanner's name is only
slightly different from the models mentioned above, please let me know.
.PP
.SH KERNEL ISSUES
If libusb-0.1.6 or later is installed, this section can be skipped. The
scanner should be found by sane\-find\-scanner without further actions. For
setting permissions and general USB information look at sane\-usb(5).
scanner should be found by
.BR sane\-find\-scanner (1)
without further actions. For setting permissions and general USB information
look at
.BR sane\-usb (5).
.PP
When you are using the scanner module, a Linux kernel 2.4.12 or newer is
required.
@ -32,11 +37,16 @@ required.
.SH FIRMWARE FILE
You need a firmware file for your scanner. That's a small file containing
software that will be uploaded to the scanner's memory. For the scanners
mentioned above, it's usually named Artec48.usb or 1200.usb. You can find it on
the installation CD that was provided by the manufacturer, normally in the
directory Win98, WinMe or similar. If the Windows-driver is installed on your
computer, then you can also find the firmware file under
c:\\windows\\system32\\drivers.
mentioned above, it's usually named
.I Artec48.usb
or
.IR 1200.usb .
You can find it on the installation CD that was provided by the manufacturer,
normally in the directory Win98, WinMe or similar.
If the Windows-driver is installed on your computer, then you can also
find the firmware file under
.IR c:\\windows\\system32\\drivers .
.SH CONFIGURATION
The contents of the
.I artec_eplus48u.conf
@ -105,13 +115,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in /usr/local/etc/sane.d. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory
separator character, then the default directories are searched after
the explicitly specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_ARTEC_EPLUS48U
If the library was compiled with debug support enabled, this
@ -122,15 +137,19 @@ Example:
export SANE_DEBUG_ARTEC_EPLUS48U=3
.SH "SEE ALSO"
sane(7), sane\-usb(5)
.BR sane (7),
.BR sane\-usb (5)
.SH AUTHOR
Michael Herder
Michael Herder.
.br
This backend is based on the gt68xx test-program written by Sergey Vlasov, Andreas Nowack, and
David Stevenson. Thanks to everyone who tested the backend or reported bugs.
.br
This man page is based on man sane\-gt68xx, written by Henning Meier-Geinitz.
This man page is based on man
.BR sane\-gt68xx (5),
written by Henning Meier-Geinitz.
.SH BUGS
This backend has been tested on Linux only. If you are using it on a different platform, please
contact us.

28
doc/sane-as6e.man
Wyświetl plik

@ -6,35 +6,29 @@ sane\-as6e \- SANE backend for using the Artec AS6E parallel port interface scan
.SH DESCRIPTION
The
.B sane\-as6e
library implements a
.B SANE
(Scanner Access Now Easy) backend
library implements a SANE (Scanner Access Now Easy) backend
that provides access to Artec AS6E flatbed scanner.
It requires the
.B as6edriver
program in order to operate. The
.B as6edriver
program is not included with the
.B SANE
package.
It can be found at
.BR http://as6edriver.sourceforge.net.
program is not included with the SANE
package. It can be found at
.IR http://as6edriver.sourceforge.net .
See the as6edriver documentation for technical information.
.PP
The
.B as6edriver
program must be in the path for executables ($PATH). Especially if you run
program must be in the path for executables
.RB ( $PATH ).
Especially if you run
.BR saned (8)
(the
.B SANE
network scanning daemon), take care to setup the path for
(the SANE network scanning daemon), take care to setup the path for
.BR inetd (8)
or
.BR xinetd (8)
correctly or place the program in a directory that is in the path.
.PP
.SH FILES
.B as6edriver
\- driver program that controls the scanner.
@ -42,7 +36,9 @@ correctly or place the program in a directory that is in the path.
.SH SEE ALSO
.BR sane (7),
.BR as6edriver (5),
.BR saned (8)
.BR saned (8),
.BR inetd (8),
.BR xinetd (8)
.br
.I http://as6edriver.sourceforge.net
@ -50,4 +46,4 @@ correctly or place the program in a directory that is in the path.
Eugene S. Weiss
.SH EMAIL-CONTACT
yossarian@users.sourceforge.net
.I yossarian@users.sourceforge.net

42
doc/sane-avision.man
Wyświetl plik

@ -5,10 +5,6 @@
sane\-avision \- SANE backend for original Avision and Avision OEM scanners
(HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film scanners.
.SH ABOUT THIS FILE
This file is a short description for the avision-backend shipped with SANE.
.SH DESCRIPTION
The
.B sane\-avision
@ -16,7 +12,7 @@ library implements a SANE (Scanner Access Now Easy) backend that
provides access to various Avision scanners and the Avision OEM
scanners labelled by HP, Minolta, Mitsubishi or Fujitsu.
It is fully big-endian aware and in every-day use on PowerPC and SPARC
It is fully big-endian aware and in everyday use on PowerPC and SPARC
systems.
.B I suggest you hold one hand on the power-button of the scanner while
@ -102,9 +98,14 @@ Where
.I scsi-spec
is the path-name to a special device or a device ID for the device that
corresponds to a SCSI scanner. The special device name must be a generic
SCSI device or a symlink to such a device, for example on Linux "/dev/sga"
or "/dev/sg0". The device ID is the ID returned by the scanner, for example
"HP" or "AVISION". See sane\-scsi(5) for details.
SCSI device or a symlink to such a device, for example on Linux
.I /dev/sga
or
.IR /dev/sg0 .
The device ID is the ID returned by the scanner, for example
"HP" or "AVISION". See
.BR sane\-scsi (5)
for details.
.TP
Note:
Since the backend now includes native USB access,
@ -116,10 +117,12 @@ the HP 53xx, HP 74xx or Minolta film-scanners.
.I usb-spec
is the USB device name, the vendor/product ID pair or the name used by
libusb corresponding to the USB scanner. For example "0x03f0 0x0701" or
"libusb:002:003". See sane\-usb(5) for details.
"libusb:002:003". See
.BR sane\-usb (5)
for details.
The program
.IR sane\-find\-scanner
.BR sane\-find\-scanner (1)
helps to find out the correct scsi or usb device name.
A list with supported devices is built into the avision backend so
@ -147,13 +150,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_AVISION
If the library was compiled with debug support enabled, this
@ -165,11 +174,14 @@ Example:
export SANE_DEBUG_AVISION=7
.SH "SEE ALSO"
sane(7), sane\-scsi(5), sane\-usb(5)
.BR sane (7),
.BR sane\-scsi (5),
.BR sane\-usb (5)
.br
http://exactcode.com/site/open_source/saneavision/
.I http://exactcode.com/site/open_source/saneavision
.SH MAINTAINER
Ren\['e] Rebe
.SH AUTHOR
Ren\['e] Rebe and Meino Christian Cramer

412
doc/sane-bh.man
Wyświetl plik

@ -11,7 +11,7 @@ provides access to Bell+Howell Copiscan II series document
scanners. The Copiscan II 6338 has been the primary scanner model
used during development and testing, but since the programming interface
for the entire series is consistent the backend should work for the
following scanner models.
following scanner models:
.PP
.RS
COPISCAN II 6338 Duplex Scanner with ACE
@ -30,12 +30,12 @@ COPISCAN II 3338(A) Simplex Scanner (with ACE)
.PP
If you have a Bell+Howell scanner and are able to test it with this
backend, please contact
.IR sane\-devel@alioth-lists.debian.net
.I sane\-devel@alioth-lists.debian.net
with the model number and testing results. Have a look at
http://www.sane\-project.org/mailing\-lists.html concerning subscription to
sane\-devel. Additionally, the author is curious as to the likelihood of using
this backend with the newer 4000 and 8000 series scanners. If you have such a
beast, please let me know.
.I http://www.sane\-project.org/mailing\-lists.html
concerning subscription to sane\-devel. Additionally, the author is
curious as to the likelihood of using this backend with the newer 4000
and 8000 series scanners. If you have such a beast, please let me know.
.PP
The Bell+Howell Copiscan II series document scanners are high
volume, high throughput scanners designed for document scanning
@ -56,7 +56,7 @@ The latest backend release, additional information and helpful hints
are available from the backend homepage:
.br
.RS
.B http://www.martoneconsulting.com/sane\-bh.html
.I http://www.martoneconsulting.com/sane\-bh.html
.RE
.SH "DEVICE NAMES"
This backend expects device names of the form:
@ -74,180 +74,9 @@ name takes a format such as
.I /dev/sga
or
.IR /dev/sg0 ,
for example. See sane\-scsi(5) for details.
.SH CONFIGURATION
The contents of the
.I bh.conf
file is a list of device names that correspond to Bell+Howell
scanners. See sane\-scsi(5) on details of what constitutes a valid device name.
Additionally, options can be specified; these lines begin with the word "option".
Each option is described in detail below. Empty lines and lines starting
with a hash mark (#) are ignored.
.SH OPTIONS
The following options can be specified in the
.I bh.conf
file.
.TP
.B disable\-optional\-frames
This option prevents the backend from sending any optional frames. This
option may be useful when dealing with frontends which do not support these
optional frames. When this option is in effect, the data is sent in a
SANE_FRAME_GRAY frame. The optional frames sent by this backend are:
SANE_FRAME_G31D, SANE_FRAME_G32D, SANE_FRAME_G42D and SANE_FRAME_TEXT.
These frames are generated based on the compression and barcode options.
These frames are never sent in preview mode.
.TP
.B fake\-inquiry
This option is used for debugging purposes and its use is not encouraged.
Essentially, it allows the backend to initialize in the absence of
a scanner. This is useful for development and not much else.
This option must be specified earlier in the configuration file than
the devices which are to be "faked".
.SH FILES
.TP
.I @CONFIGDIR@/bh.conf
The backend configuration file (see also description of
.B SANE_CONFIG_DIR
below).
.TP
.I @LIBDIR@/libsane\-bh.a
The static library implementing this backend.
.TP
.I @LIBDIR@/libsane\-bh.so
The shared library implementing this backend (present on systems that
support dynamic loading).
.SH ENVIRONMENT
.TP
.B SANE_CONFIG_DIR
This environment variable specifies the list of directories that may
contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
.TP
.B SANE_DEBUG_BH
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend. E.g.,
a value of 255 requests all debug output to be printed. Smaller
levels reduce verbosity.
.SH "SUPPORTED FEATURES"
.TP
.B ADF support
With document scanners, automatic document feeder (ADF) support is a key
feature. The backend supports the ADF by default and returns
.B SANE_STATUS_NO_DOCS
when the out-of-paper condition is detected. The SANE frontend
.B scanadf
is a command line frontend that supports multi-page scans. It has been
used successfully with this backend. The SANE frontend
.B xsane
is an improved GUI frontend by Oliver Rauch. Support for multi-page
scans is included in xsane version 0.35 and above.
.TP
.B Duplex scanning
Some models, such as the COPISCAN II 6338, support duplex scanning. That
is, they scan both sides of the document during a single pass through the
scanner (the scanner has two cameras). This backend supports duplex
scanning (with the
.B \-\-duplex
option). The front and back page images are delivered consecutively
as if they were separately scanned pages.
.TP
.B Hardware compression
The scanner is capable of compressing the data into several industry
standard formats (CCITT G3, CCITT G3-2D, CCITT G4). This results in
increased performance as less data is passed from the scanner to the
host over the SCSI bus. The backend supports these compression formats
via the
.B \-\-g31d, \-\-g32d, \-\-g42d
options, respectively. Many SANE frontends are not equipped to deal with
these formats, however. The SANE frontend
.B scanadf
supports these optional frame formats. The compressed image data
is written directly to a file and can then be processed by a scan-script
using the
.B \-\-scan\-script
option. Examples of this are given on the scanadf homepage.
.TP
.B Automatic Border Detection
The scanner can automatically detect the paper size and adjust the
scanning window geometry appropriately. The backend supports this
useful feature with the
.B \-\-autoborder
option. It is enabled by default.
.TP
.B Batch Mode Scanning
The batch scan mode allows for maximum throughput. The Set Window
parameters must remain constant during the entire batch.
.TP
.B Icon Generation
The Icon function generates a thumbnail of the full page image, that can be
transferred as if it were a separate page. This allows the host to
quickly display a thumbnail representation during the scanning operation.
Perhaps this would be a great way of implementing a preview scan, but
since a normal scan is so quick, it might not be worth the trouble.
.TP
.B Multiple Sections
Multiple sections (scanning sub-windows) can be defined for the front and
back pages. Each section can have different characteristics (e.g. geometry,
compression). The sections are returned as if they were separately
scanned images. Additionally sections can be used to greatly enhance the
accuracy and efficiency of the barcode/patchcode decoding process by
limiting the search area to a small subset of the page. Most Copiscan II
series scanners support up to 8 user-defined sections.
.TP
.B Support Barcode/Patchcode Decoding
The RSC unit can recognize Bar and Patch Codes of various types embedded
in the scanned image. The codes are decoded and the data is returned to
the frontend as a text frame. The text is encoded in xml and contains
a great deal of information about the decoded data such as the location
where it was found, its orientation, and the time it took to find.
Further information on the content of this text frame as well as some
barcode decoding examples can be found on the backend homepage.
.SH LIMITATIONS
.TP
.B Decoding a single barcode type per scan
The RSC unit can search for up to six different barcode types at a time.
While the code generally supports this as well, the
.B \-\-barcode\-search\-bar
option only allows the user to specify a single barcode type.
Perhaps another option which allows a comma separated list of barcode
type codes could be added to address this.
.TP
.B Scanning a fixed number of pages in batch mode
The separation of front and back end functionality in SANE presents a
problem in supporting the 'cancel batch' functionality in the scanner.
In batch mode, the scanner is always a page ahead of the host. The host,
knowing ahead of time which page will be the last, can cancel batch mode
prior to initiating the last scan command. Currently, there is no mechanism
available for the frontend to pass this knowledge to the backend.
If batch mode is enabled and the \-\-end\-count terminates a scanadf session,
an extra page will be pulled through the scanner, but is neither read
nor delivered to the frontend. The issue can be avoided by specifying
\-\-batch=no when scanning a fixed number of pages.
.TP
.B Revision 1.2 Patch detector
There is an enhanced patchcode detection algorithm available in the RSC
with revision 1.2 or higher that is faster and more reliable than the
standard Bar/Patch code decoder. This is not currently supported.
for example. See
.BR sane\-scsi (5)
for details.
.SH OPTIONS
.TP
@ -256,7 +85,8 @@ standard Bar/Patch code decoder. This is not currently supported.
.B \-\-preview[=(yes|no)] [no]
Request a preview-quality scan. When preview is set to yes image
compression is disabled and the image is delivered in a
SANE_FRAME_GRAY frame.
.B SANE_FRAME_GRAY
frame.
.TP
.B \-\-mode lineart|halftone [lineart]
Selects the scan mode (e.g., lineart,monochrome, or color).
@ -268,6 +98,7 @@ a list of standard resolutions; only these resolutions can be used.
.B \-\-compression none|g31d|g32d|g42d [none]
Sets the compression mode of the scanner. Determines the type of data
returned from the scanner. Values are:
.RS
.br
.B none
@ -282,7 +113,9 @@ returned from the scanner. Values are:
.B g42d
\- CCITT G4 (MMR) \- delivered in a SANE_FRAME_G42D frame
.br
NOTE: The use of g31d, g32d, and g42d compression values causes the backend
.BR NOTE :
The use of g31d, g32d, and g42d compression values causes the backend
to generate optional frame formats which may not be supported by all SANE
frontends.
.RE
@ -314,7 +147,8 @@ Bottom-right y position of scan area.
.TP
.B \-\-source Automatic Document Feeder|Manual Feed Tray [Automatic Document Feeder]
Selects the scan source (such as a document feeder). This option is provided
to allow multiple image scans with xsane; it has no other purpose.
to allow multiple image scans with
.BR xsane (1); it has no other purpose.
.TP
.B \-\-batch[=(yes|no)] [no]
Enable/disable batch mode scanning. Batch mode allows scanning at maximum throughput
@ -385,6 +219,7 @@ Length of icon (thumbnail) image in pixels.
Specifies the barcode type to search for. If this option is
not specified, or specified with a value of none, then the barcode decoding
feature is completely disabled. The valid barcode type are:
.RS
.br
.B none
@ -428,6 +263,7 @@ to its maximum value (7).
.B \-\-barcode\-search\-mode <see list> [horiz\-vert]
Chooses the orientation of barcodes to be searched. The valid orientations
are:
.RS
.br
.B horiz\-vert
@ -474,7 +310,8 @@ Ordinarily barcodes are searched in the entire image. However, when you
specify sections all barcode searching is done within the specific sections
identified. This can significantly speed up the decoding process.
The following functioncodes are available:
The following function codes are available:
.RS
.br
.B front
@ -530,18 +367,215 @@ there are more white pixels in the code.
.B \-\-barcode\-patchmode 0..1 [0]
Controls Patch Code detection.
.SH CONFIGURATION
The contents of the
.I bh.conf
file is a list of device names that correspond to Bell+Howell
scanners. See
.BR sane\-scsi (5)
on details of what constitutes a valid device name.
Additionally, options can be specified; these lines begin with the word "option".
Each option is described in detail below. Empty lines and lines starting
with a hash mark (#) are ignored.
.SH OPTIONS
The following options can be specified in the
.I bh.conf
file.
.TP
.B disable\-optional\-frames
This option prevents the backend from sending any optional frames. This
option may be useful when dealing with frontends which do not support these
optional frames. When this option is in effect, the data is sent in a
.B SANE_FRAME_GRAY
frame. The optional frames sent by this backend are:
.BR SANE_FRAME_G31D ", " SANE_FRAME_G32D ", " SANE_FRAME_G42D " and " SANE_FRAME_TEXT .
These frames are generated based on the compression and barcode options.
These frames are never sent in preview mode.
.TP
.B fake\-inquiry
This option is used for debugging purposes and its use is not encouraged.
Essentially, it allows the backend to initialize in the absence of
a scanner. This is useful for development and not much else.
This option must be specified earlier in the configuration file than
the devices which are to be "faked".
.SH FILES
.TP
.I @CONFIGDIR@/bh.conf
The backend configuration file (see also description of
.B SANE_CONFIG_DIR
below).
.TP
.I @LIBDIR@/libsane\-bh.a
The static library implementing this backend.
.TP
.I @LIBDIR@/libsane\-bh.so
The shared library implementing this backend (present on systems that
support dynamic loading).
.SH ENVIRONMENT
.TP
.B SANE_CONFIG_DIR
This environment variable specifies the list of directories that may
contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory
separator character, then the default directories are searched after
the explicitly specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_BH
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend. E.g.,
a value of 255 requests all debug output to be printed. Smaller
levels reduce verbosity.
.SH "SUPPORTED FEATURES"
.TP
.B ADF support
With document scanners, automatic document feeder (ADF) support is a key
feature. The backend supports the ADF by default and returns
.B SANE_STATUS_NO_DOCS
when the out-of-paper condition is detected. The SANE frontend
.BR scanadf (1)
is a command line frontend that supports multi-page scans. It has been
used successfully with this backend. The SANE frontend
.BR xsane (1)
is an improved GUI frontend by Oliver Rauch. Support for multi-page
scans is included in xsane version 0.35 and above.
.TP
.B Duplex scanning
Some models, such as the COPISCAN II 6338, support duplex scanning. That
is, they scan both sides of the document during a single pass through the
scanner (the scanner has two cameras). This backend supports duplex
scanning (with the
.B \-\-duplex
option). The front and back page images are delivered consecutively
as if they were separately scanned pages.
.TP
.B Hardware compression
The scanner is capable of compressing the data into several industry
standard formats (CCITT G3, CCITT G3-2D, CCITT G4). This results in
increased performance as less data is passed from the scanner to the
host over the SCSI bus. The backend supports these compression formats
via the
.B \-\-g31d, \-\-g32d, \-\-g42d
options, respectively. Many SANE frontends are not equipped to deal with
these formats, however. The SANE frontend
.BR scanadf (1)
supports these optional frame formats. The compressed image data
is written directly to a file and can then be processed by a scan-script
using the
.B \-\-scan\-script
option. Examples of this are given on the
.BR scanadf (1)
homepage.
.TP
.B Automatic Border Detection
The scanner can automatically detect the paper size and adjust the
scanning window geometry appropriately. The backend supports this
useful feature with the
.B \-\-autoborder
option. It is enabled by default.
.TP
.B Batch Mode Scanning
The batch scan mode allows for maximum throughput. The Set Window
parameters must remain constant during the entire batch.
.TP
.B Icon Generation
The Icon function generates a thumbnail of the full page image, that can be
transferred as if it were a separate page. This allows the host to
quickly display a thumbnail representation during the scanning operation.
Perhaps this would be a great way of implementing a preview scan, but
since a normal scan is so quick, it might not be worth the trouble.
.TP
.B Multiple Sections
Multiple sections (scanning sub-windows) can be defined for the front and
back pages. Each section can have different characteristics (e.g. geometry,
compression). The sections are returned as if they were separately
scanned images. Additionally sections can be used to greatly enhance the
accuracy and efficiency of the barcode/patchcode decoding process by
limiting the search area to a small subset of the page. Most Copiscan II
series scanners support up to 8 user-defined sections.
.TP
.B Support Barcode/Patchcode Decoding
The RSC unit can recognize Bar and Patch Codes of various types embedded
in the scanned image. The codes are decoded and the data is returned to
the frontend as a text frame. The text is encoded in xml and contains
a great deal of information about the decoded data such as the location
where it was found, its orientation, and the time it took to find.
Further information on the content of this text frame as well as some
barcode decoding examples can be found on the backend homepage.
.SH LIMITATIONS
.TP
.B Decoding a single barcode type per scan
The RSC unit can search for up to six different barcode types at a time.
While the code generally supports this as well, the
.B \-\-barcode\-search\-bar
option only allows the user to specify a single barcode type.
Perhaps another option which allows a comma separated list of barcode
type codes could be added to address this.
.TP
.B Scanning a fixed number of pages in batch mode
The separation of front and back end functionality in SANE presents a
problem in supporting the 'cancel batch' functionality in the scanner.
In batch mode, the scanner is always a page ahead of the host. The host,
knowing ahead of time which page will be the last, can cancel batch mode
prior to initiating the last scan command. Currently, there is no mechanism
available for the frontend to pass this knowledge to the backend.
If batch mode is enabled and the
.B \-\-end\-count
terminates a scanadf session,
an extra page will be pulled through the scanner, but is neither read
nor delivered to the frontend. The issue can be avoided by specifying
.B \-\-batch=no
when scanning a fixed number of pages.
.TP
.B Revision 1.2 Patch detector
There is an enhanced patchcode detection algorithm available in the RSC
with revision 1.2 or higher that is faster and more reliable than the
standard Bar/Patch code decoder. This is not currently supported.
.SH BUGS
This is a new backend; detailed bug reports are welcome -- and expected ;)
.PP
If you have found something that you think is a bug, please attempt to
recreate it with the SANE_DEBUG_BH environment variable set to
255, and send a report detailing the conditions surrounding the bug to
recreate it with the
.B SANE_DEBUG_BH
environment variable set to 255, and send a report detailing the conditions
surrounding the bug to
.IR sane\-devel@alioth-lists.debian.net .
.SH "SEE ALSO"
sane(7), sane\-scsi(5), scanimage(1), scanadf(1)
.BR sane (7),
.BR sane\-scsi (5),
.BR scanimage (1),
.BR scanadf (1),
.BR xsane (1)
.SH AUTHOR
The sane\-bh backend was written by Tom Martone, based on the sane\-ricoh
The
.B sane\-bh backend
was written by Tom Martone, based on the
.BR sane\-ricoh (5)
backend by Feico W. Dillema and the bnhscan program by Sean Reifschneider
of tummy.com ltd. Some 8000 enhancements added by Mark Temple.

28
doc/sane-canon.man
Wyświetl plik

@ -39,25 +39,30 @@ It cannot be excluded (although we consider it extremely unlikely) that your
scanner will be damaged.
.PP
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Manuel Panea <mpd@rzg.mpg.de>; for questions concerning the FB620 and
FB1200S contact Mitsuru Okaniwa <m\-okaniwa@bea.hi\-ho.ne.jp>, for the
FS2710S Ulrich Deiters <ukd@xenon.pc.uni\-koeln.de>.
.PP
Manuel Panea
.IR <mpd@rzg.mpg.de> ;
for questions concerning the FB620 and FB1200S contact Mitsuru Okaniwa
.IR <m\-okaniwa@bea.hi\-ho.ne.jp> ,
for the FS2710S Ulrich Deiters
.IR <ukd@xenon.pc.uni\-koeln.de> .
.SH TIPS (FS2700F)
.PP
Scanning either slides or negatives has been found to require rather
large gamma corrections of about 2.2 to 2.4 (same value for red, green,
and blue). It is recommended to use the automatic exposure controls
of the frontend xsane for best results.
of the frontend
.BR xsane (1)
for best results.
.PP
The "Auto Focus" function triggers a special pass to determine the focus
value. After that, the real scanning pass takes place.
.PP
Even with "Auto Focus" turned on, the scanned image is often a bit too
blurred. Using the GIMP to do a "Filter->Enhance->Sharpen" at about 40
to 60 improves the image considerably.
.PP
blurred. Using the
.BR gimp (1)
to do a "Filter->Enhance->Sharpen" at about 40 to 60 improves the image
considerably.
.SH TIPS (FS2710S)
.PP
@ -97,7 +102,10 @@ export SANE_DEBUG_CANON=4
(installation of a CanoScan 2700F)
.br
.SH AUTHOR
Helmut Koeberle, Manuel Panea, and Markus Mertinat; FB620S and FB1200S support
by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters
Helmut Koeberle, Manuel Panea, and Markus Mertinat;
.br
FB620S and FB1200S support by Mitsuru Okaniwa;
.br
FS2710S support by Ulrich Deiters
.br
Man page by Henning Meier-Geinitz (mostly based on canon.README)

18
doc/sane-canon630u.man
Wyświetl plik

@ -19,7 +19,8 @@ Color scanning is supported at 75, 150, 300, and 600 dpi, and gamma and
analog gain are adjustable.
.PP
TESTERS ARE WELCOME. Send your bug reports and comments to
Nathan Rutman <nthn1@yahoo.com>
Nathan Rutman
.IR <nthn1@yahoo.com> .
.PP
.SH CONFIGURATION
The contents of the
@ -90,16 +91,17 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory
separator character, then the default directories are searched after
the explicitly specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR tmp/config,
.IR ".",
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_CANON630U

129
doc/sane-canon_dr.man
Wyświetl plik

@ -14,8 +14,8 @@ This document describes backend version 57, which shipped with SANE 1.0.28.
.SH SUPPORTED HARDWARE
This version has only been tested with a few scanner models. Please see
http://www.sane\-project.org/sane\-supported\-devices.html for the most recent
list.
.I http://www.sane\-project.org/sane\-supported\-devices.html
for the most recent list.
This backend may support other Canon scanners. The best
way to determine level of support is to test the scanner directly,
@ -31,35 +31,32 @@ no way to detect if they are required, so they must be hard-coded.
.SH OPTIONS
Effort has been made to expose most hardware options, including:
.PP
source s
.RS
Selects the source for the scan. Options
may include "Flatbed", "ADF Front", "ADF Back", "ADF Duplex".
.RE
.PP
mode m
.RS
Selects the mode for the scan. Options
may include "Lineart", "Halftone", "Gray", and "Color".
.RE
.PP
resolution
.RS
.TP
.B \-\-source Flatbed|ADF Front|ADF Back|ADF Duplex
Selects the source for the scan.
.TP
.B \-\-mode Lineart|Halftone|Gray|Color
Selects the mode for the scan.
.TP
.B \-\-resolution
Controls scan resolution.
.RE
.PP
tl\-x, tl\-y, br\-x, br\-y
.RS
.TP
.B \-\-tl\-x, \-\-tl\-y, \-\-br\-x, \-\-br\-y
Sets scan area upper left and lower right coordinates. These are renamed
t, l, x, y by some frontends.
.RE
.PP
page\-width, page\-height
.RS
.BR -t ,
.BR -l ,
.BR -x ,
.B -y
by some frontends.
.TP
.B \-\-page\-width, \-\-page\-height
Sets paper size. Used by scanner to determine centering of scan
coordinates when using ADF and to detect double feed errors.
.RE
.PP
Other options will be available based on the capabilities of the scanner:
enhancement, compression, buttons and sensors, etc.
@ -71,35 +68,34 @@ capabilities. Please note that these features are somewhat simplistic, and
may not perform as well as the native implementations. Note also that these
features all require that the driver cache the entire image in memory. This
will almost certainly result in a reduction of scanning speed.
.PP
swcrop
.RS
.TP
.B \-\-swcrop
Requests the driver to detect the extremities of the paper within the larger
image, and crop the empty edges.
.RE
.PP
swdeskew
.RS
.TP
.B \-\-swdeskew
Requests the driver to detect the rotation of the paper within the larger
image, and counter the rotation.
.RE
.PP
swdespeck X
.RS
.TP
.B \-\-swdespeck X
Requests the driver to find and remove dots of X diameter or smaller from the
image, and fill the space with the average surrounding color.
.RE
Use 'scanimage \-\-help' to get a list, but be aware that some options may
be settable only when another option has been set, and that advanced options
may be hidden by some frontend programs.
.PP
.SH CONFIGURATION FILE
The configuration file "canon_dr.conf" is used to tell the backend how to look
for scanners, and provide options controlling the operation of the backend.
This file is read each time the frontend asks the backend for a list
of scanners, generally only when the frontend starts. If the configuration
file is missing, the backend will fail to run.
The configuration file
.I canon_dr.conf
is used to tell the backend how to look for scanners, and provide options
controlling the operation of the backend. This file is read each time the
frontend asks the backend for a list of scanners, generally only when the
frontend starts. If the configuration file is missing, the backend will
fail to run.
.PP
Scanners can be specified in the configuration file in 4 ways:
.PP
@ -164,13 +160,15 @@ Some scanners prepend all data transmitted to host with 12 bytes. Enable this op
Some scanners pad the upper edge of one side of a duplex scan. There is some variation in the amount of padding. Modify this option if your unit shows an unwanted band of image data on only one side.
.RE
.PP
Note: 'option' lines may appear multiple times in the configuration file.
.BR NOTE :
'option' lines may appear multiple times in the configuration file.
They only apply to scanners discovered by the next 'scsi/usb' line.
.PP
.SH ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_CANON_DR, which
enables debugging output to stderr. Valid values are:
The backend uses a single environment variable,
.BR SANE_DEBUG_CANON_DR ,
which enables debugging output to stderr. Valid values are:
.PP
.RS
5 Errors
@ -195,26 +193,39 @@ machines have not been tested. Their protocol is unknown.
.SH CREDITS
The various authors of the sane\-fujitsu backend provided useful code
The various authors of the
.BR sane\-fujitsu (5)
backend provided useful code.
.br
Yabarana Corp. www.yabarana.com provided significant funding
Yabarana Corp.
.I www.yabarana.com
provided significant funding.
.br
EvriChart, Inc. www.evrichart.com provided funding and loaned equipment
EvriChart, Inc.
.I www.evrichart.com
provided funding and loaned equipment.
.br
Canon, USA. www.usa.canon.com loaned equipment
Canon, USA.
.I www.usa.canon.com
loaned equipment.
.br
HPrint hprint.com.br provided funding and testing for DR-2510 support
HPrint
.I hprint.com.br
provided funding and testing for DR-2510 support.
.br
Stone-IT www.stone-it.com provided funding for DR-2010 and DR-2050 support
Stone-IT
.I www.stone-it.com
provided funding for DR-2010 and DR-2050 support.
.br
Gerhard Pfeffer provided access and testing for P-208 and P-215
Gerhard Pfeffer provided access and testing for P-208 and P-215.
.br
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brummelen, Thanos Diacakis and Junren Shi for testing and feedback.
.SH "SEE ALSO"
sane(7),
sane\-scsi(5),
sane\-usb(5)
.BR sane (7),
.BR sane\-scsi (5),
.BR sane\-usb(5)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.IR "<kitno455 a t gmail d o t com>" .

61
doc/sane-canon_lide70.man
Wyświetl plik

@ -17,49 +17,50 @@ present in the Windows XP driver has been left out. There is, for example,
no active calibration.
.PP
Testers and reviewers are welcome. Send your bug reports and comments to
the sane\-devel mailing list <sane\-devel@alioth-lists.debian.net>
the sane\-devel mailing list
.IR <sane\-devel@alioth-lists.debian.net> .
.PP
.SH CONFIGURATION
The
.I @CONFIGDIR@/canon_lide70.conf
file identifies the LiDE 70 by its vendor code 0x04a9 and its
product code 0x2225. For the LiDE 600(f) the product code is 0x2224.
.PP
.SH BACKEND SPECIFIC OPTIONS
.PP
.B Scan Mode:
.TP
\-\-resolution 75|150|300|600|1200 [default 600]
.BR
.B \-\-resolution 75|150|300|600|1200 [default 600]
Sets the resolution of the scanned image in dots per inch. Scanning at 1200 dpi
is not available on the LiDE 600(F) and it is very slow on the LiDE 70.
.TP
\-\-mode Color|Gray|Lineart [default: Color]
.BR
.B \-\-mode Color|Gray|Lineart [default: Color]
Selects the scan mode. Lineart means fully black and fully white pixels only.
.TP
\-\-threshold 0..100 (in steps of 1) [default 75]
.BR
.B \-\-threshold 0..100 (in steps of 1) [default 75]
Select minimum-brightness percentage to get a white point, relevant only for Lineart
.TP
\-\-non-blocking[=(yes|no)] [inactive]
.BR
.B \-\-non-blocking[=(yes|no)] [inactive]
This option has not yet been implemented. Scans are captured in a temporary file with a typical size of 100MB.
.PP
.B Geometry:
.TP
\-l 0..216.069 [default 0]
Top-left x position of scan area in millimeters.
.B \-l 0..216.069 [default 0]
Top-left x position of scan area in millimeters.
.TP
\-t 0..297 [default 0]
Top-left y position of scan area in millimeters.
.B \-t 0..297 [default 0]
Top-left y position of scan area in millimeters.
.TP
\-x 0..216.069 [default 80]
Width of scan-area in millimeters.
.B \-x 0..216.069 [default 80]
Width of scan-area in millimeters.
.TP
\-y 0..297 [default 100]
Height of scan-area in millimeters.
.PP
.B \-y 0..297 [default 100]
Height of scan-area in millimeters.
.SH FILES
.TP
.I @CONFIGDIR@/canon_lide70.conf
@ -85,17 +86,25 @@ SANE_DEBUG_CANON_LIDE70=128 scanimage > /dev/null
At low resolutions (75 and 150 dpi, implying high slider speeds)
the LiDE 70 misses the top one millimeter of the scan area. This can
be remedied by shifting the document one millimeter downward, in cases
where such precision matters. Note that xsane uses the 75 dpi mode for
prescans. The problem is worse on the LiDE 600(F), where the
offset is five millimeters.
where such precision matters. Note that
.BR xsane (1)
uses the 75 dpi mode for prescans. The problem is worse on the LiDE 600(F),
where the offset is five millimeters.
.PP
It is recommended that in xsane the gamma value be set to approximately 1.7
It is recommended that in
.BR xsane (1)
the gamma value be set to approximately 1.7
to get more realistic colors. This also wipes out some artifacts caused by
the lack of real calibration.
.SH "SEE ALSO"
sane(7), sane\-usb(5), sane\-find\-scanner(1), scanimage(1)
.BR sane (7),
.BR sane\-usb (5),
.BR sane\-find\-scanner (1),
.BR scanimage (1),
.BR xsane (1),
.br
http://www.juergen-ernst.de/info_sane.html
.br
.SH AUTHOR
pimvantend, building upon pioneering work by Juergen Ernst.

36
doc/sane-canon_pp.man
Wyświetl plik

@ -27,7 +27,7 @@ CanoScan N640P ex
.PP
No USB scanners are supported and there are no plans to support them in the
future. Other projects are working on support for USB scanners. See the
.B PROJECTS
.I PROJECTS
file for more detail. The FB310P and FB610P are re-badged Avision scanners
which use a different command set, so are unlikely to be supported by this
backend in the future.
@ -38,12 +38,11 @@ appreciated. Please send any bug reports to the maintainers as listed on the
web page (listed in
.B SEE ALSO
below).
.PP
.
.PP
.SH "DEVICE NAMES"
This backend expects device names of the form presented by libieee1284. These
names are highly dependent on operating system and version.
This backend expects device names of the form presented by
.BR libieee1284 (3).
These names are highly dependent on operating system and version.
On Linux 2.4 kernels this will be of the form
.I "parport0"
@ -136,13 +135,18 @@ This environment variable specifies the list of directories that may contain
the configuration file. Under UNIX, the directories are separated by a colon
(`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable
is not set, the configuration file is searched in two default directories:
first, the current working directory (".") and then in @CONFIGDIR@. If the
value of the environment variable ends with the directory separator character,
then the default directories are searched after the explicitly specified
directories. For example, setting
first, the current working directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory separator
character, then the default directories are searched after the explicitly
specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_CANON_PP
If the library was compiled with debug support enabled, this environment
@ -219,9 +223,11 @@ but not where another scan can be made.
.SH "SEE ALSO"
sane(7), sane\-dll(5)
.BR
http://canon\-fb330p.sourceforge.net/
.BR sane (7),
.BR sane\-dll(5),
.BR libieee1284 (3),
.br
.I http://canon\-fb330p.sourceforge.net/
.SH AUTHOR
This backend is primarily the work of Simon Krix (Reverse Engineering), and

24
doc/sane-cardscan.man
Wyświetl plik

@ -7,9 +7,7 @@ sane\-cardscan \- SANE backend for Corex CardScan usb scanners
.SH DESCRIPTION
The
.B sane\-cardscan
library implements a
.B SANE
(Scanner Access Now Easy) backend which
library implements a SANE (Scanner Access Now Easy) backend which
provides access to the Corex CardScan 800c & 600c small-format scanners.
The backend supports only grayscale and color modes and media of
@ -21,12 +19,11 @@ driver in action, and send it to the author.
.SH OPTIONS
The cardscan backend supports the following options:
.PP
mode m
.RS
Selects the mode for the scan. Options are "Gray" and "Color".
.RE
.PP
.TP
.B --mode Gray|Color
Selects the mode for the scan.
.SH CONFIGURATION FILE
The configuration file
.I cardscan.conf
@ -35,8 +32,7 @@ for scanners, and provide options controlling the operation of the backend.
This file is read each time the frontend asks the backend for a list
of scanners, generally only when the frontend starts. If the configuration
file is missing, the backend will use a set of compiled defaults, which
are identical to the default configuration file shipped with
.BR SANE .
are identical to the default configuration file shipped with SANE.
.PP
Scanners can be specified in the configuration file in 2 ways:
.PP
@ -109,11 +105,13 @@ windows driver.
.SH CREDITS
The hardware to build this driver was provided to the author by:
Jeff Kowalczyk <jtk a t yahoo d o t com>
Jeff Kowalczyk
.IR "<jtk a t yahoo d o t com>" .
.SH "SEE ALSO"
.BR sane (7),
.BR sane\-usb (5)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.I "<kitno455 a t gmail d o t com>" .

29
doc/sane-config.man
Wyświetl plik

@ -7,11 +7,7 @@ sane\-config \- get information about the installed version of libsane
.PP
.B sane\-config
is a tool that is used to determine the compiler and linker
flags that should be used to compile and link
.B SANE
frontends to a
.B SANE
backend library (libsane).
flags that should be used to compile and link SANE frontends to a SANE backend library (libsane).
.
.SH OPTIONS
.B sane\-config
@ -21,34 +17,31 @@ accepts the following options (you can't use more than one option at the same ti
Print the currently installed version of libsane on the standard output.
.TP 8
.B \-\-help OPTION
Print a short usage message. If OPTION is specified, help for that option
(e.g.
.BR \-\-libs)
Print a short usage message. If
.I OPTION
is specified, help for that option (e.g.
.BR \-\-libs )
is printed (if available).
.TP 8
.B \-\-libs
Print the additional libraries that are necessary to link a
.B SANE
frontend to libsane.
Print the additional libraries that are necessary to link a SANE frontend to libsane.
.TP 8
.B \-\-ldflags
Print the linker flags that are necessary to link a
.B SANE
frontend to libsane.
Print the linker flags that are necessary to link a SANE frontend to libsane.
.TP 8
.B \-\-cflags
Print the compiler flags that are necessary to compile a
.B SANE
frontend.
Print the compiler flags that are necessary to compile a SANE frontend.
.TP 8
.B \-\-prefix
Print the prefix used during compilation of libsane.
.TP 8
.B \-\-exec\-prefix
Print the exec\-prefix used during compilation of libsane.
.SH "SEE ALSO"
.BR sane (7)
.SH AUTHOR
This manual page was written by Julien BLACHE
.RI < jblache@debian.org >,
.RI < jblache@debian.org > ,
for the Debian GNU/Linux system (but may be used by others).

25
doc/sane-coolscan.man
Wyświetl plik

@ -13,11 +13,13 @@ This file is a short description of the coolscan backend for
The
.B sane\-coolscan
library implements a
.B SANE
backend that provides the interface to the following Nikon Coolscan Film scanners: Nikon LS20, LS30, LS1000, LS2000.
library implements a SANE backend that provides the interface to the following Nikon
Coolscan Film scanners: Nikon LS20, LS30, LS1000, LS2000.
.B Even though the backend has worked for a number of people, there are still some problems, especially in combination with some SCSI card/drivers (AHA-1505/aha152x.o) and the autofocus command. You should consider this backend 'alpha' and be careful when using it the first time.
.B Even though the backend has worked for a number of people, there are still some
problems, especially in combination with some SCSI card/drivers (AHA-1505/aha152x.o)
and the autofocus command.
You should consider this backend 'alpha' and be careful when using it the first time.
.SH CONFIGURATION
@ -46,10 +48,7 @@ Coolscan scanners. These systems hang when the autofocus command is send to the
To see a list of which card/driver combinations work or don't work have a look at:
.I http://andreas.rick.free.fr/sane/autofocus.html.
.SH FILES
.TP
The backend configuration file:
.I @CONFIGDIR@/coolscan.conf
@ -88,6 +87,8 @@ The gamma table is not implemented for the LS1000 yet.
The dust-removal is not working yet.
.SH SEE ALSO
.BR sane (7),
.BR sane\-scsi (5)
.TP
.I http://andreas.rick.free.fr/sane/
@ -95,22 +96,16 @@ The homepage of this backend.
.TP
.I http://www.sema.be/coolscan/
The original version of the coolscan backend by Didier.
.PP
.BR sane (7),
.BR sane\-scsi (5)
.SH THANKS TO
.PP
Didier Carlier \- For writing the original Coolscan backend (without it I would not have started this).
.PP
Oliver Rauch \- For adapting xsane so quickly to the infrared stuff.
.PP
All the other people working on
.BR SANE .
All the other people working on SANE.
.SH AUTHOR
Andreas Rick
.SH EMAIL-CONTACT
andreas.rick@free.fr
.I andreas.rick@free.fr

8
doc/sane-coolscan2.man
Wyświetl plik

@ -98,7 +98,7 @@ formats cannot handle depths greater than 8 bits.
.TP
.B \-\-autofocus
Perform autofocus operation. Unless otherwise specified by the other options (
.I \-\-focus\-on\-centre
.B \-\-focus\-on\-centre
and friends), focusing is performed on the centre of the selected scan area.
.TP
.B \-\-ae\-wb
@ -129,7 +129,9 @@ which
does not work.
.SH CONFIGURATION FILE
The configuration file @CONFIGDIR@/coolscan2.conf specifies the device(s)
The configuration file
.I @CONFIGDIR@/coolscan2.conf
specifies the device(s)
that the backend will use. Owing to the nature of the supported connection
types SCSI, USB, and IEEE 1394, the default configuration file supplied with
the SANE distribution should work without being edited.
@ -198,4 +200,4 @@ or the SANE developers' email list.
.SH AUTHORS
The backend is written and maintained by Andr\['a]s Major
(andras@users.sourceforge.net).
.IR <andras@users.sourceforge.net> .

39
doc/sane-coolscan3.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-coolscan3 \- SANE backend for Nikon Coolscan film scanners
.SH DESCRIPTION
The
.B sane\-coolscan3
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to Nikon Coolscan film scanners. Some functions of this
backend should be considered
.B beta-quality
@ -42,7 +40,8 @@ The options the backend supports can either be selected through command line
options to programs like
.BR scanimage (1)
or through GUI elements in
.BR xscanimage (1) or
.BR xscanimage (1)
or
.BR xsane (1).
Valid command line options and their syntax can be listed by using:
@ -61,9 +60,7 @@ first scanner identified. Use the command:
scanimage \-L
.RE
.PP
to list all devices recognized by your
.B SANE
installation.
to list all devices recognized by your SANE installation.
The options should be fully described by the description or tooltips given by
frontend. Here is a description of some of the most important options, in the
@ -130,12 +127,12 @@ which
does not work.
.SH CONFIGURATION FILE
The configuration file @CONFIGDIR@/coolscan3.conf specifies the device(s)
that the backend will use. Owing to the nature of the supported connection
types SCSI, USB, and IEEE 1394, the default configuration file supplied with
the
.B SANE
distribution should work without being edited.
The configuration file
.I @CONFIGDIR@/coolscan3.conf
specifies the device(s) that the backend will use. Owing to the nature of
the supported connection types SCSI, USB, and IEEE 1394, the default
configuration file supplied with the SANE distribution should work without
being edited.
Each line in the configuration file is either of the following, where all
entries are case-sensitive:
@ -151,9 +148,7 @@ configuration file is present.
.I a line of the form <interface>:<device>
Here <interface> can be one of "scsi" or "usb", and <device> is the device
file of the scanner. Note that IEEE 1394 devices are handled by the SBP-2
module in the kernel and appear to
.B SANE
as SCSI devices.
module in the kernel and appear to SANE as SCSI devices.
.SH FILES
.TP
@ -184,9 +179,7 @@ levels reduce verbosity.
.BR xsane(1)
.SH BUGS
Currently, the
.B SANE
protocol does not allow automatically updating options
Currently, the SANE protocol does not allow automatically updating options
whenever the hardware changes. Thus the number of choices for the
.B \-\-frame
option will be fixed when the backend is initialized (usually when the user
@ -200,12 +193,10 @@ from IEEE 1394 scanners to 36 bytes, discarding vital information
about the scanner. The IEEE 1394 models therefore only work with
2.4.19 or later.
No real bugs currently known, please report any to the
.B SANE
developers' list.
No real bugs currently known, please report any to the SANE developers' list.
.SH AUTHORS
coolscan3 written by A. Zummo
.RI ( a.zummo@towertech.it ),
.RI < a.zummo@towertech.it >,
based heavily on coolscan2 written by Andr\['a]s Major
.RI ( andras@users.sourceforge.net ).
.RI < andras@users.sourceforge.net >.

13
doc/sane-dc210.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-dc210 \- SANE backend for Kodak DC210 Digital Camera
.SH DESCRIPTION
The
.B sane\-dc210
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to the Kodak DC210 camera. THIS IS EXTREMELY ALPHA
CODE! USE AT YOUR OWN RISK!!
.SH "DEVICE NAMES"
@ -22,7 +20,8 @@ rate specifies the maximum rate to use while downloading pictures. (The
camera is always initialized using 9600 baud, then switches to the
higher rate). On my 90MHz Pentium, I usually have no problems downloading
at 115200 baud as long as the system is not excessively busy and
the "interrupt-unmask flag" is set in the IDE driver (hdparm \-u1).
the "interrupt-unmask flag" is set in the IDE driver
.RI ( "hdparm \-u1" ).
Supported baud rates are: 9600, 19200, 38400, 57600, and 115200.
.PP
The
@ -114,11 +113,7 @@ Henning Meier-Geinitz.
Known bugs/limitations are: ?
.PP
More general comments, suggestions, and inquiries about frontends
or
.B SANE
should go to the
.B SANE
Developers mailing list
or SANE should go to the SANE Developers mailing list
(see
.I http://www.sane\-project.org/mailing\-lists.html
for details).

15
doc/sane-dc240.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-dc240 \- SANE backend for Kodak DC240 Digital Camera
.SH DESCRIPTION
The
.B sane\-dc240
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to the Kodak DC240 camera. THIS IS EXTREMELY ALPHA
CODE! USE AT YOUR OWN RISK!!
.SH "DEVICE NAMES"
@ -23,7 +21,8 @@ camera is always initialized using 9600 baud, then switches to the
higher rate). On a 450MHz Pentium, I usually have no problems downloading
at 115200 baud, though the camera sometimes has to resend packets due
to lost characters. Results are better when
the "interrupt-unmask flag" is set in the IDE driver (hdparm \-u1).
the "interrupt-unmask flag" is set in the IDE driver
.RI ( "hdparm \-u1" ).
Supported baud rates are: 9600, 19200, 38400, 57600, and 115200.
.PP
The
@ -99,7 +98,7 @@ A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
.SH "SEE ALSO"
.BT sane (7)
.BR sane (7)
.SH AUTHOR
Peter S. Fales
@ -118,11 +117,7 @@ Not only should we check for the additional directory, but pictures may
actually be found in multiple directories.
.PP
More general comments, suggestions, and inquiries about frontends
or
.B SANE
should go to the
.B SANE
Developers mailing list
or SANE should go to the SANE Developers mailing list
(see
.I http://www.sane\-project.org/mailing\-lists.html
for details).

24
doc/sane-dc25.man
Wyświetl plik

@ -20,7 +20,8 @@ specifies the maximum rate to use while downloading pictures. (The
camera is always initialized using 9600 baud, then switches to the
higher rate). On my 90MHz Pentium, I usually have no problems downloading
at 115200 baud as long as the system is not excessively busy and
the "interrupt-unmask flag" is set in the IDE driver (hdparm \-u1).
the "interrupt-unmask flag" is set in the IDE driver
.RI ( "hdparm \-u1" ).
Supported baud rates are: 9600, 19200, 38400, 57600, and 115200.
.PP
The dumpinquiry line causes some information about the camera to
@ -64,13 +65,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_DC25
If the library was compiled with debugging support enabled, this
@ -79,10 +86,11 @@ A value of 128 requests maximally copious debug output; smaller
levels reduce verbosity.
.SH "SEE ALSO"
sane(7)
.BR sane (7)
.SH AUTHOR
Peter Fales, dc25\-devel@fales\-lorenz.net
Peter Fales,
.IR dc25\-devel@fales\-lorenz.net .
.SH BUGS
Known bugs/limitations are:
@ -94,6 +102,8 @@ updated immediately.
.PP
More general comments, suggestions, and inquiries about frontends
or SANE should go to the SANE Developers mailing list
(see http://www.sane\-project.org/mailing\-lists.html for details).
(see
.I http://www.sane\-project.org/mailing\-lists.html
for details).
You must be subscribed to the list, otherwise your mail won't be
sent to the subscribers.

17
doc/sane-dll.man
Wyświetl plik

@ -140,13 +140,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory
separator character, then the default directories are searched after
the explicitly specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_DLL
If the library was compiled with debug support enabled, this

19
doc/sane-dmc.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-dmc \- SANE backend for the Polaroid Digital Microscope Camera
.SH DESCRIPTION
The
.B sane\-dmc
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to the Polaroid Digital Microscope Camera.
.SH "DEVICE NAMES"
This backend expects device names of the form:
@ -108,10 +106,11 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory separator
character, then the default directories are searched after the explicitly
specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR "tmp/config",
@ -133,7 +132,7 @@ may read less than you ask for. If you ask sane_read to read
less than a single line, it returns SANE_STATUS_INVAL.
.PP
In the "Super Resolution" mode, images must be read in units of
\fItwo\fR lines (3198 pixels or 9594 bytes.) If you try to read less
\fItwo\fR lines (3198 pixels or 9594 bytes). If you try to read less
than two lines, you get SANE_STATUS_INVAL. The Super Resolution mode
is very slow.
.PP
@ -141,12 +140,14 @@ In the "Viewfinder" and "Thumbnail" modes, the entire image must
be read in one SCSI transfer. In this case, the driver performs
buffering and you can read the image in as small an increment as you
like.
.SH "SEE ALSO"
.BR sane (7),
.BR sane\-scsi (5)
.SH AUTHOR
David F. Skoll
.PP
The backend is derived from
.BR sane\-hp
.BR sane\-hp (5)
by David Mosberger

20
doc/sane-epjitsu.man
Wyświetl plik

@ -7,18 +7,23 @@ sane\-epjitsu \- SANE backend for Epson-based Fujitsu USB scanners.
.SH DESCRIPTION
The
.B sane\-epjitsu
library implements a
.B SANE
(Scanner Access Now Easy) backend which provides basic access the Fujitsu fi\-60F/fi\-65F and ScanSnap S300/S1300(i)/S1100(i) scanners.
library implements a SANE (Scanner Access Now Easy) backend which provides basic access the
Fujitsu fi\-60F/fi\-65F and ScanSnap S300/S1300(i)/S1100(i) scanners.
.SH HARDWARE SUPPORT
These scanners are fairly limited, only supporting a couple of modes and resolutions, and always scanning full width. The backend supports missing modes (binary, grayscale) and intermediate resolutions in software, but provides only minimal scan area controls. See
These scanners are fairly limited, only supporting a couple of modes and resolutions, and
always scanning full width. The backend supports missing modes (binary, grayscale) and
intermediate resolutions in software, but provides only minimal scan area controls. See
.B KNOWN ISSUES.
This backend may support other scanners. If physical inspection reveals an Epson chipset, please contact the author for instructions on collecting a USB trace under Windows to verify.
This backend may support other scanners. If physical inspection reveals an Epson chipset,
please contact the author for instructions on collecting a USB trace under Windows to verify.
.SH OPTIONS
A limited effort has been made to expose the standard options to the API. This allows a frontend to set resolution, color mode, and choose the ADF setting. The epjitsu backend supports the following basic options for most scanners:
A limited effort has been made to expose the standard options to the API. This allows a
frontend to set resolution, color mode, and choose the ADF setting. The
.B sane\-epjitsu
backend supports the following basic options for most scanners:
.PP
.BR source s
.RS
@ -114,4 +119,5 @@ Improved calibration code provided by Richard Goedeken.
.BR scanimage (1)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.RI < "kitno455 a t gmail d o t com" >

4
doc/sane-epson.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-epson \- SANE backend for EPSON scanners
.SH DESCRIPTION
The
.B sane\-epson
library implements a
.B SANE
Scanner Access Now Easy) backend that
library implements a SANE Scanner Access Now Easy) backend that
provides access to Epson flatbed scanners. Some functions of this
backend should be considered
.B beta-quality

12
doc/sane-epson2.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-epson2 \- SANE backend for EPSON scanners
.SH DESCRIPTION
The
.B sane\-epson2
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to Epson flatbed scanners. This library supports
a similar set of scanners as the sane\-epson driver but was
developed to support a wider range of connections to the scanner;
@ -279,7 +277,9 @@ The
option select the ADF mode (simplex/duplex).
.SH CONFIGURATION FILE
The configuration file @CONFIGDIR@/epson2.conf specifies the device(s) that the
The configuration file
.I @CONFIGDIR@/epson2.conf
specifies the device(s) that the
backend will use. Possible connection types are:
.TP
.B SCSI
@ -371,9 +371,7 @@ If the scanner is not even recognized as an Epson scanner this is
probably because the device name reported by the scanner is not in the
correct format. Please send this information to the backend maintainer
(email address is in the AUTHOR section of this man page or in the
AUTHORS file of the
.B SANE
distribution).
AUTHORS file of the SANE distribution).
.SH AUTHOR

12
doc/sane-epsonds.man
Wyświetl plik

@ -5,9 +5,8 @@ sane\-epsonds \- SANE backend for EPSON ESC/I-2 scanners
.SH DESCRIPTION
The
.B sane\-epsonds
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides access to Epson ESC/I-2 scanners.
library implements a SANE (Scanner Access Now Easy) backend that provides access
to Epson ESC/I-2 scanners.
.PP
Valid command line options and their syntax can be listed by using
.PP
@ -70,8 +69,9 @@ The
option select the ADF mode (simplex/duplex).
.SH CONFIGURATION FILE
The configuration file @CONFIGDIR@/epsonds.conf specifies the device(s) that the
backend will use. Possible connection types are:
The configuration file
.I @CONFIGDIR@/epsonds.conf
specifies the device(s) that the backend will use. Possible connection types are:
.TP
.B USB
For not automatically detected USB scanners, their VENDOR and PRODUCT ID can
@ -99,7 +99,7 @@ support dynamic loading).
If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend. E.g.,
a value of 128 requests all debug output to be printed. Smaller
levels reduce verbosity. Values around 11-16 will usuallybe enough for
levels reduce verbosity. Values around 11-16 will usually be enough for
a bug report.
.SH "SEE ALSO"

16
doc/sane-escl.man
Wyświetl plik

@ -5,9 +5,8 @@ sane\-escl \- SANE backend for eSCL scanners
.SH DESCRIPTION
The
.B sane\-escl
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides access to eSCL protocol scanners.
library implements a SANE (Scanner Access Now Easy) backend that provides access to
eSCL protocol scanners.
.PP
Currently, the following models work with this backend (This list is not exhaustive):
.PP
@ -37,9 +36,13 @@ RICOH SP3710S
XEROX VERSALINK C7220
.RE
.PP
The "escl" backend for SANE supports AirScan/eSCL devices that announce
The.
.B sane\-escl
backend for SANE supports AirScan/eSCL devices that announce
themselves on mDNS as _uscan._utcp or _uscans._utcp.
If the device is available, the "escl" backend recovers these capacities.
If the device is available, the
.B sane\-escl
backend recovers these capacities.
The user configures and starts scanning.
A list of devices that use the eSCL protocol can be found at
.IR https://support.apple.com/en-us/HT201311 .
@ -56,6 +59,7 @@ The static library implementing this backend.
.I @LIBDIR@/libsane\-escl.so
The shared library implementing this backend (present on systems that
support dynamic loading).
.SH ENVIRONMENT
.TP
.B SANE_DEBUG_ESCL
@ -63,10 +67,12 @@ If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend. E.g.,
a value of 128 requests all debug output to be printed. Smaller
levels reduce verbosity.
.SH "SEE ALSO"
.BR sane (7)
.BR scanimage (1)
.BR xscanimage (1)
.BR xsane (1)
.SH AUTHORS
Touboul Nathane, Thierry HUCHARD

24
doc/sane-find-scanner.man
Wyświetl plik

@ -28,7 +28,7 @@ and
The test is done by sending a SCSI inquiry command and looking for a device
type of "scanner" or "processor" (some old HP scanners seem to send
"processor"). So
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
will find any SCSI scanner connected to those default device files even if it
isn't supported by any SANE backend.
.PP
@ -43,23 +43,23 @@ are tested. The files are opened and the vendor and device ids are determined,
if the operating system supports this feature. Currently USB scanners are only
found this way if they are supported by the Linux scanner module or the
FreeBSD or OpenBSD uscanner driver. After that test,
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
tries to scan for USB devices found by the USB library libusb (if
available). There is no special USB class for scanners, so the heuristics used
to distinguish scanners from other USB devices is not
perfect.
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
also tries to find out the type of USB chip used in the scanner. If detected,
it will be printed after the vendor and product ids.
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
will even find USB scanners, that are not supported by any SANE backend.
.PP
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
won't find most
parallel port scanners, or scanners connected to proprietary ports. Some
.B parallel port
scanners may be detected by
.B sane\-find\-scanner -p.
.I sane\-find\-scanner -p.
At the time of writing this will only detect Mustek parallel port scanners.
.SH OPTIONS
@ -69,7 +69,7 @@ Prints a short usage message.
.TP 8
.B \-v
Verbose output. If used once,
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
shows every device name and the test result. If used twice, SCSI inquiry
information and the USB device descriptors are also printed.
.TP 8
@ -82,13 +82,13 @@ Probe parallel port scanners.
.B \-f
Force opening all explicitly given devices as SCSI and USB devices. That's
useful if
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
is wrong in determining the device type.
.TP 8
.B \-F filename
filename is a file that contains USB descriptors in the format of
/proc/bus/usb/devices as used by Linux.
.BR sane\-find\-scanner (1)
.B sane\-find\-scanner
tries to identify the chipset(s) of all USB scanners found in such a file. This
option is useful for developers when the output of
.I "cat /proc/bus/usb/devices"
@ -97,16 +97,16 @@ is available but the scanner itself isn't.
.B devname
Test device file "devname". No other devices are checked if devname is given.
.SH EXAMPLE
.B sane\-find\-scanner \-v
.I sane\-find\-scanner \-v
.br
Check all SCSI and USB devices for available scanners and print a line for
every device file.
.PP
.B sane\-find\-scanner /dev/scanner
.I sane\-find\-scanner /dev/scanner
.br
Look for a (SCSI) scanner only at /dev/scanner and print the result.
.PP
.B sane\-find\-scanner \-p
.I sane\-find\-scanner \-p
.br
Probe for parallel port scanners.
.SH "SEE ALSO"

48
doc/sane-fujitsu.man
Wyświetl plik

@ -7,10 +7,8 @@ sane\-fujitsu \- SANE backend for Fujitsu flatbed and ADF scanners
.SH DESCRIPTION
The
.B sane\-fujitsu
library implements a
.B SANE
(Scanner Access Now Easy) backend which provides access to most Fujitsu flatbed
and ADF scanners.
library implements a SANE (Scanner Access Now Easy) backend which provides
access to most Fujitsu flatbed and ADF scanners.
This document describes backend version 136, which shipped with SANE 1.0.30.
@ -19,7 +17,8 @@ This version supports every known model which speaks the Fujitsu SCSI and
SCSI\-over\-USB protocols. Specifically, the SCSI M309x and M409x series, the
SCSI fi\-series, most of the USB fi\-series, the USB ScanSnap S5xx/S15xx, and
the USB iX1xx/5xx series scanners are supported. Please see the list at
http://www.sane\-project.org/sane\-supported\-devices.html for details.
.I http://www.sane\-project.org/sane\-supported\-devices.html
for details.
This backend may support other Fujitsu scanners. The best
way to determine level of support is to test the scanner directly,
@ -105,9 +104,11 @@ Use
to get a list, but be aware that some options may
be settable only when another option has been set, and that advanced options
may be hidden by some frontend programs.
.PP
.SH CONFIGURATION FILE
The configuration file "fujitsu.conf" is used to tell the backend how to look
The configuration file
.I fujitsu.conf
is used to tell the backend how to look
for scanners, and provide options controlling the operation of the backend.
This file is read each time the frontend asks the backend for a list
of scanners, generally only when the frontend starts. If the configuration
@ -157,8 +158,9 @@ warned.
.PP
.SH ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_FUJITSU, which
enables debugging output to stderr. Valid values are:
The backend uses a single environment variable,
.BR SANE_DEBUG_FUJITSU ,
which enables debugging output to stderr. Valid values are:
.PP
.RS
5 Errors
@ -191,26 +193,32 @@ JPEG output is supported by the backend, but not by the SANE protocol, so is
disabled in this release. It can be enabled if you rebuild from source.
.SH CREDITS
m3091 backend: Frederik Ramm <frederik a t remote d o t org>
m3091 backend: Frederik Ramm
.RI < "frederik a t remote d o t org" >
.br
m3096g backend: Randolph Bentson <bentson a t holmsjoen d o t com>
m3096g backend: Randolph Bentson
.RI < "bentson a t holmsjoen d o t com" >
.br
(with credit to the unnamed author of the coolscan driver)
.br
fujitsu backend, m3093, fi\-4340C, ipc, cmp, long\-time maintainer:
.br
Oliver Schirrmeister <oschirr a t abm d o t de>
Oliver Schirrmeister
.RI < "oschirr a t abm d o t de" >
.br
m3092: Mario Goppold <mgoppold a t tbzpariv d o t tcc\-chemnitz dot de>
m3092: Mario Goppold
.RI < "mgoppold a t tbzpariv d o t tcc\-chemnitz dot de" >
.br
fi\-4220C and basic USB support: Ron Cemer <ron a t roncemer d o t com>
fi\-4220C and basic USB support: Ron Cemer
.RI < "ron a t roncemer d o t com" >
.br
fi\-4120, fi\-series color, backend re\-write, jpeg, current maintainer:
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.RI < "kitno455 a t gmail d o t com" >
JPEG output and low memory usage support funded by:
Archivista GmbH
www.archivista.ch
.I www.archivista.ch
Endorser support funded by:
O A S Oilfield Accounting Service Ltd
@ -218,19 +226,19 @@ Endorser support funded by:
Calgary, Alberta
T2P 3G2 Canada
1\-403\-263\-2600
www.oas.ca
.I www.oas.ca
Automatic length detection support funded by:
Martin G. Miller
mgmiller at optonline.net
.I mgmiller at optonline.net
Hardware donated, software image enhancement and fi-6/7xxx support funded by:
Fujitsu Computer Products of America, Inc.
www.fcpa.com
.I www.fcpa.com
iX500 support funded by:
Prefix Computer Services
www.prefixservice.com
.I www.prefixservice.com
.SH "SEE ALSO"
.BR sane (7),

160
doc/sane-genesys.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-genesys \- SANE backend for GL646, GL841, GL843, GL847 and GL124 based USB
.SH "DESCRIPTION"
The
.B sane\-genesys
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to USB flatbed scanners based on the Genesys GL646, GL841, GL843, GL847 and GL124 chips.
At present, the following scanners are known to work with this backend:
.PP
@ -70,73 +68,62 @@ A value of -1 means forever, 0 means no cache.
.SH EXTRAS SCAN OPTIONS
.TP
.B \-\-lamp\-off\-time number
.RS
The lamp will be turned off after the given time (in minutes). A value of 0 means that the lamp won't be turned off.
.RE
The lamp will be turned off after the given time (in minutes). A value of 0 means that the lamp won't be turned off.
.TP
.B \-\-threshold percent
.RS
0..100% (in steps of 1). Select minimum brightness to get a white point. Pixels
0..100% (in steps of 1). Select minimum brightness to get a white point. Pixels
with brightness below that value will be scanned as black.
.RE
.TP
.B \-\-brightness value
.RS
\-100..100 (in steps of 1). Set the brightness enhancement. 0 for no enhancement, negative
\-100..100 (in steps of 1). Set the brightness enhancement. 0 for no enhancement, negative
values to decrease brightness, and positive values to increase it.
.RE
.TP
.B \-\-contrast value
.RS
\-100..100 (in steps of 1). Set the contrast enhancement. 0 for no enhancement, negative
\-100..100 (in steps of 1). Set the contrast enhancement. 0 for no enhancement, negative
values to decrease contrast, and positive values to increase it.
.RE
.TP
.B \-\-disable-interpolation yes|no
.RS
When using high resolutions where the horizontal resolution is smaller than vertical resolution,
When using high resolutions where the horizontal resolution is smaller than vertical resolution,
data is expanded by software to preserve picture geometry. This can be disabled by this option to get
real scanned data.
.RE
.TP
.B \-\-disable-dynamic-lineart yes|no
.RS
Disable use of a software adaptive algorithm to generate lineart and rely on hardware lineart.
.RE
Disable use of a software adaptive algorithm to generate lineart and rely on hardware lineart.
.TP
.B \-\-color-filter None|Red|Green|Blue
.RS
When using gray or lineart this option selects the used color. Using a color filter
When using gray or lineart this option selects the used color. Using a color filter
will give a monochrome scan. CIS based scanners can to true gray when no filter (None value) is
selected.
.RE
.TP
.B \-\-lamp\-off\-scan
.RS
The lamp will be turned off during the scan. Calibration is still done with lamp on.
.RE
The lamp will be turned off during the scan. Calibration is still done with lamp on.
.TP
.B \-\-clear\-calibration
.RS
Clear calibration cache data, triggering a new calibration for the device when the
Clear calibration cache data, triggering a new calibration for the device when the
next scan will happen.
.RE
.TP
.B \-\-calibration\-file
.RS
Specify the calibration file name to use. At least the directory containing the file
Specify the calibration file name to use. At least the directory containing the file
must exist, since it won't be created. This option is disabled if the backend is run
as root. It maybe used in case of sheet-fed scanners to share a calibration file for several
users.
.RE
.TP
.B \-\-expiration\-time
.RS
Specify the time (in minutes) a cached calibration is considered valid. If older than the given value, a new
Specify the time (in minutes) a cached calibration is considered valid. If older than the given value, a new
calibration is done. A value of -1 means no expiration and cached value are kept forever unless cleared by
userwith the calibration clear option. A value of 0 means cache is disabled.
.RE
.PP
Additionally, several 'software' options are exposed by the backend. These
@ -146,35 +133,30 @@ capabilities. Please note that these features are somewhat simplistic, and
may not perform as well as the native implementations. Note also that these
features all require that the driver cache the entire image in memory. This
will almost certainly result in a reduction of scanning speed.
.PP
.B \-\-swcrop
.RS
Requests the driver to detect the extremities of the paper within the larger
image, and crop the empty edges.
.RE
.PP
.B \-\-swdeskew
.RS
Requests the driver to detect the rotation of the paper within the larger
image, and counter the rotation.
.RE
.PP
.B \-\-swdespeck \-\-despeck X
.RS
Requests the driver to find and remove dots of X diameter or smaller from the
image, and fill the space with the average surrounding color.
.RE
.PP
.B \-\-swskip 0..100% (in steps of 1) [0]
.RS
Request driver to discard pages with low numbers of dark pixels.
.RE
.PP
.B \-\-swderotate[=(yes|no)] [no]
.RS
Request driver to detect and correct 90 degree image rotation.
.PP
.TP
.B \-\-swcrop
Requests the driver to detect the extremities of the paper within the larger
image, and crop the empty edges.
.TP
.B \-\-swdeskew
Requests the driver to detect the rotation of the paper within the larger
image, and counter the rotation.
.TP
.B \-\-swdespeck \-\-despeck X
Requests the driver to find and remove dots of X diameter or smaller from the
image, and fill the space with the average surrounding color.
.TP
.B \-\-swskip 0..100% (in steps of 1) [0]
Request driver to discard pages with low numbers of dark pixels.
.TP
.B \-\-swderotate[=(yes|no)] [no]
Request driver to detect and correct 90 degree image rotation.
.SH "SYSTEM ISSUES"
This backend needs libusb-0.1.6 or later installed, and hasn't tested in other
configuration than a linux kernel 2.6.9 or higher. However, it should work any
@ -218,13 +200,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory separator
character, then the default directories are searched after the explicitly
specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_GENESYS
If the library was compiled with debug support enabled, this environment
@ -261,7 +248,9 @@ Syscan/Ambir DocketPORT 467/485/487/665/685
Xerox Travel Scanner 100, Onetouch 2400
.RE
.TP
cncsolutions (http://www.cncsolutions.com.br) sponsored and supported the work on the Panasonic KV-SS080.
cncsolutions
.RI ( http://www.cncsolutions.com.br )
sponsored and supported the work on the Panasonic KV-SS080.
.br
.TP
Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE 700F.
@ -283,32 +272,35 @@ Luc Verhaegen for donating a Canoscan LiDE 120.
Oliver Rauch
.br
Henning Meier-Geinitz
.I <henning@meier\-geinitz.de>
.RI < henning@meier\-geinitz.de >
.br
Gerhard Jaeger
.I<gerhard@gjaeger.de>
.RI < gerhard@gjaeger.de >
.br
St\['e]phane Voltz
.I<stef.dev@free.fr>
.RI < stef.dev@free.fr >
.br
Philipp Schmid
.I <philipp8288@web.de>
.RI < philipp8288@web.de >
.br
Pierre Willenbrock
.I <pierre@pirsoft.dnsalias.org>
.RI < pierre@pirsoft.dnsalias.org >
.br
Alexey Osipov
.I <simba@lerlan.ru> for HP2400 final support
.RI < simba@lerlan.ru >
for HP2400 final support
.SH "LIMITATIONS"
Powersaving isn't implemented for gl646 based scanner. Dynamic (emulated from gray data and with dithering) isn't enabled for gl646 scanners. Hardware lineart is limited up to 600 dpi for gl847 based scanners, due to the way image sensors are built.
.br
.TP
This backend will be much slower if not using libusb\-1.0. So be sure that sane\-backends is built with the \-\-enable-libusb_1_0 option.
.br
Powersaving isn't implemented for gl646 based scanner. Dynamic (emulated from gray data and with dithering)
isn't enabled for gl646 scanners. Hardware lineart is limited up to 600 dpi for gl847 based scanners,
due to the way image sensors are built.
.PP
This backend will be much slower if not using libusb\-1.0. So be sure that sane\-backends is built with
the
.B \-\-enable-libusb_1_0 option.
.SH "BUGS"
For the LiDE 200, the scanned data at 4800 dpi is obtained "as is" from sensor. It seems the windows driver does some digital processing
to improve it, which is not implemented in the backend.
For the LiDE 200, the scanned data at 4800 dpi is obtained "as is" from sensor.
It seems the windows driver does some digital processing to improve it, which is not implemented in the backend.
.PP

20
doc/sane-gphoto2.man
Wyświetl plik

@ -5,17 +5,20 @@ sane\-gphoto2 \- SANE backend for gphoto2 supported cameras
.SH DESCRIPTION
The
.B sane\-gphoto2
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to the digital cameras supported by gphoto2.
This backend has only been tested with a handful of cameras so far. Patches
to support other models are welcome.
.PP
Because of the limited testing of this backend, it is commented out
in @CONFIGDIR@/dll.conf by default. Either the comment
in
.I @CONFIGDIR@/dll.conf
by default. Either the comment
character must be removed or the backend must be called explicitly.
E.g. `scanimage \-d gphoto2' or `xscanimage gphoto2'.
E.g.
.I "scanimage \-d gphoto2"
or
.IR "xscanimage gphoto2" .
.SH "DEVICE NAMES"
The current version of the backend only allows one camera to be
connected. The device name is always "0".
@ -133,10 +136,9 @@ The manpage was largely copied from the dc210 manpage.
Many, no doubt.
.PP
More general comments, suggestions, and inquiries about frontends
or
.B SANE
should go to the SANE Developers mailing list
or SANE should go to the SANE Developers mailing list
(see
.IR http://www.sane\-project.org/mailing\-lists.html for details).
.I http://www.sane\-project.org/mailing\-lists.html
for details).
You must be subscribed to the list, otherwise your mail won't be
sent to the subscribers.

30
doc/sane-gt68xx.man
Wyświetl plik

@ -18,7 +18,7 @@ the scan area.
If you own a scanner other than the ones listed on the gt68xx homepage that works with this
backend, please let me know this by sending the scanner's exact model name and
the USB vendor and device ids (e.g. from
.I sane\-find\-scanner
.BR sane\-find\-scanner (1)
or syslog) to me. Even if the scanner's name is only slightly different from
the models already listed as supported, please let me know.
.PP
@ -30,8 +30,8 @@ following web page:
.SH LIBUSB ISSUES
Please use libusb-0.1.8 or later. Without libusb or with older libusb versions
all kinds of trouble can be expected. The scanner should be found by
sane\-find\-scanner without further actions. For setting permissions and general
USB information looks at
.BR sane\-find\-scanner (1)
without further actions. For setting permissions and general USB information looks at
.BR sane\-usb (5).
.PP
@ -163,13 +163,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_GT68XX
If the library was compiled with debug support enabled, this environment
@ -196,7 +202,8 @@ export SANE_DEBUG_GT68XX=4
.I http://www.meier\-geinitz.de/sane/gt68xx
.SH AUTHOR
Henning Meier-Geinitz <henning@meier\-geinitz.de>
Henning Meier-Geinitz
.RI < henning@meier\-geinitz.de >
.br
The original gt68xx driver was written by Sergey Vlasov, Andreas Nowack, and
David Stevenson. Thanks for sending patches and answering questions to them
@ -213,6 +220,11 @@ Support for buttons is missing.
.PP
More detailed bug information is available at the gt68xx backend homepage
.IR http://www.meier\-geinitz.de/sane/gt68xx\-backend/ .
.br
Please contact us if you find a bug or missing feature:
<sane\-devel@alioth-lists.debian.net>. Please send a debug log if your scanner isn't
detected correctly (see SANE_DEBUG_GT68XX above).
.RI < sane\-devel@alioth-lists.debian.net >.
.br
Please send a debug log if your scanner isn't
detected correctly (see
.B SANE_DEBUG_GT68XX
above).

24
doc/sane-hp.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hp \- SANE backend for HP ScanJet scanners
.SH DESCRIPTION
The
.B sane\-hp
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to HP ScanJet scanners which support SCL (Scanner
Control Language by HP). The following
scanners are known positively to work with this backend:
@ -52,7 +50,9 @@ the kernel scanner driver or libusb. See
.BR sane\-usb (5)
for more details.
.PP
The "hp" backend no longer supports OfficeJet multi-function peripherals.
The
.B sane\-hp
backend no longer supports OfficeJet multi-function peripherals.
For these devices use the external "hpoj" backend in version 0.90 and later of
the "HP OfficeJet Linux driver", available at
.br
@ -62,8 +62,9 @@ the "HP OfficeJet Linux driver", available at
Because Hewlett-Packard does no longer produce scanners that support
SCL (beside the OfficeJets), the above list of supported scanners is
complete.
Other HP scanners are not supported by the "hp" backend, but might be supported
by another one. See
Other HP scanners are not supported by the
.B sane\-hp
backend, but might be supported by another one. See
.IR http://www.sane\-project.org/ .
You can also watch the sane\-devel mailing list at
.IR http://www.sane\-project.org/mailing\-lists.html .
@ -131,10 +132,12 @@ the scanner is connected by USB.
Option
.B connect\-device
specifies that the scanner is connected to the system by a special
device. Input/output is performed by read()/write()-operations
device. Input/output is performed by
.BR read ()/ write "()-operations"
on the device. This option must be used for HP ScanJet Plus
or scanners connected to USB which are accessed through a named device
(e.g. /dev/usb/scanner0).
(e.g.
.IR /dev/usb/scanner0 ).
For device names that contain "usb", "uscanner" or "ugen", it is not
necessary to specify option connect\-device.
@ -296,5 +299,6 @@ is supported by the ppSCSI-driver (see above).
.BR scanimage (1)
.SH AUTHOR
The sane\-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
PhotoScanner support by Peter Kirchgessner.
The sane\-hp backend was written by Geoffrey T. Dairiki.
.br
HP PhotoSmart PhotoScanner support by Peter Kirchgessner.

7
doc/sane-hp3500.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hp3500 \- SANE backend for Hewlett-Packard ScanJet 3500 series scanners
.SH DESCRIPTION
The
.B sane\-hp3500
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to the following Hewlett-Packard USB flatbed scanners:
.PP
.RS
@ -51,4 +49,5 @@ export SANE_DEBUG_HP3500=4
.I http://projects.troy.rollo.name/rt-scanners/
.SH AUTHOR
Troy Rollo <sane@troy.rollo.name>
Troy Rollo
.RI < sane@troy.rollo.name >

13
doc/sane-hp3900.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hp3900 \- SANE backend for RTS8822 chipset based scanners
.SH DESCRIPTION
The
.B sane\-hp3900
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access at least to the following USB flatbed scanners:
.PP
.RS
@ -34,7 +32,9 @@ backend homepage
.IR http://sourceforge.net/projects/hp3900\-series/ .
.PP
This is ALPHA software. Keep your hand at the scanner's plug and unplug it, if
scanner does not start to scan. See also the BUGS section.
scanner does not start to scan. See also the
.B BUGS
section.
.PP
If you own a scanner other than the ones listed above that works with this
backend, please let us know this by sending the scanner's exact model name and
@ -94,7 +94,7 @@ to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
.I "/etc/sane.d"
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_HP3900
@ -115,7 +115,8 @@ export SANE_DEBUG_HP3900=4
.I http://jkdsoftware.dyndns.org/drupal/?q=es/books/151
.SH AUTHOR
Jonathan Bravo Lopez <jkdsoft@gmail.com>
Jonathan Bravo Lopez
.RI < jkdsoft@gmail.com >
.SH BUGS
Scanning is only tested with Linux/ix86/gcc. Be careful when testing on other

4
doc/sane-hp4200.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hp4200 \- SANE backend for Hewlett-Packard 4200 scanners
.SH DESCRIPTION
The
.B sane\-hp4200
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to the following Hewlett-Packard USB flatbed scanners:
.PP
.RS

4
doc/sane-hp5400.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hp5400 \- SANE backend for Hewlett-Packard 54XX scanners
.SH DESCRIPTION
The
.B sane\-hp5400
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to the following Hewlett-Packard USB flatbed scanners:
.PP
.RS

20
doc/sane-hp5590.man
Wyświetl plik

@ -8,9 +8,10 @@ sane-hp5590 - SANE backend for Hewlett-Packard
4500C/4570C/5500C/5550C/5590/7650 Workgroup/Document scanners
.SH DESCRIPTION
.PP
The \f[B]sane-hp5590\f[R] library implements a SANE (Scanner Access Now
Easy) backend that provides access to the following Hewlett-Packard
Workgroup/Document scanners:
The
.B sane-hp5590
library implements a SANE (Scanner Access Now Easy) backend that provides access
to the following Hewlett-Packard Workgroup/Document scanners:
.IP \[bu] 2
ScanJet 4500C
.IP \[bu] 2
@ -27,8 +28,9 @@ ScanJet 7650
If you own a scanner other than the ones listed above that works with
this backend, please let us know this by sending the scanner\[cq]s exact
model name and the USB vendor and device ids (e.g.\ from
\f[I]/sys/bus/usb/devices\f[R], \f[I]sane-find-scanner\f[R] or syslog)
to us.
.IR /sys/bus/usb/devices ,
.BR sane-find-scanner (1)
or syslog) to us.
Even if the scanner\[cq]s name is only slightly different from the
models mentioned above, please let us know.
.SH OPTIONS
@ -207,26 +209,28 @@ Get the id of the last button pressed.
Id is one of \[lq]none\[rq], \[lq]power\[rq], \[lq]scan\[rq],
\[lq]collect\[rq], \[lq]file\[rq], \[lq]email\[rq], \[lq]copy\[rq],
\[lq]up\[rq], \[lq]down\[rq], \[lq]mode\[rq], \[lq]cancel\[rq].
.PD 0
.P
.PD
.br
The scanner stores the id of the last button pressed until it is read.
After read out, the state is reset and subsequent readings will return
\[lq]none\[rq].
.TP
.B --color-led
Get the state of the color LED indicators.
The state is either \[lq]color\[rq] or \[lq]black_white\[rq].
.TP
.B --counter-value
Get the counter value as shown on LCD.
The value is in the range of 1 ..
99.
.TP
.B --doc-in-adf
Get the state of the document-available indicator of the automatic
document feeder (ADF).
The state is either \[lq]yes\[rq] or \[lq]no\[rq].
.SH HINTS FOR USERS OF SCANBD
.PP
.BR scanbd (8)

4
doc/sane-hpljm1005.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hpljm1005 \- SANE backend for Hewlett-Packard LaserJet M1005 MFP Scanner
.SH DESCRIPTION
The
.B sane\-hpljm1005
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to the following Hewlett-Packard scanner:
.PP
.RS

30
doc/sane-hpsj5s.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hpsj5s \- SANE backend for HP ScanJet 5S sheet-fed scanner
.SH DESCRIPTION
The
.B sane\-hpsj5s
library implements a
.B SANE
(Scanner Access Now Easy) backend that
library implements a SANE (Scanner Access Now Easy) backend that
provides access to a parallel port Hewlett-Packard ScanJet 5S scanner.
.PP
IMPORTANT: this is alpha code. Don't expect this to work
@ -26,8 +24,8 @@ too,this backend should work. If you ported
for your platform, please let me know. Your system should support
.B EPP
(or
.B EPP+ECP
) mode to operate this scanner. Future versions will support ECP and SPP
.BR EPP+ECP )
mode to operate this scanner. Future versions will support ECP and SPP
(Nibble and Byte) modes also. It's planned to support scanners not only
at daisy-chain position 0, but anywhere. Support for multiple scanners could
be implemented too.
@ -36,7 +34,8 @@ Current version implements only gray scale scanning. True Color and B/W modes ar
not supported for now.
.PP
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
Max Vorobiev <pcwizard@yandex.ru>.
Max Vorobiev
.RI < pcwizard@yandex.ru >.
.PP
.SH "DEVICE NAMES"
This backend expects device names of the form:
@ -88,13 +87,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_HPSJ5S
If the library was compiled with debug support enabled, this environment
@ -105,11 +110,12 @@ increase the verbosity of the output.
.BR sane (7),
.BR libieee1284 (3)
.br
http://hpsj5s.sourceforge.net
.I http://hpsj5s.sourceforge.net
.br
http://cyberelk.net/tim/libieee1284
.I http://cyberelk.net/tim/libieee1284
.br
.SH AUTHOR
Max Vorobiev
.br
Man page mostly based on canon.man
Man page mostly based on
.IR canon.man .

27
doc/sane-hs2p.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-hs2p \- SANE backend for Ricoh SCSI flatbed/ADF scanners
.SH DESCRIPTION
The
.B sane\-hs2p
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to the Ricoh IS450 family of scanners. Should also work with the IS420,
IS410, and IS430 scanners, but these are untested.
Please contact the maintainer or the sane\-devel mailing list if you own such a scanner.
@ -27,7 +25,7 @@ Where
.I special
is either the path-name for the special device that corresponds to a SCSI
scanner. The program
.I sane\-find\-scanner
.BR sane\-find\-scanner (1)
helps to find out the correct device. Under Linux, such a device name could be
.I /dev/sg0
or
@ -66,13 +64,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_HS2P
If the library was compiled with debug support enabled, this
@ -80,7 +84,9 @@ environment variable controls the debug level for this backend.
A value of 255 prints all debug output. Smaller values reduce verbosity.
.SH CURRENT STATUS
The hs2p backend is now in version 1.00. All major scanning-related features
The
.B sane\-hs2p
backend is now in version 1.00. All major scanning-related features
are supported, except for those features requiring the optional IPU. Scanning
from the flatbed or ADF (either simplex or duplex) is supported. Lineart,
halftone, 4-bit gray, and 8-bit gray are supported. Pre-set gamma tables and
@ -108,8 +114,9 @@ suited to a stand-alone utility to be used by a technician when
replacing the lamp or ADF unit. Nor is support for reading or changing
IPU (93H) parameters and adjustments planned, since my IS450 lacks
such a unit. The 31-byte Auto Photo/Letter struct and 21-byte Dynamic
threshold struct are documented in the hs2p-scsi.h file should someone
wish to use their IPU for image data processing.
threshold struct are documented in the
.I hs2p-scsi.h
file should someone wish to use their IPU for image data processing.
.SH "SEE ALSO"
.BR sane (7),

18
doc/sane-ibm.man
Wyświetl plik

@ -5,9 +5,7 @@ sane\-ibm \- SANE backend for IBM and Ricoh SCSI flatbed scanners
.SH DESCRIPTION
The
.B sane\-ibm
library implements a
.B SANE
(Scanner Access Now Easy) backend that provides
library implements a SANE (Scanner Access Now Easy) backend that provides
access to the IBM 2456 and the Ricoh IS-410, IS-420, and IS-430 flatbed
scanners. Support for the IS-410 and IS-430 is untested. Please contact the
maintainer or the sane\-devel mailing list if you own such a scanner.
@ -27,7 +25,7 @@ Where
.I special
is either the path-name for the special device that corresponds to a SCSI
scanner. The program
.I sane\-find\-scanner
.BR sane\-find\-scanner (1)
helps to find out the correct device. Under Linux, such a device name could be
.I /dev/sg0
or
@ -66,13 +64,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_IBM
If the library was compiled with debug support enabled, this

12
doc/sane-kodak.man
Wyświetl plik

@ -63,7 +63,9 @@ coordinates when using ADF and to detect double feed errors.
.RE
.PP
Other options will be available based on the capabilities of the scanner.
Use 'scanimage \-\-help' to get a list, but be aware that some options may
Use
.I scanimage \-\-help
to get a list, but be aware that some options may
be settable only when another option has been set, and that advanced options
may be hidden by some frontend programs.
.PP
@ -108,8 +110,9 @@ warned.
.PP
.SH ENVIRONMENT
The backend uses a single environment variable, SANE_DEBUG_KODAK, which
enables debugging output to stderr. Valid values are:
The backend uses a single environment variable,
.BR SANE_DEBUG_KODAK ,
which enables debugging output to stderr. Valid values are:
.PP
.RS
5 Errors
@ -146,4 +149,5 @@ Kodak provided access to hardware, documentation and personnel.
.BR scanimage (1)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.RI < "kitno455 a t gmail d o t com" >

4
doc/sane-kodakaio.man
Wyświetl plik

@ -7,9 +7,7 @@ sane\-kodakaio \- SANE backend for Kodak aio printer / scanners
.SH DESCRIPTION
The
.B sane\-kodakaio
library implements a
.B SANE
(Scanner Access Now Easy) backend which
library implements a SANE (Scanner Access Now Easy) backend which
provides access to Kodak aio printer/scanners, like the ESP and Hero series.
This document describes backend version 2.4, which is the first candidate for

3
doc/sane-kvs1025.man
Wyświetl plik

@ -28,4 +28,5 @@ The backend was tested on KV-S1025C and 1045C by Tiago Zaniquelli.
.BR sane\-usb (5)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.RI < "kitno455 a t gmail d o t com" >

3
doc/sane-kvs20xx.man
Wyświetl plik

@ -27,4 +27,5 @@ by m. allan noah.
.BR sane\-scsi (5)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.RI < "kitno455 a t gmail d o t com" >

3
doc/sane-kvs40xx.man
Wyświetl plik

@ -29,4 +29,5 @@ by m. allan noah.
.BR sane\-scsi (5)
.SH AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
m. allan noah:
.RI < "kitno455 a t gmail d o t com" >

16
doc/sane-leo.man
Wyświetl plik

@ -25,10 +25,10 @@ The scanners that should work with this backend are:
.RE
The options the backend supports can either be selected through
command line options to programs like
command line options to programs like
.BR scanimage (1)
or through GUI elements in
.BR xscanimage (1)
or through GUI elements in
.BR xscanimage (1)
or
.BR xsane (1).
@ -116,9 +116,9 @@ selected. The default is "no".
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/leo.conf
supports only one information: the device name to use (eg
supports only one information: the device name to use (eg
.IR /dev/scanner ).
@ -147,8 +147,7 @@ backend. However they are only software adjustments. This backend only
implements what the scanner can support.
.SH BUGS
SH BUGS
None known.
@ -156,7 +155,7 @@ None known.
.BR sane\-scsi (5),
.BR scanimage (1),
.BR xscanimage (1),
.BR xscanimage (1),
.BR xsane (1),
.BR sane (7)
@ -166,4 +165,3 @@ None known.
.TP
The package is actively maintained by Frank Zago.
.I http://www.zago.net/sane/#leo

18
doc/sane-lexmark.man
Wyświetl plik

@ -33,11 +33,15 @@ The scanners that should work with this backend are:
.RE
The options the backend supports can either be selected through
command line options to programs like scanimage or through GUI
elements in xscanimage or xsane.
command line options to programs like
.BR scanimage (1)
or through GUI elements in
.BR xscanimage (1)
or
.BR xsane (1).
.br
If you have any strange behavior, please report to the backend
If you notice any strange behavior, please report to the backend
maintainer or to the SANE mailing list.
Valid command line options and their syntax can be listed by using
@ -93,7 +97,7 @@ The default value of the threshold option is 50.
.SH "CONFIGURATION FILE"
The configuration file
The configuration file
.I @CONFIGDIR@/lexmark.conf
contains only the usb device id (eg usb 0x043d 0x007c).
@ -138,7 +142,7 @@ No bugs currently known.
.BR sane\-scsi (5),
.BR scanimage (1),
.BR xscanimage (1),
.BR xsane (1),
.BR xsane (1),
.BR sane (7)
@ -150,7 +154,9 @@ The backend was originally written by Fred Odendaal.
The new version is currently developed by St\['e]phane Voltz.
.I http://stef.dev.free.fr/sane/lexmark
.TP
X74 support was written by Torsten Houwaart (<ToHo@gmx.de>)
X74 support was written by Torsten Houwaart
.RI < ToHo@gmx.de >
.SH "CREDITS"
.TP
Many thanks go to:

15
doc/sane-ma1509.man
Wyświetl plik

@ -96,13 +96,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_MA1509
If the library was compiled with debug support enabled, this
@ -121,7 +127,8 @@ debug levels increase the verbosity of the output.
.I http://www.meier\-geinitz.de/sane/ma1509\-backend/
.SH AUTHOR
Henning Meier-Geinitz <henning@meier\-geinitz.de>
Henning Meier-Geinitz
.RI < henning@meier\-geinitz.de >
.SH BUGS
Resolutions higher than 600 dpi don't work

17
doc/sane-magicolor.man
Wyświetl plik

@ -43,17 +43,18 @@ The static library implementing this backend.
.TP
.I @LIBDIR@/libsane\-magicolor.so
The shared library implementing this backend (present on systems that support dynamic loading).
.SH "ENVIRONMENT"
.TP
.B SANE_CONFIG_DIR
This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi\-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in
This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi\-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR "/tmp/config" ,
to "/tmp/config:" would result in directories
.IR "/tmp/config" ,
.IR "." ,
and
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
@ -62,7 +63,8 @@ If the library was compiled with debug support enabled, this environment variabl
Example: export SANE_DEBUG_MAGICOLOR=127
To obtain debug messages from the backend, set this environment variable before calling your favorite frontend (e.g. xscanimage).
To obtain debug messages from the backend, set this environment variable before calling your favorite frontend (e.g.
.BR xscanimage (1)).
Example: SANE_DEBUG_MAGICOLOR=65 xscanimage
.SH "KNOWN BUGS AND RESTRICTIONS"
@ -70,10 +72,13 @@ Example: SANE_DEBUG_MAGICOLOR=65 xscanimage
Large color scans may sometimes timeout due to unknown reasons (the scanner simply stops returning data)
.PP
Cancelling large scans may lock up the scanner.
.SH "SEE ALSO"
.BR sane (7),
.br
.I http://wiki.kainhofer.com/hardware/magicolor_scan
.SH "AUTHOR"
.PP
Reinhold Kainhofer <reinhold@kainhofer.com>
Reinhold Kainhofer
.RI < reinhold@kainhofer.com >

11
doc/sane-matsushita.man
Wyświetl plik

@ -104,9 +104,9 @@ options set the gamma curve. It is only valid for Gray modes, and is not availab
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/matsushita.conf
supports the device name to use (eg
supports the device name to use (eg
.IR /dev/scanner )
and the SCSI option to auto-detect the scanners supported.
@ -148,10 +148,11 @@ The backend does not support the setting of different options for each side. The
.SH SCANNING EXAMPLE
To date, the only frontend capable of using this scanner at full speed is
.B
scanadf.
.BR scanadf (1).
A scanadf command line would be:
A
.BR scanadf (1)
command line would be:
scanadf \-d matsushita \-\-output\-file scan%04d.pbm \-\-start\-count 0 \-\-duplex \-\-resolution 300 \-\-feeder\-mode="All pages" \-\-paper\-size="A4"

18
doc/sane-microtek.man
Wyświetl plik

@ -65,7 +65,7 @@ are available from the backend homepage:
.br
.PP
.RS
.B http://www.mir.com/mtek/
.I http://www.mir.com/mtek/
.RE
.SH "DEVICE NAMES"
@ -135,14 +135,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
@ -186,11 +186,12 @@ option in the configuration file (first one, then both), and see if it helps.
(If it does, report it.)
.PP
Send lengthy bug reports and new scanner information to
.BR mtek\-bugs@mir.com .
.IR mtek\-bugs@mir.com .
All bug reports and new scanner inquiries should include an error log file.
You can generate copious
stderr output by setting the SANE_DEBUG_MICROTEK environment variable
described above. For example:
stderr output by setting the
.B SANE_DEBUG_MICROTEK
environment variable described above. For example:
.PP
.RS
setenv SANE_DEBUG_MICROTEK 128
@ -198,6 +199,7 @@ setenv SANE_DEBUG_MICROTEK 128
.PP
More general comments, suggestions, and inquiries about frontends
or SANE should go to
.BR sane\-devel@alioth-lists.debian.net ,
.IR sane\-devel@alioth-lists.debian.net ,
the SANE Developers mailing list. Have a look at
http://www.sane\-project.org/mailing\-lists.html concerning subscription to sane\-devel.
.I http://www.sane\-project.org/mailing\-lists.html
concerning subscription to sane\-devel.

21
doc/sane-microtek2.man
Wyświetl plik

@ -9,15 +9,17 @@ provides access to Microtek scanners with a SCSI-2 command set.
This backend can be considered alpha to beta. Some scanner models are reported
to work well, others not. New development versions of this backend can be
obtained from
.B http://karstenfestag.gmxhome.de
.IR http://karstenfestag.gmxhome.de .
.PP
There exists a different backend for Microtek scanners with SCSI-1 command
set.
Refer to sane\-microtek(5) for details.
Refer to
.BR sane\-microtek (5)
for details.
.PP
And there is work in progress for the ScanMaker 3600.
See
.B http://sourceforge.net/projects/sm3600
.IR http://sourceforge.net/projects/sm3600 .
.PP
At present, the following scanners are known positively to work with this
backend:
@ -53,7 +55,7 @@ Scanpaq SQ2030 Parport
.ft R
.PP
Additional information can be found at
.BR http://www.sane\-project.org/ .
.IR http://www.sane\-project.org/ .
.PP
If you own a Microtek scanner other than the ones listed above,
it may or may not work with SANE! Because equal scanners are sold under
@ -109,7 +111,9 @@ supported by the scanner in dependence of the scanning-mode and other
options.
Not supported options are disabled.
.PP
The following options are supported by the Microtek2-driver:
The following options are supported by the
.B sane\-microtek2
driver:
.PP
Color, grayscale, halftone and lineart scans.
.PP
@ -299,8 +303,8 @@ If the library was compiled with debug support enabled, this
environment variable controls the debug level for this backend. E.g.,
a value of 255 requests all debug output to be printed. Smaller
levels reduce verbosity. To see error messages on stderr set
SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging levels should
be better revised).
.B SANE_DEBUG_MICROTEK2
to 1 (Remark: The whole debugging levels should be better revised).
.br
E.g. just say:
.br
@ -313,4 +317,5 @@ export SANE_DEBUG_MICROTEK2=128
.SH "AUTHORS"
Bernd Schroeder (not active anymore)
.br
Karsten Festag karsten.festag@gmx.de
Karsten Festag
.RI < karsten.festag@gmx.de >.

12
doc/sane-mustek.man
Wyświetl plik

@ -95,7 +95,7 @@ and a debug output to
.IR sane\-devel@alioth-lists.debian.net .
You can get the debug output by setting the environment variable
.B SANE_DEBUG_MUSTEK
to 5 and showing the list of available scanners with
to 5 and showing the list of available scanners with
.IR "scanimage \-L" .
Please send all of it to the mailing list. You must be subscribed to sane\-devel
before you can send mail to the list. See
@ -117,7 +117,7 @@ be found (see section
.B "PARALLEL PORT SCANNERS"
below). For SCSI scanners, the special device name must be a generic SCSI
device or a symlink to such a device. The program
.I sane\-find\-scanner
.BR sane\-find\-scanner (1)
helps to find out the correct device. Under Linux, such a device name
could be
.I /dev/sg0
@ -221,7 +221,7 @@ Finally,
is a global option. If set, the backend will wait until the device is ready
before sending the inquiry command. Further more the backend will force the
scan slider to return to its starting position (not implemented for all
scanners). This option may be necessary with the 600 II N or when
scanners). This option may be necessary with the 600 II N or when
.BR scanimage (1)
is used multiple times (e.g. in scripts). The default is off (not set).
.PP
@ -330,6 +330,7 @@ you use the scanner again, the lamp turns back on to the normal high
brightness. However, the first image scanned after such a shutdown may
have stripes and appear to be over-exposed. When this happens, just
take another scan, and the image will be fine.
.SH FILES
.TP
.I @CONFIGDIR@/mustek.conf
@ -343,6 +344,7 @@ The static library implementing this backend.
.I @LIBDIR@/libsane\-mustek.so
The shared library implementing this backend (present on systems that
support dynamic loading).
.SH ENVIRONMENT
.TP
.B SANE_CONFIG_DIR
@ -351,14 +353,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and

60
doc/sane-mustek_pp.man
Wyświetl plik

@ -97,7 +97,7 @@ systems. If that is the case for you, you can either disable ECP/EPP in your
BIOS or disable it in the backend itself (see GLOBAL OPTIONS).
.PP
Note that the backend needs to run as root or has to have appropriate access
rights to
rights to
.I /dev/parport*
if libieee1284 support is compiled in. To allow user
access to the scanner run the backend through the network interface (See
@ -112,15 +112,16 @@ i.e. if you try printing while scanning, your computer may crash. To enable
parport sharing, you have to enable libieee1284 at compile time. This backend
also conflicts with the
.BR sane\-musteka4s2 (5)
backend. You can only enable one of them in your
backend. You can only enable one of them in your
.IR dll.conf .
However, you have
to enable the backend explicitly in your dll.conf, just remove the hash mark
in the line "mustek_pp".
to enable the backend explicitly in your
.IR dll.conf ,
just remove the hash mark in the line "mustek_pp".
.SH "DEVICE DEFINITION"
This backend allows multiple devices being defined and configured via the
.B mustek_pp.conf
.I mustek_pp.conf
file (even simultaneously, provided that they are connected to different
parallel ports). Please make sure to edit this file
.B before
@ -162,8 +163,11 @@ can be different for different Linux kernel versions. For instance,
if you are using a Kernel 2.2.x or better and you have only one
parallel port, this port is named lp0 regardless of the base address. However,
this backend requires the base address of your port. If you are not sure which
port your scanner is connected to, have a look at your /etc/conf.modules,
/etc/modules.conf and/or /proc/ioports.
port your scanner is connected to, have a look at your
.IR /etc/conf.modules ,
.I /etc/modules.conf
and/or
.IR /proc/ioports .
.PP
If you are unsure which port to use, you can use the magic value
.BR *
@ -209,7 +213,7 @@ scanner Mustek_600IIIEP * ccd300
If in doubt which port you have to use, or whether your scanner is
detected at all, you can use
.B sane\-find\-scanner \-p
.I sane\-find\-scanner \-p
to probe all configured ports.
.SH CONFIGURATION
@ -369,10 +373,10 @@ option top 56
.SH GLOBAL OPTIONS
.PP
You can control the overall behaviour of the
.B sane-\mustek_pp
You can control the overall behaviour of the
.B sane-\mustek_pp
backend by global
options which precede any scanner definition in the
options which precede any scanner definition in the
.I mustek_pp.conf
file.
.sp
@ -411,14 +415,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
@ -476,15 +480,18 @@ For additional information on the CIS driver, see
.SH AUTHORS
.nf
Jochen Eisinger <jochen at penguin\-breeder dot org>
Eddy De Greef <eddy_de_greef at scarlet dot be>
Jochen Eisinger
.RI < "jochen at penguin\-breeder dot org" >
Eddy De Greef
.RI < "eddy_de_greef at scarlet dot be" >
.fi
.SH BUGS
Too many... please send bug reports to
.I sane\-devel@alioth-lists.debian.net
(note that you have to subscribe first to the list before you can send
emails... see http://www.sane\-project.org/mailing\-lists.html)
emails... see
.IR http://www.sane\-project.org/mailing\-lists.html ).
.SH BUG REPORTS
If something doesn't work, please contact us (Jochen for the CCD scanners,
@ -493,17 +500,24 @@ your scanner to be able to help you...
.TP
.I SANE version
run "scanimage \-V" to determine this
Run
.I scanimage \-V
to determine this.
.TP
.I the backend version and your scanner hardware
run "SANE_DEBUG_MUSTEK_PP=128 scanimage \-L" as root. If you don't get any output
from the mustek_pp backend, make sure a line "mustek_pp" is included into
your @CONFIGDIR@/dll.conf.
Run
.I SANE_DEBUG_MUSTEK_PP=128 scanimage \-L
as root. If you don't get any output from the
.BR sane\-mustek_pp
backend, make sure a line "mustek_pp" is included into your
.IR @CONFIGDIR@/dll.conf .
If your scanner isn't detected, make sure you've defined the right port address
in your mustek_pp.conf.
in your
.IR mustek_pp.conf .
.TP
.I the name of your scanner/vendor
also a worthy information. Please also include the optical resolution and lamp type of your scanner, both can be found in the manual of your scanner.
.I the name of your scanner/vendor also a worthy information. Please also include the
optical resolution and lamp type of your scanner, both can be found in the manual of
your scanner.
.TP
.I any further comments
if you have comments about the documentation (what could be done better), or you

15
doc/sane-mustek_usb.man
Wyświetl plik

@ -140,13 +140,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_MUSTEK_USB
If the library was compiled with debug support enabled, this
@ -186,7 +192,8 @@ export SANE_DEBUG_MUSTEK_USB=4
.I http://www.meier\-geinitz.de/sane/mustek_usb\-backend/
.SH AUTHOR
Henning Meier-Geinitz <henning@meier\-geinitz.de>
Henning Meier-Geinitz
.RI < henning@meier\-geinitz.de >
.br
This backend is based on the Mustek 1200ub backend from Mustek, maintained by
Tom Wang.

9
doc/sane-mustek_usb2.man
Wyświetl plik

@ -67,11 +67,14 @@ export SANE_DEBUG_MUSTEK_USB2=4
.SH AUTHOR
The driver has been written Roy Zhou, Jack Xu, and Vinci Cen from
Mustek. Adjustments to SANE by Henning Meier-Geinitz.
Mustek.
.br
Adjustments to SANE by Henning Meier-Geinitz.
.SH BUGS
Please contact me if you find a bug or missing feature:
<henning@meier\-geinitz.de>. Please send a debug log if your scanner isn't
detected correctly (see
.RI < henning@meier\-geinitz.de >.
.br
Please send a debug log if your scanner isn't detected correctly (see
.B SANE_DEBUG_MUSTEK_USB2
above).

9
doc/sane-net.man
Wyświetl plik

@ -123,15 +123,15 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
.I "@CONFIGDIR@"
@ -152,7 +152,7 @@ environment variable controls the debug level for this backend. E.g.,
a value of 128 requests all debug output to be printed. Smaller
levels reduce verbosity.
.SH BUGS
If
If
.BR saned (8)
has timed out, the net backend may loop with authorization requests.
@ -165,4 +165,3 @@ has timed out, the net backend may loop with authorization requests.
.I http://www.penguin-breeder.org/?page=sane\-net
.SH AUTHOR
David Mosberger and Andreas Beck

5
doc/sane-niash.man
Wyświetl plik

@ -75,6 +75,7 @@ export SANE_DEBUG_NIASH=255
.BR sane (7),
.BR sane\-usb (5)
.br
http://www.sourceforge.net/projects/hp3300backend
.I http://www.sourceforge.net/projects/hp3300backend
.SH AUTHOR
Bertrik Sikken <bertrik@zonnet.nl>
Bertrik Sikken
.RI < bertrik@zonnet.nl >

24
doc/sane-p5.man
Wyświetl plik

@ -52,7 +52,7 @@ You can rename any device using the
option. This option apply to the last port option.
.SH "CONFIGURATION"
Please make sure to edit
Please make sure to edit
.I dll.conf
.B before
you use the backend, since this backend isn't enabled by default.
@ -80,14 +80,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
@ -125,7 +125,8 @@ level debug output
.BR scanimage (1)
.SH "AUTHOR"
St\['e]phane Voltz <stef.dev@free.fr>
St\['e]phane Voltz
.RI < stef.dev@free.fr >
.SH "CREDITS"
Support for the Prima PagePartner has been made possible thank to an hardware donation
@ -133,8 +134,9 @@ by S\['e]bastien Lange.
.SH "BUG REPORTS"
If something doesn't work mail sane-devel@alioth-lists.debian.net or submit an
issue via https://gitlab.com/sane-project/backends/issues/new with a label of
backend/p5.
issue via
.I https://gitlab.com/sane-project/backends/issues/new
with a label of backend/p5.
Please give as much information as you can.
.TP
@ -142,16 +144,18 @@ Please give as much information as you can.
run "scanimage \-V" to determine this
.TP
.I the backend version and your scanner hardware
run "SANE_DEBUG_P5=255 scanimage \-L 2>log" as root. If you don't get any output
from the p5 backend, make sure a line "p5" is included into
your
run
.I "SANE_DEBUG_P5=255 scanimage \-L 2>log"
as root. If you don't get any output from the p5 backend, make sure a line "p5" is included into
your
.IR @CONFIGDIR@/dll.conf .
If your scanner isn't detected, make sure you've defined the right port address, or the
correct device
in your p5.conf.
.TP
.I the name of your scanner/vendor
also a worthy information. Please also include the optical resolution and lamp type of your scanner, both can be found in the manual of your scanner.
also a worthy information. Please also include the optical resolution and lamp type of your
scanner, both can be found in the manual of your scanner.
.TP
.I any further comments
if you have comments about the documentation (what could be done better), or you

3
doc/sane-pie.man
Wyświetl plik

@ -55,4 +55,5 @@ support dynamic loading).
.SH "CONTACT AND BUG-REPORTS"
Please send any information and bug-reports to:
.br
.B Simon Munton <simon@munton.demon.co.uk>
Simon Munton
.RI < simon@munton.demon.co.uk >

11
doc/sane-pieusb.man
Wyświetl plik

@ -45,21 +45,21 @@ detection and re-orientation when scanning multiple slides. You have
to put all slides into one orientation first !
.SH "DIRT REMOVAL"
If available,
If available,
.B sane\-pieusb
supports infrared scans for dirt detection and
removal. This must be enabled via the 'Clean image' setting.
.SH "KNOWN PROBLEMS"
The
The
.B sane\-pieusb
backend supports dirt removal based on infrared scan
information. Since SANE does not provide post-processing in the
backend,
backend,
.B sane\-pieusb
does the scanning and dirt removal during the setup
phase. The 'scan' phase is only used to transfer the completed image.
Therefore
Therefore
.B sane\-pieusb
does not multi-thread making a typical frontend
appear as 'blocked'. Also cancel requests are only honored between
@ -112,7 +112,8 @@ support dynamic loading).
.SH "CONTACT AND BUG-REPORTS"
Please send any information and bug-reports to:
.br
.B Klaus Kämpf <kkaempf@suse.com>
Klaus Kämpf
.RI < kkaempf@suse.com >
.SH AUTHORS
The pieusb backend is based on work by Jan Vleeshouwers, Michael

9
doc/sane-pint.man
Wyświetl plik

@ -22,8 +22,9 @@ If have successfully used the PINT driver with your scanner, but it
does not work using this SANE backend, please let us know. To do
this, send a mail with the relevant information for your scanner to
.IR sane\-devel@alioth-lists.debian.net .
Have a look at http://www.sane\-project.org/mailing\-lists.html concerning subscription
to sane\-devel.
Have a look at
.I http://www.sane\-project.org/mailing\-lists.html
concerning subscription to sane\-devel.
.SH "DEVICE NAMES"
This backend expects device names of the form:
@ -76,14 +77,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.BR "." ,
and

29
doc/sane-pixma.man
Wyświetl plik

@ -183,13 +183,13 @@ it as well as we could, but it may not work in all situations. You will find
an up-to-date status at the project homepage. (See below).
Users feedback is essential to help improve features and performances.
.SH OPTIONS
Besides "well-known" options (e.g. resolution, mode etc.)
.Bsane\-pixma
Besides "well-known" options (e.g. resolution, mode etc.)
.Bsane\-pixma
backend also
provides the following options, i.e. the options might change in the future.
.br
The button status can be polled i.e. with
.I 'scanimage \-A'.
The button status can be polled i.e. with
.I scanimage \-A.
.br
Button scan is disabled on MAC OS X due to darwin libusb not handling
timeouts in usb interrupt reads, but may work when using the network protocol.
@ -285,7 +285,7 @@ The file contains an optional list of networked scanners using the BJNP or MFNP
(See below for datails on networking support for scanners). Normally
only scanners that cannot be auto-detected because they are on a different
subnet shall be listed here. If you do not use Linux and your OS does not allow enumeration of
interfaces (i.e. it does not support the
interfaces (i.e. it does not support the
.BR getifaddrs ()
qfunction) you also may need
to add your scanner here as well.
@ -341,14 +341,15 @@ will cause auto-detection to be skipped. Explicitly defined network scanners wil
.SH USB SUPPORT
USB scanners will be auto-detected and require no configuration.
.SH NETWORKING SUPPORT
The
The
.B sane\-pixma
backend supports network scanners using the so called Canon BJNP
and MFNP protocols.
.PP
Canon seems to be dropping support for these protocols in recent scanners.
To verify if your scanner supports one of these protocols, check the content of
the _scanner._tcp service entry in mDNS/DNS-SD (using for example avahi-discover).
the _scanner._tcp service entry in mDNS/DNS-SD (using for example
.BR avahi-discover (1)).
If that does not list port 8610
or 8612 your scanner probably does not support the mfmp or bjnp protols.
.PP
@ -356,23 +357,23 @@ Both IPv4 and IPv6 are supported, but IPv6 is as
yet untested with MFNP. Please report your results on the mailing list.
.PP
Configuration is normally not required.
The
The
.B sane\-pixma
backend will auto-detect your scanner if it is within
the same subnet as your computer if your OS does support this.
.PP
If your scanner can not be auto-detected, you can add it to the
If your scanner can not be auto-detected, you can add it to the
.B sane\-pixma
configuration file (see above).
.SH FIREWALLING FOR NETWORKED SCANNERS
The
The
.B sane\-pixma
backend communicates with port 8610 for MFNP or port 8612
for BJNP on the scanner. So
you will have to allow outgoing traffic TO port 8610 or 8612 on the
common subnet for scanning.
.PP
Scanner detection is slightly more complicated. The
Scanner detection is slightly more complicated. The
.B sane\-pixma
backend sends
a broadcast on all direct connected subnets it can find (provided your OS
@ -392,7 +393,7 @@ So in short: open the firewall for all traffic from your computer to port
AND to port 8612 (for both BJNP and MFNP) to your computer.
.PP
With the firewall rules above there is no need to add the scanner to the
.I pixma.conf
.I pixma.conf
file, unless the scanner is on a network that is not directly
connected to your computer.
.SH ENVIRONMENT
@ -448,14 +449,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and

26
doc/sane-plustek.man
Wyświetl plik

@ -184,12 +184,12 @@ Strobe XP100 LM9833 600x1200dpi 48bit 512Kb 0x0427
.SH "OTHER PLUSTEK SCANNERS"
For parallelport device support see the
.B plustek_pp
.BR sane\-plustek_pp (5)
backend.
.br
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner
and is supported by the
.B Artec
.BR sane\-artec (5)
backend.
.br
Only the National Semiconductor LM983[1/2/] based devices of Plustek
@ -210,7 +210,7 @@ UT12 P98003 u12
.fi
.ft R
For a more complete and up to date list see:
.B http://www.sane\-project.org/sane\-supported\-devices.html
.IR http://www.sane\-project.org/sane\-supported\-devices.html .
.SH "CONFIGURATION"
To use your scanner with this backend, you need at least two
@ -290,7 +290,9 @@ option cacheCalData b
.I b
0 --> do not save calibration results,
.br
1 --> save results of calibration in ~/.sane/ directory
1 --> save results of calibration in
.I ~/.sane/
directory
.RE
.PP
option altCalibration b
@ -446,18 +448,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
.I "@CONFIGDIR@"
.I "@CONFIGDIR@"
being searched (in this order).
.TP
.B SANE_DEBUG_PLUSTEK
@ -488,14 +490,16 @@ Additional info and hints can be obtained from our
.br
Mailing-List archive at:
.br
.B http://www.sane\-project.org/mailing\-lists.html
.I http://www.sane\-project.org/mailing\-lists.html
.PP
To obtain debug messages from the backend, please set the
environment-variable
.I SANE_DEBUG_PLUSTEK
before calling your favorite scan-frontend (i.e. scanimage).
.B SANE_DEBUG_PLUSTEK
before calling your favorite scan-frontend (i.e.
.BR scanimage (1)), i.e.:
.br
.B i.e.: export SANE_DEBUG_PLUSTEK=20 ; scanimage
.I export SANE_DEBUG_PLUSTEK=20 ; scanimage
.PP
The value controls the verbosity of the backend. Please note, that
values greater than 24 force the backend to output raw data files,

35
doc/sane-plustek_pp.man
Wyświetl plik

@ -11,7 +11,9 @@ provides access to Plustek ASIC 9600[1/3] and P9800[1/3] based
parallel port flatbed scanners.
The access of the scanner is either done directly by the backend
or via kernel module, called pt_drv which can be created out of
the plustek_pp backend code \- see also section
the
.B sane\-plustek_pp
backend code \- see also section
.B "BUILDING THE KERNEL MODULE"
for further information.
@ -136,7 +138,7 @@ See this file for examples.
.SH "CONFIGURATION"
.PP
This section describes the backends' configuration file entries.
This section describes the backend's configuration file entries.
The file is located at:
.I @CONFIGDIR@/plustek_pp.conf
.PP
@ -228,14 +230,15 @@ Primax 4800Direct 30bit override (works if
OP4830 has been detected)
.RE
.PP
See the
See the
.I plustek_pp.conf
file for examples.
.PP
.SH "BUILDING THE KERNEL MODULE"
As mentioned before, the plustek_pp backend code can also
be compiled and installed as linux kernel module. To do so,
As mentioned before, the
.B sane\-plustek_pp
backend code can also be compiled and installed as linux kernel module. To do so,
you will need the source-files of this sane\-backend installation.
Unpack this tar-ball and go to the directory:
.IR sane\-backends/doc/plustek .
@ -263,8 +266,9 @@ superuser.
.SH "KERNEL MODULE SETUP"
The configuration of the kernel module is done by providing
some or more options found below to the kernel module at
load time. This can be done by invoking insmod with the
appropriate parameters or appending the options to the file
load time. This can be done by invoking
.BR insmod (8)
with the appropriate parameters or appending the options to the file
.I /etc/modules.conf (kernel < 2.6.x)
or
.I /etc/modprobe.conf (kernel >= 2.6.x)
@ -376,7 +380,10 @@ the different options
options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
.RE
.PP
Remember to call depmod after changing /etc/conf.modules.
Remember to call
.BR depmod (8)
after changing
.IR /etc/conf.modules .
.PP
.SH "PARALLEL PORT MODES"
@ -432,14 +439,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
@ -469,15 +476,15 @@ Additional info and hints can be obtained from our
.br
Mailing-List archive at:
.br
.B http://www.sane\-project.org/mailing\-lists.html
.I http://www.sane\-project.org/mailing\-lists.html
.PP
To obtain debug messages from the backend, please set the
environment-variable
.B SANE_DEBUG_PLUSTEK_PP
before calling your favorite scan-frontend (i.e.
.BR xscanimage (1)).
before calling your favorite scan-frontend (i.e.
.BR xscanimage (1)), i.e.:
.br
.B i.e.: export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
.I export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
.PP
The value controls the verbosity of the backend.
.PP

19
doc/sane-pnm.man
Wyświetl plik

@ -37,21 +37,26 @@ a value of 128 requests all debug output to be printed. Smaller
levels reduce verbosity.
.SH BUGS
If the pnm backend is installed and
If the
.B sane\-pnm
backend is installed and
.BR saned (8)
is used to allow users on remote
computers to scan on the local machine, pnm files can be read by the remote
user. This is limited to the files
computers to scan on the local machine, PNM files can be read by the remote
user. This is limited to the files
.BR saned (8)
can access (usually it's running as
user "sane"). All pnm files can be read if
user "sane"). All PNM files can be read if
.BR saned (8)
runs as root which isn't
recommended anyway. The pnm backend is disabled by default. If you want to use
it, enable it with configure (see
recommended anyway. The
.B sane\-pnm
backend is disabled by default. If you want to use it, enable it with configure (see
.I configure \-\-help
for details). Be sure that
only trusted users can access the pnm backend over
only trusted users can access the
.B sane\-pnm
backend over
.BR saned (8).
.SH AUTHOR

12
doc/sane-qcam.man
Wyświetl plik

@ -64,16 +64,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_QCAM

14
doc/sane-ricoh.man
Wyświetl plik

@ -33,7 +33,7 @@ could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See
for example. See
.BR sane\-scsi (5)
for details.
@ -58,16 +58,18 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
.I @CONFIGDIR@
being searched (in this order).
.TP
.B SANE_DEBUG_RICOH

2
doc/sane-ricoh2.man
Wyświetl plik

@ -29,7 +29,7 @@ support dynamic loading).
.SH OPTIONS
The options the backend supports can either be selected through command line
options to programs like
options to programs like
.BR scanimage (1)
or through GUI elements in programs like
.BR xscanimage (1)

2
doc/sane-rts8891.man
Wyświetl plik

@ -25,7 +25,7 @@ The scanners that work with this backend are:
The options the backend supports can either be selected through
command line options to programs like
.BR scanimage (1)
or through GUI elements in
or through GUI elements in
.BR xscanimage (1)
or
.BR xsane (1).

6
doc/sane-s9036.man
Wyświetl plik

@ -26,7 +26,7 @@ could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See
for example. See
.BR sane\-scsi (5)
for details.
@ -51,14 +51,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and

40
doc/sane-sceptre.man
Wyświetl plik

@ -27,7 +27,7 @@ Sceptre VividScan S1200 SCSI
The make of this scanner is KINPO, so other scanners from that manufacturer may also work (eg. the S600).
.SH OPTIONS
The options the backend supports can either be selected through command line
options to programs like
options to programs like
.BR scanimage (1)
or through GUI elements in
.BR xscanimage (1)
@ -46,8 +46,15 @@ scanimage \-\-help \-d sceptre
.TP
.B \-\-mode Lineart|Halftone|Gray|Color
Selects the basic mode of operation of the scanner.
The Lineart and Halftone mode are black and white only (1 bit). Gray
will produce 256 levels of gray (8 bits). Color will produce a 24 bits
The
.I Lineart
and
.I Halftone
mode are black and white only (1 bit).
.I Gray
will produce 256 levels of gray (8 bits).
.I Color
will produce a 24 bits
color image. The scanner supports 30 bits internally but it only
exports 24.
@ -58,7 +65,9 @@ resolutions between 50 and 1200.
.TP
.B \-\-halftone\-pattern 1|2|3|4
Selects the pattern mode that is used in Halftone mode.
Selects the pattern mode that is used in
.I Halftone
mode.
.TP
.B \-\-gamma\-correction Default|User Defined|High Density Printing|\
@ -69,29 +78,34 @@ controls the scanner internal gamma correction.
.B \-\-custom\-gamma
Allows the user to specify a gamma table (see the
next 3 parameters).
Color mode only.
.I Color
mode only.
.TP
.B \-\-red\-gamma\-table
Can be used to download a user defined
gamma table for the red channel. The table must be 256 bytes long.
Color mode only.
.I Color
mode only.
.TP
.B \-\-green\-gamma\-table
Can be used to download a user defined
gamma table for the green channel. The table must be 256 bytes long.
Color mode only.
.I Color
mode only.
.TP
.B \-\-blue\-gamma\-table
Can be used to download a user defined gamma table
for the blue channel. The table must be 256 bytes long.
Color mode only.
.I Color
mode only.
.TP
.B \-\-threshold 0..255
Sets the threshold for black and white pixels in lineart
Sets the threshold for black and white pixels in
.I Lineart
mode. Possible values are from 0 (darker) to 255 (lighter).
.TP
@ -105,11 +119,11 @@ selected. The default is "no".
.TP
.B \-l \-t \-x \-y
control the scan area:
control the scan area:
.B -l
sets the top left x coordinate,
.B \-t
the top left y coordinate,
the top left y coordinate,
.B \-x
selects the width and
.B \-y
@ -117,9 +131,9 @@ the height of the scan area. All parameters are specified in millimeters by defa
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/sceptre.conf
supports only one item: the device name to use
supports only one item: the device name to use
.RI "(eg " /dev/scanner ).

41
doc/sane-scsi.man
Wyświetl plik

@ -46,7 +46,8 @@ is the SCSI model string,
.I TYPE
is type SCSI device type string,
.I BUS
is the SCSI bus number (named "host" in /proc/scsi/scsi),
is the SCSI bus number (named "host" in
.IR /proc/scsi/scsi ),
.I CHANNEL
is the SCSI channel number,
.I ID
@ -56,7 +57,7 @@ is the logical unit number of the scanner device. The first two fields are
strings which must be enclosed in double-quotes if they contain any
whitespace. The remaining four fields are non-negative integer numbers. The
correct values for these fields can be found by using operating system
specific tools, e.g. for Linux by looking at the output of the command
specific tools, e.g. for Linux by looking at the output of the command
.IR "cat /proc/scsi/scsi" .
To simplify configuration, a field's value can be replaced
with an asterisk symbol (``*''). An asterisk has the effect that any value is
@ -104,7 +105,7 @@ form. This is explained below in the relevant platform-specific section.
.PP
When using a SCSI scanner, ensure that the access permission for the
generic SCSI device is set appropriately. We recommend to add a group
"scanner" to
"scanner" to
.I /etc/group
which contains all users that should have
access to the scanner. The permission of the device should then be
@ -136,11 +137,11 @@ REGISTER ^sg4 PERMISSIONS root.scanner 0660
.PP
.SH FREEBSD INFO
Auto-configuration using the "scsi *" lines in the config files only works if
the user running the frontend has read/write access to
the user running the frontend has read/write access to
.IR /dev/xpt0 .
Instead, you can also set a link
.I /dev/scanner
to the appropriate
to the appropriate
.I /dev/uk
device.
.RS
@ -168,7 +169,7 @@ Works on FreeBSD 2.2.5R and 3.0 using the
driver, provided that Plug-and-Play support is disabled on the card.
If there are no
.I uk
devices, just do a
devices, just do a
.I sh MAKEDEV uk0
in the
.i /dev
@ -192,7 +193,7 @@ To keep scanning times to a minimum, it is strongly recommended to use a large
buffer size for the generic SCSI driver. From SG driver version 2.0 on, the
maximum buffer size can be changed at program run time, and there is no restriction in size. This driver version is part of the Linux kernels from
version 2.2.7 on. If the new SG driver is available some backends
(e.g.
(e.g.
.BR sane\-umax (5),
.BR sane\-mustek (5) ,
.BR sane\-sharp (5))
@ -204,7 +205,7 @@ to the desired buffer size in bytes. It is not recommended to use more
than 1 MB, because for large values the probability increases that the
SG driver cannot allocate the necessary buffer(s). For ISA cards, even
1 MB might be a too large value. For a detailed discussion of memory
issues of the SG driver, see
issues of the SG driver, see
.I http://www.torque.net/sg.
.PP
For Linux kernels before version 2.2.7 the size of the buffer is only 32KB.
@ -245,7 +246,7 @@ list isn't complete, usually any SCSI adapter supported by Linux should work.
.RS
.TP
Acard/Advance SCSI adapters
Some old versions of the kernel driver
Some old versions of the kernel driver
.RI ( atp870u.c )
cut the inquiry information.
Therefore the scanner couldn't be detected correctly. Use a current kernel.
@ -274,15 +275,15 @@ NCR/Symbios 53c400/53c400a or Domex DTC3181E/L/LE (DTCT436/436P) ISA SCSI card
This card is supplied by Mustek (and other vendors). It's supported since
Linux 2.2. The SCSI cards are supported by the module g_NCR5380. It's
necessary to tell the kernel the io port and type of card. Example for a
53c400a:
53c400a:
.I "modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1" .
Once the kernel detects the card, it should work all right.
Once the kernel detects the card, it should work all right.
However, while it should work, do not expect good performance out of this
card---it has no interrupt line and therefore while a scan is in progress,
the system becomes almost unusable. You may change the values of the USLEEP
macros in
the system becomes almost unusable. You may change the values of the USLEEP
macros in
.IR drivers/scsi/g_NCR5380.c .
Some documentation is in this file and
Some documentation is in this file and
.IR NCR5380.c .
.TP
NCR/Symbios 810
@ -294,21 +295,21 @@ both if you have trouble.
For Linux kernels before 2.0.33 it may be necessary to increase the SCSI
timeout. The default timeout for the Linux kernels before 2.0.33 is 10
seconds, which is way too low when scanning large area. If you get messages
of the form ``restart (ncr dead ?)'' in your
of the form ``restart (ncr dead ?)'' in your
.I /var/log/messages
file or on the system console, it's an indication that the timeout is too short.
In this case, find the line ``if (np->latetime>10)'' in file
In this case, find the line ``if (np->latetime>10)'' in file
.I ncr53c8xx.
(normally in directory
(normally in directory
.IR /usr/src/linux/drivers/scsi )
and change the constant 10 to, say, 60 (one minute).
and change the constant 10 to, say, 60 (one minute).
Then rebuild the kernel/module and try again.
.TP
Tekram DC315
The driver can be downloaded from
The driver can be downloaded from
.IR http://www.garloff.de/kurt/linux/dc395/ .
For some older scanners it may be necessary to disable all the more advanced
features by using e.g.
features by using e.g.
.IR "modprobe dc395x_trm dc395x_trm=7,5,1,32" .
.TP
Tekram DC390

30
doc/sane-sharp.man
Wyświetl plik

@ -62,7 +62,7 @@ for example. See sane\-scsi(5) for details.
.SH SCAN OPTIONS
.TP
.B \-\-mode
.B \-\-mode
Scan Mode. Possible settings are:
.I Lineart
(1 bit black & white scans),
@ -79,7 +79,7 @@ Scan Mode. Possible settings are:
Halftone Pattern. Available only for the JX-330 series scanners.
Possible settings:
.IR none ", " "Dither Bayer" ", " "Dither Spiral" ", " "Dither Dispersed"
and
and
.IR "Error Diffusion" .
The default value is
.IR none .
@ -109,9 +109,9 @@ Gamma. This option is only available if
.B Custom Gamma
is set to
.IR no .
Possible values are:
Possible values are:
.IR 1.0 " or " 2.2 "."
The default value is
The default value is
.IR 2.2 .
(The JX-250 and JX-350 have no built in gamma
correction; for these scanners, a gamma table is downloaded to the scanner
@ -149,8 +149,8 @@ The default value is 150.
.TP
.BR \-l ", " \-t ", " \-x ", " \-y
Scan Window.
Top-left x position of scan area
Scan Window.
Top-left x position of scan area
.RB ( \-l ),
top-left y position of scan area
.RB ( \-t ),
@ -160,13 +160,13 @@ and bottom right y position of scan area
.RB ( \-y ).
The possible settings depend on the scanner model and, for the
JX-250 and the JX-350, also on the usage of the automatic document feeder resp. the
transparency adapter. Please refer to the values allowed by
transparency adapter. Please refer to the values allowed by
.BR xscanimage (1),
or
.BR xsane (1).
With
.BR scanimage (1),
enter one of the following commands in order to see the allowed parameter values for
enter one of the following commands in order to see the allowed parameter values for
the scan window:
.RS
@ -187,10 +187,10 @@ The default value is
.TP
.B \-\-threshold
Sets the threshold for black and white pixels in lineart mode.
Sets the threshold for black and white pixels in lineart mode.
Possible values are 1..255.
The default value is 128.
This option is only available in scan mode
This option is only available in scan mode
.IR lineart .
.TP
@ -198,7 +198,7 @@ This option is only available in scan mode
Sets the threshold for the red component of a pixel in
in lineart color scan mode. Possible values are 1..255.
The default value is 128.
This option is only available in scan mode color
This option is only available in scan mode color
.IR lineart .
.TP
@ -206,7 +206,7 @@ This option is only available in scan mode color
Sets the threshold for the green component of a pixel in
in lineart color scan mode. Possible values are 1..255.
The default value is 128.
This option is only available in scan mode color
This option is only available in scan mode color
.I lineart .
.TP
@ -222,7 +222,7 @@ This option is only available in scan mode color
Sets the color of the light source. Possible values are
.IR white ,
.IR red ,
.I green
.I green
and
.IR blue .
The default value is
@ -244,7 +244,7 @@ The contents of the
.I sharp.conf
file is a list of options and device names that correspond to Sharp
scanners. Empty lines and lines beginning with a hash mark (#) are
ignored. See
ignored. See
.BR sane\-scsi (5)
for details about device names.
.PP
@ -365,7 +365,7 @@ of the data is too slow, set the environment variable
.B SANE_DEBUG_SHARP
to 1. When a scan is finished, the backend writes the line "buffer full
conditions:
.I nn"
.IR nn """
to stderr. If
.I nn
is zero, carriage stops are caused by too slow responses of the backend

8
doc/sane-sm3600.man
Wyświetl plik

@ -10,7 +10,7 @@ provides access to some Microtek scanners with the Toshiba M011 custom
USB chip. This backend should be considered alpha.
.PP
There are also backends for Microtek scanners with SCSI command set.
Refer to
Refer to
.BR sane\-microtek (5)
and
.BR sane\-microtek2 (5)
@ -84,7 +84,9 @@ export SANE_DEBUG_SM3600=5
.SH AUTHOR
.br
Marian Eichholz (eichholz@computer.org)
Marian Eichholz
.RI < eichholz@computer.org >
.br
Glenn Ramsey (glenn@componic.com)
Glenn Ramsey
.RI < glenn@componic.com >
.br

13
doc/sane-sm3840.man
Wyświetl plik

@ -10,13 +10,13 @@ provides access to some Microtek scanners with the SCAN08
USB chip.
.PP
There exist backends for Microtek scanners with SCSI command set.
Refer to
Refer to
.BR sane\-microtek (5)
and
.BR sane\-microtek2 (5)
for details.
.PP
There also exists a Microtek 3600 series driver, see
There also exists a Microtek 3600 series driver, see
.BR sane\-sm3600 (5)
for details.
.PP
@ -36,14 +36,14 @@ Microtek ScanMaker 4800 All modes OK
.PP
If you own a Microtek scanner with the SCAN08 chip other than the ones
listed above, it may or may not work with SANE. Feel free to contact the
backend author
backend author
.RI ( earle@ziplabel.com )
to report results with scanners not on the list.
.SH "FRONTEND OPTIONS"
.PP
The following options are supported by the
The following options are supported by the
.BR sane\-sm3840
driver:
.TP
@ -102,6 +102,5 @@ to 1.
.I http://www.ziplabel.com/sm3840
.SH AUTHOR
.br
Earle F. Philhower III (earle@ziplabel.com)
.br
Earle F. Philhower III
.RI < earle@ziplabel.com >

15
doc/sane-snapscan.man
Wyświetl plik

@ -31,7 +31,7 @@ symlink to such a device. Under Linux, such a device name could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See
for example. See
.BR sane\-scsi (5)
for details.
.P
@ -47,7 +47,7 @@ e.g.
firmware @DATADIR@/sane/snapscan/firmware.bin
.RE
.PP
For further details read
For further details read
.IR http://snapscan.sourceforge.net .
.SH CONFIGURATION
@ -55,7 +55,7 @@ The contents of the
.I snapscan.conf
file is a list of device names that correspond to SnapScan
scanners. Empty lines and lines starting with a hash mark (#) are
ignored. See
ignored. See
.BR sane\-scsi (5)
on details of what constitutes a valid
device name.
@ -81,14 +81,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
@ -107,9 +107,10 @@ Man page doesn't provide much information yet.
.SH "SEE ALSO"
.BR sane (7),
.BR sane\-scsi (5)
.BR sane\-scsi (5),
.br
IR http://sourceforge.net/projects/snapscan/ "(new development website)"
.I http://sourceforge.net/projects/snapscan/
(new development website)
.SH AUTHOR
Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot,

6
doc/sane-sp15c.man
Wyświetl plik

@ -35,7 +35,7 @@ and to contact the author with test results.
.SH CONFIGURATION
A modest effort has been made to expose the standard options to the API.
This allows frontends such as
This allows frontends such as
.BR xscanimage (1)
to set scanning region,
resolution, bit-depth (and color), and enable the automatic document feeder.
@ -54,7 +54,7 @@ Fujitsu M3096GX/M3093GX/M3093DG OEM Manual, part number C150-E015...03
.SH AUTHOR
Randolph Bentson
.IR <bentson@holmsjoen.com> ,
.RI < bentson@holmsjoen.com >,
with credit to the unnamed author of the coolscan driver
.SH LIMITATIONS
@ -69,7 +69,7 @@ but I haven't seen them yet.
.br
Both scanners claim to have separate control
of resolution in X and Y directions. I confess I haven't tested this yet.
I have found that
I have found that
.BR xsane (1)
doesn't even display this capability.
.br

20
doc/sane-st400.man
Wyświetl plik

@ -23,7 +23,7 @@ and ST600. If you own one of these scanners, or a scanner other than the
ones listed above that works with this backend, please let us know by sending
the scanner's model name, SCSI ID, and firmware revision to
.IR sane\-devel@alioth-lists.debian.net .
Have a look at
Have a look at
.I http://www.sane\-project.org/mailing\-lists.html
concerning subscription to sane\-devel.
@ -43,7 +43,7 @@ a device name could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See
for example. See
.BR sane\-scsi (5)
for details.
@ -70,7 +70,9 @@ scsi SIEMENS "ST 400" Scanner * * 3 0
.RE
.PP
In this configuration, the driver can only access the ST400 model
at SCSI ID 3 LUN 0 (see section "BUGS" below for the reason).
at SCSI ID 3 LUN 0 (see section
.B BUGS
below for the reason).
To use the driver with other scanner models, add an appropriate line to
the configuration file. For example, to use it with an ST800 at SCSI
ID 3 LUN 0, add the line:
@ -100,14 +102,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and
@ -129,7 +131,7 @@ a ST400. It will happily accept everything that matches the configuration
entries. This makes it easy to test the backend with other scanners:
Just add an appropriate line to the configuration file. The configuration
file as distributed (see above) only works with the ST400. Be careful:
If there is no config file at all, the backend defaults to
If there is no config file at all, the backend defaults to
.IR /dev/scanner .
.PP
The ST400 answers on all eight SCSI LUNs. Normally this is not a problem,
@ -141,7 +143,7 @@ LUN 0 only.
.SH DEBUG
If you encounter a bug please set the environment variable
.B SANE_DEBUG_ST400
to 128 and try to regenerate the problem. Then send me a report with the
to 128 and try to regenerate the problem. Then send me a report with the
log attached.
.PP
If you encounter a SCSI bus error or trimmed and/or displaced images please
@ -156,5 +158,5 @@ to 128 before sending me the report.
.I http://www.informatik.uni-oldenburg.de/~ingo/sane/
.SH AUTHOR
Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
Ingo Wilken
.RI < Ingo.Wilken@informatik.uni-oldenburg.de >

13
doc/sane-stv680.man
Wyświetl plik

@ -32,18 +32,20 @@ for the exact status of each camera.
For startup of this backend check that if present the stv680 kernel module is
removed or disabled.
.br
Also before using, enable the backend by editing the
Also before using, enable the backend by editing the
.I @CONFIGDIR@/dll.conf
file, change #stv680 to stv680.
For problems with the untested cameras, you should contact the author for that.
The options the backend supports can either be selected through
command line options to programs like
command line options to programs like
.BR scanimage (1)
or through GUI elements in
or through GUI elements in
.BR xcam (1).
For both programs use the \-B option needed for size buffer.
For both programs use the
.B \-B
option needed for size buffer.
Some frontends examples:
@ -121,7 +123,7 @@ considered "white", when scanning some sheets by changing the calibration
value loaded into the scanner. Scale \-32 .. 0 .. +32 in steps of 1.
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/stv680.conf
supports only one item: the device name to use (eg usb 0x.... 0x....).
@ -176,4 +178,3 @@ pencam2 program
.br
.BR libghoto2 (3)
program (camlib stv0680)

6
doc/sane-tamarack.man
Wyświetl plik

@ -35,7 +35,7 @@ could be
.I /dev/sga
or
.IR /dev/sge ,
for example. See
for example. See
.BR sane\-scsi (5)
for details.
@ -60,14 +60,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR "tmp/config" ,
.IR "." ,
and

16
doc/sane-teco1.man
Wyświetl plik

@ -47,14 +47,16 @@ Note that the untested scanner will not be directly supported. You
should contact the author for that.
The TECO VM number can usually be found at the back of the scanner. It
is also part of the FCC ID.
is also part of the FCC ID.
.I sane\-find\-scanner \-v
will also show the
SCSI inquiry, and if it is a TECO scanner, the name will be there too.
The options the backend supports can either be selected through
command line options to programs like scanimage or through GUI
elements in
command line options to programs like
.BR scanimage (1)
or through GUI
elements in
.BR xscanimage (1)
or
.BR xsane (1).
@ -76,7 +78,7 @@ scanimage \-\-help \-d teco1
.TP
.B \-\-mode Black & White|Grayscale|Color
Selects the basic mode of operation of the scanner valid choices are
The
The
.I Black & White
mode is black and white only (1 bit).
.I Grayscale
@ -95,7 +97,7 @@ between 1 and 600, in increments of 1.
.TP
.B \-l \-t \-x \-y
Controls the scan area:
Controls the scan area:
.B \-l
sets the top left x coordinate,
.B \-t
@ -142,9 +144,9 @@ selected. The default is "no".
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/teco1.conf
supports only one item: the device name to use (eg
supports only one item: the device name to use (eg
.IR /dev/scanner ).

22
doc/sane-teco2.man
Wyświetl plik

@ -48,8 +48,10 @@ The TECO VM number can usually be found at the back of the
scanner. It is also part of the FCC ID.
The options the backend supports can either be selected through
command line options to programs like scanimage or through GUI
elements in
command line options to programs like
.BR scanimage (1)
or through GUI
elements in
.BR xscanimage (1),
.BR xsane (1),
.BR quiteinsane (1)
@ -74,7 +76,7 @@ scanimage \-\-help \-d teco2
.TP
.B \-\-mode Lineart|Gray|Color
selects the basic mode of operation of the scanner.
The
The
.I Lineart
mode is black and white only (1 bit).
.I Gray
@ -85,9 +87,9 @@ will produce a 24 bits color image.
.TP
.B \-\-resolution 1..600
Selects the resolution for a scan. The scanner can do all resolutions
between 1 and 600, in increments of 1, for
between 1 and 600, in increments of 1, for
.IR Lineart " and " Gray .
For
For
.IR Color ,
a restricted set of resolutions are available.
@ -95,7 +97,9 @@ a restricted set of resolutions are available.
All values with ydpi > 300 (300 x 600) or 600 (600 x 1200) result in
a wrong proportion for the scan. The proportion can be adjusted with
the following imagemagick command:
convert \-geometry (dpi/max_xdpi * 100%)x100%
.br
.I convert \-geometry (dpi/max_xdpi * 100%)x100%
.br
max_xdpi is for the vm3575 constant with 300 dpi
e.g. 600dpi adjust with: convert \-geometry 200%x100%
@ -110,7 +114,7 @@ The scan mode is user selected. The default is "no".
.TP
.B \-l, \-t, \-x, " \-y
Control the scan area:
Control the scan area:
.B \-l
sets the top left x coordinate,
.B \-t
@ -130,7 +134,7 @@ the height of the scan area. All parameters are specified in millimeters by defa
next 3 parameters).
.SH OPTIONS FOR COLOR MODE
These options are valid for scan mode
These options are valid for scan mode
.I Color
only.
@ -171,7 +175,7 @@ value loaded into the scanner. Scale 0..64 in steps of 1.
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/teco2.conf
supports only one item: the device name to use (eg
.IR /dev/scanner ).

18
doc/sane-teco3.man
Wyświetl plik

@ -34,11 +34,11 @@ The TECO VM number can usually be found at the back of the
scanner. It is also part of the FCC ID.
The options the backend supports can either be selected through
command line options to programs like
.BR scanimage (1)
command line options to programs like
.BR scanimage (1)
or through GUI
elements in
.BR xscanimage (1)
elements in
.BR xscanimage (1)
or
.BR xsane (1).
@ -60,7 +60,7 @@ scanimage \-\-help \-d teco3
.TP
.B \-\-mode Black & White|Grayscale|Color
Selects the basic mode of operation of the scanner.
The
The
.I Black & White
mode is black and white only (1 bit).
.I Grayscale
@ -84,7 +84,7 @@ selected. The default is "no".
.TP
.B \-l \-t \-x \-y
Control the scan area:
Control the scan area:
.B \-l
sets the top left x coordinate,
.B \-t
@ -92,7 +92,7 @@ the top left y coordinate,
.B \-x
selects the width and
.B \-y
the height of the scan area.
the height of the scan area.
All parameters are specified in millimeters by default.
.SH OPTIONS FOR COLOR MODE ONLY
@ -119,7 +119,7 @@ for the blue channel. The table must be 1024 bytes long.
.SH CONFIGURATION FILE
The configuration file
The configuration file
.I @CONFIGDIR@/teco3.conf
supports only one item: the device name to use (eg
.IR /dev/scanner ).
@ -158,7 +158,7 @@ Not much.
.BR sane\-scsi (5),
.BR scanimage (1),
.BR xscanimage (1),
.BR xsane (1),
.BR xsane (1),
.BR sane (7)

31
doc/sane-test.man
Wyświetl plik

@ -17,7 +17,7 @@ capabilities of SANE. Therefore
implements functions and options that are not (or seldom) found in other
backends.
.PP
The backend is commented out in
The backend is commented out in
.IR @CONFIGDIR@/dll.conf ,
so either the comment
character must be removed or the backend must be called explicitly. E.g.
@ -78,7 +78,8 @@ and "Solid black" are quite obvious, the other options need some more
explanation. Color patterns are used to determine if all modes and their
colors are represented correctly by the frontend. The grid should look like the
same in every mode and resolution. A table of all the test pictures can be
found at: http://www.meier\-geinitz.de/sane/test\-backend/test\-pictures.html.
found at:
.IR http://www.meier\-geinitz.de/sane/test\-backend/test\-pictures.html .
.PP
If option
.B invert\-endianness
@ -88,8 +89,9 @@ frontend uses the correct endianness.
.PP
If option
.B read\-limit
is set, the maximum amount of data transferred with each call to sane_read() is
limited.
is set, the maximum amount of data transferred with each call to
.BR sane_read ()
is limited.
.PP
Option
.B read\-limit\-size
@ -110,8 +112,9 @@ used over the network.
If option
.B read\-return\-value
is different from "Default", the selected status will be returned by every
call to sane_read(). This is useful to test the frontend's handling of the
SANE statuses.
call to
.BR sane_read ().
This is useful to test the frontend's handling of the SANE statuses.
.PP
If option
.B ppl\-loss
@ -126,13 +129,15 @@ parameters it got before the start of the scan (which it shouldn't).
.PP
Option
.B non\-blocking
determines if non-blocking IO for sane_read() should be used if supported by
the frontend.
determines if non-blocking IO for
.BR sane_read ()
should be used if supported by the frontend.
.PP
If option
.B select\-fd
is set, the backend offers a select filedescriptor for detecting if
sane_read() will return data.
.BR sane_read()
will return data.
.PP
If option
.B enable\-test\-options
@ -302,14 +307,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
@ -333,8 +338,8 @@ export SANE_DEBUG_TEST=4
.SH AUTHOR
Henning Meier-Geinitz
.I <henning@meier\-geinitz.de>
Henning Meier-Geinitz
.RI < henning@meier\-geinitz.de >
.SH BUGS
\- config file values aren't tested for correctness

15
doc/sane-u12.man
Wyświetl plik

@ -92,7 +92,7 @@ lamps off, 0 --> do not change lamp status
.RE
.PP
See the
See the
.I u12.conf
file for examples.
.PP
@ -130,14 +130,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
@ -171,16 +171,17 @@ Additional info and hints can be obtained from our
.br
Mailing-List archive at:
.br
.B http://www.sane\-project.org/mailing\-lists.html
.I http://www.sane\-project.org/mailing\-lists.html
.PP
To obtain debug messages from the backend, please set the
environment-variable
.B SANE_DEBUG_U12
before calling your favorite scan-frontend (i.e.
.BR xscanimage (1)).
before calling your favorite scan-frontend (i.e.
.BR xscanimage (1)),
i.e.:
.br
.B i.e.: export SANE_DEBUG_U12=20 ; xscanimage
.I export SANE_DEBUG_U12=20 ; xscanimage
.PP
The value controls the verbosity of the backend.

25
doc/sane-umax.man
Wyświetl plik

@ -6,8 +6,12 @@ sane\-umax \- SANE backend for UMAX scanners
.SH ABOUT THIS FILE
This file only is a short description of the umax-backend for sane! For detailed information take a look at
sane\-umax\-doc.html (it is included in the sane source directory and in the xsane online help)!
This file only is a short description of the
.B sane\-umax
backend for sane! For detailed information take a look at
sane\-umax\-doc.html (it is included in the sane source directory and in the
.BR xsane (1)
online help)!
.SH DESCRIPTION
@ -80,7 +84,7 @@ able to send gamma tables to the scanner or to
do a correct color calibration. This may result in
strange color effects. If the minimum value is set
too large then the backend is not able to allocate
the requested scsi buffer size and aborts with
the requested SCSI buffer size and aborts with
out of memory error. The default is 32KB, for
some scanners it should be increased to 64KB.
.TP
@ -186,15 +190,16 @@ values:
.br
default = 2
.br
most scsi drivers allow internal command queueing with a depth
most SCSI drivers allow internal command queueing with a depth
of 2 commands. In most cases it does not mprove anything when you
increase this value. When your scsi driver does not support any
increase this value. When your SCSI driver does not support any
command queueing you can try to set this value to 1.
.PP
The special device name must be a generic SCSI device or a symlink to such a device.
To find out to which device your scanner is assigned and how you have to set the
permissions of that device, have a look at sane\-scsi.
permissions of that device, have a look at
.BR sane\-scsi (5).
.SH SCSI ADAPTER TIPS
@ -205,15 +210,15 @@ SCSI-adapters are not supported. So you typically need to purchase another SCSI-
that is supported by your platform. See the relevant hardware FAQs and HOWTOs for your
platform for more information.
The UMAX-scanners do block the scsi-bus for a few seconds while scanning. It is not
The UMAX-scanners do block the SCSI-bus for a few seconds while scanning. It is not
necessary to connect the scanner to its own SCSI-adapter. But if you need short
response time for your SCSI-harddisk (e.g. if your computer is a file-server) or
other scsi devices, I suggest you use an own SCSI-adapter for your UMAX-scanner.
other SCSI devices, I suggest you use an own SCSI-adapter for your UMAX-scanner.
If you have any problems with your Umax scanner, check your scsi chain
If you have any problems with your Umax scanner, check your SCSI chain
(cable length, termination, ...).
See also:
See also:
.BR sane\-scsi (5)
.SH FILES

12
doc/sane-umax1220u.man
Wyświetl plik

@ -37,7 +37,7 @@ configuration file is shown below:
/dev/usb/scanner0
.fi
See
See
.BR sane\-usb (5)
for information on how to set the access permissions on the usb device files.
@ -90,7 +90,7 @@ export SANE_DEBUG_UMAX1220U=10
If you keep getting I/O errors, try cycling the power on your scanner to reset it.
There is no way to cancel a scan, since the driver ignores
There is no way to cancel a scan, since the driver ignores
.BR sane_cancel ().
If you try scanning an image which is too small, you will get I/O errors. Be
@ -106,17 +106,15 @@ area is zero.
.I http://umax1220u\-sane.sourceforge.net/
.SH AUTHOR
Marcio Luis Teixeira
.I <marciot@users.sourceforge.net>
Marcio Luis Teixeira
.RI < marciot@users.sourceforge.net >
.SH EMAIL-CONTACT
.I sane\-devel@alioth-lists.debian.net
.SH REPORTING BUGS
This backend isn't actively maintained. Nevertheless, bug reports and comments
should be sent to the sane\-devel mailing list. When reporting bugs, please run
the backend with
the backend with
.B SANE_DEBUG_UMAX1220U
set to 10 and attach a copy of the log messages.

28
doc/sane-umax_pp.man
Wyświetl plik

@ -55,12 +55,12 @@ if you have a kernel with ppdev support.
.PP
Note that if you don't use the ppdev character device, the backend
needs to run as root. To allow user access to the scanner
run the backend through the network interface (See
run the backend through the network interface (See
.BR saned (8)
and
.BR sane\-net (5)).
A more relaxed solution (security wise) is to add suid bit to the frontend
(See
(See
.BR chmod (1)).
The backend drop root privileges as soon as it can, right after gaining direct
access to IO ports, which lessen risks when being root.
@ -89,14 +89,14 @@ hardware access
.I /dev/ppi0
uses *BSD ppi device, depending on the
number of available parallel port, you
have to use
have to use
.IR /dev/ppi1 ,
.IR /dev/ppi2 ", ..."
.TP
.I /dev/parport0
uses Linux ppdev device, depending on the
number of available parallel port, you
have to use
have to use
.IR /dev/parport1 ,
.IR /dev/parport2 ", ..."
.TP
@ -111,7 +111,7 @@ OS/2
\fBNOTE:\fR in all cases, you must have sufficient privileges
to get access to the chosen device or address. Depending on the
security settings, devices may not be available for all users.
You have to change permissions on the
You have to change permissions on the
.I /dev/ppi*
or
.I /dev/parport*
@ -131,7 +131,7 @@ You can rename any device using the
options. These options apply to the last port option.
.SH "CONFIGURATION"
Please make sure to edit
Please make sure to edit
.I umax_pp.conf
.B before
you use the backend.
@ -221,14 +221,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
@ -293,7 +293,7 @@ For latest bug fixes and information see
.SH "AUTHOR"
St\['e]phane Voltz
.I <stef.dev@free.fr>
.RI < stef.dev@free.fr >
.SH "CREDITS"
Support for the 610P has been made possible thank to an hardware donation
@ -305,22 +305,22 @@ your scanner to be able to help you...
.TP
.I SANE version
Run
Run
.I "scanimage \-V"
to determine this
.TP
.I the backend version and your scanner hardware
Run
Run
.I "SANE_DEBUG_UMAX_PP=255 scanimage \-L 2>log"
as root. If you don't get any output
from the
from the
.B sane\-umax_pp
backend, make sure a line "umax_pp" is included into your
backend, make sure a line "umax_pp" is included into your
.I @CONFIGDIR@/dll.conf
file.
If your scanner isn't detected, make sure you've defined the right port address, or the
correct device
in your
in your
.I umax_pp.conf
file.
.TP

61
doc/sane-usb.man
Wyświetl plik

@ -8,18 +8,17 @@ interface. It focuses on two main topics: getting the scanner detected by the
operating system kernel and using it with SANE.
.PP
This page applies to USB most backends and scanners, as they use the generic
sanei_usb interface. However, there is one exceptions: USB Scanners
supported by the microtek2 backend need a special USB kernel
driver, see
sanei_usb interface. However, there is one exception: USB Scanners
supported by the
.BR sane\-microtek2 (5)
for details.
backend need a special USB kernel driver.
.SH "QUICK START"
This is a short HOWTO-like section. For the full details, read the following
sections. The goal of this section is to get the scanner detected by
.BR sane\-find\-scanner (1).
.PP
Run
Run
.BR sane\-find\-scanner (1).
If it lists your scanner with the correct vendor and
product ids, you are done. See section
@ -27,7 +26,7 @@ product ids, you are done. See section
for details on how to go on.
.PP
.BR sane\-find\-scanner (1)
doesn't list your scanner? Does it work as root? If yes, there is a permission issue.
doesn't list your scanner? Does it work as root? If yes, there is a permission issue.
See the
.B LIBUSB
section for details.
@ -64,17 +63,35 @@ none /proc/bus/usb usbfs defaults 0 0
The permissions for the device files used by libusb must be adjusted for user
access. Otherwise only root can use SANE devices. For
.IR Linux ,
the devices are located in /proc/bus/usb/ or in /dev/bus/usb, if you use
the devices are located in
.I /proc/bus/usb/
or in
.IR /dev/bus/usb ,
if you use
udev. There are directories named e.g. "001" (the bus name) containing files
"001", "002" etc. (the device files). The right device files can be found out by
running scanimage \-L as root. Setting permissions with "chmod" is not permanent,
however. They will be reset after reboot or replugging the scanner.
running:
.I "scanimage \-L:
as root. Setting permissions with
.BR chmod (1)
is not permanent, however. They will be reset after reboot or replugging the scanner.
.PP
Usually udev or for older distributions the hotplug utilities are used, which
Usually
.BR udev (7)
or for older distributions the hotplug utilities are used, which
support dynamic setting of access permissions. SANE comes with udev and hotplug
scripts in the directory tools/udev and tools/hotplug. They can be used for
setting permissions, see @DOCDIR@/README.linux, tools/README and the README in
the tools/hotplug directory for more details.
scripts in the directory
.I tools/udev
and
.IR tools/hotplug .
They can be used for setting permissions, see
.IR @DOCDIR@/README.linux ,
.IR tools/README
and the
.I README
in the
.I tools/hotplug
directory for more details.
.PP
For the
.BR BSDs ,
@ -84,9 +101,9 @@ Use chmod to apply appropriate permissions.
.SH "SANE ISSUES"
.PP
This section assumes that your scanner is detected by
This section assumes that your scanner is detected by
.BR sane\-find\-scanner (1).
It doesn't make sense to go on, if this is not the case. While
It doesn't make sense to go on, if this is not the case. While
.BR sane\-find\-scanner (1)
is able to detect any USB scanner, actual scanning will only work if the
scanner is supported by a SANE backend. Information on the level of support
@ -109,11 +126,11 @@ is the USB vendor id, and
.I PRODUCT
is the USB product id of the scanner. Both ids are non-negative integer numbers
in decimal or hexadecimal format. The correct values for these fields can be
found by running
found by running
.BR sane\-find\-scanner (1),
looking into the syslog (e.g.,
.IR /var/log/messages )
or under Linux by issuing the command
or under Linux by issuing the command
.IR "cat /proc/bus/usb/devices" .
This is an example of a config file line:
.PP
@ -146,16 +163,16 @@ If the library was compiled with debug support enabled, this
environment variable controls the debug level for the USB I/O
subsystem. E.g., a value of 128 requests all debug output to be
printed. Smaller levels reduce verbosity. Values greater than 4 enable
libusb debugging (if available). Example:
libusb debugging (if available). Example:
.IR "export SANE_DEBUG_SANEI_USB=4" .
.PP
.TP
.B SANE_USB_WORKAROUND
If your scanner does not work when plugged into a USB3 port, try
setting the environment variable
setting the environment variable
.B SANE_USB_WORKAROUND
to 1. This may work around issues which happen with particular kernel
versions. Example:
versions. Example:
.I export SANE_USB_WORKAROUND=1.
.SH "SEE ALSO"
@ -165,5 +182,5 @@ versions. Example:
.BR sane\-scsi (5)
.SH AUTHOR
Henning Meier-Geinitz
.I <henning@meier\-geinitz.de>
Henning Meier-Geinitz
.RI < henning@meier\-geinitz.de >

5
doc/sane-v4l.man
Wyświetl plik

@ -63,14 +63,14 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
@ -98,4 +98,3 @@ for details.
.SH SEE ALSO
.BR sane (7),
.BR xcam (1)

15
doc/sane-xerox_mfp.man
Wyświetl plik

@ -23,7 +23,7 @@ For SCX\-4500W in network mode you need to specify
.PP
The
.B host_address
is passed through resolver, thus can be a dotted quad or a name from
is passed through resolver, thus can be a dotted quad or a name from
.I /etc/hosts
or resolvable through DNS.
.SH FILES
@ -54,24 +54,23 @@ Multicast autoconfiguration for LAN scanners is not implemented yet. IPv6 addres
.SH BUGS AND SUPPORT
If you have found a bug or need support please follow open\-source way of acquiring support via
mail\-lists
mail\-lists
.I http://www.sane\-project.org/mailing\-lists.html
or SANE bug tracker
.IR http://www.sane\-project.org/bugs.html .
.SH AUTHORS
Alex Belkin
.IR <abc@telekom.ru> .
.RI < abc@telekom.ru >.
.br
Samsung SCX\-4500W scan over network support by
Alexander Kuznetsov
.IR <acca(at)cpan.org> .
Alexander Kuznetsov
.RI < acca(at)cpan.org >.
.br
Color scanning on Samsung M2870 model and Xerox Cognac 3215 & 3225 models by
Laxmeesh Onkar Markod
.IR <m.laxmeesh@samsung.com> .
Laxmeesh Onkar Markod
.RI < m.laxmeesh@samsung.com >.
.SH "SEE ALSO"
.BR sane (7),
.BR sane\-usb (5)

6
doc/sane.man
Wyświetl plik

@ -255,6 +255,11 @@ Supports Epson SCSI, parallel port and USB flatbed scanners. See
.BR sane\-epson (5)
for details.
.TP
.B escl
Supports scanners through the eSCL protocol. See
.BR sane\-escl (5)
for details.
.TP
.B fujitsu
Supports most Fujitsu SCSI and USB, flatbed and adf scanners. See
.BR sane\-fujitsu (5)
@ -861,6 +866,7 @@ for details).
.BR sane\-dll (5),
.BR sane\-dmc (5),
.BR sane\-epson (5),
.BR sane\-escl (5),
.BR sane\-fujitsu (5),
.BR sane\-genesys (5),
.BR sane\-gphoto2 (5),

137
doc/saned.man
Wyświetl plik

@ -34,7 +34,7 @@ flag requests that
run in standalone daemon mode. In this mode,
.B saned
will listen for incoming client connections;
.B inetd
.BR inetd (8)
is not required for
.B saned
operations in this mode. The
@ -91,8 +91,12 @@ flag displays a short help message.
.PP
If
.B saned
is run from other programs such as inetd, xinetd and systemd, check that
program's documentation on how to pass command-line options.
is run from other programs such as
.BR inetd (8),
.BR xinetd (8)
and
.BR systemd (1),
check that program's documentation on how to pass command-line options.
.SH CONFIGURATION
First and foremost:
.B saned
@ -116,13 +120,16 @@ list.
\fBdata_portrange\fP = \fImin_port\fP - \fImax_port\fP
Specify the port range to use for the data connection. Pick a port
range between 1024 and 65535; don't pick a too large port range, as it
may have performance issues. Use this option if your \fBsaned\fP
may have performance issues. Use this option if your
.B saned
server is sitting behind a firewall. If that firewall is a Linux
machine, we strongly recommend using the Netfilter
\fInf_conntrack_sane\fP module instead.
.TP
\fBdata_connect_timeout\fP = \fItimeout\fP
Specify the time in milliseconds that saned will wait for a data
Specify the time in milliseconds that
.B saned
will wait for a data
connection. Without this option, if the data connection is not done
before the scanner reaches the end of scan, the scanner will continue
to scan past the end and may damage it depending on the
@ -167,16 +174,29 @@ For
.B saned
to work properly in its default mode of operation, it is also necessary to
add the appropriate configuration for
.I (x)inetd or systemd.
.BR xinetd (8),
.BR inetd (8)
or
.BR systemd (1)
(see below).
Note that your inetd must support IPv6 if you
want to connect to saned over IPv6 ; xinetd, openbsd-inetd and systemd
are known to support IPv6, check the documentation for your inetd daemon.
Note that your
.BR inetd (8)
must support IPv6 if you want to connect to
.B saned
over IPv6;
.BR xinetd (8),
.BR openbsd-inetd (8)
and
.BR systemd (1)
are known to support IPv6, check the documentation for your
.BR inetd (8)
daemon.
.PP
In the sections below the configuration for
.I inetd, xinetd
.BR inetd (8),
.BR xinetd (8)
and
.I systemd
.BR systemd (1)
are described in more detail.
.PP
For the configurations below it is necessary to add a line of the following
@ -189,8 +209,11 @@ sane\-port 6566/tcp # SANE network scanner daemon
.PP
The official IANA short name for port 6566 is "sane\-port". The older name
"sane" is now deprecated.
.SH INETD CONFIGURATION
It is required to add a single line to the inetd configuration file
It is required to add a single line to the
.BR inetd (8)
configuration file
.IR (/etc/inetd.conf)
.
.PP
@ -202,7 +225,8 @@ sane\-port stream tcp nowait saned.saned @SBINDIR@/saned saned
.PP
However, if your system uses
.BR tcpd (8)
for additional security screening, you may want to disable saned
for additional security screening, you may want to disable
.B saned
access control by putting ``+'' in
.IR saned.conf
and use a line of the following form in
@ -222,9 +246,13 @@ access permissions on the special device are set such that
.B saned
can access the scanner (the program generally needs read and
write access to scanner devices).
.SH XINETD CONFIGURATION
If xinetd is installed on your system instead of inetd the following example
for
If
.BR xinetd (8)
is installed on your system instead of
.BR inetd (8)
the following example for
.I /etc/xinetd.conf
may be helpful:
.PP
@ -247,20 +275,34 @@ service sane\-port
.fi
.ft R
.RE
.SH SYSTEMD CONFIGURATION
Saned can be compiled with explicit systemd support. This
.B saned
can be compiled with explicit
.BR systemd (1) support. This
will allow logging debugging information to be forwarded
to the systemd journal. The systemd support
requires compilation with the systemd-devel package
to the
.BR systemd (1)
journal. The
.BR systemd (1)
support requires compilation with the systemd-devel package
installed on the system. this is the preferred option.
Saned can be used with systemd without the systemd integration
compiled in, but then logging of debug information is not supported.
.B saned
can be used with
.BR systemd (1)
without the
.BR systemd (1)
integration compiled in, but then logging of debug information is not supported.
The
.BR systemd (1)
configuration is different for the 2 options, so both are described below.
The systemd configuration is different for the 2 options, so
both are described below.
.SH Systemd configuration for saned with systemd support compiled in
for the systemd configuration we need to add 2 configuration files in
For
.BR systemd (1)
configuration we need to add 2 configuration files in
.I /etc/systemd/system.
.PP
The first file we need to add here is called
@ -316,15 +358,20 @@ Also=saned.socket
.PP
You need to set an environment variable for
.B SANE_CONFIG_DIR
pointing to the directory where saned can find its configuration files.
pointing to the directory where
.B saned
can find its configuration files.
you will have to remove the # on the last line and set the variables
for the desired debugging information if required. Multiple variables
can be set by separating the assignments by spaces as shown in the
example above.
.PP
Unlike
.I (x)inetd
, systemd allows debugging output from backends set using
.BR xinetd (8)
and
.BR inetd (8),
.BR systemd (1)
allows debugging output from backends set using
.B SANE_DEBUG_XXX
to be captured. See the man-page for your backend to see what options
are supported.
@ -332,15 +379,24 @@ With the service unit as described above, the debugging output is
forwarded to the system log.
.SH Systemd configuration when saned is compiled without systemd support
This configuration will also work when Saned is compiled WITH systemd integration
support, but it does not allow debugging information to be logged.
This configuration will also work when
.B saned
is compiled WITH
.BR systemd (1) integration support, but it does not allow debugging
information to be logged.
.PP
for systemd configuration for saned, we need to add 2 configuration files in
For
.BR systemd (1)
configuration for
.BR saned ,
we need to add 2 configuration files in
.I /etc/systemd/system.
.PP
The first file we need to add here is called
.I saned.socket.
It is identical to the version for systemd with the support compiled in.
It is identical to the version for
.BR systemd (1)
with the support compiled in.
It shall have the following contents:
.PP
.RS
@ -362,7 +418,9 @@ WantedBy=sockets.target
.PP
The second file to be added is
.I saned@.service
This one differs from the version with systemd integration compiled in:
This one differs from the version with
.BR systemd (1)
integration compiled in:
.PP
.RS
.ft CR
@ -415,13 +473,19 @@ contain the configuration file. Under UNIX, the directories are
separated by a colon (`:'), under OS/2, they are separated by a
semi-colon (`;'). If this variable is not set, the configuration file
is searched in two default directories: first, the current working
directory (".") and then in @CONFIGDIR@. If the value of the
directory (".") and then in
.IR @CONFIGDIR@ .
If the value of the
environment variable ends with the directory separator character, then
the default directories are searched after the explicitly specified
directories. For example, setting
.B SANE_CONFIG_DIR
to "/tmp/config:" would result in directories "tmp/config", ".", and
"@CONFIGDIR@" being searched (in this order).
to "/tmp/config:" would result in directories
.IR tmp/config ,
.IR . ,
and
.I "@CONFIGDIR@"
being searched (in this order).
.SH "SEE ALSO"
.BR sane (7),
@ -430,7 +494,10 @@ to "/tmp/config:" would result in directories "tmp/config", ".", and
.BR xcam (1),
.BR sane\-dll (5),
.BR sane\-net (5),
.BR sane\-"backendname" (5)
.BR sane\-"backendname" (5),
.BR inetd (8),
.BR xinetd (8),
.BR systemd (1),
.br
.I http://www.penguin-breeder.org/?page=sane\-net
.SH AUTHOR

18
doc/scanimage.man
Wyświetl plik

@ -77,7 +77,7 @@ To print all available options:
.SH OPTIONS
Parameters are separated by a blank from single-character options (e.g.
.BR "\-d epson" )
and by a "=" from multi-character options (e.g.
and by a "=" from multi-character options (e.g.
.BR \-\-device\-name=epson ).
.PP
@ -103,7 +103,7 @@ The
.B \-\-format
.I format
option selects how image data is written to standard output or the file specified by
the
the
.B \-\-output\-file
option.
.I format
@ -171,21 +171,21 @@ feeders.
is used to specify the format of the filename that each page will be written
to. Each page is written out to a single file. If
.I format
is not specified, the default of
is not specified, the default of
.I out%d.pnm
(or
.I out%d.tif
for
for
.BR "\-\-format tiff" ,
.I out%d.png
for
.B "\-\-format png"
or
.I out%d.jpg
for
for
.BR "\-\-format jpeg" )
will be used.
This option is incompatible with the
This option is incompatible with the
.B \-\-output\-path
option.
.I format
@ -240,7 +240,7 @@ or
option requests that
.B scanimage
saves the scanning output to the given path. This option is incompatible with the
\-\-batch option. The program will try to guess
\-\-batch option. The program will try to guess
.B \-\-format
from the file name. If that is not possible, it will print an error message and exit.
.PP
@ -312,7 +312,7 @@ distribution that it came with and the version of the backend that it
loads. Usually that's the dll backend. If more information about the version
numbers of the backends are necessary, the
.B DEBUG
variable for the dll backend can be used. Example:
variable for the dll backend can be used. Example:
.I "SANE_DEBUG_DLL=3 scanimage \-L" .
.PP
As you might imagine, much of the power of
@ -491,7 +491,7 @@ user:password:resource
.B scanimage
uses this information to answer user authorization requests
automatically. The file must have 0600 permissions or stricter. You should
use this file in conjunction with the
use this file in conjunction with the
.B \-\-accept\-md5\-only
option to avoid
server-side attacks. The resource may contain any character but is limited