diff --git a/man/gamma4scanimage.1.html b/man/gamma4scanimage.1.html
index 54c16941..4cd69f08 100644
--- a/man/gamma4scanimage.1.html
+++ b/man/gamma4scanimage.1.html
@@ -2,7 +2,7 @@
gamma4scanimage.1
-
+
gamma4scanimage.1
@@ -27,39 +27,39 @@
You also can specify the size (maxin) and maximum output value (maxout)
of the gamma table.
- gamma is a floating point value, neutral value is 1.0, if the value is
- larger than 1.0 then the image gets brighter.
+ gamma is a floating point value, neutral value being 1.0. If the value
+ is larger than 1.0 then the image is brighter.
shadow defines the minimum input value that is necessary to create an
output value larger than zero. shadow has to be in the range
- [0..maxin]. Its default value is 0.
+ [0..maxin]. Its default value is 0.
highlight defines the maximum input value that produces an output value
- smaller than maxout. highlight has to be in the range [0..maxin],
- highlight has to be larger than shadow. Its default value is the same
- as maxin (16383 if not set).
+ smaller than maxout. highlight must be in the range [0..maxin] and
+ larger than shadow. Its default value is the same as maxin (16383 if
+ not set).
maxin defines the size of the gamma table. The size depends on the
- scanner/backend. If the scanner uses 8 bits gamma input then maxin has
- to be set to 255, for 10 bits 1023, for 12 bits 4095, for 14 bits
- 16383. The default is 16383. To find out what value maxin has to be
- call scanimage with a very large gamma table [0]0-[99999]255 then scan-
- image prints an error message with the needed size of the gamma table.
+ scanner/backend. If the scanner uses 8 bit gamma input then maxin must
+ be set to 255, 1023 for 10 bits, 4095 for 12 bits, and 16383 for 14
+ bits. The default is 16383. To find out what value maxin has to be,
+ call scanimage(1) with a very large gamma table [0]0-[99999]255 and
+ scanimage(1) will print an error message with the needed gamma table
+ size.
- maxout defines the maximum output value. Take a look at the output of
- scanimage -h to find out what maxout has to be. The default value is
- 255.
+ maxout defines the maximum output value. Take a look at the output of
+ scanimage -h to find out what maxout must be. The default value is 255.
EXAMPLE
- scanimage --custom-gamma=yes --gamma-table `gamma4scanimage 1.8 0 11500
- 16383 255` >image.pnm
+ scanimage --custom-gamma=yes --gamma-table `gamma4scanimage 1.8 0 11500
+ 16383 255` >image.pnm
SEE ALSO
- scanimage(1)
+ sane(7), scanimage(1)
@@ -69,7 +69,7 @@
EMAIL-CONTACT
- Oliver.Rauch@Rauch-Domain.DE
+ Oliver.Rauch@Rauch-Domain.DE
10 Jul 2008 gamma4scanimage(1)
diff --git a/man/sane-abaton.5.html b/man/sane-abaton.5.html
index 814394f8..344e8242 100644
--- a/man/sane-abaton.5.html
+++ b/man/sane-abaton.5.html
@@ -2,7 +2,7 @@
sane-abaton.5
-
+
sane-abaton.5
@@ -27,12 +27,12 @@
with this backend, or if you own an Abaton scanner that does not work
with this backend, please contact sane-devel@alioth-lists.debian.net
with the model number, so that arrangements can be made to include sup-
- port for it. Have a look at http://www.sane-project.org/mail-
- ing-lists.html concerning subscription to sane-devel.
+ port for it. Have a look at http://www.sane-project.org/mail-
+ ing-lists.html concerning subscription to sane-devel.
- Abaton is out of business, and these scanners are not supported by
- Everex (the parent company of Abaton), nor is there any programming
- information to be found. This driver is therefore based on information
+ Abaton is out of business, and these scanners are not supported by Ev-
+ erex (the parent company of Abaton), nor is there any programming in-
+ formation to be found. This driver is therefore based on information
obtained by running Abaton's scanning desk accessory under MacsBug and
tracing the MacOS SCSI Manager calls it made during image acquisition.
@@ -86,17 +86,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_ABATON
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -139,8 +139,8 @@
AUTHOR
- The sane-abaton backend was partially written by David Huggins-Daines,
- based on the sane-apple backend by Milon Firikis.
+ The sane-abaton backend was partially written by David Huggins-Daines,
+ based on the sane-apple(5) backend by Milon Firikis.
11 Jul 2008 sane-abaton(5)
diff --git a/man/sane-agfafocus.5.html b/man/sane-agfafocus.5.html
index afde6731..e25460c1 100644
--- a/man/sane-agfafocus.5.html
+++ b/man/sane-agfafocus.5.html
@@ -2,7 +2,7 @@
sane-agfafocus.5
-
+
sane-agfafocus.5
@@ -35,7 +35,7 @@
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 sane-devel@alioth-lists.debian.net.
- Have a look at http://www.sane-project.org/mailing-lists.html concern-
+ Have a look at http://www.sane-project.org/mailing-lists.html concern-
ing subscription to sane-devel.
All of these scanners are pre-SCSI-2, and do not even report properly
@@ -61,8 +61,8 @@
CONFIGURATION
The contents of the agfafocus.conf file is a list of device names that
correspond to AGFA Focus scanners. Empty lines and lines starting with
- a hash mark (#) are ignored. A sample configuration file is shown
- below:
+ a hash mark (#) are ignored. A sample configuration file is shown be-
+ low:
/dev/scanner
# this is a comment
@@ -91,19 +91,19 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 sepa-
- rator character, then the default directories are searched after
- the explicitly specified directories. For example, setting
- SANE_CONFIG_DIR to "/tmp/config:" would result in directories
- "tmp/config", ".", and "/etc/sane.d" being searched (in this
- order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_AGFAFOCUS
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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:
+ Smaller levels reduce verbosity. SANE_DEBUG_AGFAFOCUS values:
Number Remark
0 print important errors (printed each time)
@@ -133,8 +133,8 @@
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)
+ run SANE_DEBUG_AGFAFOCUS=128 scanimage -L in a terminal and look for
+ the "disconnect:" line.
@@ -143,12 +143,12 @@
the Artec backend is disabled. Somehow, this backend causes at least
my scanner not to respond correctly to SCSI inquiry commands.
- 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.
+ If you encounter a bug please set the environment variable SANE_DE-
+ BUG_AGFAFOCUS to 128 and try to regenerate the problem. Then send me a
+ report with the log attached.
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
+ please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
before sending me the report.
diff --git a/man/sane-apple.5.html b/man/sane-apple.5.html
index 1d06f92a..03154cec 100644
--- a/man/sane-apple.5.html
+++ b/man/sane-apple.5.html
@@ -2,7 +2,7 @@
sane-apple.5
-
+
sane-apple.5
@@ -28,9 +28,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 sane-devel@alioth-
- lists.debian.net. See http://www.sane-project.org/mailing-lists.html
- for details on how to subscribe to sane-devel.
+ name, SCSI id, and firmware revision to sane-devel@alioth-lists.de-
+ bian.net. See http://www.sane-project.org/mailing-lists.html for de-
+ tails on how to subscribe to sane-devel.
@@ -53,8 +53,8 @@
mark (#) are ignored. See sane-scsi(5) on details of what constitutes
a valid device name.
- Options come in two flavors: global and positional ones. Global
- options apply to all devices managed by the backend, whereas positional
+ Options come in two flavors: global and positional ones. Global op-
+ tions apply to all devices managed by the backend, whereas positional
options apply just to the most recently mentioned device. Note that
this means that the order in which the options appear matters!
@@ -89,12 +89,12 @@
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 search-
- ing the current working directory (".") and then /etc/sane.d.
- If the value of $SANE_CONFIG_DIR ends with the separator charac-
- ter, the default directories are searched after the directory
- list. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in that order).
+ ing the current working directory (".") and then /usr/lo-
+ cal/etc/sane.d. If the value of $SANE_CONFIG_DIR ends with the
+ separator character, the default directories are searched after
+ the directory list. For example, setting SANE_CONFIG_DIR to
+ "/tmp/config:" would result in directories tmp/config, ., and
+ /usr/local/etc/sane.d being searched (in that order).
SANE_DEBUG_APPLE
Controls the debug level. A value of 255 prints all debug out-
@@ -107,7 +107,7 @@
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, ColorOneS-
canner) I can only develop/test for the AppleScanner effectively. How-
- ever with this release I almost completed the gui part of all scanners.
+ ever 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
@@ -127,8 +127,8 @@
ColorOneScanner
Cannot up/download halftone patterns, calibration vectors, cus-
- tom Color Correction Tables (CCT) and of course custom gamma
- tables.
+ tom Color Correction Tables (CCT) and of course custom gamma ta-
+ bles.
Park/UnPark (OneScanner, ColorOneScanner)
Some capabilities are missing.
@@ -159,8 +159,8 @@
feature and a challenge for me to code if it could intermix dif-
ferent options for different windows (scan areas). This way it
could scan a document in LineArt mode but the figures in it in
- Gray and at a different resolution. Unfortunately this is
- impossible.
+ Gray and at a different resolution. Unfortunately this is im-
+ possible.
Scan Direction (OneScanner)
It controls the scan direction. (?)
@@ -177,12 +177,12 @@
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
- ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher-
- als_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.
+ across various Apple modes and models from the documentation ftp://ft-
+ pdev.info.apple.com/devworld/Technical_Documentation/Peripherals_Docu-
+ mentation/ is an interesting exercise. I may have missed some dependen-
+ cies. For example of the threshold parameter the Apple Scanners Pro-
+ gramming Guide says nothing. I had to assume it is valid only in Lin-
+ eArt mode.
Scanner specific bugs are mostly due to mandatory round-offs in order
to scan. In the documentation in one place states that the width of the
@@ -190,9 +190,9 @@
width of the scan area should be an even byte multiple. Go figure...
Other sources of bugs are due to scsi communication, scsi connects and
- disconnects. However the classical bugs are still there. So you may
- encounter buffer overruns, null pointers, memory corruption and SANE
- API violations.
+ disconnects. However the classical bugs are still there. So you may en-
+ counter buffer overruns, null pointers, memory corruption and SANE API
+ violations.
SIGSEGV on SliceBars
When you try to modify the scan area from the slice bar you have
@@ -225,20 +225,20 @@
DEBUG
If you encounter a GUI bug please set the environmental variable
- 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.
+ 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 at-
+ tached.
If you have an Apple Macintosh with the AppleScanners driver installed,
reporting to me which options are grayed out (inactive) in what modes
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 macro.
- You can select the scanner model through the APPLE_MODEL_SELECT macro.
- Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
+ don't have the model you would like to help with, or you are a SANE de-
+ veloper and you just want to take a look at how the apple backend looks
+ like, goto to apple.h and #define the NEUTRALIZE_BACKEND macro. You can
+ select the scanner model through the APPLE_MODEL_SELECT macro. Avail-
+ able options are APPLESCANNER, ONESCANNER, and COLORONESCANNER.
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
@@ -248,8 +248,8 @@
TODO
Non Blocking Support
- Make sane-apple a non blocking backend. Properly support
- sane_set_io_mode and sane_get_select_fd
+ Make sane-apple a non blocking backend. Properly support
+ sane_set_io_mode() and sane_get_select_fd()
Scan Make scanning possible for all models in all supported modes.
@@ -263,9 +263,9 @@
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 sane-apple backend was written not entirely from scratch by Milon
+ Firikis. It is mostly based on the sane-mustek(5) backend from David
+ Mosberger and Andreas Czechanowski
11 Jul 2008 sane-apple(5)
diff --git a/man/sane-artec.5.html b/man/sane-artec.5.html
index 4605f20c..12dcc405 100644
--- a/man/sane-artec.5.html
+++ b/man/sane-artec.5.html
@@ -2,7 +2,7 @@
sane-artec.5
-
+
sane-artec.5
@@ -33,18 +33,15 @@
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:
- http://www4.infi.net/~cpinkham/sane/
+ available from the backend homepage:
+ http://www4.infi.net/~cpinkham/sane.
-
-DOCUMENTATION
-
CONFIGURATION
- The contents of the artec.conf file are a list of device names that
- correspond to Artec scanners. Empty lines and lines starting with a
- hash mark (#) are ignored. See sane-scsi(5) on details of what consti-
+ The contents of the artec.conf file are a list of device names that
+ correspond to Artec scanners. Empty lines and lines starting with a
+ hash mark (#) are ignored. See sane-scsi(5) on details of what consti-
tutes a valid device name.
Sample file:
@@ -79,18 +76,18 @@
SCSI ADAPTER TIPS
- Some Artec scanners come with an included SCSI adapter. If your scan-
+ Some Artec scanners come with an included SCSI adapter. If your scan-
ner came with a DTC ISA scsi cards, you can probably use it with recent
- (>= 2.2.0) kernels using the generic NCR5380 support. You must pass
+ (>= 2.2.0) kernels using the generic NCR5380 support. You must pass
the following boot argument to the kernel: "dtc3181e=0x2c0,0"
- I do not have any information on the PCI SCSI adapter included with
+ I do not have any information on the PCI SCSI adapter included with
some newer Artec scanners.
FILES
/usr/local/etc/sane.d/artec.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-artec.a
@@ -106,22 +103,22 @@
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 con-
- figuration file is searched in two default directories: first,
- the current working direc- tory (".") 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ are separated by a colon (`:'), under OS/2, they are separated
+ by a semi- colon (`;'). If this variable is not set, the con-
+ figuration file is searched in two default directories: first,
+ the current working direc- tory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
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
+ If the library was compiled with debug support enabled, this en-
+ vironment 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:
Number Remark
0 print important errors
@@ -148,23 +145,23 @@
BUGS
- Known bugs in this release: A6000C+ users with firmware v1.92 or ear-
+ Known bugs in this release: A6000C+ users with firmware v1.92 or ear-
lier have problems with the backend, the cause has not been determined.
Sometimes the backend is not particularly robust, you can possibly lock
- up the SCSI bus (and/or machine) by not having patience enough when
- scanning. 3-channel gamma correction is not implemented and single-
- channel gamma correction is not totally working on models other than
+ up the SCSI bus (and/or machine) by not having patience enough when
+ scanning. 3-channel gamma correction is not implemented and single-
+ channel gamma correction is not totally working on models other than
the AT3.
SEE ALSO
- sane(7), sane-scsi(5)
+ sane(7), sane-scsi(5)
AUTHOR
- Chris Pinkham (cpinkham@corp.infi.net)
+ Chris Pinkham <cpinkham@corp.infi.net>
11 Jul 2008 sane-artec(5)
diff --git a/man/sane-artec_eplus48u.5.html b/man/sane-artec_eplus48u.5.html
index 3a3b4e4d..4fea6646 100644
--- a/man/sane-artec_eplus48u.5.html
+++ b/man/sane-artec_eplus48u.5.html
@@ -2,7 +2,7 @@
sane-artec_eplus48u.5
-
+
sane-artec_eplus48u.5
@@ -19,8 +19,8 @@
DESCRIPTION
The sane-artec_eplus48u library implements a SANE (Scanner Access Now
- Easy) backend that provides access to several USB flatbed scanners
- using the GT6816 chipset like the Artec E+ 48U. These scanners have a
+ Easy) backend that provides access to several USB flatbed scanners us-
+ ing the GT6816 chipset like the Artec E+ 48U. These scanners have a
contact image sensor (CIS) and an USB interface.
A complete list of supported devices can be found on
@@ -33,16 +33,16 @@
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 scan-
ner'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 slightly different from the models mentioned
+ /proc/bus/usb/devices, 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.
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
+ scanner should be found by sane-find-scanner(1) without further ac-
+ tions. For setting permissions and general USB information look at
sane-usb(5).
When you are using the scanner module, a Linux kernel 2.4.12 or newer
@@ -53,11 +53,11 @@
FIRMWARE FILE
You need a firmware file for your scanner. That's a small file contain-
ing software that will be uploaded to the scanner's memory. For the
- scanners mentioned above, it's usually named Artec48.usb or 1200.usb.
+ 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 manu-
- facturer, normally in the directory Win98, WinMe or similar. If the
+ facturer, 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.
+ the firmware file under c:264vers.
@@ -131,17 +131,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_ARTEC_EPLUS48U
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_ARTEC_EPLUS48U=3
@@ -152,14 +152,13 @@
sane(7), sane-usb(5)
-
AUTHOR
- Michael Herder
+ Michael Herder.
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.
- This man page is based on man sane-gt68xx, written by Henning Meier-
+ This man page is based on man sane-gt68xx(5), written by Henning Meier-
Geinitz.
diff --git a/man/sane-as6e.5.html b/man/sane-as6e.5.html
index d9211102..3a760c14 100644
--- a/man/sane-as6e.5.html
+++ b/man/sane-as6e.5.html
@@ -2,7 +2,7 @@
sane-as6e.5
-
+
sane-as6e.5
@@ -19,16 +19,16 @@
DESCRIPTION
The sane-as6e library implements a SANE (Scanner Access Now Easy) back-
- end that provides access to Artec AS6E flatbed scanner. It requires
- the as6edriver program in order to operate. The as6edriver program is
- not included with the SANE package. It can be found at
- http://as6edriver.sourceforge.net. See the as6edriver documentation
+ end that provides access to Artec AS6E flatbed scanner. It requires
+ the as6edriver program in order to operate. The as6edriver program is
+ not included with the SANE package. It can be found at
+ http://as6edriver.sourceforge.net. See the as6edriver documentation
for technical information.
- The as6edriver program must be in the path for executables ($PATH).
- Especially if you run saned (the SANE network scanning daemon), take
- care to setup the path for inetd or xinetd correctly or place the pro-
- gram in a directory that is in the path.
+ The as6edriver program must be in the path for executables ($PATH).
+ Especially if you run saned(8) (the SANE network scanning daemon), take
+ care to setup the path for inetd(8) or xinetd(8) correctly or place the
+ program in a directory that is in the path.
@@ -38,7 +38,8 @@
SEE ALSO
- sane(7), as6edriver(5), saned(8), http://as6edriver.sourceforge.net
+ sane(7), as6edriver(5), saned(8), inetd(8), xinetd(8)
+ http://as6edriver.sourceforge.net
@@ -48,7 +49,7 @@
EMAIL-CONTACT
- yossarian@users.sourceforge.net
+ yossarian@users.sourceforge.net
11 Jul 2008 sane-as6e(5)
diff --git a/man/sane-avision.5.html b/man/sane-avision.5.html
index 43a5fb8c..cddd9020 100644
--- a/man/sane-avision.5.html
+++ b/man/sane-avision.5.html
@@ -2,7 +2,7 @@
sane-avision.5
-
+
sane-avision.5
@@ -17,33 +17,27 @@
scanners.
-
-ABOUT THIS FILE
- This file is a short description for the avision-backend shipped with
- SANE.
-
-
DESCRIPTION
- The sane-avision library implements a SANE (Scanner Access Now Easy)
- backend that provides access to various Avision scanners and the Avi-
+ The sane-avision library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to various Avision scanners and the Avi-
sion 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.
- I suggest you hold one hand on the power-button of the scanner while
+ I suggest you hold one hand on the power-button of the scanner while
you try the first scans - especially with film-scanners!
CONFIGURATION
- The configuration file for this backend resides in
- /usr/local/etc/sane.d/avision.conf.
+ The configuration file for this backend resides in /usr/lo-
+ cal/etc/sane.d/avision.conf.
- Its contents is a list of device names that correspond to Avision and
- Avision compatible scanners and backend-options. Empty lines and lines
- starting with a hash mark (#) are ignored. A sample configuration file
+ Its contents is a list of device names that correspond to Avision and
+ Avision compatible scanners and backend-options. Empty lines and lines
+ starting with a hash mark (#) are ignored. A sample configuration file
is shown below:
# this is a comment
@@ -59,37 +53,37 @@
usb 0x03f0 0x0701
force-a4:
- Forces the backend to overwrite the scanable area returned by
- the scanner to ISO A4. Scanner that are known to return bogus
+ Forces the backend to overwrite the scanable area returned by
+ the scanner to ISO A4. Scanner that are known to return bogus
data are marked in the backend so if you need this option please
report this to the backend maintainer. USE WITH CARE!
force-a3:
- Forces the backend to overwrite the scanable area returned by
- the scanner to ISO A3. Scanner that are known to return bogus
+ Forces the backend to overwrite the scanable area returned by
+ the scanner to ISO A3. Scanner that are known to return bogus
data are marked in the backend so if you need this option please
report this to the backend maintainer. USE WITH CARE!
skip-adf:
Forces the backend to ignore an inconsistent ADF status returned
by the scanner (ADF not present, but ADF model number non-zero).
- Without this option, the backend will make several attempts to
- reset the ADF and retry the query in this situation, and will
- fail with a "not supported" error if the ADF still doesn't
- respond.
+ Without this option, the backend will make several attempts to
+ reset the ADF and retry the query in this situation, and will
+ fail with a "not supported" error if the ADF still doesn't re-
+ spond.
disable-gamma-table:
- Disables the usage of the scanner's gamma-table. You might try
+ Disables the usage of the scanner's gamma-table. You might try
this if your scans hang or only produces random garbage.
disable-calibration:
- Disables the scanner's color calibration. You might try this if
+ Disables the scanner's color calibration. You might try this if
your scans hang or only produces random garbage.
- Note: Any option above modifies the default code-flow for your scan-
+ Note: Any option above modifies the default code-flow for your scan-
ner. The options should only be used when you encounter problems
- with the default be- haviour of the backend. Please report the
- need of options to the backend-author so the backend can be
+ with the default be- haviour of the backend. Please report the
+ need of options to the backend-author so the backend can be
fixed as soon as possible.
@@ -102,24 +96,24 @@
usb usb-spec
Where 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 exam-
- ple 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.
+ 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 exam-
+ ple 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 de-
+ tails.
- Note: Since the backend now includes native USB access, it is no
+ Note: Since the backend now includes native USB access, it is no
longer needed - even considered obsolete - to access USB scanner
- via the SCSI emulation (named hpusbscsi on Linux) for Avision
- USB devices such as the HP 53xx, HP 74xx or Minolta film-scan-
+ via the SCSI emulation (named hpusbscsi on Linux) for Avision
+ USB devices such as the HP 53xx, HP 74xx or Minolta film-scan-
ners.
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
+ used by libusb corresponding to the USB scanner. For example "0x03f0
0x0701" or "libusb:002:003". See sane-usb(5) for details.
- The program sane-find-scanner helps to find out the correct scsi or usb
- device name.
+ The program 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 nor-
mally specifying an ID should not be necessary.
@@ -128,7 +122,7 @@
FILES
/usr/local/etc/sane.d/avision.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-avision.a
@@ -144,22 +138,22 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_AVISION
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
- Higher debug levels increase the verbosity of the output. The
- debug level 7 is the author's preferred value to debug backend
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output. The
+ debug level 7 is the author's preferred value to debug backend
problems.
Example: export SANE_DEBUG_AVISION=7
@@ -168,7 +162,7 @@
SEE ALSO
sane(7), sane-scsi(5), sane-usb(5)
- http://exactcode.com/site/open_source/saneavision/
+ http://exactcode.com/site/open_source/saneavision
diff --git a/man/sane-bh.5.html b/man/sane-bh.5.html
index 519066d3..d4270fd7 100644
--- a/man/sane-bh.5.html
+++ b/man/sane-bh.5.html
@@ -2,7 +2,7 @@
sane-bh.5
-
+
sane-bh.5
@@ -23,7 +23,7 @@
ners. 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 follow-
- ing scanner models.
+ ing scanner models:
COPISCAN II 6338 Duplex Scanner with ACE
COPISCAN II 2135 Simplex Scanner
@@ -35,7 +35,7 @@
If you have a Bell+Howell scanner and are able to test it with this
backend, please contact 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
+ 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.
@@ -55,7 +55,7 @@
The latest backend release, additional information and helpful hints
are available from the backend homepage:
- http://www.martoneconsulting.com/sane-bh.html
+ http://www.martoneconsulting.com/sane-bh.html
@@ -71,186 +71,14 @@
See sane-scsi(5) for details.
-
-CONFIGURATION
- The contents of the bh.conf file is a list of device names that corre-
- spond to Bell+Howell scanners. See sane-scsi(5) on details of what
- constitutes a valid device name. Additionally, options can be speci-
- fied; 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.
-
-
-
-OPTIONS
- The following options can be specified in the bh.conf file.
-
- 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.
-
- 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".
-
-
-
-FILES
- /usr/local/etc/sane.d/bh.conf
- The backend configuration file (see also description of
- SANE_CONFIG_DIR below).
-
- /usr/local/lib/sane/libsane-bh.a
- The static library implementing this backend.
-
- /usr/local/lib/sane/libsane-bh.so
- The shared library implementing this backend (present on systems
- that support dynamic loading).
-
-
-
-ENVIRONMENT
- 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 config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
-
- 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.
-
-
-
-SUPPORTED FEATURES
- ADF support
- With document scanners, automatic document feeder (ADF) support
- is a key feature. The backend supports the ADF by default and
- returns SANE_STATUS_NO_DOCS when the out-of-paper condition is
- detected. The SANE frontend scanadf is a command line frontend
- that supports multi-page scans. It has been used successfully
- with this backend. The SANE frontend xsane is an improved GUI
- frontend by Oliver Rauch. Support for multi-page scans is
- included in xsane version 0.35 and above.
-
- Duplex scanning
- Some models, such as the COPISCAN II 6338, support duplex scan-
- ning. 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 --duplex
- option). The front and back page images are delivered consecu-
- tively as if they were separately scanned pages.
-
- 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 --g31d, --g32d,
- --g42d options, respectively. Many SANE frontends are not
- equipped to deal with these formats, however. The SANE frontend
- scanadf supports these optional frame formats. The compressed
- image data is written directly to a file and can then be pro-
- cessed by a scan-script using the --scan-script option. Exam-
- ples of this are given on the scanadf homepage.
-
- Automatic Border Detection
- The scanner can automatically detect the paper size and adjust
- the scanning window geometry appropriately. The backend sup-
- ports this useful feature with the --autoborder option. It is
- enabled by default.
-
- Batch Mode Scanning
- The batch scan mode allows for maximum throughput. The Set Win-
- dow parameters must remain constant during the entire batch.
-
- 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.
-
- Multiple Sections
- Multiple sections (scanning sub-windows) can be defined for the
- front and back pages. Each section can have different charac-
- teristics (e.g. geometry, compression). The sections are
- returned as if they were separately scanned images. Addition-
- ally 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.
-
- 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 decod-
- ing examples can be found on the backend homepage.
-
-
-
-LIMITATIONS
- 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
- --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.
-
- 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' functional-
- ity 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.
-
- 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.
-
-
OPTIONS
Scan Mode Options:
--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.
+ Request a preview-quality scan. When preview is set to yes im-
+ age compression is disabled and the image is delivered in a
+ SANE_FRAME_GRAY frame.
--mode lineart|halftone [lineart]
Selects the scan mode (e.g., lineart,monochrome, or color).
@@ -263,13 +91,15 @@
--compression none|g31d|g32d|g42d [none]
Sets the compression mode of the scanner. Determines the type
of data returned from the scanner. Values are:
+
none - uncompressed data - delivered in a SANE_FRAME_GRAY frame
g31d - CCITT G3 1 dimension (MH) - delivered in a
SANE_FRAME_G31D frame
g32d - CCITT G3 2 dimensions (MR, K=4) - delivered in a
SANE_FRAME_G32D frame
g42d - CCITT G4 (MMR) - delivered in a SANE_FRAME_G42D frame
- NOTE: The use of g31d, g32d, and g42d compression values causes
+
+ 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.
@@ -300,9 +130,9 @@
--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.
+ Selects the scan source (such as a document feeder). This op-
+ tion is provided to allow multiple image scans with
+ xsane(1);ithasnootherpurpose.
--batch[=(yes|no)] [no]
Enable/disable batch mode scanning. Batch mode allows scanning
@@ -338,10 +168,10 @@
--control-panel[=(yes|no)] [yes]
Enables the scanner's control panel for selecting image enhance-
- ment parameters. When the option is set to no the following
- options are used to control image enhancement. See the
- Bell+Howell scanner users' guide for complete information on ACE
- functionality.
+ ment parameters. When the option is set to no the following op-
+ tions are used to control image enhancement. See the Bell+How-
+ ell scanner users' guide for complete information on ACE func-
+ tionality.
--ace-function -4..4 [3]
Specify the Automatic Contrast Enhancement (ACE) Function.
@@ -379,6 +209,7 @@
specified, or specified with a value of none, then the barcode
decoding feature is completely disabled. The valid barcode type
are:
+
none
ean-8
ean-13
@@ -404,6 +235,7 @@
--barcode-search-mode <see list> [horiz-vert]
Chooses the orientation of barcodes to be searched. The valid
orientations are:
+
horiz-vert
horizontal
vertical
@@ -421,8 +253,8 @@
--section <string> []
Specifies a series of image sections. A section can be used to
- gather a subset image or to provide a small area for barcode
- decoding. Each section is specified in the following format
+ gather a subset image or to provide a small area for barcode de-
+ coding. Each section is specified in the following format
(units are in millimeters):
<width>x<height>+<top-left-x>+<top-left-y>[:functioncode...]
@@ -445,7 +277,8 @@
sections identified. This can significantly speed up the decoding
process.
- The following functioncodes are available:
+ The following function codes are available:
+
front - generate an image for the front page section
back - generate an image for the back page section
frontbar - perform barcode search in front page section
@@ -479,27 +312,200 @@
Controls Patch Code detection.
+
+CONFIGURATION
+ The contents of the bh.conf file is a list of device names that corre-
+ spond to Bell+Howell scanners. See sane-scsi(5) on details of what
+ constitutes a valid device name. Additionally, options can be speci-
+ fied; these lines begin with the word "option". Each option is de-
+ scribed in detail below. Empty lines and lines starting with a hash
+ mark (#) are ignored.
+
+
+
+OPTIONS
+ The following options can be specified in the bh.conf file.
+
+ 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 op-
+ tional 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 op-
+ tions. These frames are never sent in preview mode.
+
+ 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".
+
+
+
+FILES
+ /usr/local/etc/sane.d/bh.conf
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below).
+
+ /usr/local/lib/sane/libsane-bh.a
+ The static library implementing this backend.
+
+ /usr/local/lib/sane/libsane-bh.so
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+
+ENVIRONMENT
+ 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 config-
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
+
+ SANE_DEBUG_BH
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
+
+
+
+SUPPORTED FEATURES
+ ADF support
+ With document scanners, automatic document feeder (ADF) support
+ is a key feature. The backend supports the ADF by default and
+ returns SANE_STATUS_NO_DOCS when the out-of-paper condition is
+ detected. The SANE frontend scanadf(1) is a command line front-
+ end that supports multi-page scans. It has been used success-
+ fully with this backend. The SANE frontend xsane(1) is an im-
+ proved GUI frontend by Oliver Rauch. Support for multi-page
+ scans is included in xsane version 0.35 and above.
+
+ Duplex scanning
+ Some models, such as the COPISCAN II 6338, support duplex scan-
+ ning. 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 --duplex op-
+ tion). The front and back page images are delivered consecu-
+ tively as if they were separately scanned pages.
+
+ Hardware compression
+ The scanner is capable of compressing the data into several in-
+ dustry 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 --g31d, --g32d, --g42d op-
+ tions, respectively. Many SANE frontends are not equipped to
+ deal with these formats, however. The SANE frontend 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 --scan-script option. Examples of this
+ are given on the scanadf(1) homepage.
+
+ Automatic Border Detection
+ The scanner can automatically detect the paper size and adjust
+ the scanning window geometry appropriately. The backend sup-
+ ports this useful feature with the --autoborder option. It is
+ enabled by default.
+
+ Batch Mode Scanning
+ The batch scan mode allows for maximum throughput. The Set Win-
+ dow parameters must remain constant during the entire batch.
+
+ 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 al-
+ lows the host to quickly display a thumbnail representation dur-
+ ing 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.
+
+ Multiple Sections
+ Multiple sections (scanning sub-windows) can be defined for the
+ front and back pages. Each section can have different charac-
+ teristics (e.g. geometry, compression). The sections are re-
+ turned as if they were separately scanned images. Additionally
+ sections can be used to greatly enhance the accuracy and effi-
+ ciency of the barcode/patchcode decoding process by limiting the
+ search area to a small subset of the page. Most Copiscan II se-
+ ries scanners support up to 8 user-defined sections.
+
+ 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 decod-
+ ing examples can be found on the backend homepage.
+
+
+
+LIMITATIONS
+ 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
+ --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 ad-
+ dress this.
+
+ 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' functional-
+ ity 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.
+
+ 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 re-
+ liable than the standard Bar/Patch code decoder. This is not
+ currently supported.
+
+
BUGS
This is a new backend; detailed bug reports are welcome -- and expected
;)
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
- sane-devel@alioth-lists.debian.net.
+ recreate it with the SANE_DEBUG_BH environment variable set to 255, and
+ send a report detailing the conditions surrounding the bug to sane-de-
+ vel@alioth-lists.debian.net.
SEE ALSO
- sane(7), sane-scsi(5), scanimage(1), scanadf(1)
+ sane(7), sane-scsi(5), scanimage(1), scanadf(1), xsane(1)
AUTHOR
- The sane-bh backend was written by Tom Martone, based on the sane-ricoh
- backend by Feico W. Dillema and the bnhscan program by Sean Reifschnei-
- der of tummy.com ltd. Some 8000 enhancements added by Mark Temple.
+ The sane-bh backend was written by Tom Martone, based on the sane-ri-
+ coh(5) backend by Feico W. Dillema and the bnhscan program by Sean
+ Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
+ Temple.
10 Jul 2008 sane-bh(5)
diff --git a/man/sane-canon.5.html b/man/sane-canon.5.html
index cbde10be..c6e2aaf9 100644
--- a/man/sane-canon.5.html
+++ b/man/sane-canon.5.html
@@ -2,7 +2,7 @@
sane-canon.5
-
+
sane-canon.5
@@ -29,21 +29,21 @@
CanoScan FS2710S
Parallel port and USB scanners are not supported by this backend; see
- the manual pages for sane-canon_pp and sane-canon630u for further
+ the manual pages for sane-canon_pp(5) and sane-canon630u(5) for further
information.
IMPORTANT: This is beta code. We tested the code on the scanners listed
above, using the computers and operating systems available to us, but
- we cannot guarantee that the backend will work smoothly with future
- operating systems, SCSI adapters, SANE frontend programs, or Canon
- scanners not contained in the list above. In some cases your computer
- might even hang. It cannot be excluded (although we consider it
- extremely unlikely) that your scanner will be damaged.
+ we cannot guarantee that the backend will work smoothly with future op-
+ erating systems, SCSI adapters, SANE frontend programs, or Canon scan-
+ ners not contained in the list above. In some cases your computer might
+ even hang. It cannot be excluded (although we consider it extremely
+ unlikely) that your scanner will be damaged.
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>.
+ 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>.
@@ -51,14 +51,14 @@
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.
+ the frontend xsane(1) for best results.
- The "Auto Focus" function triggers a special pass to determine the
- focus value. After that, the real scanning pass takes place.
+ The "Auto Focus" function triggers a special pass to determine the fo-
+ cus value. After that, the real scanning pass takes place.
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.
+ blurred. Using the gimp(1) to do a "Filter->Enhance->Sharpen" at about
+ 40 to 60 improves the image considerably.
@@ -88,8 +88,8 @@
ENVIRONMENT
SANE_DEBUG_CANON
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_CANON=4
@@ -98,14 +98,15 @@
SEE ALSO
sane-scsi(5)
- http://www.rzg.mpg.de/~mpd/sane/
- doc/canon.install2700F.txt (installation of a CanoScan 2700F
+ http://www.rzg.mpg.de/~mpd/sane/doc/canon.install2700F.txt (installa-
+ tion of a CanoScan 2700F)
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;
+ FB620S and FB1200S support by Mitsuru Okaniwa;
+ FS2710S support by Ulrich Deiters
Man page by Henning Meier-Geinitz (mostly based on canon.README)
11 Jul 2008 sane-canon(5)
diff --git a/man/sane-canon630u.5.html b/man/sane-canon630u.5.html
index 6bd1d3ac..ee14305a 100644
--- a/man/sane-canon630u.5.html
+++ b/man/sane-canon630u.5.html
@@ -2,7 +2,7 @@
sane-canon630u.5
-
+
sane-canon630u.5
@@ -27,7 +27,7 @@
analog gain are adjustable.
TESTERS ARE WELCOME. Send your bug reports and comments to Nathan Rut-
- man <nthn1@yahoo.com>
+ man <nthn1@yahoo.com>.
@@ -35,14 +35,14 @@
The contents of the canon630u.conf file is a list of device names that
correspond to Canon USB scanners. Empty lines and lines starting with
a hash mark (#) are ignored. Only one device name can be listed in
- canon630u.conf. The program sane-find-scanner helps to find out the
+ canon630u.conf. The program sane-find-scanner(1) helps to find out the
correct device. Under Linux, such a device name could be /dev/usb/scan-
ner0 for example. See sane-usb(5) for details.
This product-specific scanner driver uses the lower-level kernel USB
driver "scanner". Check for "Driver=usbscanner" under
- /proc/bus/usb/devices. If "Driver=(none)", try forcing it with "insmod
- scanner vendor=0x04a9 product=0x2204"
+ /proc/bus/usb/devices. If "Driver=(none)", try forcing it with insmod
+ scanner vendor=0x04a9 product=0x2204
@@ -56,11 +56,11 @@
able in kernel 2.4.12 or later.
Some users have reported that this driver doesn't work at all. This
- seems to be a hardware specific issue, although I don't know what
- exactly the problem is. If you are having problems, please send me the
- info in /proc/bus/usb/devices, /proc/pci, the kernel scanner.c driver
- version from /var/log/messages, and the output from
- "SANE_DEBUG_CANON630U=12 scanimage > /dev/null"
+ seems to be a hardware specific issue, although I dsane-uson't know
+ what exactly the problem is. If you are having problems, please send
+ me the info in /proc/bus/usb/devices, /proc/pci, the kernel scanner.c
+ driver version from /var/log/messages, and the output from SANE_DE-
+ BUG_CANON630U=12 scanimage > /dev/null
@@ -90,17 +90,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_CANON630U
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example:
@@ -110,7 +110,7 @@
SEE ALSO
sane(7), sane-usb(5), sane-find-scanner(1)
- http://canon-fb630u.sourceforge.net/
+ http://canon-fb630u.sourceforge.net/
diff --git a/man/sane-canon_dr.5.html b/man/sane-canon_dr.5.html
index 5a9fffc4..fe75607a 100644
--- a/man/sane-canon_dr.5.html
+++ b/man/sane-canon_dr.5.html
@@ -2,7 +2,7 @@
sane-canon_dr.5
-
+
sane-canon_dr.5
@@ -27,7 +27,7 @@
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
+ 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 deter-
@@ -48,22 +48,20 @@
OPTIONS
Effort has been made to expose most hardware options, including:
- source s
- Selects the source for the scan. Options may include "Flatbed",
- "ADF Front", "ADF Back", "ADF Duplex".
+ --source Flatbed|ADF Front|ADF Back|ADF Duplex
+ Selects the source for the scan.
- mode m
- Selects the mode for the scan. Options may include "Lineart",
- "Halftone", "Gray", and "Color".
+ --mode Lineart|Halftone|Gray|Color
+ Selects the mode for the scan.
- resolution
+ --resolution
Controls scan resolution.
- tl-x, tl-y, br-x, br-y
+ --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.
+ renamed -t, -l, -x, -y by some frontends.
- page-width, page-height
+ --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.
@@ -72,43 +70,43 @@
Additionally, several 'software' options are exposed by the backend.
These are reimplementations of features provided natively by larger
- scanners, but running on the host computer. This enables smaller
- machines to have similar 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.
+ scanners, but running on the host computer. This enables smaller ma-
+ chines to have similar capabilities. Please note that these features
+ are somewhat simplistic, and may not perform as well as the native im-
+ plementations. Note also that these features all require that the
+ driver cache the entire image in memory. This will almost certainly re-
+ sult in a reduction of scanning speed.
- swcrop
+ --swcrop
Requests the driver to detect the extremities of the paper
within the larger image, and crop the empty edges.
- swdeskew
+ --swdeskew
Requests the driver to detect the rotation of the paper within
the larger image, and counter the rotation.
- swdespeck X
+ --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 sur-
rounding color.
- 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.
+ Use 'scanimage --help' to get a list, but be aware that some op-
+ tions may be settable only when another option has been set, and
+ that advanced options may be hidden by some frontend programs.
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
+ 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.
Scanners can be specified in the configuration file in 4 ways:
"scsi CANON DR"
- Requests backend to search all scsi busses in the system for a
+ Requests backend to search all scsi buses in the system for a
device which reports itself to be a scanner made by 'CANON',
with a model name starting with 'DR'.
@@ -119,9 +117,9 @@
other "scsi" line above.
"usb 0x04a9 0x1603" (or other vendor/product ids)
- Requests backend to search all usb busses in the system for a
- device which uses that vendor and product id. The device will
- then be queried to determine if it is a Canon scanner.
+ Requests backend to search all usb buses in the system for a de-
+ vice which uses that vendor and product id. The device will then
+ be queried to determine if it is a Canon scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
@@ -158,14 +156,13 @@
option if your unit shows an unwanted band of image data on only
one side.
- Note: 'option' lines may appear multiple times in the configuration
- file. They only apply to scanners discovered by the next 'scsi/usb'
+ NOTE: They only apply to scanners discovered by the next 'scsi/usb'
line.
ENVIRONMENT
- The backend uses a single environment variable, SANE_DEBUG_CANON_DR,
+ The backend uses a single environment variable, SANE_DEBUG_CANON_DR,
which enables debugging output to stderr. Valid values are:
5 Errors
@@ -179,34 +176,37 @@
KNOWN ISSUES
- This backend was entirely reverse engineered from usb traces of the
- proprietary driver. Various advanced features of the machines may not
- be enabled. Many machines have not been tested. Their protocol is
- unknown.
+ This backend was entirely reverse engineered from usb traces of the
+ proprietary driver. Various advanced features of the machines may not
+ be enabled. Many machines have not been tested. Their protocol is un-
+ known.
CREDITS
- The various authors of the sane-fujitsu backend provided useful code
- Yabarana Corp. www.yabarana.com provided significant funding
- EvriChart, Inc. www.evrichart.com provided funding and loaned equipment
- Canon, USA. www.usa.canon.com loaned equipment
- HPrint hprint.com.br provided funding and testing for DR-2510 support
- Stone-IT www.stone-it.com provided funding for DR-2010 and DR-2050 sup-
- port
- Gerhard Pfeffer provided access and testing for P-208 and P-215
- Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum-
+ The various authors of the sane-fujitsu(5) backend provided useful
+ code.
+ Yabarana Corp. www.yabarana.com provided significant funding.
+ EvriChart, Inc. www.evrichart.com provided funding and loaned equip-
+ ment.
+ Canon, USA. www.usa.canon.com loaned equipment.
+ HPrint hprint.com.br provided funding and testing for DR-2510 support.
+ Stone-IT www.stone-it.com provided funding for DR-2010 and DR-2050 sup-
+ port.
+ Gerhard Pfeffer provided access and testing for P-208 and P-215.
+ Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum-
melen, Thanos Diacakis and Junren Shi for testing and feedback.
SEE ALSO
- sane(7), sane-scsi(5), sane-usb(5)
+ sane(7), sane-scsi(5), sane-usb(5)
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com>.
+
31 Aug 2015 sane-canon_dr(5)
diff --git a/man/sane-canon_lide70.5.html b/man/sane-canon_lide70.5.html
index 06230de9..4a3fe055 100644
--- a/man/sane-canon_lide70.5.html
+++ b/man/sane-canon_lide70.5.html
@@ -2,7 +2,7 @@
sane-canon_lide70.5
-
+
sane-canon_lide70.5
@@ -12,71 +12,69 @@
NAME
- sane-canon_lide70 - SANE backend for the Canon LiDE 70 USB flatbed
- scanner
+ sane-canon_lide70 - SANE backend for the Canon LiDE 70 and 600(F) USB
+ flatbed scanners
DESCRIPTION
The canon_lide70 library implements a SANE (Scanner Access Now Easy)
- backend that provides access to the Canon Inc. CanoScan LiDE 70 flatbed
- scanner.
+ backend that provides access to the Canon Inc. CanoScan LiDE 70 and
+ 600(F) flatbed scanners. The film unit of the LiDE 600F is not sup-
+ ported.
- Due to Canon's unwillingness to provide scanner documentation, this
- software was developed by analyzing the USB traffic of the Windows XP
+ Due to Canon's unwillingness to provide scanner documentation, this
+ software was developed by analyzing the USB traffic of the Windows XP
driver. The precise meaning of the individual commands that are sent to
the scanner is known only to a very limited extent. Some sophistication
present in the Windows XP driver has been left out. There is, for exam-
ple, no active calibration.
- TESTERS ARE WELCOME. Send your bug reports and comments to the
- sane-devel mailing list <sane-devel@alioth-lists.debian.net>
-
- The Canoscan LiDE 600 (or 600f, with film unit) is closely related to
- the LiDE 70, but it does not work with this backend. Support for the
- LiDE 600 will be added by the end of 2020.
+ Testers and reviewers are welcome. Send your bug reports and comments
+ to the sane-devel mailing list <sane-devel@alioth-lists.debian.net>.
CONFIGURATION
The /usr/local/etc/sane.d/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 would be 0x2224.
+ by its vendor code 0x04a9 and its product code 0x2225. For the LiDE
+ 600(f) the product code is 0x2224.
BACKEND SPECIFIC OPTIONS
Scan Mode:
- --resolution 75|150|300|600|1200 [default 600]
- Sets the resolution of the scanned image in dots per inch.
- Scanning at 1200 dpi is very slow.
+ --resolution 75|150|300|600|1200 [default 600]
+ Sets the resolution of the scanned image in dots per inch. Scan-
+ ning at 1200 dpi is not available on the LiDE 600(F) and it is
+ very slow on the LiDE 70.
- --mode Color|Gray|Lineart [default: Color]
- Selects the scan mode. Lineart means fully black and fully
- white pixels only.
+ --mode Color|Gray|Lineart [default: Color]
+ Selects the scan mode. Lineart means fully black and fully white
+ pixels only.
- --threshold 0..100 (in steps of 1) [default 75]
- Select minimum-brightness percentage to get a white point, rel-
- evant only for Lineart
+ --threshold 0..100 (in steps of 1) [default 75]
+ Select minimum-brightness percentage to get a white point, rele-
+ vant only for Lineart
- --non-blocking[=(yes|no)] [inactive]
- This option has not yet been implemented. Scans are captured in
+ --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.
Geometry:
- -l 0..216.069 [default 0]
- Top-left x position of scan area in millimeters.
+ -l 0..216.069 [default 0]
+ Top-left x position of scan area in millimeters.
- -t 0..297 [default 0]
- Top-left y position of scan area in millimeters.
+ -t 0..297 [default 0]
+ Top-left y position of scan area in millimeters.
- -x 0..216.069 [default 80]
- Width of scan-area in millimeters.
+ -x 0..216.069 [default 80]
+ Width of scan-area in millimeters.
- -y 0..297 [default 100]
- Height of scan-area in millimeters.
+ -y 0..297 [default 100]
+ Height of scan-area in millimeters.
@@ -95,8 +93,8 @@
ENVIRONMENT
SANE_DEBUG_CANON_LIDE70
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example:
@@ -106,19 +104,20 @@
KNOWN PROBLEMS
At low resolutions (75 and 150 dpi, implying high slider speeds) the
- scanner misses the top one millimeter of the scan area. This can be
+ 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.
+ where such precision matters. Note that xsane(1) uses the 75 dpi mode
+ for prescans. The problem is worse on the LiDE 600(F), where the offset
+ is five millimeters.
- It is recommended that in xsane the gamma value be set to approximately
- 1.5 to get more realistic colors. This also wipes out some artifacts
- caused by the lack of real calibration.
+ It is recommended that in xsane(1) the gamma value be set to approxi-
+ mately 1.7 to get more realistic colors. This also wipes out some arti-
+ facts caused by the lack of real calibration.
SEE ALSO
- sane(7), sane-usb(5), sane-find-scanner(1), scanimage(1)
+ sane(7), sane-usb(5), sane-find-scanner(1), scanimage(1), xsane(1),
http://www.juergen-ernst.de/info_sane.html
@@ -126,7 +125,7 @@
AUTHOR
pimvantend, building upon pioneering work by Juergen Ernst.
- 26 Nov 2019 sane-canon_lide70(5)
+ 22 Aug 2020 sane-canon_lide70(5)
diff --git a/man/sane-canon_pp.5.html b/man/sane-canon_pp.5.html
index 33d7b9f9..373f0b4a 100644
--- a/man/sane-canon_pp.5.html
+++ b/man/sane-canon_pp.5.html
@@ -2,7 +2,7 @@
sane-canon_pp.5
-
+
sane-canon_pp.5
@@ -31,9 +31,9 @@
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 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.
+ See the PROJECTS file for more detail. The FB310P and FB610P are re-
+ badged Avision scanners which use a different command set, so are un-
+ likely to be supported by this backend in the future.
IMPORTANT: this is alpha code. While we have made every effort to make
it as reliable as possible, it will not always work as expected. Feed-
@@ -43,12 +43,13 @@
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 li-
+ bieee1284(3). These names are highly dependent on operating system and
+ version.
- On Linux 2.4 kernels this will be of the form parport0 or older (2.2
- and before) kernels may produce names like 0x378 (the base address of
- your port) or simply 0 depending on your module configuration. Check
+ On Linux 2.4 kernels this will be of the form parport0 or older (2.2
+ and before) kernels may produce names like 0x378 (the base address of
+ your port) or simply 0 depending on your module configuration. Check
the contents of /proc/parport if it exists. If you don't want to spec-
ify a default port (or don't know its name), the backend should be able
to detect which port your scanner is on.
@@ -56,45 +57,45 @@
CONFIGURATION
- The contents of the canon_pp.conf file is a list of options for the
+ The contents of the canon_pp.conf file is a list of options for the
driver to use. Empty lines and lines starting with a hash mark (#) are
ignored.
The supported options are currently ieee1284, calibrate, init_mode, and
force_nibble
- Option ieee1284 port-name defines which port to use. The format of
+ Option ieee1284 port-name defines which port to use. The format of
port-name is OS dependent, based on the names presented by libieee1284.
Please only have one of these lines, or all but one will be ignored.
Option calibrate cal-file [port-name] defines which calibration file to
- use on a per-port basis. If you only have one parport, the port-name
+ use on a per-port basis. If you only have one parport, the port-name
argument may be omitted - but be careful as this will cause problems on
- multi-scanner systems. You may have as many of these lines as you
- like, as long as each has a unique port name. The tilde (`~') charac-
- ter is acceptable and will be expanded to the value of the HOME envi-
+ multi-scanner systems. You may have as many of these lines as you
+ like, as long as each has a unique port name. The tilde (`~') charac-
+ ter is acceptable and will be expanded to the value of the HOME envi-
ronment.
Option init_mode <AUTO|FB620P|FB630P> [portname] defines which initial-
- isation (wake-up) mode to use on a per-port basis. If you only have
- one parport, the portname argument may be omitted - but be careful as
+ isation (wake-up) mode to use on a per-port basis. If you only have
+ one parport, the portname argument may be omitted - but be careful as
this may cause problems on multi-scanner systems. You may have as many
- of these lines as you like, as long as each has a unique port name.
- The valid initialisation modes are FB620P (which strobes 10101010 and
+ of these lines as you like, as long as each has a unique port name.
+ The valid initialisation modes are FB620P (which strobes 10101010 and
01010101 on the data pins), FB630P (which strobes 11001100 and 00110011
- on the data pins) and AUTO, which will try FB630P mode first then
- FB620P mode second. The FB620P mode is also used by the FB320P. The
+ on the data pins) and AUTO, which will try FB630P mode first then
+ FB620P mode second. The FB620P mode is also used by the FB320P. The
FB630P mode is used by the FB330P, N340P, and N640P.
- Option force_nibble forces the driver to use nibble mode even if ECP
- mode is reported to work by libieee1284. This works-around the rare
+ Option force_nibble forces the driver to use nibble mode even if ECP
+ mode is reported to work by libieee1284. This works-around the rare
issue of ECP mode being reported to work by the library, then not work-
ing.
TIPS
- Hit the "Calibrate" button before scanning. It vastly improves the
+ Hit the "Calibrate" button before scanning. It vastly improves the
quality of scans.
To enable automatic detection of your scanner, uncomment the "canon_pp"
@@ -104,7 +105,7 @@
FILES
/usr/local/etc/sane.d/canon_pp.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-canon_pp.a
@@ -120,20 +121,20 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_CANON_PP
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_CANON_PP=4
@@ -144,74 +145,75 @@
Features available in the Windows interface
Brightness and Contrast
- These are not implemented, and probably never will be. These
- appear to be implemented entirely in software. Use GIMP or a
+ These are not implemented, and probably never will be. These
+ appear to be implemented entirely in software. Use GIMP or a
similar program if you need these features.
Descreen Mode
- This appears on our first analysis to be just oversampling with
- an anti-aliasing filter. Again, it seems to be implemented
- entirely in software, so GIMP is your best bet for now.
+ This appears on our first analysis to be just oversampling with
+ an anti-aliasing filter. Again, it seems to be implemented en-
+ tirely in software, so GIMP is your best bet for now.
Gamma Tables
- This is under investigation, but for now only a simple gamma
- profile (ie: the one returned during calibration) will be
+ This is under investigation, but for now only a simple gamma
+ profile (ie: the one returned during calibration) will be
loaded.
Communication Problems
- ECP mode in libieee1284 doesn't always work properly, even with new
- hardware. We believe that this is a ppdev problem. If you change the
- configuration file to include force_nibble , the problem will go away,
+ ECP mode in libieee1284 doesn't always work properly, even with new
+ hardware. We believe that this is a ppdev problem. If you change the
+ configuration file to include force_nibble , the problem will go away,
but you will only be able to scan in nibble mode.
- Sometimes the scanner can be left in a state where our code cannot
- revive it. If the backend reports no scanner present, try unplugging
- the power and plugging it back in. Also try unplugging printers from
- the pass-through port.
+ Sometimes the scanner can be left in a state where our code cannot re-
+ vive it. If the backend reports no scanner present, try unplugging the
+ power and plugging it back in. Also try unplugging printers from the
+ pass-through port.
- The scanner will not respond correctly to our commands when you first
- plug in the power. You may find if you try a scan very soon after
+ The scanner will not respond correctly to our commands when you first
+ plug in the power. You may find if you try a scan very soon after
plugging in the power that the backend will incorrectly report that you
- have no scanner present. To avoid this, give it about 10 seconds to
+ have no scanner present. To avoid this, give it about 10 seconds to
reset itself before attempting any scans.
Repeated Lines
- Sometimes at high resolutions (ie. 600dpi) you will notice lines which
- appear twice. These lines correspond to points where the scanner head
+ Sometimes at high resolutions (ie. 600dpi) you will notice lines which
+ appear twice. These lines correspond to points where the scanner head
has stopped during the scan (it stops every time the internal 64kb buf-
- fer is full). Basically it's a mechanical problem inside the scanner,
- that the tolerance of movement for a start/stop event is greater than
- 1/600 inches. I've never tried the windows driver so I'm not sure how
- (or if) it works around this problem, but as we don't know how to
- rewind the scanner head to do these bits again, there's currently no
+ fer is full). Basically it's a mechanical problem inside the scanner,
+ that the tolerance of movement for a start/stop event is greater than
+ 1/600 inches. I've never tried the windows driver so I'm not sure how
+ (or if) it works around this problem, but as we don't know how to
+ rewind the scanner head to do these bits again, there's currently no
nice way to deal with the problem.
Grey-scale Scans
Be aware that the scanner uses the green LEDs to read grey-scale scans,
- meaning green coloured things will appear lighter than normal, and red
+ meaning green coloured things will appear lighter than normal, and red
and blue coloured items will appear darker than normal. For high-accu-
racy grey-scale scans of colour items, it's best just to scan in colour
and convert to grey-scale in graphics software such as the GIMP.
FB620P/FB320P Caveats
- These models can not be reset in the same way as the others. The win-
- dows driver doesn't know how to reset them either - when left with an
+ These models can not be reset in the same way as the others. The win-
+ dows driver doesn't know how to reset them either - when left with an
inconsistent scanner, it will start scanning half way down the page!
- Aborting is known to work correctly on the FB*30P models, and is known
+ Aborting is known to work correctly on the FB*30P models, and is known
to be broken on the FB*20P models. The FB620P which I tested on simply
returns garbage after a scan has been aborted using the method we know.
- Aborting is able to leave the scanner in a state where it can be shut
+ Aborting is able to leave the scanner in a state where it can be shut
down, but not where another scan can be made.
SEE ALSO
- sane(7), sane-dll(5) http://canon-fb330p.sourceforge.net/
+ sane(7), sane-dll(5), libieee1284(3),
+ http://canon-fb330p.sourceforge.net/
diff --git a/man/sane-cardscan.5.html b/man/sane-cardscan.5.html
index 481a0b80..d3817148 100644
--- a/man/sane-cardscan.5.html
+++ b/man/sane-cardscan.5.html
@@ -2,7 +2,7 @@
sane-cardscan.5
-
+
sane-cardscan.5
@@ -33,16 +33,16 @@
OPTIONS
The cardscan backend supports the following options:
- mode m
- Selects the mode for the scan. Options are "Gray" and "Color".
+ --mode Gray|Color
+ Selects the mode for the scan.
CONFIGURATION FILE
- The configuration file "cardscan.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
+ The configuration file cardscan.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 use a set of compiled
defaults, which are identical to the default configuration file shipped
with SANE.
@@ -50,9 +50,9 @@
Scanners can be specified in the configuration file in 2 ways:
"usb 0x04c5 0x1042" (or other vendor/product ids)
- Requests backend to search all usb busses in the system for a
- device which uses that vendor and product id. The device will
- then be queried to determine if it is a cardscan scanner.
+ Requests backend to search all usb buses in the system for a de-
+ vice which uses that vendor and product id. The device will then
+ be queried to determine if it is a cardscan scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
@@ -62,8 +62,8 @@
tocol used by the backend:
"lines_per_block 16" (or other number from 1 to 32)
- Controls the number of lines of image data which will be
- acquired in each pass. Older scanners will require this number
+ Controls the number of lines of image data which will be ac-
+ quired in each pass. Older scanners will require this number
set lower, often 1.
"has_cal_buffer 1" (1 or 0)
@@ -74,7 +74,7 @@
ENVIRONMENT
- The backend uses a single environment variable, SANE_DEBUG_CARDSCAN,
+ The backend uses a single environment variable, SANE_DEBUG_CARDSCAN,
which enables debugging output to stderr. Valid values are:
5 Errors
@@ -100,8 +100,8 @@
CREDITS
- The hardware to build this driver was provided to the author by:
- Jeff Kowalczyk <jtk a t yahoo d o t com>
+ The hardware to build this driver was provided to the author by: Jeff
+ Kowalczyk <jtk a t yahoo d o t com>.
@@ -111,7 +111,7 @@
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com> .
10 Feb 2010 sane-cardscan(5)
diff --git a/man/sane-config.1.html b/man/sane-config.1.html
index 358629d6..eb2b9a4b 100644
--- a/man/sane-config.1.html
+++ b/man/sane-config.1.html
@@ -2,7 +2,7 @@
sane-config.1
-
+
sane-config.1
@@ -24,7 +24,7 @@
DESCRIPTION
sane-config is a tool that is used to determine the compiler and linker
- flags that should be used to compile and link SANE frontends to a SANE
+ flags that should be used to compile and link SANE frontends to a SANE
backend library (libsane).
@@ -38,18 +38,18 @@
dard output.
--help OPTION
- Print a short usage message. If OPTION is specified, help for
- that option (e.g. --libs) is printed (if available).
+ Print a short usage message. If OPTION is specified, help for
+ that option (e.g. --libs) is printed (if available).
--libs Print the additional libraries that are necessary to link a
- SANE frontend to libsane.
+ SANE frontend to libsane.
--ldflags
- Print the linker flags that are necessary to link a SANE fron-
- tend to libsane.
+ Print the linker flags that are necessary to link a SANE front-
+ end to libsane.
--cflags
- Print the compiler flags that are necessary to compile a SANE
+ Print the compiler flags that are necessary to compile a SANE
frontend.
--prefix
@@ -66,7 +66,7 @@
AUTHOR
- This manual page was written by Julien BLACHE <jblache@debian.org>, for
+ This manual page was written by Julien BLACHE <jblache@debian.org>, for
the Debian GNU/Linux system (but may be used by others).
10 Jul 2008 sane-config(1)
diff --git a/man/sane-coolscan.5.html b/man/sane-coolscan.5.html
index 900159b4..37c09c5f 100644
--- a/man/sane-coolscan.5.html
+++ b/man/sane-coolscan.5.html
@@ -2,7 +2,7 @@
sane-coolscan.5
-
+
sane-coolscan.5
@@ -17,7 +17,7 @@
ABOUT THIS FILE
- This file is a short description of the coolscan-backend for sane!
+ This file is a short description of the coolscan backend for SANE.
@@ -27,20 +27,20 @@
LS30, LS1000, LS2000.
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.
+ 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.
CONFIGURATION
- The configuration file for this backend resides in
- /usr/local/etc/sane.d/coolscan.conf.
+ The configuration file for this backend resides in /usr/lo-
+ cal/etc/sane.d/coolscan.conf.
- Its contents is a list of device names that correspond to Nikon
- Coolscan scanners. Empty lines and lines starting with a hash mark (#)
- are ignored. A sample configuration file is shown below:
+ Its content is a list of device names that correspond to Nikon Coolscan
+ scanners. Empty lines and lines starting with a hash mark (#) are ig-
+ nored. A sample configuration file is shown below:
#scsi Vendor Model Type
scsi Nikon * Scanner
@@ -48,8 +48,8 @@
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.
+ and how you can set the permissions of that device, have a look at
+ sane-scsi(5).
@@ -57,8 +57,8 @@
Some SCSI-adapters and low-level SCSI drivers do not work correctly
with this backend and the Coolscan scanners. These systems hang when
the autofocus command is send to the Scanner. To see a list of which
- card/driver combinations work or don't work have a look at:
- http://andreas.rick.free.fr/sane/autofocus.html.
+ card/driver combinations work or don't work have a look at: http://an-
+ dreas.rick.free.fr/sane/autofocus.html.
@@ -77,45 +77,45 @@
ENVIRONMENT
SANE_DEBUG_COOLSCAN
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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_COOLSCAN values
+ Smaller levels reduce verbosity.
Examples:
- on bash:
+ On bash:
export SANE_DEBUG_COOLSCAN=8
- on csh:
+ On csh:
setenv SANE_DEBUG_COOLSCAN 8
BUGS
The autofocus command does not work with some SCSI card/driver combina-
- tions
+ tions.
The gamma table is not implemented for the LS1000 yet.
- The dust-removal is not working yet
+ The dust-removal is not working yet.
SEE ALSO
+ sane(7), sane-scsi(5)
+
http://andreas.rick.free.fr/sane/
- The homepage of this backend
+ The homepage of this backend.
http://www.sema.be/coolscan/
- The original version of the coolscan backend by Didier
-
- sane(7), sane-scsi(5)
+ The original version of the coolscan backend by Didier.
THANKS TO
Didier Carlier - For writing the original Coolscan backend (without it
- I would not have started this)
+ I would not have started this).
Oliver Rauch - For adapting xsane so quickly to the infrared stuff.
@@ -129,7 +129,7 @@
EMAIL-CONTACT
- andreas.rick@free.fr
+ andreas.rick@free.fr
13 Jul 2008 sane-coolscan(5)
diff --git a/man/sane-coolscan2.5.html b/man/sane-coolscan2.5.html
index eb158b92..17f1e810 100644
--- a/man/sane-coolscan2.5.html
+++ b/man/sane-coolscan2.5.html
@@ -2,7 +2,7 @@
sane-coolscan2.5
-
+
sane-coolscan2.5
@@ -20,8 +20,8 @@
The sane-coolscan2 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 beta-quality software.
- Most functions have been stable for a long time, but of course new
- development can not and will not function properly from the very first
+ Most functions have been stable for a long time, but of course new de-
+ velopment can not and will not function properly from the very first
day. Please report any strange behaviour to the maintainer of the back-
end.
@@ -42,102 +42,107 @@
OPTIONS
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.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
+
+ Valid command line options and their syntax can be listed by using:
- Valid command line options and their syntax can be listed by using
scanimage --help -d coolscan2:<interface>:<device>
+
where <interface> and <device> specify the device in question, as in
- the configuration file (see next section). The -d parameter and its
- argument can be omitted to obtain information on the first scanner
- identified. Use the command
+ the configuration file (see next section). The -d parameter and its ar-
+ gument can be omitted to obtain information on the first scanner iden-
+ tified. Use the command:
+
scanimage -L
+
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 syntax with which they must be supplied to scanimage:
+ options, in the syntax with which they must be supplied to scanim-
+ age(1):
- --frame <n>
- This option specifies which frame to operate on, if a motorized
- film strip feeder or APS adapter are used. The frame number <n>
+ --frame <n>
+ This option specifies which frame to operate on, if a motorized
+ film strip feeder or APS adapter are used. The frame number <n>
ranges from 1 to the number of frames available, which is sensed
- each time the backend is initialized (usually each time you
+ each time the backend is initialized (usually each time you
start the frontend).
- --subframe <x>
- This option shifts the scan window by the specified amount
- (default unit is mm).
+ --subframe <x>
+ This option shifts the scan window by the specified amount (de-
+ fault unit is mm).
- --infrared=yes/no
- If set to "yes", the scanner will read the infrared channel,
- thus allowing defect removal in software. The infrared image is
- read during a second scan, with no options altered. The backend
- must not be restarted between the scans. If you use scanimage,
- perform a batch scan with batch-count=2 to obtain the IR infor-
- mation.
+ --infrared=yes/no
+ If set to "yes", the scanner will read the infrared channel,
+ thus allowing defect removal in software. The infrared image is
+ read during a second scan, with no options altered. The backend
+ must not be restarted between the scans. If you use scanim-
+ age(1), perform a batch scan with batch-count=2 to obtain the IR
+ information.
- --depth <n>
+ --depth <n>
Here <n> can either be 8 or the maximum number of bits supported
- by the scanner (10, 12, or 14). It specifies whether or not the
- scanner reduces the scanned data to 8 bits before sending it to
+ by the scanner (10, 12, or 14). It specifies whether or not the
+ scanner reduces the scanned data to 8 bits before sending it to
the backend. If 8 bits are used, some information and thus image
- quality is lost, but the amount of data is smaller compared to
- higher depths. Also, many imaging programs and image formats
+ quality is lost, but the amount of data is smaller compared to
+ higher depths. Also, many imaging programs and image formats
cannot handle depths greater than 8 bits.
- --autofocus
- Perform autofocus operation. Unless otherwise specified by the
- other options ( --focus-on-centre and friends), focusing is per-
+ --autofocus
+ Perform autofocus operation. Unless otherwise specified by the
+ other options ( --focus-on-centre and friends), focusing is per-
formed on the centre of the selected scan area.
- --ae-wb
+ --ae-wb
- --ae Perform a pre-scan to calculate exposure values automatically.
- --ae-wb will maintain the white balance, while --ae will adjust
+ --ae Perform a pre-scan to calculate exposure values automatically.
+ --ae-wb will maintain the white balance, while --ae will adjust
each channel separately.
- --exposure
- Multiply all exposure times with this value. This allows expo-
+ --exposure
+ Multiply all exposure times with this value. This allows expo-
sure correction without modifying white balance.
- --load Load the next slide when using the slide loader.
+ --load Load the next slide when using the slide loader.
- --eject
- Eject the film strip or mounted slide when using the slide
+ --eject
+ Eject the film strip or mounted slide when using the slide
loader.
- --reset
- Reset scanner. The scanner will perform the same action as when
- power is turned on: it will eject the film strip and calibrate
- itself. Use this whenever the scanner refuses to load a film
- strip properly, as a result of which --eject does not work.
+ --reset
+ Reset scanner. The scanner will perform the same action as when
+ power is turned on: it will eject the film strip and calibrate
+ itself. Use this whenever the scanner refuses to load a film
+ strip properly, as a result of which --eject does not work.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/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 con-
+ The configuration file /usr/local/etc/sane.d/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 con-
figuration file supplied with the SANE distribution should work without
being edited.
- Each line in the configuration file is either of the following, where
+ Each line in the configuration file is either of the following, where
all entries are case-sensitive:
blank or starting with a '#' character
- These lines are ignored, thus '#' can be used to include com-
+ These lines are ignored, thus '#' can be used to include com-
ments.
containing only the word "auto"
- This instructs the backend to probe for a scanner by scanning
- the buses for devices with know identifiers. This is the action
- taken when no configuration file is present.
+ This instructs the backend to probe for a scanner by scanning
+ the buses for devices with known identifiers. This is the de-
+ fault action when no configuration file is present.
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 SANE as
+ 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 SANE as
SCSI devices.
@@ -151,16 +156,16 @@
that support dynamic loading).
/usr/local/etc/sane.d/coolscan2.conf
- Configuration file for this backend, read each time the backend
+ Configuration file for this backend, read each time the backend
is initialized.
ENVIRONMENT
SANE_DEBUG_COOLSCAN2
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -171,27 +176,27 @@
BUGS
- Currently, the SANE protocol does not allow automatically updating
- options whenever the hardware changes. Thus the number of choices for
- the --frame option will be fixed when the backend is initialized (usu-
- ally when the user runs the frontend). In particular, if there is no
- film strip in the automatic film strip feeder when the backend is ini-
- tialized, the frame option will not appear at all. Also, restarting the
+ Currently, the SANE protocol does not allow automatically updating op-
+ tions whenever the hardware changes. Thus the number of choices for the
+ --frame option will be fixed when the backend is initialized (usually
+ when the user runs the frontend). In particular, if there is no film
+ strip in the automatic film strip feeder when the backend is initial-
+ ized, the frame option will not appear at all. Also, restarting the
frontend after swapping film adapters is strongly recommended.
- Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
+ Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
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
+ 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 backend main-
+ No real bugs currently known, please report any to the backend main-
tainer or the SANE developers' email list.
AUTHORS
- The backend is written and maintained by Andras Major
- (andras@users.sourceforge.net).
+ The backend is written and maintained by Andras Major <an-
+ dras@users.sourceforge.net>.
11 Jul 2008 sane-coolscan2(5)
diff --git a/man/sane-coolscan3.5.html b/man/sane-coolscan3.5.html
index e5313d0d..783018a3 100644
--- a/man/sane-coolscan3.5.html
+++ b/man/sane-coolscan3.5.html
@@ -2,7 +2,7 @@
sane-coolscan3.5
-
+
sane-coolscan3.5
@@ -20,8 +20,8 @@
The sane-coolscan3 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 beta-quality software.
- Most functions have been stable for a long time, but of course new
- development can not and will not function properly from the very first
+ Most functions have been stable for a long time, but of course new de-
+ velopment can not and will not function properly from the very first
day.
At present, the following scanners are known to work with this backend:
@@ -35,109 +35,114 @@
LS-4000 ED IEEE 1394
LS-8000 ED IEEE 1394
- Please send mail to sane-devel@alioth-lists.debian.net to report suc-
+ Please send mail to sane-devel@alioth-lists.debian.net to report suc-
cesses or failures.
OPTIONS
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.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
+
+ Valid command line options and their syntax can be listed by using:
- Valid command line options and their syntax can be listed by using
scanimage --help -d coolscan3:<interface>:<device>
+
where <interface> and <device> specify the device in question, as in
- the configuration file (see next section). The -d parameter and its
- argument can be omitted to obtain information on the first scanner
- identified. Use the command
+ the configuration file (see next section). The -d parameter and its ar-
+ gument can be omitted to obtain information on the first scanner iden-
+ tified. Use the command:
+
scanimage -L
+
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 syntax with which they must be supplied to scanimage:
+ options, in the syntax with which they must be supplied to scanim-
+ age(1):
- --frame <n>
- This option specifies which frame to operate on, if a motorized
- film strip feeder or APS adapter are used. The frame number <n>
+ --frame <n>
+ This option specifies which frame to operate on, if a motorized
+ film strip feeder or APS adapter are used. The frame number <n>
ranges from 1 to the number of frames available, which is sensed
- each time the backend is initialized (usually each time you
+ each time the backend is initialized (usually each time you
start the frontend).
- --subframe <x>
- This option shifts the scan window by the specified amount
- (default unit is mm).
+ --subframe <x>
+ This option shifts the scan window by the specified amount (de-
+ fault unit is mm).
- --infrared=yes/no
- If set to "yes", the scanner will read the infrared channel,
- thus allowing defect removal in software. The infrared image is
- read during a second scan, with no options altered. The backend
- must not be restarted between the scans. If you use scanimage,
- perform a batch scan with batch-count=2 to obtain the IR infor-
+ --infrared=yes/no
+ If set to "yes", the scanner will read the infrared channel,
+ thus allowing defect removal in software. The infrared image is
+ read during a second scan, with no options altered. The backend
+ must not be restarted between the scans. If you use scanimage,
+ perform a batch scan with batch-count=2 to obtain the IR infor-
mation.
- --depth <n>
+ --depth <n>
Here <n> can either be 8 or the maximum number of bits supported
- by the scanner (10, 12, or 14). It specifies whether or not the
- scanner reduces the scanned data to 8 bits before sending it to
+ by the scanner (10, 12, or 14). It specifies whether or not the
+ scanner reduces the scanned data to 8 bits before sending it to
the backend. If 8 bits are used, some information and thus image
- quality is lost, but the amount of data is smaller compared to
- higher depths. Also, many imaging programs and image formats
+ quality is lost, but the amount of data is smaller compared to
+ higher depths. Also, many imaging programs and image formats
cannot handle depths greater than 8 bits.
- --autofocus
- Perform autofocus operation. Unless otherwise specified by the
- other options ( --focus-on-centre and friends), focusing is per-
+ --autofocus
+ Perform autofocus operation. Unless otherwise specified by the
+ other options ( --focus-on-centre and friends), focusing is per-
formed on the centre of the selected scan area.
- --ae-wb
+ --ae-wb
- --ae Perform a pre-scan to calculate exposure values automatically.
- --ae-wb will maintain the white balance, while --ae will adjust
+ --ae Perform a pre-scan to calculate exposure values automatically.
+ --ae-wb will maintain the white balance, while --ae will adjust
each channel separately.
- --exposure
- Multiply all exposure times with this value. This allows expo-
+ --exposure
+ Multiply all exposure times with this value. This allows expo-
sure correction without modifying white balance.
- --load Load the next slide when using the slide loader.
+ --load Load the next slide when using the slide loader.
- --eject
- Eject the film strip or mounted slide when using the slide
+ --eject
+ Eject the film strip or mounted slide when using the slide
loader.
- --reset
- Reset scanner. The scanner will perform the same action as when
- power is turned on: it will eject the film strip and calibrate
- itself. Use this whenever the scanner refuses to load a film
- strip properly, as a result of which --eject does not work.
+ --reset
+ Reset scanner. The scanner will perform the same action as when
+ power is turned on: it will eject the film strip and calibrate
+ itself. Use this whenever the scanner refuses to load a film
+ strip properly, as a result of which --eject does not work.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/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 con-
+ The configuration file /usr/local/etc/sane.d/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 con-
figuration file supplied with the SANE distribution should work without
being edited.
- Each line in the configuration file is either of the following, where
+ Each line in the configuration file is either of the following, where
all entries are case-sensitive:
blank or starting with a '#' character
- These lines are ignored, thus '#' can be used to include com-
+ These lines are ignored, thus '#' can be used to include com-
ments.
containing only the word "auto"
- This instructs the backend to probe for a scanner by scanning
- the buses for devices with know identifiers. This is the action
+ This instructs the backend to probe for a scanner by scanning
+ the buses for devices with know identifiers. This is the action
taken when no configuration file is present.
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 SANE as
+ 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 SANE as
SCSI devices.
@@ -151,37 +156,37 @@
that support dynamic loading).
/usr/local/etc/sane.d/coolscan3.conf
- Configuration file for this backend, read each time the backend
+ Configuration file for this backend, read each time the backend
is initialized.
ENVIRONMENT
SANE_DEBUG_COOLSCAN3
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
SEE ALSO
- sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1)
+ sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1)
BUGS
- Currently, the SANE protocol does not allow automatically updating
- options whenever the hardware changes. Thus the number of choices for
- the --frame option will be fixed when the backend is initialized (usu-
- ally when the user runs the frontend). In particular, if there is no
- film strip in the automatic film strip feeder when the backend is ini-
- tialized, the frame option will not appear at all. Also, restarting the
+ Currently, the SANE protocol does not allow automatically updating op-
+ tions whenever the hardware changes. Thus the number of choices for the
+ --frame option will be fixed when the backend is initialized (usually
+ when the user runs the frontend). In particular, if there is no film
+ strip in the automatic film strip feeder when the backend is initial-
+ ized, the frame option will not appear at all. Also, restarting the
frontend after swapping film adapters is strongly recommended.
- Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
+ Linux kernels prior to 2.4.19 had a patch that truncated INQUIRY data
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
+ 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 SANE developers'
@@ -190,8 +195,8 @@
AUTHORS
- coolscan3 written by A. Zummo (a.zummo@towertech.it), based heavily on
- coolscan2 written by Andras Major (andras@users.sourceforge.net).
+ coolscan3 written by A. Zummo <a.zummo@towertech.it>, based heavily on
+ coolscan2 written by Andras Major <andras@users.sourceforge.net>.
11 Jul 2008 sane-coolscan3(5)
diff --git a/man/sane-dc210.5.html b/man/sane-dc210.5.html
index 7d0661ef..27e9d404 100644
--- a/man/sane-dc210.5.html
+++ b/man/sane-dc210.5.html
@@ -2,7 +2,7 @@
sane-dc210.5
-
+
sane-dc210.5
@@ -18,8 +18,8 @@
DESCRIPTION
The sane-dc210 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!!
+ backend that provides access to the Kodak DC210 camera. THIS IS EX-
+ TREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
@@ -31,22 +31,22 @@
CONFIGURATION
The contents of the dc210.conf specify the serial port and baud rate to
- use. The baud rate specifies the maximum rate to use while downloading
+ use. The baud 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 exces-
sively busy and the "interrupt-unmask flag" is set in the IDE driver
- (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
+ (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
115200.
- The dumpinquiry line causes some information about the camera to be
+ The dumpinquiry line causes some information about the camera to be
printed.
- cmdrespause specifies how many usec (1,000,000ths of a) between writing
+ cmdrespause specifies how many usec (1,000,000ths of a) between writing
the command and reading the result should be used. 125000 seems to be
the lowest I could go reliably.
- breakpause is the time in 1,000,000ths of a usec between sending the
+ breakpause is the time in 1,000,000ths of a usec between sending the
"back to default" break sending commands.
Empty lines and lines starting with a hash mark (#) are ignored. A
@@ -82,13 +82,13 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_DC210
If the library was compiled with debugging support enabled, this
@@ -119,7 +119,7 @@
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). You must
+ 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.
diff --git a/man/sane-dc240.5.html b/man/sane-dc240.5.html
index 14a6da9d..c9882b25 100644
--- a/man/sane-dc240.5.html
+++ b/man/sane-dc240.5.html
@@ -2,7 +2,7 @@
sane-dc240.5
-
+
sane-dc240.5
@@ -18,8 +18,8 @@
DESCRIPTION
The sane-dc240 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!!
+ backend that provides access to the Kodak DC240 camera. THIS IS EX-
+ TREMELY ALPHA CODE! USE AT YOUR OWN RISK!!
@@ -31,22 +31,22 @@
CONFIGURATION
The contents of the dc240.conf specify the serial port and baud rate to
- use. The baud rate specifies the maximum rate to use while downloading
+ use. The baud 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 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). Sup-
+ "interrupt-unmask flag" is set in the IDE driver (hdparm -u1). Sup-
ported baud rates are: 9600, 19200, 38400, 57600, and 115200.
- The dumpinquiry line causes some information about the camera to be
+ The dumpinquiry line causes some information about the camera to be
printed.
- cmdrespause specifies how many usec (1,000,000ths of a) between writing
+ cmdrespause specifies how many usec (1,000,000ths of a) between writing
the command and reading the result should be used. 125000 seems to be
the lowest I could go reliably.
- breakpause is the time in 1,000,000ths of a usec between sending the
+ breakpause is the time in 1,000,000ths of a usec between sending the
"back to default" break sending commands.
Empty lines and lines starting with a hash mark (#) are ignored. A
@@ -82,13 +82,13 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_DC240
If the library was compiled with debugging support enabled, this
@@ -114,15 +114,15 @@
BUGS
- The major limitation that I know of is that the backend assumes the
- directory in the camera is 100dc240. Once the camera has taken more
- than 9999 pictures, the directory will increment to 101dc240. Not only
+ The major limitation that I know of is that the backend assumes the di-
+ rectory in the camera is 100dc240. Once the camera has taken more than
+ 9999 pictures, the directory will increment to 101dc240. Not only
should we check for the additional directory, but pictures may actually
be found in multiple directories.
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). You must
+ 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.
diff --git a/man/sane-dc25.5.html b/man/sane-dc25.5.html
index 28d7e65f..993ac058 100644
--- a/man/sane-dc25.5.html
+++ b/man/sane-dc25.5.html
@@ -2,7 +2,7 @@
sane-dc25.5
-
+
sane-dc25.5
@@ -37,13 +37,13 @@
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 exces-
sively busy and the "interrupt-unmask flag" is set in the IDE driver
- (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
+ (hdparm -u1). Supported baud rates are: 9600, 19200, 38400, 57600, and
115200.
The dumpinquiry line causes some information about the camera to be
printed to stderr during startup. Note: This is not compatible with
- saned, so make sure you don't have any dumpinquiry lines if you are
- using saned (i.e. scanning on a remote machine using a network).
+ saned, so make sure you don't have any dumpinquiry lines if you are us-
+ ing saned (i.e. scanning on a remote machine using a network).
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
@@ -76,13 +76,13 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_DC25
If the library was compiled with debugging support enabled, this
@@ -98,7 +98,7 @@
AUTHOR
- Peter Fales, dc25-devel@fales-lorenz.net
+ Peter Fales, dc25-devel@fales-lorenz.net.
@@ -112,7 +112,7 @@
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). You must
+ 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.
diff --git a/man/sane-dll.5.html b/man/sane-dll.5.html
index f06a0875..d0115402 100644
--- a/man/sane-dll.5.html
+++ b/man/sane-dll.5.html
@@ -2,7 +2,7 @@
sane-dll.5
-
+
sane-dll.5
@@ -19,8 +19,8 @@
DESCRIPTION
The sane-dll library implements a SANE (Scanner Access Now Easy) back-
end that provides access to an arbitrary number of other SANE backends.
- These backends may either be pre-loaded at the time the sane-dll
- library is built or, on systems that support dynamic loading of shared
+ These backends may either be pre-loaded at the time the sane-dll li-
+ brary is built or, on systems that support dynamic loading of shared
libraries, the backends may be loaded at runtime. In the latter case,
adding support for a new backend simply involves installing the rele-
vant library in /usr/local/lib/sane and adding an entry to the dll.conf
@@ -45,8 +45,8 @@
CONFIGURATION
The contents of the dll.conf file is a list of backend names that may
- be loaded dynamically upon demand. Empty lines are ignored, also
- everything after a hash mark (#). A sample configuration file is shown
+ be loaded dynamically upon demand. Empty lines are ignored, also ev-
+ erything after a hash mark (#). A sample configuration file is shown
below:
net
@@ -70,8 +70,8 @@
After changing the value of this macro, it is necessary to reconfigure,
rebuild, and reinstall SANE for the change to take effect.
- Aliases are defined in the config file dll.aliases. It can contain
- entries of the form
+ Aliases are defined in the config file dll.aliases. It can contain en-
+ tries of the form
alias SomeName SaneDeviceName
alias "Some Name" SaneDeviceName
@@ -90,9 +90,8 @@
The idea is that users don't have to deal with complicated device names
(especially for networked devices), and to hide other exported devices
- which might confuse them. Note that a hidden device can still be
- accessed if the device name is known, it just doesn't appear on the
- list.
+ which might confuse them. Note that a hidden device can still be ac-
+ cessed if the device name is known, it just doesn't appear on the list.
@@ -101,7 +100,7 @@
The list of aliased or hidden backends.
/usr/local/etc/sane.d/dll.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-dll.a
@@ -117,21 +116,21 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_DLL
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
Value Description
diff --git a/man/sane-dmc.5.html b/man/sane-dmc.5.html
index 53edad85..08d7bb10 100644
--- a/man/sane-dmc.5.html
+++ b/man/sane-dmc.5.html
@@ -2,7 +2,7 @@
sane-dmc.5
-
+
sane-dmc.5
@@ -61,8 +61,8 @@
and interpolation is done in software, so this mode is very
slow. Also, this mode places restrictions on how the image is
read which means that the "preview" mode of xscanimage does not
- work in Super Resolution mode. (xcam and the non-preview modes
- of scanimage and xscanimage work fine, however.)
+ work in Super Resolution mode. (xcam(1) and the non-preview
+ modes of scanimage(1) and xscanimage(1) work fine, however.)
@@ -115,17 +115,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_DMC
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -139,7 +139,7 @@
line, it returns SANE_STATUS_INVAL.
In the "Super Resolution" mode, images must be read in units of two
- lines (3198 pixels or 9594 bytes.) If you try to read less than two
+ 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.
@@ -157,8 +157,7 @@
AUTHOR
David F. Skoll
- The backend is derived from sane-hp by David Mosberger
-
+ The backend is derived from sane-hp(5) by David Mosberger
13 Jul 2008 sane-dmc(5)
diff --git a/man/sane-epjitsu.5.html b/man/sane-epjitsu.5.html
index 7654314f..6747c4e5 100644
--- a/man/sane-epjitsu.5.html
+++ b/man/sane-epjitsu.5.html
@@ -2,7 +2,7 @@
sane-epjitsu.5
-
+
sane-epjitsu.5
@@ -38,31 +38,31 @@
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
+ the ADF setting. The sane-epjitsu backend supports the following basic
options for most scanners:
- source s
+ sources
Selects the source for the scan. Options may include "Flatbed",
"ADF Front", "ADF Back", "ADF Duplex".
- mode m
+ modem
Selects the mode for the scan. Options may include "Lineart",
"Gray", "Color".
- resolution, y-resolution
- Controls scan resolution. Setting --resolution also sets
- --y-resolution, though this behavior is overridden by some fron-
- tends.
+ resolution,y-resolution
+ Controls scan resolution. Setting --resolution also sets
+ --y-resolution, though this behavior is overridden by some
+ frontends.
Other options will be available based on the capabilities of the scan-
- ner. Use 'scanimage --help' to get a list. Be aware that some options
- may appear only when another option has been set, and that advanced
- options may be hidden by the frontend.
+ ner. Use 'scanimage --help' to get a list. Be aware that some options
+ may appear only when another option has been set, and that advanced op-
+ tions may be hidden by the frontend.
CONFIGURATION FILE
- The configuration file "/usr/local/etc/sane.d/epjitsu.conf" is used to
+ The configuration file /usr/local/etc/sane.d/epjitsu.conf is used to
tell the backend how to look for scanners, and provide options control-
ling the operation of the backend. This file is read each time the
frontend asks the backend for a list of scanners, generally only when
@@ -72,17 +72,17 @@
Scanners can be specified in the configuration file in two ways:
"usb 0x04c5 0x10c7" (or other vendor/product ids)
- Requests backend to search all usb busses in the system for a
- device which uses that vendor and product id. The device will
- then be queried to determine if it is a supported scanner.
+ Requests backend to search all usb buses in the system for a de-
+ vice which uses that vendor and product id. The device will then
+ be queried to determine if it is a supported scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
method is untested.
The only configuration option supported is "firmware /PATH/TO/FILE",
- allowing you to set the location of the firmware file you have
- extracted from the Windows driver.
+ allowing you to set the location of the firmware file you have ex-
+ tracted from the Windows driver.
Note: This firmware is a copyrighted work of Fujitsu, so cannot be pro-
vided by the backend or the author. Please do not ask.
@@ -97,7 +97,7 @@
ENVIRONMENT
- The backend uses a single environment variable, SANE_DEBUG_EPJITSU,
+ The backend uses a single environment variable, SANE_DEBUG_EPJITSU,
which enables debugging output to stderr. Valid values are:
5 Errors
@@ -125,12 +125,12 @@
SEE ALSO
- sane(7), sane-usb(5)
+ sane(7), sane-usb(5) scanimage(1)
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com>
11 Apr 2017 sane-epjitsu(5)
diff --git a/man/sane-epson.5.html b/man/sane-epson.5.html
index fbcf548a..479abead 100644
--- a/man/sane-epson.5.html
+++ b/man/sane-epson.5.html
@@ -2,7 +2,7 @@
sane-epson.5
-
+
sane-epson.5
@@ -17,13 +17,12 @@
DESCRIPTION
- The sane-epson library implements a SANE (Scanner Access Now Easy)
- backend that provides access to Epson flatbed scanners. Some functions
- of this backend should be considered beta-quality software! Most func-
- tions have been stable for a long time, but of course new development
- can not and often times will not function properly from the very first
- day. Please report any strange behavior to the maintainer of the back-
- end.
+ The sane-epson library implements a SANE Scanner Access Now Easy) back-
+ end that provides access to Epson flatbed scanners. Some functions of
+ this backend should be considered beta-quality software! Most functions
+ have been stable for a long time, but of course new development can not
+ and often times will not function properly from the very first day.
+ Please report any strange behavior to the maintainer of the backend.
At present, the following scanners are known to work with this backend:
@@ -54,177 +53,179 @@
and many more. The official list is on the Sane web site.
For other scanners the software may or may not work. Please send mail
- to the backend author (khk@khk.net) to report success with scanners not
+ to the backend author (khk@khk.net) to report success with scanners not
on the list or problems with scanners that are listed.
OPTIONS
The options the backend supports can either be selected through command
- line options to programs like scanimage or through GUI elements in pro-
- grams like xscanimage or xsane.
+ line options to programs like scanimage(1) or through GUI elements in
+ programs like xscanimage(1) or xsane(1).
+
+ Valid command line options and their syntax can be listed by using:
- Valid command line options and their syntax can be listed by using
scanimage --help -d epson
+
Not all devices support all options.
Scan Mode
- The --mode switch selects the basic mode of operation of the
- scanner. Valid choices are Binary, Gray and Color. The Binary
- mode is black and white only, Gray will produce 256 levels of
- gray or more depending on the scanner and Color means 24 bit
+ The --mode switch selects the basic mode of operation of the
+ scanner. Valid choices are Binary, Gray and Color. The Binary
+ mode is black and white only, Gray will produce 256 levels of
+ gray or more depending on the scanner and Color means 24 bit
color mode or more depending on the scanner. Some scanners will
- internally use 36 bit color, their external interface however
+ internally use 36 bit color, their external interface however
may only support 24 bits.
- The --depth option selects the bit depth the scanner is using.
- This option is only available for scanners that support more
- than one bit depth. Older scanners will always transfer the
- image in 8bit mode. Newer scanners allow one to select either 8
- bits, 12 or 14 bits per color channel. For a color scan this
- means an effective color depth of 36 or 42 bits over all three
+ The --depth option selects the bit depth the scanner is using.
+ This option is only available for scanners that support more
+ than one bit depth. Older scanners will always transfer the im-
+ age in 8bit mode. Newer scanners allow one to select either 8
+ bits, 12 or 14 bits per color channel. For a color scan this
+ means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
- The --halftoning switch selects the mode that is used in Binary
- mode. Valid options are "None", "Halftone A (Hard Tone)",
- "Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
- (4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
- Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
- ogy", "Download pattern A", and "Download pattern B".
+ The --halftoning switch selects the mode that is used in Binary
+ mode. Valid options are "None", "Halftone A (Hard Tone)", "Half-
+ tone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A (4x4
+ Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net Screen)",
+ "Dither D (8x4 Net Screen)", "Text Enhanced Technology", "Down-
+ load pattern A", and "Download pattern B".
- The --dropout switch selects the so called dropout color. Valid
- options are None, Red, Green and Blue. The default is None. The
- dropout color is used for monochrome scanning and selects the
- color that is not scanned. This can be used to e.g. scan an
+ The --dropout switch selects the so called dropout color. Valid
+ options are None, Red, Green and Blue. The default is None. The
+ dropout color is used for monochrome scanning and selects the
+ color that is not scanned. This can be used to e.g. scan an
original with a colored background.
- The --brightness switch controls the brightness of the scan.
+ The --brightness switch controls the brightness of the scan.
Valid options are integer values from -3 to 3. The default is 0.
The larger the brightness value, the brighter the image gets. If
- a user defined table for the gamma correction is selected, the
+ a user defined table for the gamma correction is selected, the
brightness parameter is not available.
- The --sharpness switch sets the sharpness of the image data.
- Valid options are integer values from -2 to 2, with -2 meaning
- "Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen
+ The --sharpness switch sets the sharpness of the image data.
+ Valid options are integer values from -2 to 2, with -2 meaning
+ "Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen
slightly" and 2 "Sharpen".
- The --gamma-correction switch controls the scanner's internal
- gamma correction. Valid options are "Default", "User defined",
- "High density printing" "Low density printing" and "High con-
+ The --gamma-correction switch controls the scanner's internal
+ gamma correction. Valid options are "Default", "User defined",
+ "High density printing" "Low density printing" and "High con-
trast printing".
- The --color-correction switch controls the scanner's internal
- color correction function. Valid options are "No Correction",
- "Impact-dot printers", "Thermal printers", "Ink-jet printers"
+ The --color-correction switch controls the scanner's internal
+ color correction function. Valid options are "No Correction",
+ "Impact-dot printers", "Thermal printers", "Ink-jet printers"
and "CRT monitors". The default is "CRT monitors".
- The --resolution switch selects the resolution for a scan. Some
- EPSON scanners will scan in any resolution between the lowest
+ The --resolution switch selects the resolution for a scan. Some
+ EPSON scanners will scan in any resolution between the lowest
and highest possible value. The list reported by the scanner can
- be displayed using the "--help -d epson" parameters to scanim-
- age.
+ be displayed using the "--help -d epson" parameters to scanim-
+ age(1).
- The --mirror option controls the way the image is scanned. By
+ The --mirror option controls the way the image is scanned. By
reading the image data from right to left the image is mirrored.
Valid options are "yes" and "no". The default is "no".
- The --speed option can improve the scan speed in monochrome
- mode. Valid options are "yes" or "no", the "yes" option will
+ The --speed option can improve the scan speed in monochrome
+ mode. Valid options are "yes" or "no", the "yes" option will
speed up the scan if this option is supported.
- The --auto-area-segmentation switch activates the automatic area
- segmentation for monochrome scans. The scanner will try to
- determine which areas are text and which contain images. The
- image areas will be halftoned, and the text will be improved.
- Valid options are "yes" and "no". The default is "yes".
+ The --auto-area-segmentation switch activates the automatic area
+ segmentation for monochrome scans. The scanner will try to de-
+ termine which areas are text and which contain images. The image
+ areas will be halftoned, and the text will be improved. Valid
+ options are "yes" and "no". The default is "yes".
- The --gamma-table parameter can be used to download a user
- defined gamma table. The option takes 256 values from the range
+ The --gamma-table parameter can be used to download a user de-
+ fined gamma table. The option takes 256 values from the range
0-255. In color mode this option equally affects the red, green,
and blue channel.
- The --red-gamma-table parameter can be used to download a user
- defined gamma table for the red channel. The valid options are
+ The --red-gamma-table parameter can be used to download a user
+ defined gamma table for the red channel. The valid options are
the same as for --gamma-table.
- The --green-gamma-table parameter can be used to download a user
+ The --green-gamma-table parameter can be used to download a user
defined gamma table for the green channel. The valid options are
the same as for --gamma-table.
- The --blue-gamma-table parameter can be used to download a user
- defined gamma table for the blue channel. The valid options are
+ The --blue-gamma-table parameter can be used to download a user
+ defined gamma table for the blue channel. The valid options are
the same as for --gamma-table.
- The color correction coefficients --cct-1 --cct-2 --cct-3 ...
- --cct-9 will install color correction coefficients for the user
- defined color correction. Values are specified as integers in
+ The color correction coefficients --cct-1 --cct-2 --cct-3 ...
+ --cct-9 will install color correction coefficients for the user
+ defined color correction. Values are specified as integers in
the range -127..127.
- The --preview option requests a preview scan. The frontend soft-
- ware automatically selects a low resolution. Valid options are
+ The --preview option requests a preview scan. The frontend soft-
+ ware automatically selects a low resolution. Valid options are
"yes" and "no". The default is "no".
- The --preview-speed options will increase the scan speed if this
- is supported by the scanner. Valid options are "yes" and "no",
+ The --preview-speed options will increase the scan speed if this
+ is supported by the scanner. Valid options are "yes" and "no",
the default is "no".
- The geometry options -l -t -x -y control the scan area: -l sets
- the top left x coordinate, -t the top left y coordinate, -x
- selects the width and -y the height of the scan area. All param-
- eters are specified in millimeters.
+ The geometry options -l -t -x -y control the scan area: -l sets
+ the top left x coordinate, -t the top left y coordinate, -x se-
+ lects the width and -y the height of the scan area. All parame-
+ ters are specified in millimeters.
- The --quick-format option lets the user select a scan area with
- predefined sizes. Valid parameters are "CD", "A5 portrait", "A5
- landscape", "Letter", "A4" and "max". The default is "max",
+ The --quick-format option lets the user select a scan area with
+ predefined sizes. Valid parameters are "CD", "A5 portrait", "A5
+ landscape", "Letter", "A4" and "max". The default is "max",
which selects the largest possible area.
- The --source option selects the scan source. Valid options
- depend on the installed options. The default is "Flatbed".
+ The --source option selects the scan source. Valid options de-
+ pend on the installed options. The default is "Flatbed".
- The --auto-eject option will eject a page after scanning from
+ The --auto-eject option will eject a page after scanning from
the document feeder.
- The --film-type option will select the film type for scans with
- the transparency unit. This option is only activated if the TPU
- is selected as scan source. Valid options are "Negative Film"
+ The --film-type option will select the film type for scans with
+ the transparency unit. This option is only activated if the TPU
+ is selected as scan source. Valid options are "Negative Film"
and "Positive Film".
- The --focus-position option selects the focus position for all
+ The --focus-position option selects the focus position for all
scans. Valid options are "Focus 2.5mm above glass" and "Focus on
- glass". The focus on the 2.5mm point above the glass is neces-
- sary for scans with the transparency unit, so that the scanner
- can focus on the film if one of the film holders is used. This
+ glass". The focus on the 2.5mm point above the glass is neces-
+ sary for scans with the transparency unit, so that the scanner
+ can focus on the film if one of the film holders is used. This
option is only functional for selected scanners, all other scan-
ners will ignore this option.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/epson.conf specifies the
+ The configuration file /usr/local/etc/sane.d/epson.conf specifies the
device(s) that the backend will use. Possible connection types are:
- SCSI This is the default, and if nothing else is specified the back-
- end software will open a given path as SCSI device. More infor-
- mation about valid syntax for SCSI devices can be found in
+ SCSI This is the default, and if nothing else is specified the back-
+ end software will open a given path as SCSI device. More infor-
+ mation about valid syntax for SCSI devices can be found in
sane-scsi(5).
Usually SCSI scanners are configured with a line "scsi EPSON" in
- this file. In some cases it may be necessary to only use the
+ this file. In some cases it may be necessary to only use the
string "scsi" (e.g. for the GT-6500).
PIO - Parallel Interface
The parallel interface can be configured in two ways: An integer
value starting at the beginning of a line will be interpreted as
- the IO address of the parallel port. To make it clearer that a
+ the IO address of the parallel port. To make it clearer that a
configured IO address is a parallel port the port address can be
- preceded by the string "PIO". The PIO connection does not use a
+ preceded by the string "PIO". The PIO connection does not use a
special device file in the /dev directory. The IO address can be
specified in hex mode (prefixed with "0x").
USB A device file that is preceded by the string "USB" is treated as
- a scanner connected via the Universal Serial Bus. The correct
- special device file has to be created prior to using it with
- Sane. See the USB documentation for more information about how
+ a scanner connected via the Universal Serial Bus. The correct
+ special device file has to be created prior to using it with
+ Sane. See the USB documentation for more information about how
to set up the USB subsystem and the required device files.
@@ -241,24 +242,24 @@
ENVIRONMENT
SANE_DEBUG_EPSON
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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_EPSON_SCSI
- If the library was compiled with debug support enabled, this
- environment variable controls the SCSI related debug level for
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the SCSI related debug level for
this backend. Only a value of 2 is supported.
SANE_EPSON_CMD_LVL
- This allows one to override the function or command level that
- the backend uses to communicate with the scanner. The function
+ This allows one to override the function or command level that
+ the backend uses to communicate with the scanner. The function
level a scanner supports is determined during the initialization
- of the device. If the backend does not recognize the function
- level reported by the scanner it will default to function level
- B3. Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6,
- B7, B8, D1 and F5. Use this feature only if you know what you
+ of the device. If the backend does not recognize the function
+ level reported by the scanner it will default to function level
+ B3. Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6,
+ B7, B8, D1 and F5. Use this feature only if you know what you
are doing!
@@ -274,16 +275,16 @@
UNSUPPORTED DEVICES
- The backend may be used with Epson scanners that are not yet listed
- under the list of supported devices. A scanner that is not recognized
- may default to the function level B3, which means that not all func-
- tions that the scanner may be capable of are accessible.
+ The backend may be used with Epson scanners that are not yet listed un-
+ der the list of supported devices. A scanner that is not recognized may
+ default to the function level B3, which means that not all functions
+ that the scanner may be capable of are accessible.
If the scanner is not even recognized as an Epson scanner this is prob-
ably because the device name reported by the scanner is not in the cor-
- rect 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 SANE distribution).
+ rect format. Please send this information to the backend maintainer
+ (email address is in the AUTHOR section of this man page or in the AU-
+ THORS file of the SANE distribution).
The Perfection 600, Perfection 650, Perfection 660, Perfection 1250 and
Perfection 1260 are not supported by this backend.
@@ -291,8 +292,9 @@
AUTHOR
- The package is actively maintained by Karl Heinz Kremer (khk@khk.net).
- The software is based on work by Christian Bucher and Kazuhiro Sasayama
+ The package is actively maintained by Karl Heinz Kremer (khk@khk.net).
+ The software is based on work by Christian Bucher and Kazuhiro
+ Sasayama.
11 Jul 2008 sane-epson(5)
diff --git a/man/sane-epson2.5.html b/man/sane-epson2.5.html
index f14b0c0e..b5d78445 100644
--- a/man/sane-epson2.5.html
+++ b/man/sane-epson2.5.html
@@ -2,7 +2,7 @@
sane-epson2.5
-
+
sane-epson2.5
@@ -19,15 +19,15 @@
DESCRIPTION
The sane-epson2 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;
- include network access.
+ supports a similar set of scanners as the sane-epson driver but was de-
+ veloped to support a wider range of connections to the scanner; include
+ network access.
- Because sane-epson and sane-epson2 drivers support many of the same
- devices, if one driver gives you problems you may try disabling it to
- try the other. This can be done by removing the driver name from the
- dll.conf or perhaps by commenting out the options in epson.conf or
- epson2.conf.
+ Because sane-epson and sane-epson2 drivers support many of the same de-
+ vices, if one driver gives you problems you may try disabling it to try
+ the other. This can be done by removing the driver name from the
+ dll.conf or perhaps by commenting out the options in epson.conf or ep-
+ son2.conf.
At present, the following scanners are known to work with this backend:
@@ -101,15 +101,17 @@
OPTIONS
The options the backend supports can either be selected through command
- line options to programs like scanimage or through GUI elements in pro-
- grams like xscanimage or xsane.
+ line options to programs like scanimage(1) or through GUI elements in
+ programs like xscanimage(1) or xsane(1).
Valid command line options and their syntax can be listed by using
+
scanimage --help -d epson2
+
Not all devices support all options.
Scan Mode
- The --mode switch selects the basic mode of operation of the
+ The --mode switch selects the basic mode of operation of the
scanner. Valid choices are Binary, Gray and Color. The Binary
mode is black and white only, Gray will produce 256 levels of
gray or more depending on the scanner and Color means 24 bit
@@ -117,109 +119,109 @@
internally use 36 bit color, their external interface however
may only support 24 bits.
- The --depth option selects the bit depth the scanner is using.
+ The --depth option selects the bit depth the scanner is using.
This option is only available for scanners that support more
- than one bit depth. Older scanners will always transfer the
- image in 8bit mode. Newer scanners allow one to select either 8
+ than one bit depth. Older scanners will always transfer the im-
+ age in 8bit mode. Newer scanners allow one to select either 8
bits, 12 or 14 bits per color channel. For a color scan this
means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
- The --halftoning switch selects the mode that is used in Binary
- mode. Valid options are "None", "Halftone A (Hard Tone)",
- "Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
- (4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
- Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
- ogy", "Download pattern A", and "Download pattern B".
+ The --halftoning switch selects the mode that is used in Binary
+ mode. Valid options are "None", "Halftone A (Hard Tone)", "Half-
+ tone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A (4x4
+ Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net Screen)",
+ "Dither D (8x4 Net Screen)", "Text Enhanced Technology", "Down-
+ load pattern A", and "Download pattern B".
- The --dropout switch selects the so called dropout color. Valid
+ The --dropout switch selects the so called dropout color. Valid
options are None, Red, Green and Blue. The default is None. The
dropout color is used for monochrome scanning and selects the
color that is not scanned. This can be used to e.g. scan an
original with a colored background.
- The --brightness switch controls the brightness of the scan.
+ The --brightness switch controls the brightness of the scan.
Valid options are integer values from -3 to 3. The default is 0.
The larger the brightness value, the brighter the image gets. If
a user defined table for the gamma correction is selected, the
brightness parameter is not available.
- The --sharpness switch sets the sharpness of the image data.
+ The --sharpness switch sets the sharpness of the image data.
Valid options are integer values from -2 to 2, with -2 meaning
"Defocus", -1 "Defocus slightly", 0 "Normal", 1 "Sharpen
slightly" and 2 "Sharpen".
- The --gamma-correction switch controls the scanner's internal
+ The --gamma-correction switch controls the scanner's internal
gamma correction. Valid options are "Default", "User defined",
"High density printing" "Low density printing" and "High con-
trast printing".
- The --color-correction switch controls the scanner's internal
+ The --color-correction switch controls the scanner's internal
color correction function. Valid options are "No Correction",
"Impact-dot printers", "Thermal printers", "Ink-jet printers"
and "CRT monitors". The default is "CRT monitors".
- The --resolution switch selects the resolution for a scan. Some
+ The --resolution switch selects the resolution for a scan. Some
EPSON scanners will scan in any resolution between the lowest
and highest possible value. The list reported by the scanner can
- be displayed using the "--help -d epson" parameters to scanim-
- age.
+ be displayed using the "--help -d epson" parameters to scanim-
+ age(1).
- The --threshold switch selects the minimum brightness to get a
+ The --threshold switch selects the minimum brightness to get a
white point.
- The --mirror option controls the way the image is scanned. By
+ The --mirror option controls the way the image is scanned. By
reading the image data from right to left the image is mirrored.
Valid options are "yes" and "no". The default is "no".
- The --auto-area-segmentation switch activates the automatic area
- segmentation for monochrome scans. The scanner will try to
- determine which areas are text and which contain images. The
- image areas will be halftoned, and the text will be improved.
- Valid options are "yes" and "no". The default is "yes".
+ The --auto-area-segmentation switch activates the automatic area
+ segmentation for monochrome scans. The scanner will try to de-
+ termine which areas are text and which contain images. The image
+ areas will be halftoned, and the text will be improved. Valid
+ options are "yes" and "no". The default is "yes".
- The --red-gamma-table parameter can be used to download a user
+ The --red-gamma-table parameter can be used to download a user
defined gamma table for the red channel. The valid options are
the same as for --gamma-table.
- The --green-gamma-table parameter can be used to download a user
+ The --green-gamma-table parameter can be used to download a user
defined gamma table for the green channel. The valid options are
the same as for --gamma-table.
- The --blue-gamma-table parameter can be used to download a user
+ The --blue-gamma-table parameter can be used to download a user
defined gamma table for the blue channel. The valid options are
the same as for --gamma-table.
- The --wait-for-button parameter can be used to wait until the
+ The --wait-for-button parameter can be used to wait until the
button on the scanner is pressed to actually start the scan
process.
- The color correction coefficients --cct-1 --cct-2 --cct-3 ...
- --cct-9 will install color correction coefficients for the user
+ The color correction coefficients --cct-1 --cct-2 --cct-3 ...
+ --cct-9 will install color correction coefficients for the user
defined color correction. Values are specified as integers in
the range -127..127.
- The --preview option requests a preview scan. The frontend soft-
+ The --preview option requests a preview scan. The frontend soft-
ware automatically selects a low resolution. Valid options are
"yes" and "no". The default is "no".
- The geometry options -l -t -x -y control the scan area: -l sets
- the top left x coordinate, -t the top left y coordinate, -x
- selects the width and -y the height of the scan area. All param-
- eters are specified in millimeters.
+ The geometry options -l -t -x -y control the scan area: -l sets
+ the top left x coordinate, -t the top left y coordinate, -x se-
+ lects the width and -y the height of the scan area. All parame-
+ ters are specified in millimeters.
- The --source option selects the scan source. Valid options
- depend on the installed options. The default is "Flatbed".
+ The --source option selects the scan source. Valid options de-
+ pend on the installed options. The default is "Flatbed".
- The --auto-eject option will eject a page after scanning from
+ The --auto-eject option will eject a page after scanning from
the document feeder.
- The --film-type option will select the film type for scans with
+ The --film-type option will select the film type for scans with
the transparency unit. This option is only activated if the TPU
is selected as scan source. Valid options are "Negative Film"
and "Positive Film".
- The --focus-position option selects the focus position for all
+ The --focus-position option selects the focus position for all
scans. Valid options are "Focus 2.5mm above glass" and "Focus on
glass". The focus on the 2.5mm point above the glass is neces-
sary for scans with the transparency unit, so that the scanner
@@ -227,19 +229,19 @@
option is only functional for selected scanners, all other scan-
ners will ignore this option.
- The --bay option selects which bay to scan
+ The --bay option selects which bay to scan
- The --eject option ejects the sheet in the ADF.
+ The --eject option ejects the sheet in the ADF.
- The --adf-mode option select the ADF mode (simplex/duplex).
+ The --adf-mode option select the ADF mode (simplex/duplex).
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/epson2.conf specifies the
+ The configuration file /usr/local/etc/sane.d/epson2.conf specifies the
device(s) that the backend will use. Possible connection types are:
- SCSI This is the default, and if nothing else is specified the back-
+ SCSI This is the default, and if nothing else is specified the back-
end software will open a given path as SCSI device. More infor-
mation about valid syntax for SCSI devices can be found in
sane-scsi(5).
@@ -247,23 +249,23 @@
this file. In some cases it may be necessary to only use the
string "scsi" (e.g. for the GT-6500).
- PIO - Parallel Interface
+ PIO - Parallel Interface
The parallel interface can be configured in two ways: An integer
value starting at the beginning of a line will be interpreted as
the IO address of the parallel port. To make it clearer that a
configured IO address is a parallel port the port address can be
preceded by the string "PIO". The PIO connection does not use a
- special device file in the /dev directory. The IO address can be
+ special device file in the /dev directory. The IO address can be
specified in hex mode (prefixed with "0x").
- USB For USB scanners not automatically detect, their VENDOR and
+ USB For USB scanners not automatically detect, their VENDOR and
PRODUCT ID can be specified manually in the config file. More
information about valid syntax for USB devices can be found in
sane-usb(5).
- Network
- Network scanners can be auto-discovered if autodiscovery is
- specified after net keyword. An IP address to connect to can
+ Network
+ Network scanners can be auto-discovered if autodiscovery is
+ specified after net keyword. An IP address to connect to can
also be used.
@@ -280,21 +282,21 @@
ENVIRONMENT
SANE_DEBUG_EPSON2
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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_EPSON2_SCSI
- If the library was compiled with debug support enabled, this
- environment variable controls the SCSI related debug level for
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the SCSI related debug level for
this backend. Only a value of 2 is supported.
SANE_DEBUG_EPSON2_NET
- If the library was compiled with debug support enabled, this
- environment variable controls the network related debug level
- for this backend. E.g., a value of 128 requests all debug out-
- put to be printed. Smaller levels reduce verbosity.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the network related debug level for
+ this backend. E.g., a value of 128 requests all debug output to
+ be printed. Smaller levels reduce verbosity.
SANE_EPSON2_CMD_LVL
This allows one to override the function or command level that
@@ -319,23 +321,23 @@
UNSUPPORTED DEVICES
- The backend may be used with Epson scanners that are not yet listed
- under the list of supported devices. A scanner that is not recognized
- may default to the function level B3, which means that not all func-
- tions that the scanner may be capable of are accessible.
+ The backend may be used with Epson scanners that are not yet listed un-
+ der the list of supported devices. A scanner that is not recognized may
+ default to the function level B3, which means that not all functions
+ that the scanner may be capable of are accessible.
If the scanner is not even recognized as an Epson scanner this is prob-
ably because the device name reported by the scanner is not in the cor-
rect 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 SANE distribution).
+ (email address is in the AUTHOR section of this man page or in the AU-
+ THORS file of the SANE distribution).
AUTHOR
The package is written by Alessandro Zummo and is based on previous
work done by Karl Hienz Kremer in the epson package as well as based on
- work by Christian Bucher and Kazuhiro Sasayama
+ work by Christian Bucher and Kazuhiro Sasayama.
22 Jan 2009 sane-epson2(5)
diff --git a/man/sane-epsonds.5.html b/man/sane-epsonds.5.html
index 3f72593c..602fd004 100644
--- a/man/sane-epsonds.5.html
+++ b/man/sane-epsonds.5.html
@@ -2,7 +2,7 @@
sane-epsonds.5
-
+
sane-epsonds.5
@@ -21,11 +21,13 @@
backend that provides access to Epson ESC/I-2 scanners.
Valid command line options and their syntax can be listed by using
+
scanimage --help -d epsonds
+
Not all devices support all options.
Scan Mode
- The --mode switch selects the basic mode of operation of the
+ The --mode switch selects the basic mode of operation of the
scanner. Valid choices are Lineart, Gray and Color. The Lineart
mode is black and white only, Gray will produce 256 levels of
gray or more depending on the scanner and Color means 24 bit
@@ -33,46 +35,46 @@
internally use 36 bit color, their external interface however
may only support 24 bits.
- The --depth option selects the bit depth the scanner is using.
+ The --depth option selects the bit depth the scanner is using.
This option is only available for scanners that support more
- than one bit depth. Older scanners will always transfer the
- image in 8bit mode. Newer scanners allow one to select either 8
+ than one bit depth. Older scanners will always transfer the im-
+ age in 8bit mode. Newer scanners allow one to select either 8
bits, 12 or 14 bits per color channel. For a color scan this
means an effective color depth of 36 or 42 bits over all three
channels. The valid choices depend on the scanner model.
- The --resolution switch selects the resolution for a scan. Some
+ The --resolution switch selects the resolution for a scan. Some
EPSON scanners will scan in any resolution between the lowest
and highest possible value. The list reported by the scanner can
- be displayed using the "--help -d epson" parameters to scanim-
- age.
+ be displayed using the "--help -d epson" parameters to scanim-
+ age(1).
- The geometry options -l -t -x -y control the scan area: -l sets
- the top left x coordinate, -t the top left y coordinate, -x
- selects the width and -y the height of the scan area. All param-
- eters are specified in millimeters.
+ The geometry options -l -t -x -y control the scan area: -l sets
+ the top left x coordinate, -t the top left y coordinate, -x se-
+ lects the width and -y the height of the scan area. All parame-
+ ters are specified in millimeters.
- The --source option selects the scan source. Valid options
- depend on the installed options. The default is "Flatbed".
+ The --source option selects the scan source. Valid options de-
+ pend on the installed options. The default is "Flatbed".
- The --eject option ejects the sheet in the ADF.
+ The --eject option ejects the sheet in the ADF.
- The --adf-mode option select the ADF mode (simplex/duplex).
+ The --adf-mode option select the ADF mode (simplex/duplex).
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/epsonds.conf specifies the
+ The configuration file /usr/local/etc/sane.d/epsonds.conf specifies the
device(s) that the backend will use. Possible connection types are:
- USB For not automatically detected USB scanners, their VENDOR and
+ USB For not automatically detected USB scanners, their VENDOR and
PRODUCT ID can be specified manually in the config file. More
information about valid syntax for USB devices can be found in
sane-usb(5).
- Network (not yet supported)
- Network scanners can be auto-discovered if autodiscovery is
- specified after net keyword. An IP address to connect to can
+ Network (not yet supported)
+ Network scanners can be auto-discovered if autodiscovery is
+ specified after net keyword. An IP address to connect to can
also be used.
@@ -89,11 +91,11 @@
ENVIRONMENT
SANE_DEBUG_EPSONDS
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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 usu-
- allybe enough for a bug report.
+ ally be enough for a bug report.
diff --git a/man/sane-escl.5.html b/man/sane-escl.5.html
index 6b117568..9e889a26 100644
--- a/man/sane-escl.5.html
+++ b/man/sane-escl.5.html
@@ -2,7 +2,7 @@
sane-escl.5
-
+
sane-escl.5
@@ -24,21 +24,25 @@
not exhaustive):
BROTHER DCP-L2530
+ BROTHER HL-L2590DW
CANON IR C3520
+ CANON PIXMA MG5765
CANON PIXMA TS3100, TS3150, TS3300, TS3151, TS3350, TS3351,
- CANON PIXMA TS3352, TS6150, TS8050, TS9100, TR4540, TR8500,
- CANON PIXMA TR8520
+ CANON PIXMA TS3352, TS5351, TS6150, TS8050, TS9100, TR4540,
+ CANON PIXMA TR8500, TR8520
EPSON ET3740, ET4750
- HP LASERJET MFP M28W, OFFICEJET 4630, OFFICEJET PRO 8610
+ HP DESKJET 2710, DESKJET 2723, DESKJET 3760, LASERJET MFP M28W,
+ HP OFFICEJET 4630, OFFICEJET PRO 8610
RICOH SP3710S
XEROX VERSALINK C7220
- The "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. The user con-
- figures and starts scanning. A list of devices that use the eSCL pro-
- tocol can be found at https://support.apple.com/en-us/HT201311. While
- these devices are expected to work, your mileage may vary.
+ The. sane-escl backend for SANE supports AirScan/eSCL devices that an-
+ nounce themselves on mDNS as _uscan._utcp or _uscans._utcp. If the de-
+ vice is available, the 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 https://support.apple.com/en-
+ us/HT201311. While these devices are expected to work, your mileage
+ may vary.
@@ -57,15 +61,15 @@
ENVIRONMENT
SANE_DEBUG_ESCL
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
SEE ALSO
- sane(7), scanimage(1), xscanimage(1), xsane(1)
+ sane(7) scanimage(1) xscanimage(1) xsane(1)
diff --git a/man/sane-find-scanner.1.html b/man/sane-find-scanner.1.html
index 6a716da1..546b94e0 100644
--- a/man/sane-find-scanner.1.html
+++ b/man/sane-find-scanner.1.html
@@ -2,7 +2,7 @@
sane-find-scanner.1
-
+
sane-find-scanner.1
@@ -17,14 +17,14 @@
SYNOPSIS
- sane-find-scanner [-?|-h|--help] [-v] [-q] [-p] [-f] [-F filename]
- [devname]
+ sane-find-scanner [-?|-h|--help] [-v] [-q] [-p] [-f] [-F filename] [de-
+ vname]
DESCRIPTION
sane-find-scanner is a command-line tool to find SCSI and USB scanners
- and determine their Unix device files. Its primary aim is to make sure
+ and determine their UNIX device files. Its primary aim is to make sure
that scanners can be detected by SANE backends.
For SCSI scanners, it checks the default generic SCSI device files
@@ -40,18 +40,18 @@
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,
- sane-find-scanner tries to scan for USB devices found by the USB
- library libusb (if available). There is no special USB class for scan-
- ners, so the heuristics used to distinguish scanners from other USB
- devices is not perfect. sane-find-scanner also tries to find out the
+ sane-find-scanner tries to scan for USB devices found by the USB li-
+ brary libusb (if available). There is no special USB class for scan-
+ ners, so the heuristics used to distinguish scanners from other USB de-
+ vices is not perfect. 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. sane-find-scanner will even find USB
scanners, that are not supported by any SANE backend.
sane-find-scanner won't find most parallel port scanners, or scanners
- connected to proprietary ports. Some parallel port scanners may be
- detected by sane-find-scanner -p. At the time of writing this will
- only detect Mustek parallel port scanners.
+ connected to proprietary ports. Some parallel port scanners may be de-
+ tected by sane-find-scanner -p. At the time of writing this will only
+ detect Mustek parallel port scanners.
@@ -59,40 +59,40 @@
-?, -h, --help
Prints a short usage message.
- -v Verbose output. If used once, 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.
+ -v Verbose output. If used once, sane-find-scanner shows every de-
+ vice name and the test result. If used twice, SCSI inquiry in-
+ formation and the USB device descriptors are also printed.
-q Be quiet. Print only the devices, no comments.
-p Probe parallel port scanners.
- -f Force opening all explicitly given devices as SCSI and USB
- devices. That's useful if sane-find-scanner is wrong in deter-
- mining the device type.
+ -f Force opening all explicitly given devices as SCSI and USB de-
+ vices. That's useful if sane-find-scanner is wrong in determin-
+ ing the device type.
-F filename
filename is a file that contains USB descriptors in the format
of /proc/bus/usb/devices as used by Linux. 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 out-
- put of "cat /proc/bus/usb/devices" is available but the scanner
+ put of cat /proc/bus/usb/devices is available but the scanner
itself isn't.
- devname Test device file "devname". No other devices are checked if
- devname is given.
+ devname Test device file "devname". No other devices are checked if de-
+ vname is given.
EXAMPLE
- sane-find-scanner -v
+ sane-find-scanner -v
Check all SCSI and USB devices for available scanners and print a line
for every device file.
- sane-find-scanner /dev/scanner
+ sane-find-scanner /dev/scanner
Look for a (SCSI) scanner only at /dev/scanner and print the result.
- sane-find-scanner -p
+ sane-find-scanner -p
Probe for parallel port scanners.
diff --git a/man/sane-fujitsu.5.html b/man/sane-fujitsu.5.html
index 08279c2f..7384625e 100644
--- a/man/sane-fujitsu.5.html
+++ b/man/sane-fujitsu.5.html
@@ -2,7 +2,7 @@
sane-fujitsu.5
-
+
sane-fujitsu.5
@@ -27,10 +27,10 @@
SUPPORTED HARDWARE
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
+ and SCSI-over-USB protocols. Specifically, the SCSI M309x and M409x se-
+ ries, 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
+ see the list at http://www.sane-project.org/sane-supported-devices.html
for details.
This backend may support other Fujitsu scanners. The best way to deter-
@@ -61,25 +61,25 @@
OPTIONS
Effort has been made to expose all hardware options, including:
- source s
+ source s
Selects the source for the scan. Options may include "Flatbed",
"ADF Front", "ADF Back", "ADF Duplex", "Card Front", "Card
Back", "Card Duplex".
- mode m
+ mode m
Selects the mode for the scan. Options may include "Lineart",
"Halftone", "Gray", and "Color".
- resolution, y-resolution
- Controls scan resolution. Setting --resolution also sets
- --y-resolution, though this behavior is overridden by some fron-
- tends.
+ resolution, y-resolution
+ Controls scan resolution. Setting --resolution also sets
+ --y-resolution, though this behavior is overridden by some
+ frontends.
- tl-x, tl-y, br-x, br-y
+ 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.
+ renamed t, l, x, y by some frontends.
- page-width, page-height
+ 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.
@@ -90,31 +90,31 @@
Additionally, several 'software' options are exposed by the backend.
These are reimplementations of features provided natively by larger
- scanners, but running on the host computer. This enables smaller
- machines to have similar 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.
+ scanners, but running on the host computer. This enables smaller ma-
+ chines to have similar capabilities. Please note that these features
+ are somewhat simplistic, and may not perform as well as the native im-
+ plementations. Note also that these features all require that the
+ driver cache the entire image in memory. This will almost certainly re-
+ sult in a reduction of scanning speed.
- 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.
+ 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 ad-
+ vanced options may be hidden by some frontend programs.
CONFIGURATION FILE
- The configuration file "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
+ The configuration file 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 file is missing, the backend will be unable to locate any
scanners.
Scanners can be specified in the configuration file in 4 ways:
"scsi FUJITSU"
- Requests backend to search all scsi busses in the system for a
+ Requests backend to search all scsi buses in the system for a
device which reports itself to be a scanner made by 'FUJITSU'.
"scsi /dev/sg0" (or other scsi device file)
@@ -124,9 +124,9 @@
other "scsi" line above.
"usb 0x04c5 0x1042" (or other vendor/product ids)
- Requests backend to search all usb busses in the system for a
- device which uses that vendor and product id. The device will
- then be queried to determine if it is a Fujitsu scanner.
+ Requests backend to search all usb buses in the system for a de-
+ vice which uses that vendor and product id. The device will then
+ be queried to determine if it is a Fujitsu scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
@@ -150,7 +150,7 @@
ENVIRONMENT
- The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
+ The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
which enables debugging output to stderr. Valid values are:
5 Errors
@@ -180,40 +180,35 @@
CREDITS
- m3091 backend: Frederik Ramm <frederik a t remote d o t org>
- m3096g backend: Randolph Bentson <bentson a t holmsjoen d o t com>
+ m3091 backend: Frederik Ramm <frederik a t remote d o t org>
+ m3096g backend: Randolph Bentson <bentson a t holmsjoen d o t com>
(with credit to the unnamed author of the coolscan driver)
fujitsu backend, m3093, fi-4340C, ipc, cmp, long-time maintainer:
- Oliver Schirrmeister <oschirr a t abm d o t de>
- m3092: Mario Goppold <mgoppold a t tbzpariv d o t tcc-chemnitz dot de>
- fi-4220C and basic USB support: Ron Cemer <ron a t roncemer d o t com>
+ Oliver Schirrmeister <oschirr a t abm d o t de>
+ m3092: Mario Goppold <mgoppold a t tbzpariv d o t tcc-chemnitz dot de>
+ fi-4220C and basic USB support: Ron Cemer <ron a t roncemer d o t com>
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: <kitno455 a t gmail d o t com>
JPEG output and low memory usage support funded by:
- Archivista GmbH
- www.archivista.ch
+ Archivista GmbH www.archivista.ch
Endorser support funded by:
O A S Oilfield Accounting Service Ltd
1500, 840 - 7th Avenue S.W.
Calgary, Alberta
T2P 3G2 Canada
- 1-403-263-2600
- www.oas.ca
+ 1-403-263-2600 www.oas.ca
Automatic length detection support funded by:
- Martin G. Miller
- mgmiller at optonline.net
+ Martin G. Miller 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
+ Fujitsu Computer Products of America, Inc. www.fcpa.com
iX500 support funded by:
- Prefix Computer Services
- www.prefixservice.com
+ Prefix Computer Services www.prefixservice.com
@@ -222,6 +217,7 @@
sane-epjitsu(5)
+
AUTHOR
m. allan noah: <kitno455 a t gmail d o t com>
diff --git a/man/sane-genesys.5.html b/man/sane-genesys.5.html
index 88dd9bc0..92388043 100644
--- a/man/sane-genesys.5.html
+++ b/man/sane-genesys.5.html
@@ -2,7 +2,7 @@
sane-genesys.5
-
+
sane-genesys.5
@@ -58,16 +58,16 @@
by passing the --calibrate option to scanimage or by clicking on the
available 'calibrate' button in the 'advanced options' in a graphical
frontend. The result of the calibration is stored in a file in the home
- directory of the user doing it. If you plug the scanner in another
- machine or use it with another account, calibration will have to be
- redone, unless you use the --calibration-file option. If no home
- directory is defined, USERAPPPROFILE will be used, then TMPDIR or TMP.
- If none of these directories exist, the backend will try to write in
- the current working directory. Flatbed scanners also make use of the
- calibration file as a cache to avoid calibration before each scan. Cal-
- ibration file name is the name of the scanner model if only one scanner
- is detected. In the case of several identical model, the file name will
- be the name of the logical USB device name. The expiration time manages
+ directory of the user doing it. If you plug the scanner in another ma-
+ chine or use it with another account, calibration will have to be re-
+ done, unless you use the --calibration-file option. If no home direc-
+ tory is defined, USERAPPPROFILE will be used, then TMPDIR or TMP. If
+ none of these directories exist, the backend will try to write in the
+ current working directory. Flatbed scanners also make use of the cali-
+ bration file as a cache to avoid calibration before each scan. Calibra-
+ tion file name is the name of the scanner model if only one scanner is
+ detected. In the case of several identical model, the file name will be
+ the name of the logical USB device name. The expiration time manages
the time a calibration is valid in cache. A value of -1 means forever,
0 means no cache.
@@ -75,91 +75,89 @@
EXTRAS SCAN OPTIONS
--lamp-off-time number
- 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.
+ 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.
--threshold percent
- 0..100% (in steps of 1). Select minimum brightness to get a
+ 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.
--brightness value
- -100..100 (in steps of 1). Set the brightness enhancement.
- 0 for no enhancement, negative values to decrease brigthness,
- and positive values to increase it.
+ -100..100 (in steps of 1). Set the brightness enhancement. 0 for
+ no enhancement, negative values to decrease brightness, and pos-
+ itive values to increase it.
--contrast value
- -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.
+ -100..100 (in steps of 1). Set the contrast enhancement. 0 for
+ no enhancement, negative values to decrease contrast, and posi-
+ tive values to increase it.
--disable-interpolation yes|no
- When using high resolutions where the horizontal resolu-
- tion 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.
+ 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 op-
+ tion to get real scanned data.
--disable-dynamic-lineart yes|no
- Disable use of a software adaptive algorithm to generate
- lineart and rely on hardware lineart.
+ Disable use of a software adaptive algorithm to generate lineart
+ and rely on hardware lineart.
--color-filter None|Red|Green|Blue
- 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.
+ 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 se-
+ lected.
--lamp-off-scan
- The lamp will be turned off during the scan. Calibration
- is still done with lamp on.
+ The lamp will be turned off during the scan. Calibration is
+ still done with lamp on.
--clear-calibration
- Clear calibration cache data, triggering a new calibra-
- tion for the device when the next scan will happen.
+ Clear calibration cache data, triggering a new calibration for
+ the device when the next scan will happen.
--calibration-file
- Specify the calibration file name to use. At least the
- directory containing the file must exist, since it won't be cre-
- ated. This option is disabled if the backend is ran as root. It
- maybe used in case of sheet-fed scanners to share a calibration
- file for several users.
+ 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.
--expiration-time
- Specify the time (in minutes) a cached calibration is
- considered valid. If older than the given value, a new calibra-
- tion 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.
+ 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 for-
+ ever unless cleared by userwith the calibration clear option. A
+ value of 0 means cache is disabled.
Additionally, several 'software' options are exposed by the backend.
These are reimplementations of features provided natively by larger
- scanners, but running on the host computer. This enables smaller
- machines to have similar 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.
+ scanners, but running on the host computer. This enables smaller ma-
+ chines to have similar capabilities. Please note that these features
+ are somewhat simplistic, and may not perform as well as the native im-
+ plementations. Note also that these features all require that the
+ driver cache the entire image in memory. This will almost certainly re-
+ sult in a reduction of scanning speed.
--swcrop
- Requests the driver to detect the extremities of the paper
+ Requests the driver to detect the extremities of the paper
within the larger image, and crop the empty edges.
--swdeskew
- Requests the driver to detect the rotation of the paper
- within the larger image, and counter the rotation.
+ Requests the driver to detect the rotation of the paper within
+ the larger image, and counter the rotation.
--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.
+ Requests the driver to find and remove dots of X diameter or
+ smaller from the image, and fill the space with the average sur-
+ rounding color.
--swskip 0..100% (in steps of 1) [0]
- Request driver to discard pages with low numbers of dark
- pixels.
+ Request driver to discard pages with low numbers of dark pixels.
--swderotate[=(yes|no)] [no]
- Request driver to detect and correct 90 degree image
- rotation.
+ Request driver to detect and correct 90 degree image rotation.
@@ -204,25 +202,25 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_GENESYS
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. If the
debug level is set to 1 or higher, some debug options become
available that are normally hidden. Handle them with care. This
will print messages related to core genesys functions.
SANE_DEBUG_GENESYS_IMAGE
- If the library was compiled with debug support enabled, this
- environment variable enables logging of intermediate image data.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable enables logging of intermediate image data.
To enable this mode, set the environmental variable to 1.
Example (full and highly verbose output for gl646):
@@ -240,8 +238,9 @@
Syscan/Ambir DocketPORT 467/485/487/665/685
Xerox Travel Scanner 100, Onetouch 2400
- cncsolutions (http://www.cncsolutions.com.br) sponsored and supported
- the work on the Panasonic KV-SS080.
+ cncsolutions
+ (http://www.cncsolutions.com.br) sponsored and supported the
+ work on the Panasonic KV-SS080.
Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE
700F.
@@ -259,12 +258,13 @@
AUTHOR
Oliver Rauch
- Henning Meier-Geinitz <henning@meier-geinitz.de>
- Gerhard Jaeger <gerhard@gjaeger.de>
- Stephane Voltz <stef.dev@free.fr>
- Philipp Schmid <philipp8288@web.de>
- Pierre Willenbrock <pierre@pirsoft.dnsalias.org>
- Alexey Osipov <simba@lerlan.ru> for HP2400 final support
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
+ Gerhard Jaeger <gerhard@gjaeger.de>
+ Stephane Voltz <stef.dev@free.fr>
+ Philipp Schmid <philipp8288@web.de>
+ Pierre Willenbrock <pierre@pirsoft.dnsalias.org>
+ Alexey Osipov <simba@lerlan.ru> for HP2400 final support
+
@@ -275,13 +275,13 @@
ners, due to the way image sensors are built.
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.
+ that sane-backends is built with the --enable-libusb_1_0 option.
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
+ sensor. It seems the windows driver does some digital processing to
improve it, which is not implemented in the backend.
4 Jul 2012 sane-genesys(5)
diff --git a/man/sane-gphoto2.5.html b/man/sane-gphoto2.5.html
index caad49fc..fcdd7d23 100644
--- a/man/sane-gphoto2.5.html
+++ b/man/sane-gphoto2.5.html
@@ -2,7 +2,7 @@
sane-gphoto2.5
-
+
sane-gphoto2.5
@@ -23,9 +23,9 @@
so far. Patches to support other models are welcome.
Because of the limited testing of this backend, it is commented out in
- /usr/local/etc/sane.d/dll.conf by default. Either the comment charac-
+ /usr/local/etc/sane.d/dll.conf by default. Either the comment charac-
ter must be removed or the backend must be called explicitly. E.g.
- `scanimage -d gphoto2' or `xscanimage gphoto2'.
+ scanimage -d gphoto2 or xscanimage gphoto2.
@@ -38,25 +38,25 @@
CONFIGURATION
The contents of the gphoto2.conf specify the characteristics of the
camera to be used. Resolutions (high resolution, low resolution, and
- thumbnail size) are required since they are needed by the sane fron-
- tends, but can't be obtained through the gphoto2 interface. Valid
- ports and cameras can be obtained by "gphoto2 --list-cameras" and
- "gphoto2 --list-ports".
+ thumbnail size) are required since they are needed by the sane front-
+ ends, but can't be obtained through the gphoto2 interface. Valid ports
+ and cameras can be obtained by gphoto2 --list-cameras and gphoto2
+ --list-ports .
- The dumpinquiry line causes some information about the camera to be
+ The dumpinquiry line causes some information about the camera to be
printed.
Empty lines and lines starting with a hash mark (#) are ignored. A
sample configuration file is shown below:
- The "topfolder" line specifies the "fixed" part of the file path. For
+ The topfolder line specifies the "fixed" part of the file path. For
example, on the Kodak DC-240, files are stored in the directory
- /DCIM/100DC240. The /DCIM portion is constant, but 100DC240 will
+ /DCIM/100DC240. The /DCIM portion is constant, but 100DC240 will
change and must be read from the camera. In this case, the line would
read "topfolder=/DCIM"
Some cameras don't implement a file structure and store all pictures in
- the "/" directory. This is indicated by setting "subdirs=0" with "top-
+ the / directory. This is indicated by setting "subdirs=0" with "top-
folder=/"
port=usb:
@@ -91,13 +91,13 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (.) and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_GPHOTO2
If the library was compiled with debugging support enabled, this
@@ -112,7 +112,7 @@
SEE ALSO
- sane(7)
+ sane(7) scanimage(1) xscanimage(1)
@@ -128,7 +128,7 @@
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). You must
+ 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.
diff --git a/man/sane-gt68xx.5.html b/man/sane-gt68xx.5.html
index 42305064..81df47fc 100644
--- a/man/sane-gt68xx.5.html
+++ b/man/sane-gt68xx.5.html
@@ -2,7 +2,7 @@
sane-gt68xx.5
-
+
sane-gt68xx.5
@@ -30,9 +30,9 @@
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
- sane-find-scanner 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.
+ 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.
If you own a scanner that isn't detected by the gt68xx backend but has
a GT-6801 or GT-6816 chipset, you can try to add it to the backend.
@@ -44,8 +44,8 @@
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 permis-
- sions and general USB information looks at sane-usb(5).
+ found by sane-find-scanner(1) without further actions. For setting per-
+ missions and general USB information looks at sane-usb(5).
@@ -101,13 +101,13 @@
the same vendor/product ids so you can set the "correct" name here.
The afe option allows one to set custom offset and gain values for the
- Analog FrontEnd of the scanner. This option can be either used to
- select the AFE values if automatic coarse calibration is disabled, or
- to make automatic coarse calibration faster. For the latter usage,
- enable debug level 3 (see below), scan an image and look for debug line
- string with "afe". Copy this line to gt68xx.conf. The option has six
- parameters: red offset, red gain, green offset, green gain, blue off-
- set, and blue gain.
+ Analog FrontEnd of the scanner. This option can be either used to se-
+ lect the AFE values if automatic coarse calibration is disabled, or to
+ make automatic coarse calibration faster. For the latter usage, enable
+ debug level 3 (see below), scan an image and look for debug line string
+ with "afe". Copy this line to gt68xx.conf. The option has six parame-
+ ters: red offset, red gain, green offset, green gain, blue offset, and
+ blue gain.
A sample configuration file is shown below:
@@ -141,17 +141,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_GT68XX
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output. If the
debug level is set to 1 or higher, some debug options become
available that are normally hidden. Handle them with care.
@@ -169,7 +169,7 @@
AUTHOR
- Henning Meier-Geinitz <henning@meier-geinitz.de>
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
The original gt68xx driver was written by Sergey Vlasov, Andreas
Nowack, and David Stevenson. Thanks for sending patches and answering
questions to them and all the other contributors.
@@ -185,10 +185,11 @@
Support for buttons is missing.
More detailed bug information is available at the gt68xx backend home-
- page http://www.meier-geinitz.de/sane/gt68xx-backend/. 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).
+ page http://www.meier-geinitz.de/sane/gt68xx-backend/.
+ Please contact us if you find a bug or missing feature: <sane-de-
+ vel@alioth-lists.debian.net>.
+ Please send a debug log if your scanner isn't detected correctly (see
+ SANE_DEBUG_GT68XX above).
13 Jul 2008 sane-gt68xx(5)
diff --git a/man/sane-hp.5.html b/man/sane-hp.5.html
index 95b9769e..96b72d71 100644
--- a/man/sane-hp.5.html
+++ b/man/sane-hp.5.html
@@ -2,7 +2,7 @@
sane-hp.5
-
+
sane-hp.5
@@ -45,23 +45,23 @@
PhotoSmart C5100A R029,R030,R032 SCSI
Support for models 5100C/5200C connected to the parallel port requires
- the ppSCSI driver available at http://cyberelk.net/tim/par-
- port/ppscsi.html and http://penguin-breeder.org/kernel/download/.
+ the ppSCSI driver available at http://cyberelk.net/tim/parport/pp-
+ scsi.html and http://penguin-breeder.org/kernel/download/.
Support for models 5200C/62X0C/63X0C connected to the USB require the
kernel scanner driver or libusb. See sane-usb(5) for more details.
- The "hp" backend no longer supports OfficeJet multi-function peripher-
- als. For these devices use the external "hpoj" backend in version 0.90
- and later of the "HP OfficeJet Linux driver", available at
+ The sane-hp backend no longer supports OfficeJet multi-function periph-
+ erals. For these devices use the external "hpoj" backend in version
+ 0.90 and later of the "HP OfficeJet Linux driver", available at
http://hpoj.sourceforge.net
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 http://www.sane-project.org/.
- You can also watch the sane-devel mailing list at
- http://www.sane-project.org/mailing-lists.html.
+ complete. Other HP scanners are not supported by the sane-hp backend,
+ but might be supported by another one. See
+ http://www.sane-project.org/. You can also watch the sane-devel mail-
+ ing list at http://www.sane-project.org/mailing-lists.html.
More details about the hp backend can be found on its homepage
http://www.kirchgessner.net/sane.html.
@@ -82,8 +82,8 @@
cial device name must be the device that corresponds to the parallel
interface card that was shipped with the scanner. That is /dev/hpscan.
A special driver is required for this card. See
- ftp://rvs.ctrl-c.liu.se/pub/wingel/hpscan for details. If the link does
- not work, try ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.
+ ftp://rvs.ctrl-c.liu.se/pub/wingel/hpscan for details. If the link does
+ not work, try ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.
@@ -95,25 +95,25 @@
Options specified in front of the first line that contains a device
name are defaults for all devices. Options specified below a line that
- contains a device name apply just to the most recently mentioned
- device.
+ contains a device name apply just to the most recently mentioned de-
+ vice.
- Supported options are connect-scsi, connect-device,
- enable-image-buffering, and dumb-read.
+ Supported options are connect-scsi, connect-device, enable-im-
+ age-buffering, and dumb-read.
Option connect-scsi specifies that the scanner is connected to the sys-
tem by SCSI. Input/output is performed using SCSI-commands. This is
the default. But if your SCSI device name contains "usb", "uscanner"
- or "ugen", option connect-scsi must be specified. Otherwise it is
- assumed that the scanner is connected by USB.
+ or "ugen", option connect-scsi must be specified. Otherwise it is as-
+ sumed that the scanner is connected by USB.
Option connect-device specifies that the scanner is connected to the
system by a special device. Input/output is performed by
- read()/write()-operations on the device. This option must be used for
+ 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). For device names that contain
- "usb", "uscanner" or "ugen", it is not necessary to specify option con-
- nect-device.
+ a named device (e.g. /dev/usb/scanner0). For device names that con-
+ tain "usb", "uscanner" or "ugen", it is not necessary to specify option
+ connect-device.
Option enable-image-buffering stores the scanned image in memory before
passing it to the frontend. Could be used in case of forward/backward
@@ -121,18 +121,18 @@
Option dumb-read can be used to work around problems with "Error during
device I/O". These problems may occur with certain SCSI-to-USB convert-
- ers or Buslogic SCSI cards. The option should not be used for SCSI
- devices which are working correctly. Otherwise startup of frontends
- and changing parameters might be slower.
+ ers or Buslogic SCSI cards. The option should not be used for SCSI de-
+ vices which are working correctly. Otherwise startup of frontends and
+ changing parameters might be slower.
A sample configuration file is shown below:
/dev/scanner
# this is a comment
/dev/hpscan
- option connect-device
+ option connect-device
- /dev/scanner is typically a symlink to the actual SCSI scanner device.
+ /dev/scanner is typically a symlink to the actual SCSI scanner device.
@@ -149,11 +149,10 @@
that support dynamic loading).
$HOME/.sane/calib-hp:<device>.dat
- Calibration data for HP PhotoSmart PhotoScanner that is
- retrieved from the scanner after calibration. The data is
- uploaded to the scanner at start of the backend if it is in
- media mode 'print media' or if the media mode is changed to
- 'print media'.
+ Calibration data for HP PhotoSmart PhotoScanner that is re-
+ trieved from the scanner after calibration. The data is uploaded
+ to the scanner at start of the backend if it is in media mode
+ 'print media' or if the media mode is changed to 'print media'.
@@ -161,25 +160,25 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (.) and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_HP
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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_HOME_HP
- Only used for OS/2 and along with use of HP PhotoSmart Photo-
+ Only used for OS/2 and along with use of HP PhotoSmart Photo-
Scanner. Must be set to the directory where the directory .sane
is located. Is used to save and read the calibration file.
@@ -188,72 +187,73 @@
SANE_HP_KEEPOPEN_USB
SANE_HP_KEEPOPEN_DEVICE
- For each type of connection (connect-scsi, connect-usb, con-
+ For each type of connection (connect-scsi, connect-usb, con-
nect-device) it can be specified if the connection to the device
should be kept open ("1") or not ("0"). Usually the connections
- are closed after an operation is performed. Keeping connection
- open to SCSI-devices can result in errors during device IO when
- the scanner has not been used for some time. By default, USB-
+ are closed after an operation is performed. Keeping connection
+ open to SCSI-devices can result in errors during device IO when
+ the scanner has not been used for some time. By default, USB-
connections are kept open. Other connections are closed.
SANE_HP_RDREDO
- Specifies number of retries for read operation before returning
- an EOF error. Only supported for non-SCSI devices. Default: 1
+ Specifies number of retries for read operation before returning
+ an EOF error. Only supported for non-SCSI devices. Default: 1
retry. Time between retries is 0.1 seconds.
BUGS
HP PhotoSmart PhotoScanner
- In media mode 'slide' and 'negative', scan resolutions are
- rounded to multiple of 300 dpi. The scanner does not scale the
+ In media mode 'slide' and 'negative', scan resolutions are
+ rounded to multiple of 300 dpi. The scanner does not scale the
data correctly on other resolutions. Some newer models (firmware
- code R030 and later) do not support adjustment of con-
- trast/intensity level and tone map. The backend will simulate
- this by software, but only for gray and 24 bit color.
+ code R030 and later) do not support adjustment of contrast/in-
+ tensity level and tone map. The backend will simulate this by
+ software, but only for gray and 24 bit color.
Automatic Document Feeder (ADF)
- For use of the ADF with xscanimage(1), first place paper in the
- ADF and then change option scan source to 'ADF'. Press 'change
- document' to load a sheet. Then press 'scan' to start a scan.
+ For use of the ADF with xscanimage(1), first place paper in the
+ ADF and then change option scan source to 'ADF'. Press 'change
+ document' to load a sheet. Then press 'scan' to start a scan.
Maybe it is sufficient to press 'scan' without 'change document'
- for repeated scans. The use of the preview window is not recom-
+ for repeated scans. The use of the preview window is not recom-
mended when working with the ADF. Setting a window to scan from
ADF is not supported with xscanimage(1). Try xsane(1).
Immediate actions
- Some actions in xscanimage(1) (i.e. unload, select media, cali-
- brate) have an immediate effect on the scanner without starting
- a scan. These options can not be used with scanimage.
+ Some actions in xscanimage(1) (i.e. unload, select media, cali-
+ brate) have an immediate effect on the scanner without starting
+ a scan. These options can not be used with scanimage(1).
TODO
HP PhotoSmart PhotoScanner
PhotoScanners with firmware release R030 and up have no firmware
- support for contrast/brightness/gamma table. In the current
- backend this is simulated by software on 24 bits data. Simula-
+ support for contrast/brightness/gamma table. In the current
+ backend this is simulated by software on 24 bits data. Simula-
tion on 30 bits should give better results.
Data widths greater than 8 bits
Custom gamma table does not work.
Parallel scanner support
- Beside the ScanJet Plus which came with its own parallel inter-
- face card, currently only the HP ScanJet 5100C/5200C are sup-
- ported. These scanners are using an internal parallel-to-SCSI
+ Beside the ScanJet Plus which came with its own parallel inter-
+ face card, currently only the HP ScanJet 5100C/5200C are sup-
+ ported. These scanners are using an internal parallel-to-SCSI
converter which is supported by the ppSCSI-driver (see above).
SEE ALSO
- sane(7), sane-scsi(5), sane-usb(5)
+ sane(7), sane-scsi(5), sane-usb(5) scanimage(1), xscanimage(1), scanim-
+ age(1)
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.
+ HP PhotoSmart PhotoScanner support by Peter Kirchgessner.
13 Jul 2008 sane-hp(5)
diff --git a/man/sane-hp3500.5.html b/man/sane-hp3500.5.html
index 40602204..0159fb40 100644
--- a/man/sane-hp3500.5.html
+++ b/man/sane-hp3500.5.html
@@ -2,7 +2,7 @@
sane-hp3500.5
-
+
sane-hp3500.5
@@ -29,8 +29,8 @@
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 the USB vendor and device ids (e.g. from
- /proc/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
- scanner's name is only slightly different from the models mentioned
+ /proc/bus/usb/devices, sane-find-scanner (1) or syslog) to us. Even if
+ the scanner's name is only slightly different from the models mentioned
above, please let us know.
@@ -51,8 +51,8 @@
ENVIRONMENT
- SANE_DEBUG_HP3500 If the library was compiled with debug support
- enabled, this environment variable controls the debug level for this
+ SANE_DEBUG_HP3500 If the library was compiled with debug support en-
+ abled, this environment variable controls the debug level for this
backend. Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP3500=4
@@ -66,7 +66,7 @@
AUTHOR
- Troy Rollo <sane@troy.rollo.name>
+ Troy Rollo <sane@troy.rollo.name>
13 Jul 2008 sane-hp3500(5)
diff --git a/man/sane-hp3900.5.html b/man/sane-hp3900.5.html
index 27887d5a..ff11eef0 100644
--- a/man/sane-hp3900.5.html
+++ b/man/sane-hp3900.5.html
@@ -2,7 +2,7 @@
sane-hp3900.5
-
+
sane-hp3900.5
@@ -33,17 +33,17 @@
UMAX Astra 4900/4950 RTS8822L-01H *
BenQ 5550 RTS8823L-01E *
- More details can be found on the hp3900 backend homepage http://source-
- forge.net/projects/hp3900-series/.
+ More details can be found on the sane-hp3900(1) backend homepage
+ http://sourceforge.net/projects/hp3900-series/.
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.
+ it, if scanner does not start to scan. See also the BUGS section.
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 the USB vendor and device ids (e.g. from
- /proc/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
- scanner's name is only slightly different from the models mentioned
+ /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if
+ the scanner's name is only slightly different from the models mentioned
above, please let us know.
@@ -52,8 +52,8 @@
The contents of the hp3900.conf file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 39XX
- scanner. Empty lines and lines starting with a hash mark (#) are
- ignored. The scanners are autodetected by usb vendor_id product_id
+ scanner. Empty lines and lines starting with a hash mark (#) are ig-
+ nored. The scanners are autodetected by usb vendor_id product_id
statements which are already included into hp3900.conf. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
@@ -82,17 +82,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and "/etc/sane.d"
- being searched (in this order).
+ current working directory (.) and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_HP3900
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP3900=4
@@ -100,20 +100,20 @@
SEE ALSO
- sane(7), sane-usb(5),
- http://sourceforge.net/projects/hp3900-series/ http://jkdsoftware.dyn-
- dns.org/drupal/?q=es/books/151
+ sane(7), sane-usb(5), sane-find-scanner(1),
+ http://sourceforge.net/projects/hp3900-series/
+ http://jkdsoftware.dyndns.org/drupal/?q=es/books/151
AUTHOR
- Jonathan Bravo Lopez <jkdsoft@gmail.com>
+ Jonathan Bravo Lopez <jkdsoft@gmail.com>
BUGS
Scanning is only tested with Linux/ix86/gcc. Be careful when testing on
- other operating systems and especially on big-endian platforms. The
+ other operating systems and especially on big-endian platforms. The
scanner may get wrong data.
06 Jan 2009 sane-hp3900(5)
diff --git a/man/sane-hp4200.5.html b/man/sane-hp4200.5.html
index dafb20f5..749ff197 100644
--- a/man/sane-hp4200.5.html
+++ b/man/sane-hp4200.5.html
@@ -2,7 +2,7 @@
sane-hp4200.5
-
+
sane-hp4200.5
@@ -34,8 +34,8 @@
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 the USB vendor and device ids (e.g. from
- /proc/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
- scanner's name is only slightly different from the models mentioned
+ /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if
+ the scanner's name is only slightly different from the models mentioned
above, please let us know.
@@ -44,8 +44,8 @@
The contents of the hp4200.conf file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 4200
- scanner. Empty lines and lines starting with a hash mark (#) are
- ignored. The scanners are autodetected by usb vendor_id product_id
+ scanner. Empty lines and lines starting with a hash mark (#) are ig-
+ nored. The scanners are autodetected by usb vendor_id product_id
statements which are already included into hp4200.conf. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
@@ -74,17 +74,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (.) and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_HP4200
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP4200=4
@@ -92,7 +92,7 @@
SEE ALSO
- sane(7), sane-usb(5),
+ sane(7), sane-usb(5), sane-find-scanner(1),
http://hp4200-backend.sourceforge.net/
@@ -100,7 +100,7 @@
AUTHOR
Adrian Perez Jorge, Andrew John Lewis, Arnar Mar Hrafnkelsson, Frank
Zago, Henning Meier-Geinitz. Current maintainer: Henning Meier-Geinitz
- <henning@meier-geinitz.de>.
+ <henning@meier-geinitz.de>.
@@ -111,8 +111,8 @@
Scanning is slow due to backtracking.
- Send bug reports to the sane-devel mailing list: sane-devel@alioth-
- lists.debian.net.
+ Send bug reports to the sane-devel mailing list: sane-devel@alioth-
+ lists.debian.net.
13 Jul 2008 sane-hp4200(5)
diff --git a/man/sane-hp5400.5.html b/man/sane-hp5400.5.html
index 0b0249e4..6b167319 100644
--- a/man/sane-hp5400.5.html
+++ b/man/sane-hp5400.5.html
@@ -2,7 +2,7 @@
sane-hp5400.5
-
+
sane-hp5400.5
@@ -35,8 +35,8 @@
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 the USB vendor and device ids (e.g. from
- /proc/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
- scanner's name is only slightly different from the models mentioned
+ /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if
+ the scanner's name is only slightly different from the models mentioned
above, please let us know.
@@ -45,8 +45,8 @@
The contents of the hp5400.conf file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain the names of device files that correspond to an HP 54XX
- scanner. Empty lines and lines starting with a hash mark (#) are
- ignored. The scanners are autodetected by usb vendor_id product_id
+ scanner. Empty lines and lines starting with a hash mark (#) are ig-
+ nored. The scanners are autodetected by usb vendor_id product_id
statements which are already included into hp5400.conf. "vendor_id"
and "product_id" are hexadecimal numbers that identify the scanner. If
autodetection does not work, add the device name of your scanner to the
@@ -75,17 +75,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (.) and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_HP5400
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_HP5400=4
@@ -93,15 +93,15 @@
SEE ALSO
- sane(7), sane-usb(5),
+ sane(7), sane-usb(5), sane-find-scanner(1),
http://hp5400backend.sourceforge.net/
AUTHOR
- Martijn van Oosterhout <kleptog@svana.org>, Thomas Soumarmon
- <soumarmt@nerim.net>. Manpage by Henning Meier-Geinitz <hen-
- ning@meier-geinitz.de>.
+ Martijn van Oosterhout <kleptog@svana.org>, Thomas Soumarmon
+ <soumarmt@nerim.net>. Manpage by Henning Meier-Geinitz <hen-
+ ning@meier-geinitz.de>.
diff --git a/man/sane-hp5590.5.html b/man/sane-hp5590.5.html
index 1cea5bc8..6bec8780 100644
--- a/man/sane-hp5590.5.html
+++ b/man/sane-hp5590.5.html
@@ -2,7 +2,7 @@
sane-hp5590.5
-
+
sane-hp5590.5
@@ -37,23 +37,23 @@
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 the USB vendor and device ids (e.g. from
- /sys/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
- scanner's name is only slightly different from the models mentioned
+ /sys/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if
+ the scanner's name is only slightly different from the models mentioned
above, please let us know.
OPTIONS
The options the backend supports can either be selected through command
- line options to programs like scanimage or through GUI elements in xs-
- canimage or xsane. Valid command line options and their syntax can be
- listed by using:
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1). Valid command line options and their syntax
+ can be listed by using:
scanimage --help -d hp5590:interface:device
where interface and device specify the device in question, as in the
- configuration file. Add --all-options to also list the hardware read-
- out options. The -d parameter and its argument can be omitted to ob-
+ configuration file. Add --all-options to also list the hardware read-
+ out options. The -d parameter and its argument can be omitted to ob-
tain information on the first scanner identified.
Use the command:
@@ -130,11 +130,11 @@
--hide-eop-pixel[=yes|no]
Hide end-of-page indicator pixels and overwrite with color of
next neighbor pixels. (Default: yes)
- The scanner uses the last pixel in every scan line for storing the end-
- of-page status. This is needed to detect the end of the document sheet
- when the automatic document feeder (ADF) is used. Unfortunately the
- end-of-page pixels are also generated in flatbed scans. It is recom-
- mended to hide these pixels.
+ The scanner uses the last pixel in every scan line for storing
+ the end-of-page status. This is needed to detect the end of the
+ document sheet when the automatic document feeder (ADF) is used.
+ Unfortunately the end-of-page pixels are also generated in
+ flatbed scans. It is recommended to hide these pixels.
--trailing-lines-mode mode
Filling mode of trailing lines after end of page when automatic
@@ -157,52 +157,53 @@
Set color value for filling trailing scan lines in trailing
lines mode "color" (see previous option). (Default color: vio-
let)
- The RGB color value must be specified and calculated as 65536 * r + 256
- * g + b, with r, g, b being values in the range of 0 .. 255.
+ The RGB color value must be specified and calculated as 65536 *
+ r + 256 * g + b, with r, g, b being values in the range of 0 ..
+ 255.
READ OUT OPTIONS
- The following options allow reading out the button state, counter val-
- ue, color setting, and the state of document in ADF. This can be used
- to programmatically control corresponding scanner options like switch-
- ing between flatbed and ADF mode, or triggering prost processing tasks
+ The following options allow reading out the button state, counter val-
+ ue, color setting, and the state of document in ADF. This can be used
+ to programmatically control corresponding scanner options like switch-
+ ing between flatbed and ADF mode, or triggering post processing tasks
after scanning.
--button-pressed
- Get the id of the last button pressed. Id is one of "none",
+ Get the id of the last button pressed. Id is one of "none",
"power", "scan", "collect", "file", "email", "copy", "up",
"down", "mode", "cancel".
- 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
- "none".
+ The scanner stores the id of the last button pressed until it is
+ read. After read out, the state is reset and subsequent read-
+ ings will return "none".
--color-led
- Get the state of the color LED indicators. The state is either
+ Get the state of the color LED indicators. The state is either
"color" or "black_white".
--counter-value
- Get the counter value as shown on LCD. The value is in the
+ Get the counter value as shown on LCD. The value is in the
range of 1 .. 99.
--doc-in-adf
- Get the state of the document-available indicator of the auto-
+ Get the state of the document-available indicator of the auto-
matic document feeder (ADF). The state is either "yes" or "no".
HINTS FOR USERS OF SCANBD
- Scanbd is a scanner button daemon, which can read scanner buttons and
- trigger scan actions.
+ scanbd(8) is a scanner button daemon, which can read scanner buttons
+ and trigger scan actions.
- Do not use the old scanbuttond interface with hp5590. It is outdated
- and shall not be used any more. Scanbd's regular interface is fully
- supported by the current version of the hp5590 backend.
+ Do not use the old scanbuttond(8) interface with hp5590. It is outdat-
+ ed and shall not be used any more. The regular interface of scanbd(8)
+ is fully supported by the current version of the hp5590 backend.
- This example shows a minimum configuration file and the corresponding
- script file for scanbd to be included in scanbd.conf.
+ This example shows a minimum configuration file and the corresponding
+ script file for scanbd(8) to be included in scanbd.conf.
- o hp5590.conf
+ o hp5590.conf
device hp5590 {
# Device matching
@@ -257,7 +258,7 @@
ENVIRONMENT
- If the library was compiled with debug support enabled, this environ-
+ If the library was compiled with debug support enabled, this environ-
ment variable controls the debug level for this backend.
SANE_DEBUG_HP5590
@@ -275,12 +276,13 @@
SEE ALSO
- sane(7), sane-usb(5)
+ sane(7), sane-usb(5) scanbd(8), scanimage(1), xscanimage(1), xsane(1)
AUTHORS
- Ilia Sotnikov <hostcc@gmail.com>.
+ Ilia Sotnikov <hostcc@gmail.com>.
+
13 Jul 2008 sane-hp5590(5)
diff --git a/man/sane-hpljm1005.5.html b/man/sane-hpljm1005.5.html
index 408020d5..0ed3cd55 100644
--- a/man/sane-hpljm1005.5.html
+++ b/man/sane-hpljm1005.5.html
@@ -2,7 +2,7 @@
sane-hpljm1005.5
-
+
sane-hpljm1005.5
@@ -26,8 +26,8 @@
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 the USB vendor and device ids (e.g. from
- /proc/bus/usb/devices, sane-find-scanner or syslog) to us. Even if the
- scanner's name is only slightly different from the models mentioned
+ /proc/bus/usb/devices, sane-find-scanner(1) or syslog) to us. Even if
+ the scanner's name is only slightly different from the models mentioned
above, please let us know.
@@ -46,14 +46,25 @@
that support dynamic loading).
+
+ENVIRONMENT
+ SANE_DEBUG_HPLJM1005
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+ There is not currently a great deal of diagnostic output, it be-
+ ing mainly confined to error conditions.
+
+
SEE ALSO
- sane(7), sane-usb(5),
+ sane(7), sane-usb(5), sane-find-scanner(1)
AUTHOR
- Philippe Retornaz <couriousous@mandriva.org>
+ Philippe Retornaz <couriousous@mandriva.org>
13 Jul 2008 sane-hpljm1005(5)
diff --git a/man/sane-hpsj5s.5.html b/man/sane-hpsj5s.5.html
index 3388c3b6..534fe2ea 100644
--- a/man/sane-hpsj5s.5.html
+++ b/man/sane-hpsj5s.5.html
@@ -2,7 +2,7 @@
sane-hpsj5s.5
-
+
sane-hpsj5s.5
@@ -27,10 +27,10 @@
extremely improbable) that your scanner will be damaged.
LIMITATIONS: For now this backend works only on Linux. This limitation
- is due to dependence on the libieee1284 library. If your system sup-
- ports libieee1284 too, this backend should work. If you ported
- libieee1284 for your platform, please let me know. Your system should
- support EPP (or EPP+ECP ) mode to operate this scanner. Future versions
+ is due to dependence on the libieee1284(3) library. If your system sup-
+ ports libieee1284(3) too,this backend should work. If you ported li-
+ bieee1284(3) for your platform, please let me know. Your system should
+ support EPP (or 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. Sup-
port for multiple scanners could be implemented too.
@@ -39,7 +39,7 @@
modes are not supported for now.
That said, TESTERS ARE WELCOME. Send your bug reports and comments to
- Max Vorobiev <pcwizard@yandex.ru>.
+ Max Vorobiev <pcwizard@yandex.ru>.
@@ -48,9 +48,9 @@
special
- Where special is the parallel port name in form, libieee1284 expects.
- It seems to be system dependent. Under Linux it's parport0, parport1,
- etc.
+ Where special is the parallel port name in form, libieee1284(3) ex-
+ pects. It seems to be system dependent. Under Linux it's parport0, par-
+ port1, etc.
@@ -92,24 +92,31 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
- SEE ALSO
- sane(7)
- http://hpsj5s.sourceforge.net
- http://cyberelk.net/tim/libieee1284
+ SANE_DEBUG_HPSJ5S
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
+
+
+
+SEE ALSO
+ sane(7), libieee1284(3)
+ http://hpsj5s.sourceforge.net
+ http://cyberelk.net/tim/libieee1284
AUTHOR
Max Vorobiev
- Man page mostly based on canon.man
+ Man page mostly based on canon.man.
13 Jul 2008 sane-hpsj5s(5)
diff --git a/man/sane-hs2p.5.html b/man/sane-hs2p.5.html
index 99b67d07..5ba34f28 100644
--- a/man/sane-hs2p.5.html
+++ b/man/sane-hs2p.5.html
@@ -2,7 +2,7 @@
sane-hs2p.5
-
+
sane-hs2p.5
@@ -35,8 +35,8 @@
special
Where special is either the path-name for the special device that cor-
- responds to a SCSI scanner. The program sane-find-scanner helps to find
- out the correct device. Under Linux, such a device name could be
+ responds to a SCSI scanner. The program sane-find-scanner(1) helps to
+ find out the correct device. Under Linux, such a device name could be
/dev/sg0 or /dev/sga, for example. See sane-scsi(5) for details.
@@ -70,27 +70,27 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_HS2P
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
- A value of 255 prints all debug output. Smaller values reduce
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend. A
+ value of 255 prints all debug output. Smaller values reduce
verbosity.
CURRENT STATUS
- The 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
+ The sane-hs2p backend is now in version 1.00. All major scanning-re-
+ lated features are supported, except for those features requiring the
+ optional IPU. Scanning from the flatbed or ADF (either simplex or du-
+ plex) is supported. Lineart, halftone, 4-bit gray, and 8-bit gray are
supported. Pre-set gamma tables and halftone patterns are supported, as
well as brightness, threshold, contrast. Also supported is scan wait
mode, binary and gray filtering, negative scanning, and absolute or
@@ -110,17 +110,17 @@
MISSING FUNCTIONALITY
- The SCSI commands for uploading (2AH) or downloading (28H) custom
- halftone patterns (02H) and gamma vectors (03H) should work, but
- require implementing the SANE Option-Value code to allow the user to
- create the tables to be uploaded to the scanner. No support for Mainte-
- nance Data (80H) is planned as this functionality is more 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) parame-
- ters 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.
+ The SCSI commands for uploading (2AH) or downloading (28H) custom half-
+ tone patterns (02H) and gamma vectors (03H) should work, but require
+ implementing the SANE Option-Value code to allow the user to create the
+ tables to be uploaded to the scanner. No support for Maintenance Data
+ (80H) is planned as this functionality is more 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 adjust-
+ ments 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.
@@ -130,8 +130,8 @@
AUTHOR
- jeremy <jeremy@acjlaw.net>
- Maintained by Jeremy Johnson <jeremy@acjlaw.net>
+ jeremy <jeremy@acjlaw.net>
+ Maintained by Jeremy Johnson <jeremy@acjlaw.net>
13 Jul 2008 sane-hs2p(5)
diff --git a/man/sane-ibm.5.html b/man/sane-ibm.5.html
index a0833fca..f68a9824 100644
--- a/man/sane-ibm.5.html
+++ b/man/sane-ibm.5.html
@@ -2,7 +2,7 @@
sane-ibm.5
-
+
sane-ibm.5
@@ -35,8 +35,8 @@
special
Where special is either the path-name for the special device that cor-
- responds to a SCSI scanner. The program sane-find-scanner helps to find
- out the correct device. Under Linux, such a device name could be
+ responds to a SCSI scanner. The program sane-find-scanner(1) helps to
+ find out the correct device. Under Linux, such a device name could be
/dev/sg0 or /dev/sga, for example. See sane-scsi(5) for details.
@@ -70,17 +70,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_IBM
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
@@ -91,8 +91,8 @@
AUTHOR
- mf <massifr@tiscalinet.it>
- Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
+ mf <massifr@tiscalinet.it>
+ Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de>
13 Jul 2008 sane-ibm(5)
diff --git a/man/sane-kodak.5.html b/man/sane-kodak.5.html
index 8c05a5cb..31871669 100644
--- a/man/sane-kodak.5.html
+++ b/man/sane-kodak.5.html
@@ -2,7 +2,7 @@
sane-kodak.5
-
+
sane-kodak.5
@@ -29,7 +29,7 @@
This version should support models which speak the Kodak SCSI and
Firewire protocols. The i1860 was used to develop the backend, but
other models may work with only minimal modifications. Please see the
- list at http://www.sane-project.org/sane-supported-devices.html for an
+ list at http://www.sane-project.org/sane-supported-devices.html for an
updated list.
If you have a machine not on that list, or reported as 'untested': the
@@ -49,35 +49,35 @@
OPTIONS
Effort has been made to expose the basic hardware options, including:
- source s
+ --source s
Selects the source for the scan. Options may include "Flatbed",
"ADF Front", "ADF Back", "ADF Duplex".
- mode m
+ --mode m
Selects the mode for the scan. Options may include "Lineart",
"Halftone", "Gray", and "Color".
- resolution
+ --resolution
Controls scan resolution. Available choices may be limited by
mode.
- tl-x, tl-y, br-x, br-y
+ --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.
+ renamed -t, -l, -x, -y by some frontends.
- page-width, page-height
+ --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.
Other options will be available based on the capabilities of the scan-
- ner. 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
+ ner. Use scanimage --help to get a list, but be aware that some op-
+ tions may be settable only when another option has been set, and that
advanced options may be hidden by some frontend programs.
CONFIGURATION FILE
- The configuration file "kodak.conf" is used to tell the backend how to
+ The configuration file kodak.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
@@ -88,7 +88,7 @@
Scanners can be specified in the configuration file in 2 ways:
"scsi KODAK"
- Requests backend to search all scsi busses in the system for a
+ Requests backend to search all scsi buses in the system for a
device which reports itself to be a scanner made by 'KODAK'.
"scsi /dev/sg0" (or other scsi device file)
@@ -115,7 +115,7 @@
ENVIRONMENT
- The backend uses a single environment variable, SANE_DEBUG_KODAK, which
+ The backend uses a single environment variable, SANE_DEBUG_KODAK, which
enables debugging output to stderr. Valid values are:
5 Errors
@@ -136,18 +136,19 @@
CREDITS
- The various authors of the sane-fujitsu backend provided useful code.
+ The various authors of the sane-fujitsu(5) backend provided useful
+ code.
Kodak provided access to hardware, documentation and personnel.
SEE ALSO
- sane(7), sane-scsi(5)
+ sane(7), sane-scsi(5), scanimage(1)
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com>
10 Feb 2010 sane-kodak(5)
diff --git a/man/sane-kodakaio.5.html b/man/sane-kodakaio.5.html
index 71bfa9bf..8d1efc09 100644
--- a/man/sane-kodakaio.5.html
+++ b/man/sane-kodakaio.5.html
@@ -2,7 +2,7 @@
sane-kodakaio.5
-
+
sane-kodakaio.5
@@ -18,7 +18,7 @@
DESCRIPTION
The sane-kodakaio library implements a SANE (Scanner Access Now Easy)
- backend which provides access to Kodak aio printer / scanners, like the
+ 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 candi-
@@ -38,25 +38,32 @@
CONFIGURATION FILE
- The configuration file "kodakaio.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.
+ The configuration file kodakaio.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.
ENVIRONMENT
- The backend uses a single environment variable, SANE_DEBUG_KODAKAIO,
- which enables debugging output to stderr.
+ SANE_DEBUG_KODAKAIO
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
KNOWN ISSUES
- Most hardware options are either not supported or not exposed for con-
- trol by the user, including: multifeed detection, image compression
+ Most hardware options are either not supported or not exposed for con-
+ trol by the user, including: multifeed detection, image compression
etc.
+
+SEE ALSO
+ sane(7)
+
+
AUTHOR
P. Newall
diff --git a/man/sane-kvs1025.5.html b/man/sane-kvs1025.5.html
index 50e26fa7..ed0e86f6 100644
--- a/man/sane-kvs1025.5.html
+++ b/man/sane-kvs1025.5.html
@@ -2,7 +2,7 @@
sane-kvs1025.5
-
+
sane-kvs1025.5
@@ -41,12 +41,12 @@
SEE ALSO
- sane(7), sane-usb(5)
+ sane(7), sane-usb(5)
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com>
16 Apr 2010 sane-kvs1025(5)
diff --git a/man/sane-kvs20xx.5.html b/man/sane-kvs20xx.5.html
index 746d074d..7214afc8 100644
--- a/man/sane-kvs20xx.5.html
+++ b/man/sane-kvs20xx.5.html
@@ -2,7 +2,7 @@
sane-kvs20xx.5
-
+
sane-kvs20xx.5
@@ -13,7 +13,7 @@
NAME
sane-kvs20xx - SANE backend for Panasonic KV-S20xxC USB/SCSI ADF scan-
- ners.
+ ners
@@ -45,7 +45,7 @@
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com>
09 Jun 2010 sane-kvs20xx(5)
diff --git a/man/sane-kvs40xx.5.html b/man/sane-kvs40xx.5.html
index a9fd13b1..b32a3832 100644
--- a/man/sane-kvs40xx.5.html
+++ b/man/sane-kvs40xx.5.html
@@ -2,7 +2,7 @@
sane-kvs40xx.5
-
+
sane-kvs40xx.5
@@ -29,8 +29,8 @@
regarding the capabilities or reliability of the backend. All informa-
tion contained here is suspect.
- The backend uses pthreads directly, and so requires pthreads to be
- enabled.
+ The backend uses pthreads directly, and so requires pthreads to be en-
+ abled.
@@ -48,7 +48,7 @@
AUTHOR
- m. allan noah: <kitno455 a t gmail d o t com>
+ m. allan noah: <kitno455 a t gmail d o t com>
03 Jun 2011 sane-kvs40xx(5)
diff --git a/man/sane-leo.5.html b/man/sane-leo.5.html
index 15533e44..f7cb003e 100644
--- a/man/sane-leo.5.html
+++ b/man/sane-leo.5.html
@@ -2,7 +2,7 @@
sane-leo.5
-
+
sane-leo.5
@@ -27,11 +27,11 @@
Vendor Model status
---------------------- -----------
Across FS-1130 tested
- Leo S3 tested
+ LEO S3 tested
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.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
If you have any strange behavior, please report to the backend main-
tainer or to the SANE mailing list.
@@ -89,8 +89,8 @@
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/leo.conf supports only one
- information: the device name to use (eg /dev/scanner).
+ The configuration file /usr/local/etc/sane.d/leo.conf supports only one
+ information: the device name to use (eg /dev/scanner).
@@ -106,8 +106,8 @@
ENVIRONMENT
SANE_DEBUG_LEO
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -118,10 +118,7 @@
However they are only software adjustments. This backend only imple-
ments what the scanner can support.
-
-
-BUGS
- None known.
+ SH BUGS None known.
@@ -129,6 +126,7 @@
sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+
AUTHOR
The package is actively maintained by Frank Zago.
diff --git a/man/sane-lexmark.5.html b/man/sane-lexmark.5.html
index f692ab84..5b655ab9 100644
--- a/man/sane-lexmark.5.html
+++ b/man/sane-lexmark.5.html
@@ -2,7 +2,7 @@
sane-lexmark.5
-
+
sane-lexmark.5
@@ -33,17 +33,18 @@
Lexmark X1180 good
Lexmark X1185 complete
Lexmark X12xx good in USB1.1,
- not fully tested in USB2.0
+ not fully tested in USB2.0
Dell A920 good
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.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
- If you have any strange behavior, please report to the backend main-
+ If you notice any strange behavior, please report to the backend main-
tainer or to the SANE mailing list.
Valid command line options and their syntax can be listed by using
+
scanimage --help -d lexmark:usb:<usb port>
Scan Mode Options
@@ -78,13 +79,13 @@
--threshold
selects the minimum-brightness to get a white point. The
threshold is only used with Lineart mode scans. It is specified
- as a percentage in the range 0..100% (in steps of 1). The
- default value of the threshold option is 50.
+ as a percentage in the range 0..100% (in steps of 1). The de-
+ fault value of the threshold option is 50.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/lexmark.conf contains only
+ The configuration file /usr/local/etc/sane.d/lexmark.conf contains only
the usb device id (eg usb 0x043d 0x007c).
@@ -101,10 +102,13 @@
ENVIRONMENT
SANE_DEBUG_LEXMARK
- SANE_DEBUG_LEXMARK_LOW 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
+
+ SANE_DEBUG_LEXMARK_LOW
+ Provides debug output for low level Lexmark functions.
@@ -136,13 +140,14 @@
The new version is currently developed by Stephane Voltz.
http://stef.dev.free.fr/sane/lexmark
- X74 support was written by Torsten Houwaart (<ToHo@gmx.de>)
+ X74 support was written by Torsten Houwaart
+ <ToHo@gmx.de>
CREDITS
Many thanks go to:
- Julien Furgerot who lend me a Dell A920. Robert Price, Dani Ele
+ Julien Furgerot who lent me a Dell A920. Robert Price, Dani Ele
and Dalai Felinto for the time they spent recording USB activity
and testing the experimental version.
diff --git a/man/sane-ma1509.5.html b/man/sane-ma1509.5.html
index cf0c6d49..6f5d6b6b 100644
--- a/man/sane-ma1509.5.html
+++ b/man/sane-ma1509.5.html
@@ -2,7 +2,7 @@
sane-ma1509.5
-
+
sane-ma1509.5
@@ -36,8 +36,8 @@
the operating system. See sane-usb(5) for details.
If you own a scanner other than the Mustek BearPaw 1200F 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
+ with this backend, please let me know this by sending the scanner's ex-
+ act model name and the USB vendor and device ids (e.g. from
/proc/bus/usb/devices or syslog) to me.
@@ -62,12 +62,12 @@
usb vendor_id product_id statements which are already included into
ma1509.conf. This is only supported with Linux 2.4.8 and higher and
all systems that support libsub. "vendor_id" and "product_id" are hexa-
- decimal numbers that identify the scanner. If this doesn't work, a
- device name must be placed in ma1509.conf as described above.
+ decimal numbers that identify the scanner. If this doesn't work, a de-
+ vice name must be placed in ma1509.conf as described above.
To set the time the lamp needs for warm-up, use option warmup-time in
- ma1509.conf. The time is given in seconds after the option. The
- default is 30 seconds.
+ ma1509.conf. The time is given in seconds after the option. The de-
+ fault is 30 seconds.
@@ -92,17 +92,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_MA1509
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
@@ -115,7 +115,7 @@
AUTHOR
- Henning Meier-Geinitz <henning@meier-geinitz.de>
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
diff --git a/man/sane-magicolor.5.html b/man/sane-magicolor.5.html
index f0d730eb..da7ba76a 100644
--- a/man/sane-magicolor.5.html
+++ b/man/sane-magicolor.5.html
@@ -2,7 +2,7 @@
sane-magicolor.5
-
+
sane-magicolor.5
@@ -69,24 +69,24 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "/tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories /tmp/config, ., and /usr/local/etc/sane.d
+ being searched (in this order).
SANE_DEBUG_MAGICOLOR
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_MAGICOLOR=127
To obtain debug messages from the backend, set this environment
- variable before calling your favorite frontend (e.g. xscanim-
- age).
+ variable before calling your favorite frontend (e.g. xscanim-
+ age(1)).
Example: SANE_DEBUG_MAGICOLOR=65 xscanimage
@@ -107,7 +107,7 @@
AUTHOR
- Reinhold Kainhofer <reinhold@kainhofer.com>
+ Reinhold Kainhofer <reinhold@kainhofer.com>
10 Jan 2011 sane-magicolor(5)
diff --git a/man/sane-matsushita.5.html b/man/sane-matsushita.5.html
index 6658c000..0e97888e 100644
--- a/man/sane-matsushita.5.html
+++ b/man/sane-matsushita.5.html
@@ -2,7 +2,7 @@
sane-matsushita.5
-
+
sane-matsushita.5
@@ -41,6 +41,7 @@
end.
Valid command line options and their syntax can be listed by using
+
scanimage --help -d matsushita
Scan Mode
@@ -61,8 +62,8 @@
Geometry
--paper-size A4|...|Legal|Letter [A4]
- options selects the area to scan. It adjust the -l -t -x -y
- options accordingly. It does not need to be the real size of the
+ options selects the area to scan. It adjust the -l -t -x -y op-
+ tions accordingly. It does not need to be the real size of the
paper.
-l -t -x -y
@@ -112,8 +113,8 @@
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/matsushita.conf supports
- the device name to use (eg /dev/scanner) and the SCSI option to auto-
+ The configuration file /usr/local/etc/sane.d/matsushita.conf supports
+ the device name to use (eg /dev/scanner) and the SCSI option to auto-
detect the scanners supported.
@@ -130,8 +131,8 @@
ENVIRONMENT
SANE_DEBUG_MATSUSHITA
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -154,19 +155,19 @@
Duplex mode
The backend does not support the setting of different options
- for each side. The scan will occur with the same options
- (halftone pattern, brightness, image emphasis) for both sides.
+ for each side. The scan will occur with the same options (half-
+ tone pattern, brightness, image emphasis) for both sides.
SCANNING EXAMPLE
To date, the only frontend capable of using this scanner at full speed
- is scanadf.
+ is scanadf(1).
- A scanadf command line would be:
+ A 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"
+ scanadf -d matsushita --output-file scan%04d.pbm --start-count 0 --du-
+ plex --resolution 300 --feeder-mode="All pages" --paper-size="A4"
diff --git a/man/sane-microtek.5.html b/man/sane-microtek.5.html
index c0951c7f..b274539c 100644
--- a/man/sane-microtek.5.html
+++ b/man/sane-microtek.5.html
@@ -2,7 +2,7 @@
sane-microtek.5
-
+
sane-microtek.5
@@ -47,9 +47,9 @@
The driver does not support the newest Microtek scanners, such as the
V330 and V660, which use a new and very different SCSI-II command set.
- For those, try the alternate microtek2 backend. Most non-SCSI scanners
- would use the new command set. Most scanners newer than the Scanmaker
- E6 would use the new command set.
+ For those, try the alternate microtek2(5) backend. Most non-SCSI scan-
+ ners would use the new command set. Most scanners newer than the Scan-
+ maker E6 would use the new command set.
If you own a Microtek scanner other than the ones listed above, tell us
what happens --- see the BUGS section at the end of this document.
@@ -57,7 +57,8 @@
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:
- http://www.mir.com/mtek/
+
+ http://www.mir.com/mtek/
@@ -112,13 +113,13 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_MICROTEK
If the library was compiled with debugging support enabled, this
@@ -129,7 +130,7 @@
SEE ALSO
- sane(7), sane-scsi(5)
+ sane(7), sane-scsi(5), sane-microtek2(5)
@@ -154,17 +155,17 @@
(If it does, report it.)
Send lengthy bug reports and new scanner information to
- mtek-bugs@mir.com. All bug reports and new scanner inquiries should
+ 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.
+ setting the SANE_DEBUG_MICROTEK environment variable described above.
For example:
setenv SANE_DEBUG_MICROTEK 128
More general comments, suggestions, and inquiries about frontends or
- SANE should go to sane-devel@alioth-lists.debian.net, the SANE Develop-
- ers mailing list. Have a look at http://www.sane-project.org/mail-
- ing-lists.html concerning subscription to sane-devel.
+ SANE should go to sane-devel@alioth-lists.debian.net, the SANE Develop-
+ ers mailing list. Have a look at http://www.sane-project.org/mail-
+ ing-lists.html concerning subscription to sane-devel.
13 Jul 2008 sane-microtek(5)
diff --git a/man/sane-microtek2.5.html b/man/sane-microtek2.5.html
index fe1d0ac8..4e59db59 100644
--- a/man/sane-microtek2.5.html
+++ b/man/sane-microtek2.5.html
@@ -2,7 +2,7 @@
sane-microtek2.5
-
+
sane-microtek2.5
@@ -22,13 +22,13 @@
backend that 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 http://karstenfestag.gmxhome.de
+ backend can be obtained from http://karstenfestag.gmxhome.de.
There exists a different backend for Microtek scanners with SCSI-1 com-
mand set. Refer to sane-microtek(5) for details.
And there is work in progress for the ScanMaker 3600. See
- http://sourceforge.net/projects/sm3600
+ http://sourceforge.net/projects/sm3600.
At present, the following scanners are known positively to work with
this backend:
@@ -59,7 +59,7 @@
Scanport SQ4836 SCSI
Scanpaq SQ2030 Parport
- Additional information can be found at http://www.sane-project.org/.
+ Additional information can be found at http://www.sane-project.org/.
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 dif-
@@ -94,15 +94,15 @@
How to create the logfile?
- put the line
- "option dump 2" into your microtek2.conf file or change the
- existing "option dump" to "2"
+ "option dump 2" into your microtek2.conf file or change the ex-
+ isting "option dump" to "2"
- in a terminal (bash) type
"export SANE_DEBUG_MICROTEK2=30" and then
"scanimage -l0 -t0 -x100 -y20 2>scan.log >sout.pnm"
You get two files: scan.log contains the logfile and sout.pnm
- the scanned image (if there was scanned something). Zip them
- before sending.
+ the scanned image (if there was scanned something). Zip them be-
+ fore sending.
@@ -111,7 +111,7 @@
supported by the scanner in dependence of the scanning-mode and other
options. Not supported options are disabled.
- The following options are supported by the Microtek2-driver:
+ The following options are supported by the sane-microtek2 driver:
Color, grayscale, halftone and lineart scans.
@@ -139,8 +139,8 @@
CONFIGURATION
- The configuration file for this backend resides in
- /usr/local/etc/sane.d/microtek2.conf.
+ The configuration file for this backend resides in /usr/lo-
+ cal/etc/sane.d/microtek2.conf.
Its contents is a list of device names that correspond to Microtek
scanners with SCSI-2 interface. Empty lines and lines starting with a
@@ -149,10 +149,10 @@
The configuration file may also contain options. Global options that
are valid for all devices are placed above the device names. Device-
specific options are placed under the device name. Note that, except
- for option dump <n> and option strip-height <n>, the entry in the
- microtek2.conf file only enables the corresponding option for being
- showed in the frontend. There, in the frontend, you can switch the
- options on and off. Currently the following options are supported:
+ for option dump <n> and option strip-height <n>, the entry in the mi-
+ crotek2.conf file only enables the corresponding option for being
+ showed in the frontend. There, in the frontend, you can switch the op-
+ tions on and off. Currently the following options are supported:
option dump <n>
option strip-height <n>
@@ -168,8 +168,8 @@
primarily useful for debugging purpose. This option has to be a global
option and is best placed at the top of the microtek2.conf file.
- If n=1 the contents of the command blocks and the results for the
- INQUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
+ If n=1 the contents of the command blocks and the results for the IN-
+ QUIRY and READ SCANNER ATTRIBUTES command are printed to stderr.
If n=2 the contents of the command blocks for all other SCSI commands
are printed to stderr, too. If n=3 the contents of the gamma table is
@@ -189,8 +189,8 @@
sized scan area.
The following options enable or disable additional frontend options. If
- an option is set to <on> an appropriate option will appear in the fron-
- tend.
+ an option is set to <on> an appropriate option will appear in the
+ frontend.
option no-backtrack-option <on/off> prevents the scanner head from mov-
ing backwards between the read commands. This speeds up scanning. Try
@@ -265,11 +265,11 @@
ENVIRONMENT
SANE_DEBUG_MICROTEK2
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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 lev-
+ set SANE_DEBUG_MICROTEK2 to 1 (Remark: The whole debugging lev-
els should be better revised).
E.g. just say:
export SANE_DEBUG_MICROTEK2=128
@@ -277,13 +277,13 @@
SEE ALSO
- sane-scsi(5), sane(7)
+ sane-scsi(5), sane(7)
AUTHORS
Bernd Schroeder (not active anymore)
- Karsten Festag karsten.festag@gmx.de
+ Karsten Festag <karsten.festag@gmx.de>.
13 Jul 2008 sane-microtek2(5)
diff --git a/man/sane-mustek.5.html b/man/sane-mustek.5.html
index b8b55f04..98ee2861 100644
--- a/man/sane-mustek.5.html
+++ b/man/sane-mustek.5.html
@@ -2,7 +2,7 @@
sane-mustek.5
-
+
sane-mustek.5
@@ -65,8 +65,8 @@
sane-mustek_usb(5), sane-gt68xx(5), and sane-plustek(5).
Mustek scanners have no protection against exceeding the physical scan
- area height. That is, if a scan is attempted with a height that
- exceeds the height of the scan surface, the scanner begins making loud
+ area height. That is, if a scan is attempted with a height that ex-
+ ceeds the height of the scan surface, the scanner begins making loud
noises and the scan mechanism may be damaged. Thus, if you hear such a
noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your
scanner is in the list of known scanners. There is more information in
@@ -77,9 +77,9 @@
ner's exact model name (look at the front and back of the scanner) and
a debug output to sane-devel@alioth-lists.debian.net. You can get the
debug output by setting the environment variable SANE_DEBUG_MUSTEK to 5
- and showing the list of available scanners with 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
+ and showing the list of available scanners with scanimage -L. Please
+ send all of it to the mailing list. You must be subscribed to sane-de-
+ vel before you can send mail to the list. See
http://www.sane-project.org/mailing-lists.html for details.
@@ -92,11 +92,11 @@
Where special is either the path-name for the special device that cor-
responds to a SCSI scanner or the port number at which the parallel
port scanners can be found (see section 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 sane-find-scanner
+ For SCSI scanners, the special device name must be a generic SCSI de-
+ vice or a symlink to such a device. The program sane-find-scanner(1)
helps to find out the correct device. Under Linux, such a device name
- could be /dev/sg0 or /dev/sg3, for example. See sane-scsi(5) for
- details.
+ could be /dev/sg0 or /dev/sg3, for example. See sane-scsi(5) for de-
+ tails.
@@ -110,8 +110,8 @@
buffersize, blocksize, strip-height, disable-double-buffering, dis-
able-backtracking, and force-wait.
- Options come in two flavors: global and positional ones. Global
- options apply to all devices managed by the backend whereas positional
+ Options come in two flavors: global and positional ones. Global op-
+ tions apply to all devices managed by the backend whereas positional
options apply just to the most recently mentioned device. Note that
this means that the order in which the options appear matters!
@@ -144,15 +144,15 @@
value set for the maximum amount of data scanned in one block. The buf-
fer size is specified in kilobytes. Some scanners freeze if this value
is bigger than 2048. The default value is 1 GB (so effectively no
- limit) for most scanners. Don't change this value if you don't know
- exactly what you do.
+ limit) for most scanners. Don't change this value if you don't know ex-
+ actly what you do.
Option strip-height is a global option that limits the maximum height
of the strip scanned with a single SCSI read command. The height is
specified in inches and may contain a fractional part (e.g., 1.5).
- Setting the strip-height to a small value (one inch, for example)
- reduces the likelihood of encountering problems with SCSI driver time-
- outs and/or timeouts with other devices on the same SCSI bus. Unfortu-
+ Setting the strip-height to a small value (one inch, for example) re-
+ duces the likelihood of encountering problems with SCSI driver timeouts
+ and/or timeouts with other devices on the same SCSI bus. Unfortu-
nately, it also increases scan times. With current SCSI adapters and
drivers this option shouldn't be needed any more.
@@ -171,8 +171,8 @@
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 neces-
- sary with the 600 II N or when scanimage is used multiple times (e.g.
- in scripts). The default is off (not set).
+ sary with the 600 II N or when scanimage(1) is used multiple times
+ (e.g. in scripts). The default is off (not set).
A sample configuration file is shown below:
@@ -283,17 +283,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_MUSTEK
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Value Description
@@ -310,14 +310,16 @@
SEE ALSO
sane(7), sane-find-scanner(1), sane-scsi(5), sane-mustek_usb(5),
- sane-gt68xx(5), sane-plustek(5), sane-mustek_pp(5)
+ sane-gt68xx(5), sane-plustek(5), sane-mustek_pp(5), sane-ma1509(5),
+ scanimage(1), xscanimage(1)
+
/usr/local/share/doc/sane-backends/mustek/mustek.CHANGES
http://www.meier-geinitz.de/sane/mustek-backend/
AUTHOR
- David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
+ David Mosberger, Andreas Czechanowski, Andreas Bolsch (SE extensions),
Henning Meier-Geinitz, James Perry (600 II EP).
@@ -328,10 +330,10 @@
Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
- The gamma table supports only 256 colors, even if some scanners can do
+ The gamma table supports only 256 colors, even if some scanners can do
more.
- More detailed bug information is available at the Mustek backend home-
+ More detailed bug information is available at the Mustek backend home-
page: http://www.meier-geinitz.de/sane/mustek-backend/.
13 Jul 2008 sane-mustek(5)
diff --git a/man/sane-mustek_pp.5.html b/man/sane-mustek_pp.5.html
index 37f53852..d67b9db9 100644
--- a/man/sane-mustek_pp.5.html
+++ b/man/sane-mustek_pp.5.html
@@ -2,7 +2,7 @@
sane-mustek_pp.5
-
+
sane-mustek_pp.5
@@ -90,21 +90,21 @@
in the backend itself (see GLOBAL OPTIONS).
Note that the backend needs to run as root or has to have appropriate
- access rights to /dev/parport* if libieee1284 support is compiled in.
+ access rights to /dev/parport* if libieee1284 support is compiled in.
To allow user access to the scanner run the backend through the network
- interface (See saned(8) and sane-net(5)). Note also that the backend
+ interface (See saned(8) and sane-net(5)). Note also that the backend
does not support parport sharing, i.e. if you try printing while scan-
ning, your computer may crash. To enable parport sharing, you have to
enable libieee1284 at compile time. This backend also conflicts with
- the sane-musteka4s2 backend. You can only enable one of them in your
- dll.conf. However, you have to enable the backend explicitly in your
- dll.conf, just remove the hash mark in the line "mustek_pp".
+ the sane-musteka4s2(5) backend. You can only enable one of them in your
+ dll.conf. However, you have to enable the backend explicitly in your
+ dll.conf, just remove the hash mark in the line "mustek_pp".
DEVICE DEFINITION
This backend allows multiple devices being defined and configured via
- the mustek_pp.conf file (even simultaneously, provided that they are
+ the mustek_pp.conf file (even simultaneously, provided that they are
connected to different parallel ports). Please make sure to edit this
file before you use the backend.
@@ -122,15 +122,15 @@
the port (default setup), valid port names are parport0, par-
port1, and parport2.
- In case the backend is configured for raw IO (old setup), port
- addresses have to be used instead of port names: 0x378, 0x278, or
- 0x3BC. The mapping of parallel ports (lp0, lp1, and lp2) to these
- addresses 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.
+ In case the backend is configured for raw IO (old setup), port ad-
+ dresses have to be used instead of port names: 0x378, 0x278, or 0x3BC.
+ The mapping of parallel ports (lp0, lp1, and lp2) to these addresses
+ 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.
If you are unsure which port to use, you can use the magic value * to
probe for your scanner.
@@ -166,14 +166,14 @@
scanner Mustek_600IIIEP * ccd300
- If in doubt which port you have to use, or whether your scanner is
- detected at all, you can use sane-find-scanner -p to probe all config-
- ured ports.
+ If in doubt which port you have to use, or whether your scanner is de-
+ tected at all, you can use sane-find-scanner -p to probe all configured
+ ports.
CONFIGURATION
- The contents of the mustek_pp.conf file is a list of device definitions
+ The contents of the mustek_pp.conf file is a list of device definitions
and device options that correspond to Mustek scanners. Empty lines and
lines starting with a hash mark (#) are ignored. Options have the fol-
lowing format:
@@ -199,10 +199,10 @@
CIS driver options
top_adjust <value>
Vertical adjustment of the origin, expressed in millimeter
- (floating point). This option can be used to calibrate the
- position of the origin, within certain limits. Note that CIS
- scanners are probably temperature sensitive, and that a certain
- inaccuracy may be hard to avoid. Differences in offset between
+ (floating point). This option can be used to calibrate the po-
+ sition of the origin, within certain limits. Note that CIS scan-
+ ners are probably temperature sensitive, and that a certain in-
+ accuracy may be hard to avoid. Differences in offset between
runs in the order of 1 to 2 mm are not unusual.
Default value: 0.0
Minimum: -5.0
@@ -214,8 +214,8 @@
Turns fast skipping to the start of the scan region off. When
the region to scan does not start at the origin, the driver will
try to move the scanhead to the start of the scan area at the
- fastest possible speed. On some models, this may not work,
- resulting in large inaccuracies (up to centimeters). By setting
+ fastest possible speed. On some models, this may not work, re-
+ sulting in large inaccuracies (up to centimeters). By setting
this option, the driver is forced to use normal speed during
skipping, which can circumvent the accuracy problems. Currently,
there are no models for which these inaccuracy problems are
@@ -313,9 +313,9 @@
GLOBAL OPTIONS
- You can control the overall behaviour of the mustek_pp backend by
+ You can control the overall behaviour of the sane-stek_pp backend by
global options which precede any scanner definition in the
- mustek_pp.conf file.
+ mustek_pp.conf file.
Currently, there is only one global option:
@@ -351,17 +351,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_MUSTEK_PP
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -393,28 +393,29 @@
SEE ALSO
- sane(7), sane-mustek(5), sane-net(5), saned(8), sane-find-scanner(1)
+ sane(7), sane-mustek(5), sane-net(5), saned(8), sane-find-scanner(1),
+ scanimage(1)
For latest bug fixes and information see
http://www.penguin-breeder.org/sane/mustek_pp/
-
For additional information on the CIS driver, see
http://home.scarlet.be/eddy_de_greef/
AUTHORS
- Jochen Eisinger <jochen at penguin-breeder dot org>
- Eddy De Greef <eddy_de_greef at scarlet dot be>
+ Jochen Eisinger
+ <jochen at penguin-breeder dot org>
+ Eddy De Greef
+ <eddy_de_greef at scarlet dot be>
BUGS
- Too many... please send bug reports to 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/mail-
- ing-lists.html)
+ Too many... please send bug reports to sane-devel@alioth-lists.de-
+ bian.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).
@@ -424,20 +425,20 @@
your scanner to be able to help you...
SANE version
- run "scanimage -V" to determine this
+ Run scanimage -V to determine this.
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
- /usr/local/etc/sane.d/dll.conf. If your scanner isn't detected,
- make sure you've defined the right port address in your
- mustek_pp.conf.
+ Run SANE_DEBUG_MUSTEK_PP=128 scanimage -L as root. If you don't
+ get any output from the sane-mustek_pp backend, make sure a line
+ "mustek_pp" is included into your /usr/lo-
+ cal/etc/sane.d/dll.conf. If your scanner isn't detected, make
+ sure you've defined the right port address in your
+ mustek_pp.conf.
- the name of your scanner/vendor
- also a worthy information. Please also include the optical reso-
- lution and lamp type of your scanner, both can be found in the
- manual of your scanner.
+ 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.
any further comments
if you have comments about the documentation (what could be done
diff --git a/man/sane-mustek_usb.5.html b/man/sane-mustek_usb.5.html
index 8cab9e97..73407026 100644
--- a/man/sane-mustek_usb.5.html
+++ b/man/sane-mustek_usb.5.html
@@ -2,7 +2,7 @@
sane-mustek_usb.5
-
+
sane-mustek_usb.5
@@ -61,8 +61,8 @@
CONFIGURATION
- The contents of the mustek_usb.conf file is a list of options and
- device names that correspond to Mustek USB scanners. Empty lines and
+ The contents of the mustek_usb.conf file is a list of options and de-
+ vice names that correspond to Mustek USB scanners. Empty lines and
lines starting with a hash mark (#) are ignored. If a device name is
placed in mustek_usb.conf, it must be followed by a line containing the
keyword option and an option specifying the scanner type. The following
@@ -118,17 +118,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_MUSTEK_USB
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Value Description
@@ -155,7 +155,7 @@
AUTHOR
- Henning Meier-Geinitz <henning@meier-geinitz.de>
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
This backend is based on the Mustek 1200ub backend from Mustek, main-
tained by Tom Wang.
diff --git a/man/sane-mustek_usb2.5.html b/man/sane-mustek_usb2.5.html
index 14ab2cfa..56c7d12e 100644
--- a/man/sane-mustek_usb2.5.html
+++ b/man/sane-mustek_usb2.5.html
@@ -2,7 +2,7 @@
sane-mustek_usb2.5
-
+
sane-mustek_usb2.5
@@ -32,7 +32,7 @@
If you own a scanner other than the ones listed on the mustek_usb2
homepage that works with this backend, please let me know this by send-
ing the scanner's exact model name and the USB vendor and device ids
- (e.g. from sane-find-scanner or syslog) to me. Even if the scanner's
+ (e.g. from sane-find-scanner(1) or syslog) to me. Even if the scanner's
name is only slightly different from the models already listed as sup-
ported, please let me know.
@@ -41,8 +41,8 @@
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 permis-
- sions and general USB information looks at sane-usb(5).
+ found by sane-find-scanner(1) without further actions. For setting per-
+ missions and general USB information looks at sane-usb(5).
@@ -58,8 +58,8 @@
ENVIRONMENT
SANE_DEBUG_MUSTEK_USB2
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_MUSTEK_USB2=4
@@ -68,22 +68,26 @@
SEE ALSO
sane(7), sane-usb(5), sane-plustek(5), sane-ma1509(5),
- sane-mustek_usb(5), sane-mustek(5), sane-mustek_pp(5)
+ sane-mustek_usb(5), sane-mustek(5), sane-mustek_pp(5), sane-find-scan-
+ ner(1)
+
/usr/local/share/doc/sane-backends/mustek_usb2/mustek_usb2.CHANGES
http://www.meier-geinitz.de/sane/mustek_usb2-backend/
AUTHOR
- The driver has been written Roy Zhou, Jack Xu, and Vinci Cen from
- Mustek. Adjustments to SANE by Henning Meier-Geinitz.
+ The driver has been written Roy Zhou, Jack Xu, and Vinci Cen from
+ Mustek.
+ Adjustments to SANE by Henning Meier-Geinitz.
BUGS
- Please contact me if you find a bug or missing feature: <hen-
- ning@meier-geinitz.de>. Please send a debug log if your scanner isn't
- detected correctly (see SANE_DEBUG_MUSTEK_USB2 above).
+ Please contact me if you find a bug or missing feature: <hen-
+ ning@meier-geinitz.de>.
+ Please send a debug log if your scanner isn't detected correctly (see
+ SANE_DEBUG_MUSTEK_USB2 above).
13 Jul 2008 sane-mustek_usb2(5)
diff --git a/man/sane-nec.5.html b/man/sane-nec.5.html
index 7552cd56..1babe5c5 100644
--- a/man/sane-nec.5.html
+++ b/man/sane-nec.5.html
@@ -2,7 +2,7 @@
sane-nec.5
-
+
sane-nec.5
@@ -22,15 +22,18 @@
considered alpha-quality software! In the current state it is known to
work with PC-IN500/4C scanners. Another MultiReader scanner series is
not supported. PC-IN 500/4C and MultiReader scanner are only sold in
- Japan.(except Multi Reader PetiScan.)
+ Japan (except Multi Reader PetiScan).
For other scanners, it may or may not work.
The backend has the following known problems:
+
- ColorLineart mode is not supported.
- - device name is fixed to /dev/scanner
+
+ - Device name is fixed to /dev/scanner
At present, the following scanners are known to work with this backend.
+
Vendor Product id
------ -----------
NEC PC-IN500/4C
@@ -52,8 +55,8 @@
ENVIRONMENT
SANE_DEBUG_NEC
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
diff --git a/man/sane-net.5.html b/man/sane-net.5.html
index 32c6f26b..f6308096 100644
--- a/man/sane-net.5.html
+++ b/man/sane-net.5.html
@@ -2,7 +2,7 @@
sane-net.5
-
+
sane-net.5
@@ -49,14 +49,15 @@
an host name.
connect_timeout = nsecs
- Timeout (in seconds) for the initial connection to the saned
+ Timeout (in seconds) for the initial connection to the saned(8)
server. This will prevent the backend from blocking for several
- minutes trying to connect to an unresponsive saned host (network
- outage, host down, ...). The environment variable SANE_NET_TIME-
- OUT can also be used to specify the timeout at runtime.
+ minutes trying to connect to an unresponsive saned(8) host (net-
+ work outage, host down, ...). The environment variable
+ SANE_NET_TIMEOUT can also be used to specify the timeout at run-
+ time.
- Empty lines and lines starting with a hash mark (#) are ignored. Note
- that IPv6 addresses in this file do not need to be enclosed in square
+ Empty lines and lines starting with a hash mark (#) are ignored. Note
+ that IPv6 addresses in this file do not need to be enclosed in square
brackets. A sample configuration file is shown below:
scan-server.somedomain.firm
@@ -65,20 +66,20 @@
localhost
::1
- The above list of hosts can be extended at run-time using environment
- variable SANE_NET_HOSTS. This environment variable is a colon-sepa-
- rated list of hostnames or IP addresses that should be contacted in
- addition to the hosts mentioned in the configuration file. For exam-
- ple, a user could set the environment variable to the string:
+ The above list of hosts can be extended at run-time using environment
+ variable SANE_NET_HOSTS. This environment variable is a colon-sepa-
+ rated list of hostnames or IP addresses that should be contacted in ad-
+ dition to the hosts mentioned in the configuration file. For example,
+ a user could set the environment variable to the string:
new.scanner.com:[::1]:192.168.0.2:scanner.univ.edu
- To request that hosts new.scanner.com , [::1] , 192.168.0.2 and scan-
+ To request that hosts new.scanner.com , [::1] , 192.168.0.2 and scan-
ner.univ.edu are contacted in addition to the hosts listed above.
- For this backend to function properly, it is also necessary to define
- the sane-port service in /etc/services. The sane service should be
- defined using a line of the following form:
+ For this backend to function properly, it is also necessary to define
+ the sane-port service in /etc/services. The sane service should be de-
+ fined using a line of the following form:
sane-port 6566/tcp # SANE network scanner daemon
@@ -86,7 +87,7 @@
FILES
/usr/local/etc/sane.d/net.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
/usr/local/lib/sane/libsane-net.a
@@ -102,35 +103,35 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_NET_HOSTS
- A colon-separated list of host names or IP addresses to be con-
+ A colon-separated list of host names or IP addresses to be con-
tacted by this backend.
SANE_NET_TIMEOUT
- Number of seconds to wait for a response from the saned server
- for the initial connection request.
+ Number of seconds to wait for a response from the saned(8)
+ server for the initial connection request.
SANE_DEBUG_NET
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
BUGS
- If saned has timed out, the net backend may loop with authorization
+ If saned(8) has timed out, the net backend may loop with authorization
requests.
diff --git a/man/sane-niash.5.html b/man/sane-niash.5.html
index 78632952..cc4c1e02 100644
--- a/man/sane-niash.5.html
+++ b/man/sane-niash.5.html
@@ -2,7 +2,7 @@
sane-niash.5
-
+
sane-niash.5
@@ -12,7 +12,7 @@
NAME
- sane-niash - SANE backend for scanners based on the NIASH chipset.
+ sane-niash - SANE backend for scanners based on the NIASH chipset
@@ -63,8 +63,8 @@
ENVIRONMENT
SANE_DEBUG_NIASH
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_NIASH=255
@@ -73,12 +73,12 @@
SEE ALSO
sane(7), sane-usb(5)
- http://www.sourceforge.net/projects/hp3300backend
+ http://www.sourceforge.net/projects/hp3300backend
AUTHOR
- Bertrik Sikken <bertrik@zonnet.nl>
+ Bertrik Sikken <bertrik@zonnet.nl>
14 Jul 2008 sane-niash(5)
diff --git a/man/sane-p5.5.html b/man/sane-p5.5.html
index 539f16c2..c0bd6fb9 100644
--- a/man/sane-p5.5.html
+++ b/man/sane-p5.5.html
@@ -2,7 +2,7 @@
sane-p5.5
-
+
sane-p5.5
@@ -22,8 +22,8 @@
scanner.
This backend handles 100, 150, 200, 300 and 600 dpi scan resolutions,
- in color and gray modes. The 600 dpi is actually 300x600 with lines
- enlarged to match the vertical resolution.
+ in color and gray modes. The 600 dpi is actually 300x600 with lines en-
+ larged to match the vertical resolution.
EPP/ECP MODES ONLY The current version of the backend uses only EPP or
ECP mode to communicate with the scanner. It is recommended that you
@@ -56,7 +56,7 @@
CONFIGURATION
- Please make sure to edit dll.conf before you use the backend, since
+ Please make sure to edit dll.conf before you use the backend, since
this backend isn't enabled by default.
@@ -82,17 +82,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_P5
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -108,13 +108,15 @@
64 I/O functions with traces
128 scanned/calibration data
- SEE ALSO
- sane(7), sane-net(5), saned(8)
+
+
+SEE ALSO
+ sane(7), sane-net(5), saned(8), scanimage(1)
AUTHOR
- Stephane Voltz <stef.dev@free.fr>
+ Stephane Voltz <stef.dev@free.fr>
@@ -126,7 +128,7 @@
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
+ submit an issue via https://gitlab.com/sane-project/backends/issues/new
with a label of backend/p5. Please give as much information as you
can.
@@ -134,11 +136,11 @@
run "scanimage -V" to determine this
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 /usr/local/etc/sane.d/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.
+ 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 in-
+ cluded into your /usr/local/etc/sane.d/dll.conf. If your scan-
+ ner isn't detected, make sure you've defined the right port ad-
+ dress, or the correct device in your p5.conf.
the name of your scanner/vendor
also a worthy information. Please also include the optical reso-
diff --git a/man/sane-pie.5.html b/man/sane-pie.5.html
index 6469dcfd..99e85999 100644
--- a/man/sane-pie.5.html
+++ b/man/sane-pie.5.html
@@ -2,7 +2,7 @@
sane-pie.5
-
+
sane-pie.5
@@ -64,7 +64,7 @@
CONTACT AND BUG-REPORTS
Please send any information and bug-reports to:
- Simon Munton <simon@munton.demon.co.uk>
+ Simon Munton <simon@munton.demon.co.uk>
14 Jul 2008 sane-pie(5)
diff --git a/man/sane-pieusb.5.html b/man/sane-pieusb.5.html
index 38656ca1..53b63f5a 100644
--- a/man/sane-pieusb.5.html
+++ b/man/sane-pieusb.5.html
@@ -2,7 +2,7 @@
sane-pieusb.5
-
+
sane-pieusb.5
@@ -12,8 +12,8 @@
NAME
- sane-pieusb - SANE backend for USB-connected PIE PowerSlide and
- Reflecta DigitDia/CrystalScan/ProScan slide scanners
+ sane-pieusb - SANE backend for USB-connected PIE PowerSlide and Re-
+ flecta DigitDia/CrystalScan/ProScan slide scanners
@@ -55,26 +55,27 @@
DIRT REMOVAL
- If available, pieusb supports infrared scans for dirt detection and
- removal. This must be enabled via the 'Clean image' setting.
+ If available, sane-pieusb supports infrared scans for dirt detection
+ and removal. This must be enabled via the 'Clean image' setting.
KNOWN PROBLEMS
- The pieusb backend supports dirt removal based on infrared scan infor-
- mation. Since SANE does not provide post-processing in the backend,
- pieusb does the scanning and dirt removal during the setup phase. The
- 'scan' phase is only used to transfer the completed image. Therefore
- pieusb does not multi-thread making a typical frontend appear as
- 'blocked'. Also cancel requests are only honored between scans.
+ The sane-pieusb backend supports dirt removal based on infrared scan
+ information. Since SANE does not provide post-processing in the back-
+ end, sane-pieusb does the scanning and dirt removal during the setup
+ phase. The 'scan' phase is only used to transfer the completed image.
+ Therefore sane-pieusb does not multi-thread making a typical frontend
+ appear as 'blocked'. Also cancel requests are only honored between
+ scans.
ENVIRONMENT
SANE_DEBUG_PIEUSB
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
level debug output
@@ -111,12 +112,12 @@
CONTACT AND BUG-REPORTS
Please send any information and bug-reports to:
- Klaus KAxmpf <kkaempf@suse.com>
+ Klaus KAxmpf <kkaempf@suse.com>
AUTHORS
- The pieusb backend is based on work by Jan Vleeshouwers, Michael Rick-
+ The pieusb backend is based on work by Jan Vleeshouwers, Michael Rick-
mann, and Klaus KAxmpf
10 Aug 2015 sane-pieusb(5)
diff --git a/man/sane-pint.5.html b/man/sane-pint.5.html
index 4cbdba0a..78ec1966 100644
--- a/man/sane-pint.5.html
+++ b/man/sane-pint.5.html
@@ -2,7 +2,7 @@
sane-pint.5
-
+
sane-pint.5
@@ -18,10 +18,10 @@
DESCRIPTION
The sane-pint library implements a SANE (Scanner Access Now Easy) back-
- end that provides generic access to hand-held and flatbed scanners
- using the PINT (PINT Is Not Twain) device driver. The PINT driver is
- being actively developed on the OpenBSD platform, and has been ported
- to a few other *nix-like operating systems.
+ end that provides generic access to hand-held and flatbed scanners us-
+ ing the PINT (PINT Is Not Twain) device driver. The PINT driver is be-
+ ing actively developed on the OpenBSD platform, and has been ported to
+ a few other *NIX-like operating systems.
PINT is designed to provide an ioctl(2) interface to many different
scanner types. However, this backend has only been tested with flatbed
@@ -30,9 +30,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
- sane-devel@alioth-lists.debian.net. Have a look at
- http://www.sane-project.org/mailing-lists.html concerning subscription
+ send a mail with the relevant information for your scanner to sane-de-
+ vel@alioth-lists.debian.net. Have a look at
+ http://www.sane-project.org/mailing-lists.html concerning subscription
to sane-devel.
@@ -81,17 +81,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_PINT
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -119,8 +119,8 @@
The PINT 0.5e interface does not provide a way to determine valid
ranges for DPI, modes, and scan sizes. So, the SANE backend queries
- the PINT device, and dynamically discovers valid ranges by doing a
- binary search. This means that the driver takes longer to initialize
+ the PINT device, and dynamically discovers valid ranges by doing a bi-
+ nary search. This means that the driver takes longer to initialize
than seems necessary.
Resetting the scanner does not seem to work (at least not on my HP
diff --git a/man/sane-pixma.5.html b/man/sane-pixma.5.html
index 7fb9290b..3c9937cd 100644
--- a/man/sane-pixma.5.html
+++ b/man/sane-pixma.5.html
@@ -2,7 +2,7 @@
sane-pixma.5
-
+
sane-pixma.5
@@ -21,10 +21,10 @@
The sane-pixma library implements a SANE (Scanner Access Now Easy)
backend that provides access to Canon PIXMA / i-SENSYS / imageCLASS /
imageRUNNER multi-function devices (All-in-one printers) and the Canon
- CanoScan Flatbed/TPU scanners. The backend implements both the USB
- interface and network interface (using Canon's BJNP and MFNP proto-
- cols). The network interface supports scanners over IPv4 as well as
- IPv6 (MFNP over IPv6 is untested).
+ CanoScan Flatbed/TPU scanners. The backend implements both the USB in-
+ terface and network interface (using Canon's BJNP and MFNP protocols).
+ The network interface supports scanners over IPv4 as well as IPv6 (MFNP
+ over IPv6 is untested).
Currently, the following models work with this backend:
@@ -72,144 +72,149 @@
PIXMA MP760, MP770, MP780, MP790
The following models may use the same Pixma protocol as those listed
- above, but have not yet been reported to work (or not). They are
- declared in the backend so that they get recognized and activated.
- Feedback in the sane-devel mailing list welcome.
+ above, but have not yet been reported to work (or not). They are de-
+ clared in the backend so that they get recognized and activated. Feed-
+ back in the sane-devel mailing list welcome.
PIXMA E400, E460, E470, E480, E500, E560, E600, E610
- PIXMA E3100, E3300, E4200
+ PIXMA E3100, E3300, E3400, E4200
+ PIXMA G2020, G2060, G3020, G3060, G7000, G7080
PIXMA MG4100, MG6500, MG6600, MG6800, MG6900, MG8100
PIXMA MP375R, MP493, MP740
PIXMA MX320, MX390, MX430, MX450, MX490, MX710
- PIXMA G3000, G3010, G4010, G6000, G6080, G7000, GM4000
- PIXMA TR7500, TR7530, TR8500, TR8530, TR8580, TR9530
- PIXMA TS6000, TS6130, TS6180, TS6230, TS6280, TS6300, TS6330
- PIXMA TS6380, TS7330, TS8100, TS8130, TS8180, TS8230, TS8280
- PIXMA TS8300, TS8330, TS8380, TS9000, TS9100, TS9180, TS9500
- PIXMA TS9580
- PIXUS MP5, XK50, XK60, XK70, XK80
+ PIXMA G3000, G3010, G4010, G6000, G6080, G7000, GM4000, GM4080
+ PIXMA TR7500, TR7530, TR7600, TR8500, TR8530, TR8580, TR8600
+ PIXMA TR8630, TR9530
+ PIXMA TS3400, TS5100, TS6000, TS6130, TS6180, TS6230, TS6280,
+ TS6300
+ PIXMA TS6330, TS6330, TS6380, TS6400, TS7330, TS7400, TS7430,
+ TS8100
+ PIXMA TS8130, TS8180, TS8230, TS8280, TS8300, TS8330, TS8380,
+ TS9000
+ PIXMA TS9100, TS9180, TS9500, TS9580
+ PIXUS MP5, XK50, XK60, XK70, XK80, XK90
imageCLASS MF720, MF810/820, MF5630, MF5650, MF5750, MF8170c
imageCLASS MPC190, D550
i-SENSYS MF110, MF220, MF260, MF410, MF420, MF510, MF520, MF740
i-SENSYS MF5880dn, MF5900, MF6680dn, MF8500C
MAXIFY MB5300
- The following models may use partly the same Pixma protocol as other
- devices listed above, but may still need some work. They are declared
- in the backend as experimental and need the environment variable
- PIXMA_EXPERIMENT=1 to get recognized and activated. Snoop logs are
- required to further investigate, please contact the sane-devel mailing
+ The following models may use partly the same Pixma protocol as other
+ devices listed above, but may still need some work. They are declared
+ in the backend as experimental and need the environment variable
+ PIXMA_EXPERIMENT=1 to get recognized and activated. Snoop logs are re-
+ quired to further investigate, please contact the sane-devel mailing
list.
-- none --
The backend supports:
- * resolutions of 75, 150, 300, 600, 1200, 2400, 4800, and 9600
+ * resolutions of 75, 150, 300, 600, 1200, 2400, 4800, and 9600
DPI (some maybe buggy),
- * color and grayscale mode, as well as lineart on certain mod-
+ * color and grayscale mode, as well as lineart on certain mod-
els,
* a custom gamma table,
* Automatic Document Feeder, Simplex and Duplex.
- * Transparency Unit, 24 or 48 bits depth. Infrared channel on
+ * Transparency Unit, 24 or 48 bits depth. Infrared channel on
certain models.
- The device name for USB devices is in the form pixma:xxxxyyyy_zzzzz
- where x, y and z are vendor ID, product ID and serial number respec-
+ The device name for USB devices is in the form pixma:xxxxyyyy_zzzzz
+ where x, y and z are vendor ID, product ID and serial number respec-
tively.
Example: pixma:04A91709_123456 is a MP150.
- Device names for BJNP/MFNP devices is in the form pixma:aaaa_bbbbb
+ Device names for BJNP/MFNP devices is in the form pixma:aaaa_bbbbb
where aaaa is the scanners model and bbbb is the hostname or ip-adress.
- Example: pixma:MF4800_192.168.1.45 is a MF4800 Series multi-function
+ Example: pixma:MF4800_192.168.1.45 is a MF4800 Series multi-function
peripheral.
- This backend, based on cloning original Canon drivers protocols, is in
- a production stage. Designed has been carried out without any applica-
- ble manufacturer documentation, probably never available. However, we
- have tested it as well as we could, but it may not work in all situa-
+ This backend, based on cloning original Canon drivers protocols, is in
+ a production stage. Designed has been carried out without any applica-
+ ble manufacturer documentation, probably never available. However, we
+ have tested it as well as we could, but it may not work in all situa-
tions. You will find an up-to-date status at the project homepage. (See
- below). Users feedback is essential to help improve features and per-
+ below). Users feedback is essential to help improve features and per-
formances.
OPTIONS
- Besides "well-known" options (e.g. resolution, mode etc.) pixma backend
- also provides the following options, i.e. the options might change in
- the future.
- The button status can be polled i.e. with 'scanimage -A'.
- 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
+ Besides "well-known" options (e.g. resolution, mode etc.) backend also
+ provides the following options, i.e. the options might change in the
+ future.
+ The button status can be polled i.e. with scanimage -A.
+ 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.
adf-wait
- This option enables and sets the time in seconds waiting for a
+ This option enables and sets the time in seconds waiting for a
document inserted into the Automatic Document Feeder. The maxi-
mum allowed waiting time is 3600 sec (= 1 hour).
button-controlled
- This option can be used by applications (like scanadf(1) and
- scanimage(1)) in batch mode, for example when you want to scan
- many photos or multiple-page documents. If it is enabled (i.e.
- is set to true or yes), the backend waits before every scan
- until the user presses the "SCAN" button (for MP150) or the
- color-scan button (for other models). Just put the first page in
- the scanner, press the button, then the next page, press the
- button and so on. When you finished, press the gray-scan button.
- (For MP150 you have to stop the frontend by pressing Ctrl-C for
- example.)
+ This option can be used by applications (like scanadf(1) and
+ scanimage(1)) in batch mode, for example when you want to scan
+ many photos or multiple-page documents. If it is enabled (i.e.
+ is set to true or yes), the backend waits before every scan un-
+ til the user presses the "SCAN" button (for MP150) or the color-
+ scan button (for other models). Just put the first page in the
+ scanner, press the button, then the next page, press the button
+ and so on. When you finished, press the gray-scan button. (For
+ MP150 you have to stop the frontend by pressing Ctrl-C for exam-
+ ple.)
button-update (deprecated)
- (write only) In the past this option was required to be set to
- force reading of the button status for button-1 and button-2.
- The sane-pixma no longer requires this option to be used: if no
- fresh data is available, it will be now requested automatically
- from the scanner. This option is left for backward compatibility
- reasons.
+ (write only) In the past this option was required to be set to
+ force reading of the button status for button-1 and button-2.
+ The sane-pixma backend no longer requires this option to be
+ used: if no fresh data is available, it will be now requested
+ automatically from the scanner. This option is left for backward
+ compatibility reasons.
button-1 button-2
- (read only) These options will return the value of the respec-
- tive buttons. value 0 means that the button was not pressed, 1
+ (read only) These options will return the value of the respec-
+ tive buttons. value 0 means that the button was not pressed, 1
is returned when the button was pressed. Some scanners with more
than two buttons send the button number as target.
original
(read only) Returns the value of the type or size of original to
- be scanned if the scanner provides that data. Known values of
- type: 1 = document, 2 = foto, 5 = film. Known values of size: 1
+ be scanned if the scanner provides that data. Known values of
+ type: 1 = document, 2 = photo, 5 = film. Known values of size: 1
= A4, 2 = Letter, 8 = 10x15, 9 = 13x18, b = auto. Not all scan-
ners can provide this data.
- target (read only) Returns the value of the target of the scan opera-
+ target (read only) Returns the value of the target of the scan opera-
tion if the scanner provides that data. The values depend on the
scanner type. Known values: 1 = save to disk, 2 = save to pdf, 3
- = send to email, 4 = send to application or 1 = JPEG, 2 = TIFF,
+ = send to email, 4 = send to application or 1 = JPEG, 2 = TIFF,
3 = PDF, 4 = Compact PDF. For some scanners this value is equiv-
- alent to the number of the pressed button. Not all scanners can
+ alent to the number of the pressed button. Not all scanners can
provide this data.
scan-resolution
- (read only) Returns the resolution of the scan operation if the
- scanner provides that data. Known values: 1 = 75 dpi, 2 = 150
+ (read only) Returns the resolution of the scan operation if the
+ scanner provides that data. Known values: 1 = 75 dpi, 2 = 150
dpi, 3 = 300 dpi, 4 = 600 dpi. Not all scanners can provide this
data.
document-type
- (read only) Returns the type of the scanned document if the
- scanner provides that data. Known values: 1 = Document, 2 =
+ (read only) Returns the type of the scanned document if the
+ scanner provides that data. Known values: 1 = Document, 2 =
Photo, 3 = Auto scan. Not all scanners can provide this data.
adf-status
- (read only) Returns the status of the document feeder if the
+ (read only) Returns the status of the document feeder if the
scanner provides that data. Known values: 1 = ADF empty, 2 = ADF
filled. Not all scanners can provide this data.
adf-orientation
- (read only) Returns the scan orientation of the medium scanned
- from ADF if the scanner provides that data. Known values: 1 =
+ (read only) Returns the scan orientation of the medium scanned
+ from ADF if the scanner provides that data. Known values: 1 =
Portrait, 2 = Landscape. Not all scanners can provide this data.
@@ -223,32 +228,32 @@
that support dynamic loading).
/usr/local/etc/sane.d/pixma.conf
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
SANE_CONFIG_DIR below).
- The file contains an optional list of networked scanners using
- the BJNP or MFNP protools (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 getifad-
- drs() function) you also may need to add your scanner here as
+ The file contains an optional list of networked scanners using
+ the BJNP or MFNP protools (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 getifad-
+ drs() qfunction) you also may need to add your scanner here as
well.
- Scanners shall be listed in the configuration file as follows:
+ Scanners shall be listed in the configuration file as follows:
<method>://<host>[:port][/timeout=<value>]
- where method indicates the protocol used (bjnp is used for
- inkjet multi-functionals and mfnp is used for laser multi-func-
+ where method indicates the protocol used (bjnp is used for
+ inkjet multi-functionals and mfnp is used for laser multi-func-
tionals).
- host is the hostname or IP address of the scanner, e.g.
- bjnp://10.0.1.4 for IPv4,
- bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a] for a literal
+ host is the hostname or IP address of the scanner, e.g.
+ bjnp://10.0.1.4 for IPv4,
+ bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a] for a literal
IPv6-address or bjnp://myscanner.mydomain.org for a hostname.
- The port number is optional and in normally implied by the
+ The port number is optional and in normally implied by the
method. Port 8610 is the standard port for mfnp, 8612 for bjnp.
A scanner specific timeout value for the network protocol can be
@@ -256,30 +261,30 @@
Define scanners each on a new line.
- More globally applicable timeouts can be set using the bjnp-
+ More globally applicable timeouts can be set using the bjnp-
timeout parameter as follows:
bjnp-timeout=<value>
A timeout defined using bjnp-timeout will apply to the following
- scanner definitions in the file. If required the bjnp-timeout
- setting can be defined multiple times, where each settng will
- apply only to the scanners that follow the setting. The last
- setting is used for the auto discovered scanners. If not
- explicitly set, the default 1000ms setting will apply.
+ scanner definitions in the file. If required the bjnp-timeout
+ setting can be defined multiple times, where each setting will
+ apply only to the scanners that follow the setting. The last
+ setting is used for the auto discovered scanners. If not ex-
+ plicitly set, the default 1000ms setting will apply.
Setting timeouts should only be required in exceptional cases.
- If so desired networking can be disbled as follows:
+ If so desired networking can be disabled as follows:
- - If the first non-commented line contains networking=no
- all networking will be disabled. This will cause all
- further statements in the configuration file to be
- ignored.
+ - If the first non-commented line contains networking=no
+ all networking will be disabled. This will cause all
+ further statements in the configuration file to be ig-
+ nored.
- - A line that contains auto_detection=no will cause auto-
- detection to be skipped. Explicitely defined network
- scanners will still be probed.
+ - A line that contains auto_detection=no will cause auto-
+ detection to be skipped. Explicitly defined network scan-
+ ners will still be probed.
@@ -289,62 +294,62 @@
NETWORKING SUPPORT
- The pixma backend supports network scanners using the so called Canon
- BJNP and MFNP protocols.
+ The sane-pixma backend supports network scanners using the so called
+ Canon BJNP and MFNP protocols.
- Canon seems to be dropping support for these protocols in recent scan-
+ Canon seems to be dropping support for these protocols in recent scan-
ners. 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). If that does not list port 8610 or 8612
- your scanner probably does not support the mfmp or bjnp protols.
+ the content of the _scanner._tcp service entry in mDNS/DNS-SD (using
+ for example avahi-discover(1)). If that does not list port 8610 or
+ 8612 your scanner probably does not support the mfmp or bjnp protols.
- Both IPv4 and IPv6 are supported, but IPv6 is as yet untested with
+ Both IPv4 and IPv6 are supported, but IPv6 is as yet untested with
MFNP. Please report your results on the mailing list.
- Configuration is normally not required. The pixma backend will auto-
- detect your scanner if it is within the same subnet as your computer if
- your OS does support this.
+ Configuration is normally not required. The sane-pixma backend will
+ auto-detect your scanner if it is within the same subnet as your com-
+ puter if your OS does support this.
- If your scanner can not be auto-detected, you can add it to the pixma
- configuration file (see above).
+ If your scanner can not be auto-detected, you can add it to the
+ sane-pixma configuration file (see above).
FIREWALLING FOR NETWORKED SCANNERS
- The sane pixma backend communicates with port 8610 for MFNP or port
- 8612 for BJNP on the scanner. So you will have to allow outgoing traf-
+ The sane-pixma backend communicates with port 8610 for MFNP or port
+ 8612 for BJNP on the scanner. So you will have to allow outgoing traf-
fic TO port 8610 or 8612 on the common subnet for scanning.
- Scanner detection is slightly more complicated. The pixma backend sends
- a broadcast on all direct connected subnets it can find (provided your
- OS allows for enumeration of all netowrk interfaces). The broadcast is
- sent FROM port 8612 TO port 8610 or 8612 on the broadcast address of
- each interface. The outgoing packets will be allowed by the rule
- described above.
+ Scanner detection is slightly more complicated. The sane-pixma backend
+ sends a broadcast on all direct connected subnets it can find (provided
+ your OS allows for enumeration of all network interfaces). The broad-
+ cast is sent FROM port 8612 TO port 8610 or 8612 on the broadcast ad-
+ dress of each interface. The outgoing packets will be allowed by the
+ rule described above.
- Responses from the scanner are sent back to the computer TO port 8612.
- Connection tracking however does not see a match as the response does
- not come from the broadcast address but from the scanners own address.
- For automatic detection of your scanner, you will therefore have to
- allow incoming packets TO port 8612 on your computer. This applies to
+ Responses from the scanner are sent back to the computer TO port 8612.
+ Connection tracking however does not see a match as the response does
+ not come from the broadcast address but from the scanners own address.
+ For automatic detection of your scanner, you will therefore have to al-
+ low incoming packets TO port 8612 on your computer. This applies to
both MFNP and BJNP.
- So in short: open the firewall for all traffic from your computer to
+ So in short: open the firewall for all traffic from your computer to
port 8610 (for MFNP) or 8612 (for BJNP) AND to port 8612 (for both BJNP
and MFNP) to your computer.
- With the firewall rules above there is no need to add the scanner to
- the pixma.conf file, unless the scanner is on a network that is not
- directly connected to your computer.
+ With the firewall rules above there is no need to add the scanner to
+ the pixma.conf file, unless the scanner is on a network that is not di-
+ rectly connected to your computer.
ENVIRONMENT
SANE_DEBUG_PIXMA
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend
- itself. Higher value increases the verbosity and includes the
- information printed at the lower levels.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend it-
+ self. Higher value increases the verbosity and includes the in-
+ formation printed at the lower levels.
0 print nothing (default)
1 print error and warning messages (recommended)
2 print informational messages
@@ -354,10 +359,10 @@
21 full dump USB traffic
SANE_DEBUG_BJNP
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for the BJNP and
- MFNP network protocols for this backend. Higher value increases
- the verbosity and includes the information printed at the lower
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for the BJNP and
+ MFNP network protocols for this backend. Higher value increases
+ the verbosity and includes the information printed at the lower
levels.
0 print nothing (default)
1 Print error and warning messages (recommended)
@@ -367,30 +372,31 @@
5 Print full protocol contents
PIXMA_EXPERIMENT
- Setting to a non-zero value will enable the support for experi-
+ Setting to a non-zero value will enable the support for experi-
mental models. You should also set SANE_DEBUG_PIXMA to 11.
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SEE ALSO
- sane(7), sane-dll(5), scanimage(1), gamma4scanimage(1),
+ sane(7), sane-dll(5), scanimage(1), scanadf(1), gamma4scanimage(1),
+ getifaddrs(3)
In case of trouble with a recent Pixma model, try the latest code for
- the pixma backend, available in the Sane git repository at:
+ the sane-pixma backend, available in the Sane git repository at:
https://gitlab.com/sane-project/backends.git
You can also post into the Sane-devel mailing list for support.
diff --git a/man/sane-plustek.5.html b/man/sane-plustek.5.html
index 4a9d8c90..a6b18b3f 100644
--- a/man/sane-plustek.5.html
+++ b/man/sane-plustek.5.html
@@ -2,7 +2,7 @@
sane-plustek.5
-
+
sane-plustek.5
@@ -21,7 +21,7 @@
backend that provides access to USB flatbed scanners based on National
Semiconductor Merlin chipsets (LM9831, 9832 and 9833). If you're look-
ing for parallel-port support for Plustek scanner please refer to the
- sane-plustek_pp backend.
+ sane-plustek_pp(5) backend.
@@ -128,9 +128,9 @@
OTHER PLUSTEK SCANNERS
- For parallelport device support see the plustek_pp backend.
+ For parallelport device support see the sane-plustek_pp(5) backend.
The SCSI scanner OpticPro 19200S is a rebadged Artec AM12S scanner and
- is supported by the Artec backend.
+ is supported by the sane-artec(5) backend.
Only the National Semiconductor LM983[1/2/] based devices of Plustek
are supported by this backend. Older versions of the U12, the UT12, the
U1212 and U1248 (GrandTech chipset) are not supported.
@@ -145,13 +145,14 @@
UT12 P98003 u12
1212U P98003 u12
For a more complete and up to date list see:
- http://www.sane-project.org/sane-supported-devices.html
+ http://www.sane-project.org/sane-supported-devices.html.
CONFIGURATION
To use your scanner with this backend, you need at least two entries in
the configuration file /usr/local/etc/sane.d/plustek.conf
+
[usb] vendor-id product-id
device /dev/usbscanner
@@ -166,8 +167,8 @@
The Options:
option warmup t
- t specifies the warmup period in seconds, if set to -1, the
- automatic warmup function will be used
+ t specifies the warmup period in seconds, if set to -1, the au-
+ tomatic warmup function will be used
option lampOff t
t is the time in seconds for switching off the lamps in standby
@@ -186,12 +187,12 @@
1 | no function | BearPaw 1200
option invertNegatives b
- b 0 --> do not invert the picture during negativ scans,
+ b 0 --> do not invert the picture during negative scans,
1 --> invert picture
option cacheCalData b
b 0 --> do not save calibration results,
- 1 --> save results of calibration in ~/.sane/ directory
+ 1 --> save results of calibration in ~/.sane/ directory
option altCalibration b
b 0 --> use standard calibration routines,
@@ -262,9 +263,9 @@
Note:
You have to make sure, that the USB subsystem is loaded correctly and
- you have access to the device-node. For more details see sane-usb (5)
- manpage. You might use sane-find-scanner to check that you have access
- to your device.
+ you have access to the device-node. For more details see sane-usb(5)
+ manpage. You might use sane-find-scanner(1) to check that you have ac-
+ cess to your device.
Note:
If there's no configuration file, the backend defaults to device auto
@@ -291,17 +292,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_PLUSTEK
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_PLUSTEK=10
@@ -309,7 +310,8 @@
SEE ALSO
- sane(7), sane-usb(5), sane-u12(5), sane-gt68xx(5),
+ sane(7), sane-usb(5), sane-u12(5), sane-gt68xx(5), sane-stek_pp(5),
+ sane-find-scanner(1), scanimage(1),
/usr/local/share/doc/sane-backends/plustek/Plustek-USB.changes
@@ -320,32 +322,33 @@
Additional info and hints can be obtained from our
Mailing-List archive at:
- http://www.sane-project.org/mailing-lists.html
+ http://www.sane-project.org/mailing-lists.html
- To obtain debug messages from the backend, please set the environment-
- variable SANE_DEBUG_PLUSTEK before calling your favorite scan-frontend
- (i.e. scanimage).
- i.e.: export SANE_DEBUG_PLUSTEK=20 ; scanimage
+ To obtain debug messages from the backend, please set the environment-
+ variable SANE_DEBUG_PLUSTEK before calling your favorite scan-frontend
+ (i.e. scanimage(1)),i.e.:
+
+ export SANE_DEBUG_PLUSTEK=20 ; scanimage
The value controls the verbosity of the backend. Please note, that val-
- ues greater than 24 force the backend to output raw data files, which
- could be rather large. The ending of these files is ".raw". For prob-
+ ues greater than 24 force the backend to output raw data files, which
+ could be rather large. The ending of these files is ".raw". For prob-
lem reports it should be enough the set the verbosity to 13.
KNOWN BUGS & RESTRICTIONS
- * The driver does not support these manic scalings up to 16 times the
- physical resolution. The only scaling is done on resolutions between
- the physical resolution of the CCD-/CIS-sensor and the stepper motor
+ * The driver does not support these manic scalings up to 16 times the
+ physical resolution. The only scaling is done on resolutions between
+ the physical resolution of the CCD-/CIS-sensor and the stepper motor
i.e. you have a 600x1200 dpi scanner and you are scanning using 800dpi,
- so scaling is necessary, because the sensor only delivers 600dpi but
+ so scaling is necessary, because the sensor only delivers 600dpi but
the motor is capable to perform 1200dpi steps.
- * Plusteks' model policy is somewhat inconsistent. They sell techni-
- cally different devices under the same product name. Therefore it is
- possible that some devices like the UT12 or U12 won't work - please
- check the model list above and compare the product-id to the one your
+ * Plusteks' model policy is somewhat inconsistent. They sell techni-
+ cally different devices under the same product name. Therefore it is
+ possible that some devices like the UT12 or U12 won't work - please
+ check the model list above and compare the product-id to the one your
device has.
* Negative/Slide scanning quality is poor.
diff --git a/man/sane-plustek_pp.5.html b/man/sane-plustek_pp.5.html
index 17b5024f..19078a45 100644
--- a/man/sane-plustek_pp.5.html
+++ b/man/sane-plustek_pp.5.html
@@ -2,7 +2,7 @@
sane-plustek_pp.5
-
+
sane-plustek_pp.5
@@ -20,10 +20,10 @@
DESCRIPTION
The sane-plustek_pp library implements a SANE (Scanner Access Now Easy)
backend that 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 sec-
- tion BUILDING THE KERNEL MODULE for further information.
+ based parallel port flatbed scanners. The access of the scanner is ei-
+ ther done directly by the backend or via kernel module, called pt_drv
+ which can be created out of the sane-plustek_pp backend code - see also
+ section BUILDING THE KERNEL MODULE for further information.
@@ -77,8 +77,8 @@
ARIES SCANNERS
- There's one scanner sold as Aries Scanner, but is in fact a Plustek
- device. The following table will show the relationship:
+ There's one scanner sold as Aries Scanner, but is in fact a Plustek de-
+ vice. The following table will show the relationship:
Model: Plustek Model: Remarks:
--------------------------- -------------- ------------
@@ -105,8 +105,8 @@
0x378
This "default device" will be used, if no configuration file can be
- found. It is rather the base address of the parallel port on i386
- machines.
+ found. It is rather the base address of the parallel port on i386 ma-
+ chines.
As the backend supports up to four devices, it is possible to specify
them in the configuration file
@@ -118,10 +118,11 @@
CONFIGURATION
- This section describes the backends' configuration file entries. The
+ This section describes the backend's configuration file entries. The
file is located at: /usr/local/etc/sane.d/plustek_pp.conf
For a proper setup, you will need at least two entries:
+
[direct]
device 0x378
@@ -154,46 +155,46 @@
m = 0 default: no override
- m = 1 OpticPro 9630PL override (works if OP9630 has been
- detected) forces legal size (14")
+ m = 1 OpticPro 9630PL override (works if OP9630 has been de-
+ tected) forces legal size (14")
- m = 2 Primax 4800Direct override (works if OP600 has been
- detected) swaps red/green color
+ m = 2 Primax 4800Direct override (works if OP600 has been de-
+ tected) swaps red/green color
- m = 3 OpticPro 9636 override (works if OP9636 has been
- detected) disables backends transparency/negative capa-
- bilities
+ m = 3 OpticPro 9636 override (works if OP9636 has been de-
+ tected) disables backends transparency/negative capabili-
+ ties
- m = 4 OpticPro 9636P override (works if OP9636 has been
- detected) disables backends transparency/negative capa-
- bilities
+ m = 4 OpticPro 9636P override (works if OP9636 has been de-
+ tected) disables backends transparency/negative capabili-
+ ties
- m = 5 OpticPro A3I override (works if OP12000 has been
- detected) enables A3 scanning
+ m = 5 OpticPro A3I override (works if OP12000 has been de-
+ tected) enables A3 scanning
- m = 6 OpticPro 4800P override (works if OP600 has been
- detected) swaps red/green color
+ m = 6 OpticPro 4800P override (works if OP600 has been de-
+ tected) swaps red/green color
m = 7 Primax 4800Direct 30bit override (works if OP4830 has
been detected)
- See the plustek_pp.conf file for examples.
+ See the plustek_pp.conf file for examples.
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, you will need the
+ As mentioned before, the sane-plustek_pp backend code can also be com-
+ piled 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:
- sane-backends/doc/plustek
- Within this directory, you should find a script called:
- MakeModule.sh
- Now if your Linux kernelsources are installed correctly, it should be
- possible to build, install and load the module pt_drv. Please note,
- that the kernelsources need to be configured correctly. Refer to your
- distributions manual on how this is done. As root user, try
+ and go to the directory: sane-backends/doc/plustek. Within this direc-
+ tory, you should find a script called: MakeModule.sh. Now if your
+ Linux kernelsources are installed correctly, it should be possible to
+ build, install and load the module pt_drv. Please note, that the ker-
+ nelsources need to be configured correctly. Refer to your distribu-
+ tions manual on how this is done. As root user, try
+
./MakeModule.sh
+
the script will try and get all necessary information about your run-
ning kernel and will lead you through the whole installation process.
Note: Installing and loading the can only be done as superuser.
@@ -203,9 +204,9 @@
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 /etc/modules.conf (kernel < 2.6.x) or /etc/mod-
- probe.conf (kernel >= 2.6.x)
+ done by invoking insmod(8) with the appropriate parameters or appending
+ the options to the file /etc/modules.conf (kernel < 2.6.x) or /etc/mod-
+ probe.conf (kernel >= 2.6.x)
The Options:
lampoff=lll
@@ -240,40 +241,42 @@
m = 0 default: no override
- m = 1 OpticPro 9630PL override (works if OP9630 has been
- detected) forces legal size (14")
+ m = 1 OpticPro 9630PL override (works if OP9630 has been de-
+ tected) forces legal size (14")
- m = 2 Primax 4800Direct override (works if OP600 has been
- detected) swaps red/green color
+ m = 2 Primax 4800Direct override (works if OP600 has been de-
+ tected) swaps red/green color
- m = 3 OpticPro 9636 override (works if OP9636 has been
- detected) disables backends transparency/negative capa-
- bilities
+ m = 3 OpticPro 9636 override (works if OP9636 has been de-
+ tected) disables backends transparency/negative capabili-
+ ties
- m = 4 OpticPro 9636P override (works if OP9636 has been
- detected) disables backends transparency/negative capa-
- bilities
+ m = 4 OpticPro 9636P override (works if OP9636 has been de-
+ tected) disables backends transparency/negative capabili-
+ ties
- m = 5 OpticPro A3I override (works if OP12000 has been
- detected) enables A3 scanning
+ m = 5 OpticPro A3I override (works if OP12000 has been de-
+ tected) enables A3 scanning
- m = 6 OpticPro 4800P override (works if OP600 has been
- detected) swaps red/green color
+ m = 6 OpticPro 4800P override (works if OP600 has been de-
+ tected) swaps red/green color
m = 7 Primax 4800Direct 30bit override (works if OP4830 has
been detected)
- Sample entry for file /etc/modules.conf :
- alias char-major-40 pt_drv
- pre-install pt_drv modprobe -k parport
- options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0
- slowIO=0 forceMode=0
+ Sample entry for file /etc/modules.conf:
+
+ alias char-major-40 pt_drv
+ pre-install pt_drv modprobe -k parport
+ options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0
+ mov=0 slowIO=0 forceMode=0
For multidevice support, simply add values separated by commas to the
different options
- options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
- Remember to call depmod after changing /etc/conf.modules.
+ options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
+
+ Remember to call depmod(8) after changing /etc/conf.modules.
@@ -293,7 +296,7 @@
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory available) disable swapping.
- See the plustek_pp.conf file for examples.
+ See the plustek_pp.conf file for examples.
@@ -323,17 +326,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_PLUSTEK_PP
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_PLUSTEK_PP=10
@@ -341,7 +344,7 @@
SEE ALSO
- sane(7),
+ sane(7), xscanimage(1),
/usr/local/share/doc/sane-backends/plustek/Plustek-PARPORT.changes
@@ -352,12 +355,12 @@
Additional info and hints can be obtained from our
Mailing-List archive at:
- http://www.sane-project.org/mailing-lists.html
+ http://www.sane-project.org/mailing-lists.html
To obtain debug messages from the backend, please set the environment-
- variable SANE_DEBUG_PLUSTEK_PP before calling your favorite scan-fron-
- tend (i.e. xscanimage).
- i.e.: export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
+ variable SANE_DEBUG_PLUSTEK_PP before calling your favorite scan-front-
+ end (i.e. xscanimage(1)),i.e.:
+ export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
The value controls the verbosity of the backend.
@@ -398,7 +401,7 @@
* The scanning speed on 600x1200 dpi models is slow.
- * The scanning quality of the A3I is poor
+ * The scanning quality of the A3I is poor.
14 Jul 2008 sane-plustek_pp(5)
diff --git a/man/sane-pnm.5.html b/man/sane-pnm.5.html
index 6b985ca1..0d67cb3f 100644
--- a/man/sane-pnm.5.html
+++ b/man/sane-pnm.5.html
@@ -2,7 +2,7 @@
sane-pnm.5
-
+
sane-pnm.5
@@ -20,8 +20,8 @@
The sane-pnm library implements a SANE (Scanner Access Now Easy) back-
end that provides access to PNM (Portable aNyMap files, which covers
PBM bitmap files, PGM grayscale files, and PPM pixmap files). The pur-
- pose of this backend is primarily to aid in debugging of SANE fron-
- tends. It also serves as an illustrative example of a minimal SANE
+ pose of this backend is primarily to aid in debugging of SANE front-
+ ends. It also serves as an illustrative example of a minimal SANE
backend.
@@ -48,22 +48,22 @@
ENVIRONMENT
SANE_DEBUG_PNM
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
BUGS
- If the pnm backend is installed and saned 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 saned can access (usually
- it's running as user "sane"). All pnm files can be read if saned 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 configure
- --help for details). Be sure that only trusted users can access the pnm
- backend over saned.
+ If the sane-pnm backend is installed and 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 saned(8) can
+ access (usually it's running as user "sane"). All PNM files can be read
+ if saned(8) runs as root which isn't recommended anyway. The sane-pnm
+ backend is disabled by default. If you want to use it, enable it with
+ configure (see configure --help for details). Be sure that only trusted
+ users can access the sane-pnm backend over saned(8).
@@ -73,7 +73,7 @@
SEE ALSO
- sane(7)
+ sane(7), saned(8)
14 Jul 2008 sane-pnm(5)
diff --git a/man/sane-qcam.5.html b/man/sane-qcam.5.html
index 138c2a6e..07618ea8 100644
--- a/man/sane-qcam.5.html
+++ b/man/sane-qcam.5.html
@@ -2,7 +2,7 @@
sane-qcam.5
-
+
sane-qcam.5
@@ -27,7 +27,7 @@
port
- Where port is the I/O port address at which the device resides. This
+ where port is the I/O port address at which the device resides. This
address is normally specified in hexadecimal using C syntax (e.g.,
0x37b) and may be prefixed with the letter "u" (e.g., u0x37b) to force
the backend to access the camera in uni-directional mode.
@@ -73,17 +73,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_QCAM
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
diff --git a/man/sane-ricoh.5.html b/man/sane-ricoh.5.html
index f74583f9..7b943ae5 100644
--- a/man/sane-ricoh.5.html
+++ b/man/sane-ricoh.5.html
@@ -2,7 +2,7 @@
sane-ricoh.5
-
+
sane-ricoh.5
@@ -31,11 +31,11 @@
special
Where special is the path-name for the special device that corresponds
- to a SCSI scanner. The special device name must be a generic SCSI
- device or a symlink to such a device. The program sane-find-scanner
+ to a SCSI scanner. The special device name must be a generic SCSI de-
+ vice or a symlink to such a device. The program sane-find-scanner(1)
helps to find out the correct device. Under Linux, such a device name
- could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
- details.
+ could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for de-
+ tails.
@@ -60,17 +60,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_RICOH
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_RICOH=4
@@ -78,7 +78,7 @@
SEE ALSO
- sane(7), sane-scsi(5)
+ sane(7), sane-scsi(5), sane-find-scanner(1)
diff --git a/man/sane-ricoh2.5.html b/man/sane-ricoh2.5.html
index 509846e9..cc0dd186 100644
--- a/man/sane-ricoh2.5.html
+++ b/man/sane-ricoh2.5.html
@@ -2,7 +2,7 @@
sane-ricoh2.5
-
+
sane-ricoh2.5
@@ -39,8 +39,8 @@
OPTIONS
The options the backend supports can either be selected through command
- line options to programs like scanimage or through GUI elements in pro-
- grams like xscanimage or xsane.
+ line options to programs like scanimage(1) or through GUI elements in
+ programs like xscanimage(1) or xsane(1).
The following options are supported by ricoh2:
@@ -56,14 +56,14 @@
ENVIRONMENT
SANE_DEBUG_RICOH2
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
SEE ALSO
- sane(7), sane-usb(5)
+ sane(7), sane-usb(5), scanimage(1), xscanimage(1), xsane(1)
diff --git a/man/sane-rts8891.5.html b/man/sane-rts8891.5.html
index 0782fcdb..04bc051a 100644
--- a/man/sane-rts8891.5.html
+++ b/man/sane-rts8891.5.html
@@ -2,7 +2,7 @@
sane-rts8891.5
-
+
sane-rts8891.5
@@ -30,23 +30,24 @@
HP scanjet 4470c good
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.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
- If you have any strange behavior, please report to the backend main-
+ If you notice any strange behavior, please report to the backend main-
tainer or to the SANE mailing list.
Valid command line options and their syntax can be listed by using
+
scanimage --help -d rts8891
Scan Mode Options
--mode selects the basic mode of operation of the scanner valid choices
- are R Color , Gray and Lineart The default mode is Color. The
+ are R Color, Gray and Lineart The default mode is Color. The
Lineart mode is black and white only (1 bit). Grayscale will
produce 256 levels of gray (8 bits). Color mode allows for over
- 16 million different colors produced from 24 bits of color
- information.
+ 16 million different colors produced from 24 bits of color in-
+ formation.
--resolution
selects the resolution for a scan. The horizontal and vertical
@@ -71,26 +72,29 @@
--threshold
selects the minimum-brightness to get a white point. The
threshold is only used with Lineart mode scans. It is specified
- as a percentage in the range 0..100% (in steps of 1). The
- default value of the threshold option is 50.
+ as a percentage in the range 0..100% (in steps of 1). The de-
+ fault value of the threshold option is 50.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/rts8891.conf contains the
+ The configuration file /usr/local/etc/sane.d/rts8891.conf contains the
usb device ids of supported scanners (eg usb 0x043d 0x007c) and scanner
configuration options. Empty lines and lines starting with a hash mark
(#) are ignored.
- The options supported are allowsharing , modelnumber
+ The options supported are allowsharing, modelnumber
Option
- allowsharing enables or not the sharing of the scanner between multiple
- frontends at the same time.
+ allowsharing
+ enables or not the sharing of the scanner between multiple
+ frontends at the same time.
+
+ modelnumber
+ is used to force the reported model by the backend and is only
+ useful in the case of a scanner which NVRAM has been erased.
- modelnumber is used to force the reported model by the backend and is
- only useful in the case of a scanner which NVRAM has been erased.
0 to report a HP4470c.
1 to report a HP4400c.
2 to report an Astra 4400.
@@ -110,7 +114,7 @@
ENVIRONMENT
SANE_DEBUG_RTS8891 SANE_DEBUG_RTS8891_LOW SANE_DEBUG_RTS88XX_LIB
If the library was compiled with debug support enabled, these
- environment variables controls the debug level for this backend.
+ environment variables control the debug level for this backend.
E.g., a value of 255 requests all debug output to be printed.
Smaller levels reduce verbosity.
@@ -123,7 +127,7 @@
several frontends at the same time (allowsharing option) may not work
on some USB controllers.
- XPA is no (yet) supported.
+ XPA is not (yet) supported.
diff --git a/man/sane-s9036.5.html b/man/sane-s9036.5.html
index dc053f9f..4c1b0200 100644
--- a/man/sane-s9036.5.html
+++ b/man/sane-s9036.5.html
@@ -2,7 +2,7 @@
sane-s9036.5
-
+
sane-s9036.5
@@ -28,11 +28,11 @@
special
Where special is the path-name for the special device that corresponds
- to a SCSI scanner. The special device name must be a generic SCSI
- device or a symlink to such a device. The program sane-find-scanner
+ to a SCSI scanner. The special device name must be a generic SCSI de-
+ vice or a symlink to such a device. The program sane-find-scanner(1)
helps to find out the correct device. Under Linux, such a device name
- could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
- details.
+ could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for de-
+ tails.
@@ -57,17 +57,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_S9036
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_S9036=4
@@ -82,7 +82,6 @@
AUTHOR
Ingo Schneider
-
14 Jul 2008 sane-s9036(5)
diff --git a/man/sane-sceptre.5.html b/man/sane-sceptre.5.html
index 794c1d2f..6303410e 100644
--- a/man/sane-sceptre.5.html
+++ b/man/sane-sceptre.5.html
@@ -2,7 +2,7 @@
sane-sceptre.5
-
+
sane-sceptre.5
@@ -35,72 +35,72 @@
OPTIONS
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.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
Valid command line options and their syntax can be listed by using
+
scanimage --help -d sceptre
Scan Mode
- --mode selects the basic mode of operation of the scanner valid choices
- are Lineart, Halftone, Gray and Color. 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 color
- image. The scanner supports 30 bits internally but it only
- exports 24.
+ --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 color image. The scanner supports 30 bits internally but it
+ only exports 24.
- --resolution
- selects the resolution for a scan. The scanner can do several
+ --resolution 50..1200
+ Selects the resolution for a scan. The scanner can do several
resolutions between 50 and 1200.
- --halftone-pattern
- selects the pattern mode that is used in Halftone mode. Valid
- options are 1, 2, 3 and 4.
+ --halftone-pattern 1|2|3|4
+ Selects the pattern mode that is used in Halftone mode.
- --gamma-correction
- controls the scanner internal gamma correction. Valid options
- are "Default", "User defined", "High density printing" "Low den-
- sity printing" and "High contrast printing".
+ --gamma-correction Default|User Defined|High Density Printing|Low den-
+ sity printing|High contrast printing
+ controls the scanner internal gamma correction.
--custom-gamma
- (color mode only) allows the user to specify a gamma table (see
- the next 3 parameters).
+ Allows the user to specify a gamma table (see the next 3 parame-
+ ters). Color mode only.
--red-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the red channel. The table must be 256 bytes long.
+ Can be used to download a user defined gamma table for the red
+ channel. The table must be 256 bytes long. Color mode only.
+
--green-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the green channel. The table must be 256 bytes long.
+ Can be used to download a user defined gamma table for the green
+ channel. The table must be 256 bytes long. Color mode only.
--blue-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the blue channel. The table must be 256 bytes long.
+ Can be used to download a user defined gamma table for the blue
+ channel. The table must be 256 bytes long. Color mode only.
- --threshold
- sets the threshold for black and white pixels in lineart mode.
+ --threshold 0..255
+ Sets the threshold for black and white pixels in Lineart mode.
Possible values are from 0 (darker) to 255 (lighter).
--preview
- requests a preview scan. The resolution used for that scan is 30
- dpi and the scan area is the maximum allowed. The scan mode is
+ Requests a preview scan. The resolution used for that scan is 30
+ dpi and the scan area is the maximum allowed. The scan mode is
user selected. The default is "no".
The geometry options
-l -t -x -y
- control the scan area: -l sets the top left x coordinate, -t the
- top left y coordinate, -x selects the width and -y the height of
- the scan area. All parameters are specified in millimeters by
+ control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
default.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/sceptre.conf supports only
- one information: the device name to use (eg /dev/scanner).
+ The configuration file /usr/local/etc/sane.d/sceptre.conf supports only
+ one item: the device name to use (eg /dev/scanner).
@@ -116,9 +116,9 @@
ENVIRONMENT
SANE_DEBUG_SCEPTRE
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
diff --git a/man/sane-scsi.5.html b/man/sane-scsi.5.html
index d4aeea8e..76a555d4 100644
--- a/man/sane-scsi.5.html
+++ b/man/sane-scsi.5.html
@@ -2,7 +2,7 @@
sane-scsi.5
-
+
sane-scsi.5
@@ -23,14 +23,14 @@
GENERAL INFO
- For scanners with a SCSI interface, it may be necessary to edit the
- appropriate backend configuration file before using SANE for the first
+ For scanners with a SCSI interface, it may be necessary to edit the ap-
+ propriate backend configuration file before using SANE for the first
time. For most systems, the configuration file should list the name of
the generic SCSI device that the scanner is connected to (e.g., under
- Linux, /dev/sg4 or /dev/sge is such a generic SCSI device). It is cus-
- tomary to create a symlink from /dev/scanner to the generic SCSI device
+ Linux, /dev/sg4 or /dev/sge is such a generic SCSI device). It is cus-
+ tomary to create a symlink from /dev/scanner to the generic SCSI device
that the scanner is connected to. In this case, the configuration file
- simply lists the line /dev/scanner. For a detailed description of each
+ simply lists the line /dev/scanner. For a detailed description of each
backend's configuration file, please refer to the relevant backend man-
ual page (e.g., sane-epson(5) for Epson scanners, sane-hp(5) for HP
scanners, etc.).
@@ -46,19 +46,19 @@
where VENDOR is the SCSI vendor string, MODEL is the SCSI model string,
TYPE is type SCSI device type string, BUS is the SCSI bus number (named
- "host" in /proc/scsi/scsi), CHANNEL is the SCSI channel number, ID is
+ "host" in /proc/scsi/scsi), CHANNEL is the SCSI channel number, ID is
the SCSI id, and LUN 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 "cat /proc/scsi/scsi". To sim-
- plify configuration, a field's value can be replaced with an asterisk
- symbol (``*''). An asterisk has the effect that any value is allowed
- for that particular field. This can have the effect that a single
- scsi-line matches multiple devices. When this happens, each matching
- device will be probed by the backend one by one and registered if the
- backend thinks it is a compatible device. For example, the line
+ looking at the output of the command 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 allowed for that
+ particular field. This can have the effect that a single scsi-line
+ matches multiple devices. When this happens, each matching device will
+ be probed by the backend one by one and registered if the backend
+ thinks it is a compatible device. For example, the line
scsi MUSTEK MFS-06000CX Scanner 0 00 03 00
@@ -77,9 +77,9 @@
would have the effect that all SCSI devices in the system with a vendor
string of MUSTEK would be probed and recognized by the backend.
- If the remainder of a scsi-string consists of asterisks only, the
- asterisks can be omitted. For example, the following line is equiva-
- lent to the one specified previously:
+ If the remainder of a scsi-string consists of asterisks only, the as-
+ terisks can be omitted. For example, the following line is equivalent
+ to the one specified previously:
scsi MUSTEK
@@ -89,17 +89,17 @@
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 /etc/group which contains all users that should have
- access to the scanner. The permission of the device should then be set
+ "scanner" to /etc/group which contains all users that should have ac-
+ cess to the scanner. The permission of the device should then be set
to allow group read and write access. For example, if the scanner is
- at generic SCSI device /dev/sg0, then the following two commands would
+ at generic SCSI device /dev/sg0, then the following two commands would
set the permission correctly:
$ chgrp scanner /dev/sg0
$ chmod 660 /dev/sg0
When your system uses the device filesystem (devfs), you have to edit
- /etc/devfs/perms. There you should search the line
+ There you should search the line
REGISTER ^sg[^/]* PERMISSIONS root.root 0600
@@ -112,8 +112,8 @@
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
- /dev/xpt0. Instead, you can also set a link /dev/scanner to the appro-
- priate /dev/uk device.
+ /dev/xpt0. Instead, you can also set a link /dev/scanner to the appro-
+ priate /dev/uk device.
Adaptec AHA1542CF
Reported to work fine under FreeBSD 2.2.2R with the aha
@@ -131,9 +131,9 @@
Adaptec 1505
Works on FreeBSD 2.2.5R and 3.0 using the aic driver,
provided that Plug-and-Play support is disabled on the
- card. If there are no uk devices, just do a ``sh MAKEDEV
- uk0'' in the /dev directory. The scanner should then be
- accessible as /dev/uk0 if it was probed during boot.
+ card. If there are no uk devices, just do a sh MAKEDEV
+ uk0 in the directory. The scanner should then be accessi-
+ ble as /dev/uk0 if it was probed during boot.
Tekram DC390
Reported to work fine under FreeBSD 2.2.2R with the amd
@@ -142,126 +142,125 @@
LINUX INFO
- First, make sure your kernel has SCSI generic support enabled. In
- ``make xconfig'', this shows up under ``SCSI support->SCSI generic sup-
- port''.
+ First, make sure your kernel has SCSI generic support enabled. In make
+ xconfig, this shows up under ``SCSI support->SCSI generic support''.
- To keep scanning times to a minimum, it is strongly recommended to use
+ 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. sane-umax, sane-mustek, sane-sharp) automatically
- request larger scsi buffers. If a backend does not automatically
- request a larger scsi buffer, set the environment variable
- SANE_SG_BUFFERSIZE to the desired buffer size in bytes. It is not rec-
- ommended to use more than 1 MB, because for large values the probabil-
- ity increases that the SG driver cannot allocate the necessary buf-
- fer(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
- http://www.torque.net/sg.
+ 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. sane-umax(5), sane-mustek(5), sane-sharp(5)) auto-
+ matically request larger SCSI buffers. If a backend does not automati-
+ cally request a larger SCSI buffer, set the environment variable
+ SANE_SG_BUFFERSIZE to the desired buffer size in bytes. It is not rec-
+ ommended to use more than 1 MB, because for large values the probabil-
+ ity increases that the SG driver cannot allocate the necessary buf-
+ fer(s). For ISA cards, even 1 MB might be a too large value. For a de-
+ tailed discussion of memory issues of the SG driver, see
+ http://www.torque.net/sg.
- For Linux kernels before version 2.2.7 the size of the buffer is only
- 32KB. This works, but for many cheaper scanners this causes scanning
+ For Linux kernels before version 2.2.7 the size of the buffer is only
+ 32KB. This works, but for many cheaper scanners this causes scanning
to be slower by about a factor of four than when using a size of 127KB.
- Linux defines the size of this buffer by macro SG_BIG_BUFF in header
- file /usr/include/scsi/sg.h. Unless a system is seriously short on
- memory, it is recommended to increase this value to the maximum legal
- value of 128*1024-512=130560 bytes. After changing this value, it is
+ Linux defines the size of this buffer by macro SG_BIG_BUFF in header
+ file /usr/include/scsi/sg.h. Unless a system is seriously short on
+ memory, it is recommended to increase this value to the maximum legal
+ value of 128*1024-512=130560 bytes. After changing this value, it is
necessary to recompile both the kernel (or the SCSI generic module) and
- the SCSI backends. Keep in mind that this is only necessary with older
+ the SCSI backends. Keep in mind that this is only necessary with older
Linux kernels.
- A common issue with SCSI scanners is what to do when you booted the
- system while the scanner was turned off? In such a case, the scanner
- won't be recognized by the kernel and SANE won't be able to access it.
- Fortunately, Linux provides a simple mechanism to probe a SCSI device
- on demand. Suppose you have a scanner connected to SCSI bus 2 and the
- scanner has a SCSI id of 5. When the system is up and running and the
+ A common issue with SCSI scanners is what to do when you booted the
+ system while the scanner was turned off. In such a case, the scanner
+ won't be recognized by the kernel and SANE won't be able to access it.
+ Fortunately, Linux provides a simple mechanism to probe a SCSI device
+ on demand. Suppose you have a scanner connected to SCSI bus 2 and the
+ scanner has a SCSI id of 5. When the system is up and running and the
scanner is turned on, you can issue the command:
echo "scsi add-single-device 2 0 5 0" > /proc/scsi/scsi
- and the kernel will probe and recognize your scanner (this needs to be
- done as root). It's also possible to dynamically remove a SCSI device
- by using the ``remove-single-device'' command. For details, please
- refer to to the SCSI-2.4-HOWTO.
+ and the kernel will probe and recognize your scanner (this needs to be
+ done as root). It's also possible to dynamically remove a SCSI device
+ by using the ``remove-single-device'' command. For details, please re-
+ fer to to the SCSI-2.4-HOWTO.
- Scanners are known to work with the following SCSI adapters under
- Linux. This list isn't complete, usually any SCSI adapter supported by
+ Scanners are known to work with the following SCSI adapters under
+ Linux. This list isn't complete, usually any SCSI adapter supported by
Linux should work.
Acard/Advance SCSI adapters
- Some old versions of the kernel driver (atp870u.c) cut
- the inquiry information. Therefore the scanner couldn't
+ Some old versions of the kernel driver (atp870u.c) cut
+ the inquiry information. Therefore the scanner couldn't
be detected correctly. Use a current kernel.
Adaptec AHA-1505/AHA-1542/AHA-2940
- Reported to work fine with Linux since v2.0. If you
- encounter kernel freezes or other unexpected behaviour
- get the latest Linux kernel (2.2.17 seems to work) or
- reduce SCSI buffer size to 32 kB.
+ Reported to work fine with Linux since v2.0. If you en-
+ counter kernel freezes or other unexpected behaviour get
+ the latest Linux kernel (2.2.17 seems to work) or reduce
+ SCSI buffer size to 32 kB.
ASUS SC200
Reported to work fine with Linux v2.0.
BusLogic BT958
- To configure the BusLogic card, you may need to follow
+ To configure the BusLogic card, you may need to follow
these instructions (contributed by Jeremy
- <jeremy@xxedgexx.com>): During boot, when your BusLogic
- adapter is being initialized, press Ctrl-B to enter your
- BusLogic adapter setup. Choose the address which your
+ <jeremy@xxedgexx.com>): During boot, when your BusLogic
+ adapter is being initialized, press Ctrl-B to enter your
+ BusLogic adapter setup. Choose the address which your
BusLogic containing your scanner is located. Choose
``SCSI Device Configuration''. Choose ``Scan SCSI Bus''.
- Choose whatever SCSI id that contains your scanner and
- then choose ``View/Modify SCSI configuration''. Change
+ Choose whatever SCSI id that contains your scanner and
+ then choose ``View/Modify SCSI configuration''. Change
``Negotiation'' to ``async'' and change ``Disconnect'' to
- ``off''. Press Esc, save, and Esc again until you are
+ ``off''. Press Esc, save, and Esc again until you are
asked to reboot.
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
+ supported since Linux 2.2. The SCSI cards are supported
by the module g_NCR5380. It's necessary to tell the ker-
nel the io port and type of card. Example for a 53c400a:
- ``modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1''.
- 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 drivers/scsi/g_NCR5380.c. Some doc-
- umentation is in this file and NCR5380.c.
+ modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1 . Once
+ the kernel detects the card, it should work all right.
+ However, while it should work, do not expect good perfor-
+ mance 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 drivers/scsi/g_NCR5380.c. Some documentation
+ is in this file and NCR5380.c.
NCR/Symbios 810
- For some scanners it may be necessary to disable discon-
- nect/reconnect. To achieve this use the option
+ For some scanners it may be necessary to disable discon-
+ nect/reconnect. To achieve this use the option
ncr53c8xx="disc:n". Some people reported that their scan-
ner only worked with the 53c7,8xx driver, not the
ncr53c8xx. Try 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
+ 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 /var/log/mes-
- sages 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 ncr53c8xx.c (nor-
- mally in directory /usr/src/linux/drivers/scsi) and
- change the constant 10 to, say, 60 (one minute). Then
+ the form ``restart (ncr dead ?)'' in your /var/log/mes-
+ sages 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 ncr53c8xx. (nor-
+ mally in directory /usr/src/linux/drivers/scsi) and
+ change the constant 10 to, say, 60 (one minute). Then
rebuild the kernel/module and try again.
Tekram DC315
- The driver can be downloaded from
- 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. modprobe dc395x_trm
- dc395x_trm=7,5,1,32.
+ The driver can be downloaded from
+ http://www.garloff.de/kurt/linux/dc395/. For some older
+ scanners it may be necessary to disable all the more ad-
+ vanced features by using e.g. modprobe dc395x_trm
+ dc395x_trm=7,5,1,32.
Tekram DC390
- Version 1.11 of the Tekram driver seems to work fine
- mostly, except that the scan does not terminate properly
+ Version 1.11 of the Tekram driver seems to work fine
+ mostly, except that the scan does not terminate properly
(it causes a SCSI timeout after 10 minutes). The generic
AM53C974 also seems to work fine and does not suffer from
the timeout problems.
@@ -269,28 +268,28 @@
SOLARIS, OPENSTEP AND NEXTSTEP INFO
- Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
- refers to a SCSI bus, not to an individual device. For example,
- /dev/sg0 refers to the first SCSI bus. To tell SANE which device to
- use, append the character 'a'+target-id to the special device name.
+ Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
+ refers to a SCSI bus, not to an individual device. For example,
+ /dev/sg0 refers to the first SCSI bus. To tell SANE which device to
+ use, append the character 'a'+target-id to the special device name.
For example, the SCSI device connected to the first SCSI controller and
- with target-id 0 would be called /dev/sg0a, and the device with target-
- id 1 on that same bus would be called /dev/sg0b, and so on.
+ with target-id 0 would be called /dev/sg0a, and the device with target-
+ id 1 on that same bus would be called /dev/sg0b, and so on.
ENVIRONMENT
SANE_DEBUG_SANEI_SCSI
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for the generic
- SCSI I/O subsystem. E.g., a value of 128 requests all debug
- output to be printed by the backend. A value of 255 also prints
- kernel messages from the SCSI subsystem (where available).
- Smaller levels reduce verbosity.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for the generic SCSI
+ I/O subsystem. E.g., a value of 128 requests all debug output
+ to be printed by the backend. A value of 255 also prints kernel
+ messages from the SCSI subsystem (where available). Smaller
+ levels reduce verbosity.
SANE_SCSICMD_TIMEOUT
- sets the timeout value for SCSI commands in seconds. Overriding
- the default value of 120 seconds should only be necessary for
+ sets the timeout value for SCSI commands in seconds. Overriding
+ the default value of 120 seconds should only be necessary for
very slow scanners.
diff --git a/man/sane-sharp.5.html b/man/sane-sharp.5.html
index 3d883ae5..1627fbcb 100644
--- a/man/sane-sharp.5.html
+++ b/man/sane-sharp.5.html
@@ -2,7 +2,7 @@
sane-sharp.5
-
+
sane-sharp.5
@@ -58,197 +58,171 @@
SCAN OPTIONS
- Scan Mode (parameter --mode for scanimage). Possible settings:
- Lineart (1 bit black & white scans),
- Gray (8 bit gray scale scans),
- Lineart Color (bi-level color scans),
- Color (8 bit RGB scans).
- The default value is Color.
+ --mode Scan Mode. Possible settings are: Lineart (1 bit black & white
+ scans), Gray (8 bit gray scale scans), Lineart Color (bi-level
+ color scans), and Color (8 bit RGB scans). The default value is
+ Color.
- Halftone Pattern (parameter --halftone-pattern for scanimage). Avail-
- able only for the JX-330 series scanners. Possible settings:
- none
- Dither Bayer
- Dither Spiral
- Dither Dispersed
- Error Diffusion
- The default value is none.
+ --halftone-pattern
+ Halftone Pattern. Available only for the JX-330 series scanners.
+ Possible settings: none, Dither Bayer, Dither Spiral, Dither
+ Dispersed and Error Diffusion. The default value is none.
- Paper Source (parameter --source for scanimage). This option is only
- available, if an automatic document feeder or a transparency adapter is
- installed. Possible settings:
- Flatbed
- Automatic Document Feeder
- Transparency Adapter
- If an ADF or a transparency adapter is installed, using it is the
- default selection.
+ --source
+ Paper Source. This option is only available if an automatic doc-
+ ument feeder or a transparency adapter is installed. Possible
+ settings are: Flatbed, Automatic Document Feeder, and Transpar-
+ ency Adapter. If an ADF or a transparency adapter is installed,
+ using it is the default selection.
- Custom Gamma (parameter --custom-gamma for scanimage). This option
- determines whether a builtin or a custom gamma-table is used. Possible
- settings:
- yes enables custom gamma tables
- no enables a built gamma table
+ --custom-gamma
+ Custom Gamma This option determines whether a builtin or a cus-
+ tom gamma table is used. Possible settings are: yes (enables
+ custom gamma tables) or no (enables a built gamma table).
- Gamma (parameter --Gamma for scanimage). This option is only available,
- if Custom Gamma is set to no. Possible values:
- 1.0
- 2.2
- The default value is 2.2. (The JX-250 and JX-350 have no built in gamma
- correction; for these scanner, a gamma table is downloaded to the scan-
- ner by the backend.)
+ --gamma
+ Gamma. This option is only available if Custom Gamma is set to
+ no. Possible values are: 1.0 or 2.2. The default value is 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 by
+ the backend.)
- Gamma Table (parameter --gamma-table for scanimage). Allowed values:
- 0..255; 256 numbers must be defined. The default values are 0, 1, 2,
- .. 255 (i.e., gamma == 1). This table is only used for gray scale
- scans.
+ --gamma-table
+ Gamma Table. Allowed values: 0..255; 256 numbers must be de-
+ fined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
+ 1). This table is only used for gray scale scans.
- Red Gamma Table (parameter --red-gamma-table for scanimage). Allowed
- values: 0..255; 256 numbers must be defined. The default values are 0,
- 1, 2, .. 255 (i.e., gamma == 1).
+ --red-gamma-table
+ Red Gamma Table. Allowed values: 0..255; 256 numbers must be de-
+ fined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
+ 1).
- Green Gamma Table (parameter --green-gamma-table for scanimage).
- Allowed values: 0..255; 256 numbers must be defined. The default val-
- ues are 0, 1, 2, .. 255 (i.e., gamma == 1).
+ --green-gamma-table
+ Green Gamma Table. Allowed values: 0..255; 256 numbers must be
+ defined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
+ 1).
- Blue Gamma Table (parameter --blue-gamma-table for scanimage). Allowed
- values: 0..255; 256 numbers must be defined. The default values are 0,
- 1, 2, .. 255 (i.e., gamma == 1).
+ --blue-gamma-table
+ Blue Gamma Table. Allowed values: 0..255; 256 numbers must be
+ defined. The default values are 0, 1, 2, .. 255 (i.e., gamma ==
+ 1).
- Resolution in pixel per inch (parameter --resolution for scanimage).
- Selects the resolution of the scanned image. Allowed values:
- 30..600 (JX-330, JX-350 and JX-610) resp. 30..400 (JX-250)
- The default value is 150.
+ --resolution
+ Selects the resolution of the scanned image. Allowed values:
+ 30..600 (JX-330, JX-350 and JX-610) and 30..400 (JX-250). The
+ default value is 150.
- Scan Window
+ -l, -t, -x, -y
+ Scan Window. Top-left x position of scan area (-l), top-left y
+ position of scan area (-t), bottom right x position of scan area
+ (-x) and bottom right y position of scan area (-y). The possi-
+ ble 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 al-
+ lowed by xscanimage(1), or xsane(1). With scanimage(1), enter
+ one of the following commands in order to see the allowed param-
+ eter values for the scan window:
- 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
- xscanimage, or xsane. With scanimage, enter one of the following com-
- mands:
+ scanimage -d sharp --source "Automatic Document Feeder" --help
- scanimage -d sharp --source "Automatic Document Feeder" --help
+ scanimage -d sharp --source Flatbed --help
- scanimage -d sharp --source Flatbed --help
+ scanimage -d sharp --source "Transparency Adapter" --help
- scanimage -d sharp --source "Transparency Adapter" --help
+ --edge emphasis
+ Edge emphasis. This option is not available for the JX-250 and
+ the JX-350. Possible settings: None, Middle, Strong, and Blur.
+ The default value is None.
- in order to see the allowed parameter values for the scan window.
+ --threshold
+ Sets the threshold for black and white pixels in lineart mode.
+ Possible values are 1..255. The default value is 128. This op-
+ tion is only available in scan mode lineart.
- The scan window parameters are:
+ --threshold-red
+ Sets the threshold for the red component of a pixel in in lin-
+ eart color scan mode. Possible values are 1..255. The default
+ value is 128. This option is only available in scan mode color
+ lineart.
- Top-left x position of scan area (parameter -l for scanimage);
- Top-left y position of scan area (parameter -t for scanimage);
- bottom right x position of scan area (parameter -x for scanim-
- age);
- bottom right y position of scan area (parameter -y for scanim-
- age);
+ --threshold-green
+ Sets the threshold for the green component of a pixel in in lin-
+ eart color scan mode. Possible values are 1..255. The default
+ value is 128. This option is only available in scan mode color
+ lineart .
- Edge emphasis (parameter --Edge emphasis for scanimage). This option is
- not available for the JX-250 and the JX-350. Possible settings:
- None
- Middle
- Strong
- Blur
- The default value is None.
+ --threshold-blue
+ Sets the threshold for the blue component of a pixel in in lin-
+ eart color scan mode. Possible values are 1..255. The default
+ value is 128. This option is only available in scan mode color
+ lineart.
- Threshold (parameter --threshold for scanimage). Sets the threshold for
- black and white pixels in lineart mode. Possible values:
- 1..255
- The default value is 128. This option is only available in scan mode
- lineart.
-
- Threshold Red (parameter --threshold-red for scanimage). Sets the
- threshold for the red component of a pixel in in lineart color scan
- mode. Possible values:
- 1..255
- The default value is 128. This option is only available in scan mode
- color lineart.
-
- Threshold Green (parameter --threshold-green for scanimage). Sets the
- threshold for the green component of a pixel in in lineart color scan
- mode. Possible values:
- 1..255
- The default value is 128. This option is only available in scan mode
- color lineart.
-
- Threshold Blue (parameter --threshold-blue for scanimage). Sets the
- threshold for the blue component of a pixel in in lineart color scan
- mode. Possible values:
- 1..255
- The default value is 128. This option is only available in scan mode
- color lineart.
-
- Light Color (parameter --LightColor for scanimage). Sets the color of
- the light source. Possible values:
- white
- red
- green
- blue
- The default value is white. This option is only available in scan
- modes lineart color and color.
+ --lightcolor
+ Sets the color of the light source. Possible values are white,
+ red, green and blue. The default value is white. This option
+ is only available in scan modes lineart color and color.
ADF USAGE
- If a paper jam occurred, the maintenance cover must be opened and
- closed, even if the jammed paper can be removed without opening the
- maintenance cover. Otherwise, the error condition cannot be cleared.
+ If a paper jam occurrs, the maintenance cover must be opened and
+ closed, even if the jammed paper can be removed without opening the
+ maintenance cover. Otherwise, the error condition will not be cleared.
CONFIGURATION
- The contents of the sharp.conf file is a list of options and device
- names that correspond to Sharp scanners. Empty lines and lines begin-
- ning with a hash mark (#) are ignored. See sane-scsi(5) for details
+ The contents of the sharp.conf file is a list of options and device
+ names that correspond to Sharp scanners. Empty lines and lines begin-
+ ning with a hash mark (#) are ignored. See sane-scsi(5) for details
about device names.
Lines setting an option start with the key word option, followed by the
- option's name and the option's value. At present, three options are
- defined: buffers, buffersize, and readqueue.
+ option's name and the option's value. At present, three options are de-
+ fined: buffers, buffersize, and readqueue.
- Options defined at the start of sharp.conf apply to all devices;
- options defined after a device name apply to this device.
+ Options defined at the start of sharp.conf apply to all devices; op-
+ tions defined after a device name apply to this device.
- The options buffers and readqueue are only significant if the backend
- has been compiled so that for each scan a second process is forked
- (switch USE_FORK in sharp.c ). This process reads the scan data from
- the scanner and writes this data into a block of shared memory. The
+ The options buffers and readqueue are only significant if the backend
+ has been compiled so that for each scan a second process is forked
+ (switch USE_FORK in sharp.c ). This process reads the scan data from
+ the scanner and writes this data into a block of shared memory. The
parent process reads the data from this memory block and delivers it to
- the frontend. The options control the size and usage of this shared
+ the frontend. The options control the size and usage of this shared
memory block.
- option buffers defines the number of buffers used. The smallest number
+ option buffers defines the number of buffers used. The smallest number
allowed is 2.
- option buffersize defines the size of one buffer. Since each buffer is
+ option buffersize defines the size of one buffer. Since each buffer is
filled with a single read command sent to the scanner, its size is lim-
- ited automatically to the size allowed by the operating system or by
- the Sane SCSI library for SCSI read commands. A buffer size of 128 kB
+ ited automatically to the size allowed by the operating system or by
+ the Sane SCSI library for SCSI read commands. A buffer size of 128 kB
or 256 kB is recommended for scan resolutions of 300 dpi and above.
option readqueue defines how many read commands to be sent to the scan-
- ner are queued. At present, the Sane SCSI library supports queued read
- commands only for for Linux. For other operating systems, option read-
- queue should be set to 0. For Linux, option readqueue should be set to
+ ner are queued. At present, the Sane SCSI library supports queued read
+ commands only for for Linux. For other operating systems, option read-
+ queue should be set to 0. For Linux, option readqueue should be set to
2. Larger values than 2 for option readqueue are not reasonable in most
cases. option buffers should be greater than option readqueue.
Performance Considerations
- This section focuses on the problem of stops of the scanner's carriage
+ This section focuses on the problem of stops of the scanner's carriage
during a scan. Carriage stops happen mainly with the JX-250. This scan-
- ner has obviously only a small internal buffer compared to its speed.
+ ner has obviously only a small internal buffer compared to its speed.
That means that the backend must read the data as fast as possible from
the scanner in order to avoid carriage stops.
- Even the JX-250 needs only less than 10 seconds for a 400 dpi A4 gray
- scale scan, which results in a data transfer rate of more than 1.6 MB
- per second. This means that the data produced by the scanner must be
- processed fairly fast. Due to the small internal buffer of the JX-250,
- the backend must issue a read request for the next data block as soon
- as possible after reading a block of data in order to avoid carriage
+ Even the JX-250 needs only less than 10 seconds for a 400 dpi A4 gray
+ scale scan, which results in a data transfer rate of more than 1.6 MB
+ per second. This means that the data produced by the scanner must be
+ processed fairly fast. Due to the small internal buffer of the JX-250,
+ the backend must issue a read request for the next data block as soon
+ as possible after reading a block of data in order to avoid carriage
stops.
Stops of the carriage can be caused by the following reasons:
@@ -258,45 +232,45 @@
- a program which processes the data acquired by the backend too
slow.
- Too much "traffic" on the SCSI bus: This happens for example, if hard
- disks are connected to the same SCSI bus as the scanner, and when data
- transfer from/to these hard disks requires a considerable part of the
- SCSI bandwidth during a scan. If this is the case, you should consider
+ Too much "traffic" on the SCSI bus: This happens for example, if hard
+ disks are connected to the same SCSI bus as the scanner, and when data
+ transfer from/to these hard disks requires a considerable part of the
+ SCSI bandwidth during a scan. If this is the case, you should consider
to connect the scanner to a separate SCSI adapter.
- Slow responses by the backend to the scanner: Unfortunately, Unix-like
+ Slow responses by the backend to the scanner: Unfortunately, UNIX-like
operating systems generally have no real time capabilities. Thus there
- is no guarantee that the backend is under any circumstances able to
- communicate with the scanner as fast as required. To minimize this
- problem, the backend should be compiled so that a separate reader
- process is forked: Make sure that USE_FORK is defined when you compile
- sharp.c. If slow responses of the backend remain to be problem, you
- could try to reduce the load of the system. Even while the backend and
- the reader process need only a minor amount of processor time, other
- running processes can cause an increase in the time delay between two
- time slices given to the reader process. On slower systems, such an
- increased delay can be enough to cause a carriage stop with the JX-250.
+ is no guarantee that the backend is under any circumstances able to
+ communicate with the scanner as fast as required. To minimize this
+ problem, the backend should be compiled so that a separate reader
+ process is forked: Make sure that USE_FORK is defined when you compile
+ sharp.c. If slow responses of the backend remain to be problem, you
+ could try to reduce the load of the system. Even while the backend and
+ the reader process need only a minor amount of processor time, other
+ running processes can cause an increase in the time delay between two
+ time slices given to the reader process. On slower systems, such an in-
+ creased delay can be enough to cause a carriage stop with the JX-250.
For Linux, the usage of the SG driver version 2.1.36 or above is recom-
- mended, because it supports, in combination with the SCSI library of
- Sane version 1.0.2, command queueing within the kernel. This queueing
- implementation, combined with a buffer size of at least 128 kB, should
+ mended, because it supports, in combination with the SCSI library of
+ Sane version 1.0.2, command queueing within the kernel. This queueing
+ implementation, combined with a buffer size of at least 128 kB, should
avoid most carriage stops.
- Slow processing of the scan data: An example for this situation is the
- access to the scanner via a 10 MBit Ethernet, which is definitely too
- slow to transfer the scan data as fast as they are produced by the
- scanner. If you have enough memory available, you can increase option
+ Slow processing of the scan data: An example for this situation is the
+ access to the scanner via a 10 MBit Ethernet, which is definitely too
+ slow to transfer the scan data as fast as they are produced by the
+ scanner. If you have enough memory available, you can increase option
buffers, so that an entire image can be stored in these buffers.
- In order to see, if the backend is too slow or if the further process-
- ing of the data is too slow, set the environment variable
- SANE_DEBUG_SHARP to 1. When a scan is finished, the backend writes the
- line "buffer full conditions: nn" to stderr. If nn is zero, carriage
- stops are caused by too slow responses of the backend or too much
- "traffic" on the SCSI bus. If nn is greater than zero, the backend had
- to wait nn times until a buffer has been processed by the frontend.
- (Please note that option buffers must be greater than option readqueue
- in order to get useful output for "buffer full conditions".)
+ In order to see, if the backend is too slow or if the further process-
+ ing of the data is too slow, set the environment variable SANE_DE-
+ BUG_SHARP to 1. When a scan is finished, the backend writes the line
+ "buffer full conditions: nn" to stderr. If nn is zero, carriage stops
+ are caused by too slow responses of the backend or too much "traffic"
+ on the SCSI bus. If nn is greater than zero, the backend had to wait nn
+ times until a buffer has been processed by the frontend. (Please note
+ that option buffers must be greater than option readqueue in order to
+ get useful output for "buffer full conditions".)
@@ -315,36 +289,36 @@
ENVIRONMENT
SANE_DEBUG_SHARP
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
KNOWN PROBLEMS
1. ADF Mode
- After several ADF scans, the scanner moves the carriage back to
- the idle position and back to ADF scan position, before a scan
- starts. We do not know, if this is a problem of the scanner, or
- if this is a bug of the backend. At present, the scanner must
+ After several ADF scans, the scanner moves the carriage back to
+ the idle position and back to ADF scan position, before a scan
+ starts. We do not know, if this is a problem of the scanner, or
+ if this is a bug of the backend. At present, the scanner must
power off and on to stop this annoying behaviour.
2. Threshold level does not work (only JX-610)
- 3. The maximum resolution is limited to 600 dpi(JX-610 supported to
+ 3. The maximum resolution is limited to 600 dpi(JX-610 supported to
1200 dpi) resp. 400 dpi (JX-250)
4. If the JX250 is used with an ADF, the following situation can occur:
- After several scans, the scanner moves, after loading a new sheet of
+ After several scans, the scanner moves, after loading a new sheet of
paper, the carriage to the idle position, and then back to the position
- used for ADF scans. This happens for every scan, in contrast to the
- calibration, which is done after 10 scans. (For the calibration, the
- carriage is also moved to the idle position.) We do not know, if this
+ used for ADF scans. This happens for every scan, in contrast to the
+ calibration, which is done after 10 scans. (For the calibration, the
+ carriage is also moved to the idle position.) We do not know if this
behavior is caused by the backend, or if it is a bug in the firmware of
the scanner.
- 5. Usage of a transparency adapter (film scan unit) is supported, but
+ 5. Usage of a transparency adapter (film scan unit) is supported, but
not tested.
@@ -360,7 +334,7 @@
CREDITS
- The Sharp backend is based on the Canon backend written by Helmut Koe-
+ The Sharp backend is based on the Canon backend written by Helmut Koe-
berle
Parts of this man page are a plain copy of sane-mustek(5) by David Mos-
diff --git a/man/sane-sm3600.5.html b/man/sane-sm3600.5.html
index 260919d6..2ffb1056 100644
--- a/man/sane-sm3600.5.html
+++ b/man/sane-sm3600.5.html
@@ -2,7 +2,7 @@
sane-sm3600.5
-
+
sane-sm3600.5
@@ -40,8 +40,8 @@
FRONTEND OPTIONS
This backend dynamically enables the options for the frontend, that are
- supported by the scanner in dependence of the scanning-mode and other
- options. Not supported options are disabled.
+ supported by the scanner dependent on the scanning-mode and other op-
+ tions. Unsupported options are disabled.
The following options are supported by the Microtek2-driver:
@@ -73,11 +73,11 @@
ENVIRONMENT
SANE_DEBUG_SM3600
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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. To see error messages on stderr
- set SANE_DEBUG_SM3600 to 1.
+ set SANE_DEBUG_SM3600 to 1.
E.g. just say:
export SANE_DEBUG_SM3600=5
@@ -85,13 +85,14 @@
SEE ALSO
- sane-microtek2(5), http://sm3600.sourceforge.net
+ sane(7), sane-microtek(5), sane-microtek2(5)
+ http://sm3600.sourceforge.net
AUTHOR
- Marian Eichholz (eichholz@computer.org)
- Glenn Ramsey (glenn@componic.com)
+ Marian Eichholz <eichholz@computer.org>
+ Glenn Ramsey <glenn@componic.com>
14 Jul 2008 sane-sm3600(5)
diff --git a/man/sane-sm3840.5.html b/man/sane-sm3840.5.html
index 16c94fc9..202d2170 100644
--- a/man/sane-sm3840.5.html
+++ b/man/sane-sm3840.5.html
@@ -2,7 +2,7 @@
sane-sm3840.5
-
+
sane-sm3840.5
@@ -21,8 +21,8 @@
backend that provides access to some Microtek scanners with the SCAN08
USB chip.
- There exist backends for Microtek scanners with SCSI command set.
- Refer to sane-microtek(5) and sane-microtek2(5) for details.
+ There exist backends for Microtek scanners with SCSI command set. Re-
+ fer to sane-microtek(5) and sane-microtek2(5) for details.
There also exists a Microtek 3600 series driver, see sane-sm3600(5) for
details.
@@ -37,31 +37,31 @@
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 (earle@ziplabel.com) to report results with scanners
+ the backend author (earle@ziplabel.com) to report results with scanners
not on the list.
FRONTEND OPTIONS
- The following options are supported by the sm3840-driver:
+ The following options are supported by the sane-sm3840 driver:
--mode color|gray|lineart|halftone
- Color or grayscale mode.
+ Color or grayscale mode.
--resolution 150|300|600|1200
- Pixels per inch for scans.
+ Pixels per inch for scans.
--depth 8|16
- Note that the least significant bits of 16bpp mode may be noise.
+ Note that the least significant bits of 16bpp mode may be noise.
--brightness 1..4096
- Higher numbers increase brightness of returned image.
+ Higher numbers increase brightness of returned image.
--contrast 0.1..9.9
- Larger numbers decrease contrast of returned image.
+ Larger numbers decrease contrast of returned image.
--lamp-timeout 1..15
- Time in minutes until the lamp is turned off after a scan.
+ Time in minutes until the lamp is turned off after a scan.
@@ -82,21 +82,22 @@
ENVIRONMENT
SANE_DEBUG_SM3840
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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. To see error messages on stderr
- set SANE_DEBUG_SM3840 to 1.
+ set SANE_DEBUG_SM3840 to 1.
SEE ALSO
- sane-microtek2(5), sane-sm3600(5), http://www.ziplabel.com/sm3840
+ sane(7), sane-microtek(5), sane-microtek2(5), sane-sm3600(5)
+ http://www.ziplabel.com/sm3840
AUTHOR
- Earle F. Philhower III (earle@ziplabel.com)
+ Earle F. Philhower III <earle@ziplabel.com>
11 Jul 2008 sane-sm3840(5)
diff --git a/man/sane-snapscan.5.html b/man/sane-snapscan.5.html
index 90d7aee6..ad1f0d16 100644
--- a/man/sane-snapscan.5.html
+++ b/man/sane-snapscan.5.html
@@ -2,7 +2,7 @@
sane-snapscan.5
-
+
sane-snapscan.5
@@ -46,7 +46,7 @@
firmware /usr/local/share/sane/snapscan/firmware.bin
- For further details read http://snapscan.sourceforge.net.
+ For further details read http://snapscan.sourceforge.net.
@@ -79,17 +79,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_SNAPSCAN
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -101,9 +101,8 @@
SEE ALSO
- sane(7), sane-scsi(5)
- http://www.cs.ualberta.ca/~charter/SnapScan/snapscan.html
- http://sourceforge.net/projects/snapscan/ (new development website)
+ sane(7), sane-scsi(5),
+ http://sourceforge.net/projects/snapscan/ (new development website)
diff --git a/man/sane-sp15c.5.html b/man/sane-sp15c.5.html
index 25a77e13..7d803398 100644
--- a/man/sane-sp15c.5.html
+++ b/man/sane-sp15c.5.html
@@ -2,7 +2,7 @@
sane-sp15c.5
-
+
sane-sp15c.5
@@ -37,14 +37,14 @@
CONFIGURATION
A modest effort has been made to expose the standard options to the
- API. This allows frontends such as xscanimage to set scanning region,
- resolution, bit-depth (and color), and enable the automatic document
- feeder.
+ API. This allows frontends such as xscanimage(1) to set scanning re-
+ gion, resolution, bit-depth (and color), and enable the automatic docu-
+ ment feeder.
SEE ALSO
- sane(7), sane-scsi(5), sane-fujitsu(5)
+ sane(7), sane-scsi(5), sane-fujitsu(5), xscanimage(1)
Fujitsu ScanPartner 15C OEM Manual, Doc. No. 250-0081-0
Fujitsu M3096G OEM Manual, part number 50FH5028E-05
Fujitsu M3096GX/M3093GX/M3093DG OEM Manual, part number C150-E015...03
@@ -52,7 +52,7 @@
AUTHOR
- Randolph Bentson <bentson@holmsjoen.com>, with credit to the unnamed
+ Randolph Bentson <bentson@holmsjoen.com>, with credit to the unnamed
author of the coolscan driver
@@ -68,8 +68,8 @@
I'm sure there are plenty, and not too well hidden, but I haven't seen
them yet.
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
- xsane doesn't even display this capability.
+ directions. I confess I haven't tested this yet. I have found that
+ xsane(1) doesn't even display this capability.
Threshold settings on the SP15C don't seem to affect the results of
lineart mode scans.
It might be possible to merge these two drivers without much effort
diff --git a/man/sane-st400.5.html b/man/sane-st400.5.html
index df2645d7..a78d74e5 100644
--- a/man/sane-st400.5.html
+++ b/man/sane-st400.5.html
@@ -2,7 +2,7 @@
sane-st400.5
-
+
sane-st400.5
@@ -32,7 +32,7 @@
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 revi-
sion to sane-devel@alioth-lists.debian.net. Have a look at
- http://www.sane-project.org/mailing-lists.html concerning subscription
+ http://www.sane-project.org/mailing-lists.html concerning subscription
to sane-devel.
@@ -65,7 +65,7 @@
scsi SIEMENS "ST 400" Scanner * * 3 0
In this configuration, the driver can only access the ST400 model at
- SCSI ID 3 LUN 0 (see section "BUGS" below for the reason). To use the
+ SCSI ID 3 LUN 0 (see section BUGS below for the reason). To use the
driver with other scanner models, add an appropriate line to the con-
figuration file. For example, to use it with an ST800 at SCSI ID 3 LUN
0, add the line:
@@ -95,17 +95,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 sepa-
- rator character, then the default directories are searched after
- the explicitly specified directories. For example, setting
- SANE_CONFIG_DIR to "/tmp/config:" would result in directories
- "tmp/config", ".", and "/etc/sane.d" being searched (in this
- order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_ST400
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -123,7 +123,7 @@
ners: Just add an appropriate line to the configuration file. The con-
figuration file as distributed (see above) only works with the ST400.
Be careful: If there is no config file at all, the backend defaults to
- /dev/scanner.
+ /dev/scanner.
The ST400 answers on all eight SCSI LUNs. Normally this is not a prob-
lem, as LUN support is usually disabled in SCSI drivers, but if you are
@@ -134,24 +134,24 @@
DEBUG
- If you encounter a bug please set the environment variable
- SANE_DEBUG_ST400 to 128 and try to regenerate the problem. Then send me
- a report with the log attached.
+ If you encounter a bug please set the environment variable SANE_DE-
+ BUG_ST400 to 128 and try to regenerate the problem. Then send me a re-
+ port with the log attached.
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
+ please also set the environment variable SANE_DEBUG_SANEI_SCSI to 128
before sending me the report.
SEE ALSO
sane(7), sane-scsi(5)
- http://www.informatik.uni-oldenburg.de/~ingo/sane/
+ http://www.informatik.uni-oldenburg.de/~ingo/sane/
AUTHOR
- Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
+ Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
14 Jul 2008 sane-st400(5)
diff --git a/man/sane-stv680.5.html b/man/sane-stv680.5.html
index cfbc1e08..5a244f22 100644
--- a/man/sane-stv680.5.html
+++ b/man/sane-stv680.5.html
@@ -2,7 +2,7 @@
sane-stv680.5
-
+
sane-stv680.5
@@ -19,8 +19,8 @@
DESCRIPTION
The sane-stv680 library implements a SANE (Scanner Access Now Easy)
backend that provides access to some STV680 cameras. This backend
- should be considered beta-quality software! STV680 cameras are sold
- under various brands like Aiptek. This backend may or may not support
+ should be considered beta-quality software! STV680 cameras are sold un-
+ der various brands like Aiptek. This backend may or may not support
yours.
The cameras that should work with this backend are:
@@ -37,32 +37,35 @@
For startup of this backend check that if present the stv680 kernel
module is removed or disabled.
- Also before using, enable the backend by editing the
- /etc/sane.d/dll.conf file, change #stv680 to stv680.
+ Also before using, enable the backend by editing the /usr/lo-
+ cal/etc/sane.d/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 scanimage or through GUI elements in
- xcam. For both programs use the -B option needed for size buffer.
+ line options to programs like scanimage(1) or through GUI elements in
+ xcam(1). For both programs use the -B option needed for size buffer.
Some frontends examples:
- xcam
+
+ xcam(1)
xcam -B
- scanimage: for writing in batch mode to a file or to a new file each
- time.
+ scanimage(1): for writing in batch mode to a file or to a new file each
+ time:
+
scanimage -B -d stv680:libusb:001:002 --batch=out.ppm --batch-
count 5 --mode "Color RGB"
scanimage -B -d stv680:libusb:001:002 --batch=out%d.ppm --batch-
count 5 --mode "Color RGB"
- If you have any success with a camera not listed here, or if you have
- any strange behavior, please report to the backend maintainer or to the
- SANE mailing list.
+ If you have any success with a camera not listed here, or if you ob-
+ serve 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:
- Valid command line options and their syntax can be listed by using
scanimage --help -d stv680
Scan Mode
@@ -88,17 +91,17 @@
Enhancement options
- --white-level-r
+ --white-level-r -32..+32
Selects what red radiance level should be considered "white",
when scanning some sheets by changing the calibration value
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
- --white-level-g
+ --white-level-g -32..+32
Selects what green radiance level should be considered "white",
when scanning some sheets by changing the calibration i value
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
- --white-level-b
+ --white-level-b -32..+32
Selects what blue radiance level should be considered "white",
when scanning some sheets by changing the calibration value
loaded into the scanner. Scale -32 .. 0 .. +32 in steps of 1.
@@ -106,8 +109,8 @@
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/stv680.conf supports only
- one information: the device name to use (eg usb 0x.... 0x....).
+ The configuration file /usr/local/etc/sane.d/stv680.conf supports only
+ one item: the device name to use (eg usb 0x.... 0x....).
@@ -123,8 +126,8 @@
ENVIRONMENT
SANE_DEBUG_STV680
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -136,7 +139,6 @@
ments what the webcam can support.
-
BUGS
Plenty. Parts of this backend are still under development.
@@ -147,12 +149,12 @@
SEE ALSO
- sane-usb(5), scanimage(1), xcam(1), sane(7)
+ sane(7), sane-usb(5), scanimage(1), xcam(1)
AUTHORS
- Gerard Klaver http://gkall.hobby.nl/stv680-aiptek.html
+ Gerard Klaver http://gkall.hobby.nl/stv680-aiptek.html
@@ -160,7 +162,7 @@
Thanks to developers of the other stv680 programs:
STV680 kernel module
pencam2 program
- libghoto2 program (camlib stv0680)
+ libghoto2(3) program (camlib stv0680)
11 Jul 2008 sane-stv680(5)
diff --git a/man/sane-tamarack.5.html b/man/sane-tamarack.5.html
index 2405e530..0418608d 100644
--- a/man/sane-tamarack.5.html
+++ b/man/sane-tamarack.5.html
@@ -2,7 +2,7 @@
sane-tamarack.5
-
+
sane-tamarack.5
@@ -33,11 +33,11 @@
special
Where special is the path-name for the special device that corresponds
- to a SCSI scanner. The special device name must be a generic SCSI
- device or a symlink to such a device. The program sane-find-scanner
+ to a SCSI scanner. The special device name must be a generic SCSI de-
+ vice or a symlink to such a device. The program sane-find-scanner(1)
helps to find out the correct device. Under Linux, such a device name
- could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for
- details.
+ could be /dev/sga or /dev/sge, for example. See sane-scsi(5) for de-
+ tails.
@@ -62,17 +62,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_TAMARACK
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_TAMARACK=4
@@ -80,7 +80,7 @@
SEE ALSO
- sane(7), sane-scsi(5)
+ sane(7), sane-find-scanner(1), sane-scsi(5)
diff --git a/man/sane-teco1.5.html b/man/sane-teco1.5.html
index ab89ecb4..7a2dca50 100644
--- a/man/sane-teco1.5.html
+++ b/man/sane-teco1.5.html
@@ -2,7 +2,7 @@
sane-teco1.5
-
+
sane-teco1.5
@@ -51,38 +51,40 @@
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. "sane-find-scanner -v" will also show the
- scsi inquiry, and if it is a TECO scanner, the name will be there too.
+ is also part of the FCC ID. 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
- xscanimage or xsane.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
- If you have any success with a scanner not listed here, or if you have
- any strange behavior, please report to the backend maintainer or to the
- SANE mailing list.
+ If you have any success with a scanner not listed here, or if you no-
+ tice 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:
- Valid command line options and their syntax can be listed by using
scanimage --help -d teco1
Scan Mode
- --mode selects the basic mode of operation of the scanner valid choices
- are Black & White , Grayscale and Color The Black & White mode
- is black and white only (1 bit). Grayscale will produce 256 lev-
- els of gray (8 bits). Color will produce a 24 bits color image.
+ --mode Black & White|Grayscale|Color
+ Selects the basic mode of operation of the scanner valid choices
+ are The Black & White mode is black and white only (1 bit).
+ Grayscale will produce 256 levels of gray (8 bits). Color will
+ produce a 24 bits color image.
- --resolution
- selects the resolution for a scan. The scanner can do all reso-
+ --resolution 1..600
+ Selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 600, in increments of 1.
Geometry options
-l -t -x -y
- control the scan area: -l sets the top left x coordinate, -t the
- top left y coordinate, -x selects the width and -y the height of
- the scan area. All parameters are specified in millimeters by
- default.
+ Controls the scan area: -l sets the top left x coordinate, -t
+ the top left y coordinate, -x selects the width and -y the
+ height of the scan area. All parameters are specified in mil-
+ limeters by default.
Enhancement options
@@ -91,32 +93,31 @@
the next 3 parameters).
--red-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the red channel. The table must be 256 bytes long.
+ Can be used to download a user defined gamma table for the red
+ channel. The table must be 256 bytes long. Color mode only.
--green-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the green channel. The table must be 256 bytes long.
+ Can be used to download a user defined gamma table for the green
+ channel. The table must be 256 bytes long. Color mode only.
--blue-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the blue channel. The table must be 256 bytes long.
+ Can be used to download a user defined gamma table for the blue
+ channel. The table must be 256 bytes long. Color mode only.
- --dither
- (Black & White only) select the dither mask to use. Possible
- values are Line art , 2x2 , 3x3 , 4x4 bayer , 4x4 smooth , 8x8
- bayer , 8x8 smooth , 8x8 horizontal and 8x8 vertical
+ --dither Line art|2x2|3x3|4x4 bayer|4x4 smooth|8x8 bayer|8x8 smooth|8x8
+ horizontal|8x8 vertical
+ Select the dither mask to use. Black & White only.
--preview
- requests a preview scan. The resolution used for that scan is 22
- dpi and the scan area is the maximum allowed. The scan mode is
- user selected. The default is "no".
+ Requests a preview scan. The resolution used is 22 dpi and the
+ scan area is the maximum allowed. The scan mode is user se-
+ lected. The default is "no".
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/teco1.conf supports only
- one information: the device name to use (eg /dev/scanner).
+ The configuration file /usr/local/etc/sane.d/teco1.conf supports only
+ one item: the device name to use (eg /dev/scanner).
@@ -132,16 +133,16 @@
ENVIRONMENT
SANE_DEBUG_TECO1
- 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.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
LIMITATIONS
- The windows TWAIN driver has many more options than this SANE backend.
- However they are only software adjustments. This backend only imple-
+ The windows TWAIN driver has many more options than this SANE backend.
+ However they are only software adjustments. This backend only imple-
ments what the scanner can support.
@@ -163,7 +164,7 @@
CREDITS
- Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
+ Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves
Simon for the VM3510 support.
14 Jul 2008 sane-teco1(5)
diff --git a/man/sane-teco2.5.html b/man/sane-teco2.5.html
index 07593694..6707e763 100644
--- a/man/sane-teco2.5.html
+++ b/man/sane-teco2.5.html
@@ -2,7 +2,7 @@
sane-teco2.5
-
+
sane-teco2.5
@@ -25,20 +25,20 @@
The scanners that should work with this backend are:
- Vendor Model TECO model status
- ---------------------- -------------- -----------
- Mustek ScanMagic 4830S VM3575 untested
- Primax Jewel 4800 VM356A good
- Primax Profi 9600 VM6575 basic
- Primax Profi 19200 VM6586 good
- Relisys APOLLO Express 3 VM356A basic
- Relisys APOLLO Express 6 VM6565 good
- Relisys APOLLO Express 12 ? untested
- Relisys AVEC II S3 VM3564 good
- Relisys AVEC Super 3 VM3575 basic
- Relisys SCORPIO Pro VM6575 good
- Relisys SCORPIO Pro-S VM6586 untested
- Relisys SCORPIO Super 3 VM3575 good
+ Vendor Model TECO model status
+ --------------------------- -------------- -----------
+ Mustek ScanMagic 4830S VM3575 untested
+ Primax Jewel 4800 VM356A good
+ Primax Profi 9600 VM6575 basic
+ Primax Profi 19200 VM6586 good
+ Relisys APOLLO Express 3 VM356A basic
+ Relisys APOLLO Express 6 VM6565 good
+ Relisys APOLLO Express 12 ? untested
+ Relisys AVEC II S3 VM3564 good
+ Relisys AVEC Super 3 VM3575 basic
+ Relisys SCORPIO Pro VM6575 good
+ Relisys SCORPIO Pro-S VM6586 untested
+ Relisys SCORPIO Super 3 VM3575 good
For all these scanners, lineart and gray mode work well. However, most
of them do not support more than a handful of resolutions in color
@@ -52,80 +52,40 @@
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
- xscanimage, xsane, quiteinsane or kooka.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1), xsane(1), quiteinsane(1) or kooka(1).
- If you have any success with a scanner not listed here, or if you have
- any strange behavior, please report to the backend maintainer or to the
- SANE mailing list.
+ If you have any success with a scanner not listed here, or if you no-
+ tice any strange behavior, please report to the backend maintainer or
+ to the SANE mailing list.
+
+
+
+OPTIONS
+ Valid command line options and their syntax can be listed by using:
- Valid command line options and their syntax can be listed by using
scanimage --help -d teco2
Scan Mode
- --mode selects the basic mode of operation of the scanner valid choices
- are Lineart , Gray and Color The Lineart mode is black and white
- only (1 bit). Gray mode will produce 256 levels of gray (8
- bits). Color will produce a 24 bits color image.
+ --mode Lineart|Gray|Color
+ selects the basic mode of operation of the scanner. The Lineart
+ mode is black and white only (1 bit). Gray mode will produce
+ 256 levels of gray (8 bits). Color will produce a 24 bits color
+ image.
- --resolution
- Lineart and Gray selects the resolution for a scan. The scanner
- can do all resolutions between 1 and 600, in increments of 1.
- Color selects the resolution for a scan. The scanner can do only
- the resolutions listed.
+ --resolution 1..600
+ Selects the resolution for a scan. The scanner can do all reso-
+ lutions between 1 and 600, in increments of 1, for Lineart and
+ Gray. For Color, a restricted set of resolutions are available.
- All values with ydpi > 300 (300 x 600) or 600 (600 x 1200)
+ Note: 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 -geome-
- try (dpi/max_xdpi * 100%)x100% max_xdpi is for the vm3575 con-
- stant with 300 dpi e.g. 600dpi adjust with: convert -geometry
- 200%x100%
-
- Geometry options
-
- -l -t -x -y
- control the scan area: -l sets the top left x coordinate, -t the
- top left y coordinate, -x selects the width and -y the height of
- the scan area. All parameters are specified in millimeters by
- default.
-
- Enhancement options
-
- --custom-gamma (no custom gamma option for the VM3564 and VM356A)
- (color mode only) allows the user to specify a gamma table (see
- the next 3 parameters).
-
- --red-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the red channel. The table must be 256 bytes long.
-
- --green-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the green channel. The table must be 256 bytes long.
-
- --blue-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the blue channel. The table must be 256 bytes long.
-
- --white-level-r
- (VM3564, VM356A, VM3575 and VM6575 only) Selects what red radi-
- ance level should be considered "white", when scanning some
- sheets by changing the calibration value loaded into the scan-
- ner. Scale 0..64 in steps of 1.
-
- --white-level-g
- (VM3564, VM356A, VM3575 and VM6575 only) Selects what green
- radiance level should be considered "white", when scanning some
- sheets by changing the calibration i value loaded into the scan-
- ner. Scale 0..64 in steps of 1.
-
- --white-level-b
- (VM3564, VM356A, VM3575 and VM6575 only) Selects what blue radi-
- ance level should be considered "white", when scanning some
- sheets by changing the calibration value loaded into the scan-
- ner. Scale 0..64 in steps of 1.
+ adjusted with the following imagemagick command:
+ convert -geometry (dpi/max_xdpi * 100%)x100%
+ max_xdpi is for the vm3575 constant with 300 dpi e.g. 600dpi ad-
+ just with: convert -geometry 200%x100%
--preview
requests a preview scan. The resolution used for that scan is 50
@@ -133,11 +93,63 @@
imum allowed. The scan mode is user selected. The default is
"no".
+ Geometry options
+
+ -l, -t, -x, -y
+ Control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
+ default.
+
+ Enhancement options
+
+ --custom-gamma (no custom gamma option for the VM3564 and VM356A)
+ (color mode only) allows the user to specify a gamma table (see
+ the next 3 parameters).
+
+
+
+OPTIONS FOR COLOR MODE
+ These options are valid for scan mode Color only.
+
+ --red-gamma-table
+ Can be used to download a user defined gamma table for the red
+ channel. The table must be 256 bytes long.
+
+ --green-gamma-table
+ Can be used to download a user defined gamma table for the green
+ channel. The table must be 256 bytes long.
+
+ --blue-gamma-table
+ Can be used to download a user defined gamma table for the blue
+ channel. The table must be 256 bytes long.
+
+
+
+OPTIONS ONLY FOR VM3564, VM356A, VM3575 and VM6575
+ These options are only available for VM3564, VM356A, VM3575 and VM6575
+ models.
+
+ --white-level-r 0..64
+ Selects what red radiance level should be considered "white",
+ when scanning some sheets by changing the calibration value
+ loaded into the scanner. Scale 0..64 in steps of 1.
+
+ --white-level-g 0..64
+ Selects what green radiance level should be considered "white",
+ when scanning some sheets by changing the calibration i value
+ loaded into the scanner. Scale 0..64 in steps of 1.
+
+ --white-level-b 0..64
+ Selects what blue radiance level should be considered "white",
+ when scanning some sheets by changing the calibration value
+ loaded into the scanner. Scale 0..64 in steps of 1.
+
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/teco2.conf supports only
- one information: the device name to use (eg /dev/scanner).
+ The configuration file /usr/local/etc/sane.d/teco2.conf supports only
+ one item: the device name to use (eg /dev/scanner).
@@ -153,8 +165,8 @@
ENVIRONMENT
SANE_DEBUG_TECO2
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -179,7 +191,7 @@
SEE ALSO
- sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+ sane(7), sane-scsi(5), scanimage(1), xscanimage(1), xsane(1)
@@ -191,7 +203,6 @@
http://gkall.hobby.nl/teco2.html
-
CREDITS
Thanks to:
diff --git a/man/sane-teco3.5.html b/man/sane-teco3.5.html
index e369ffc5..9d0714b7 100644
--- a/man/sane-teco3.5.html
+++ b/man/sane-teco3.5.html
@@ -2,7 +2,7 @@
sane-teco3.5
-
+
sane-teco3.5
@@ -38,63 +38,70 @@
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
- xscanimage or xsane.
+ line options to programs like scanimage(1) or through GUI elements in
+ xscanimage(1) or xsane(1).
- If you have any success with a scanner not listed here, or if you have
- any strange behavior, please report to the backend maintainer or to the
- SANE mailing list.
+ If you have any success with a scanner not listed here, or if you no-
+ tice any strange behavior, please report to the backend maintainer or
+ to the SANE mailing list.
+
+
+
+OPTIONS
+ Valid command line options and their syntax can be listed by using:
- Valid command line options and their syntax can be listed by using
scanimage --help -d teco3
Scan Mode
- --mode selects the basic mode of operation of the scanner valid choices
- are Black & White , Grayscale and Color The Black & White mode
- is black and white only (1 bit). Grayscale will produce 256 lev-
- els of gray (8 bits). Color will produce a 24 bits color image.
+ --mode Black & White|Grayscale|Color
+ Selects the basic mode of operation of the scanner. The Black &
+ White mode is black and white only (1 bit). Grayscale will pro-
+ duce 256 levels of gray (8 bits). Color will produce a 24-bit
+ color image.
- --resolution
- selects the resolution for a scan. The scanner can do all reso-
+ --resolution 1..1200
+ Selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 1200, in increments of 1.
+ --preview
+ Requests a preview scan. The resolution used for that scan is 22
+ dpi and the scan area is the maximum allowed. The scan mode is
+ user selected. The default is "no".
+
Geometry options
+
-l -t -x -y
- control the scan area: -l sets the top left x coordinate, -t the
- top left y coordinate, -x selects the width and -y the height of
- the scan area. All parameters are specified in millimeters by
+ Control the scan area: -l sets the top left x coordinate, -t the
+ top left y coordinate, -x selects the width and -y the height of
+ the scan area. All parameters are specified in millimeters by
default.
- Enhancement options
+
+OPTIONS FOR COLOR MODE ONLY
--custom-gamma
- (color mode only) allows the user to specify a gamma table (see
- the next 3 parameters).
+ Allows the user to specify a gamma table (see the next 3 parame-
+ ters).
--red-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the red channel. The table must be 1024 bytes long.
+ Can be used to download a user defined gamma table for the red
+ channel. The table must be 1024 bytes long.
--green-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the green channel. The table must be 1024 bytes long.
+ Can be used to download a user defined gamma table for the green
+ channel. The table must be 1024 bytes long.
--blue-gamma-table
- (color mode only) can be used to download a user defined gamma
- table for the blue channel. The table must be 1024 bytes long.
-
- --preview
- requests a preview scan. The resolution used for that scan is 22
- dpi and the scan area is the maximum allowed. The scan mode is
- user selected. The default is "no".
+ Can be used to download a user defined gamma table for the blue
+ channel. The table must be 1024 bytes long.
CONFIGURATION FILE
- The configuration file /usr/local/etc/sane.d/teco3.conf supports only
- one information: the device name to use (eg /dev/scanner).
+ The configuration file /usr/local/etc/sane.d/teco3.conf supports only
+ one item: the device name to use (eg /dev/scanner).
@@ -110,8 +117,8 @@
ENVIRONMENT
SANE_DEBUG_TECO3
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
diff --git a/man/sane-test.5.html b/man/sane-test.5.html
index c0755987..ed166223 100644
--- a/man/sane-test.5.html
+++ b/man/sane-test.5.html
@@ -2,7 +2,7 @@
sane-test.5
-
+
sane-test.5
@@ -23,13 +23,13 @@
There is no support for real scanners or cameras. However, the backend
simulates scanning and setting options.
- The idea is not only to find bugs in frontends but also to show all
- capabilities of SANE. Therefore sane-test implements functions and
- options that are not (or seldom) found in other backends.
+ The idea is not only to find bugs in frontends but also to show all ca-
+ pabilities of SANE. Therefore sane-test implements functions and op-
+ tions that are not (or seldom) found in other backends.
- The backend is commented out in /usr/local/etc/sane.d/dll.conf, so
- either the comment character must be removed or the backend must be
- called explicitly. E.g. `scanimage -d test' or `xscanimage test'.
+ The backend is commented out in /usr/local/etc/sane.d/dll.conf, so ei-
+ ther the comment character must be removed or the backend must be
+ called explicitly. E.g. scanimage -d test or xscanimage test.
@@ -74,7 +74,7 @@
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.
+ http://www.meier-geinitz.de/sane/test-backend/test-pictures.html.
If option invert-endianness is set, the upper and lower bytes of image
data in 16 bit modes are exchanged. This option can be used to test
@@ -82,7 +82,7 @@
endianness.
If option read-limit is set, the maximum amount of data transferred
- with each call to sane_read() is limited.
+ with each call to sane_read() is limited.
Option read-limit-size sets the limit for option read-limit. A low
limit slows down scanning. It can be used to detect errors in frontend
@@ -96,23 +96,23 @@
find timing-related bugs, especially if used over the network.
If option read-return-value is different from "Default", the selected
- status will be returned by every call to sane_read(). This is useful
+ status will be returned by every call to sane_read(). This is useful
to test the frontend's handling of the SANE statuses.
If option ppl-loss is different from 0, it determines the number of
pixels that are "lost" at the end of each line. That means, lines are
padded with unused data.
- Option fuzzy-parameters selects that fuzzy (inexact) parameters are
- returned as long as the scan hasn't been started. This option can be
+ Option fuzzy-parameters selects that fuzzy (inexact) parameters are re-
+ turned as long as the scan hasn't been started. This option can be
used to test if the frontend uses the parameters it got before the
start of the scan (which it shouldn't).
- Option non-blocking determines if non-blocking IO for sane_read()
+ Option non-blocking determines if non-blocking IO for sane_read()
should be used if supported by the frontend.
If option select-fd is set, the backend offers a select filedescriptor
- for detecting if sane_read() will return data.
+ for detecting if sane_read() will return data.
If option enable-test-options is set, a fairly big list of options for
testing the various SANE option types is enabled.
@@ -148,21 +148,20 @@
means the option can't be set by the frontend but by the user (e.g. by
pressing a button at the device).
- Option bool-hard-select (3/6) is a bool test option that has hard
- select (and advanced) capabilities. That means the option can't be set
- by the frontend but by the user (e.g. by pressing a button at the
- device) and can't be read by the frontend.
+ Option bool-hard-select (3/6) is a bool test option that has hard se-
+ lect (and advanced) capabilities. That means the option can't be set
+ by the frontend but by the user (e.g. by pressing a button at the de-
+ vice) and can't be read by the frontend.
- Option bool-soft-detect (4/6) is a bool test option that has soft
- detect (and advanced) capabilities. That means the option is read-
- only.
+ Option bool-soft-detect (4/6) is a bool test option that has soft de-
+ tect (and advanced) capabilities. That means the option is read-only.
- Option bool-soft-select-soft-detect-emulated (5/6) is a Bool test
- option that has soft select, soft detect, and emulated (and advanced)
- capabilities.
+ Option bool-soft-select-soft-detect-emulated (5/6) is a Bool test op-
+ tion that has soft select, soft detect, and emulated (and advanced) ca-
+ pabilities.
- Option bool-soft-select-soft-detect-auto (6/6) is a Bool test option
- that has soft select, soft detect, and automatic (and advanced) capa-
+ Option bool-soft-select-soft-detect-auto (6/6) is a Bool test option
+ that has soft select, soft detect, and automatic (and advanced) capa-
bilities. This option can be automatically set by the backend.
@@ -170,23 +169,23 @@
INT TEST OPTIONS
There are 6 int test options in total.
- Option int (1/6) is an int test option with no unit and no constraint
+ Option int (1/6) is an int test option with no unit and no constraint
set.
Option int-constraint-range (2/6) is an int test option with unit pixel
and constraint range set. Minimum is 4, maximum 192, and quant is 2.
- Option int-constraint-word-list (3/6) is an int test option with unit
+ Option int-constraint-word-list (3/6) is an int test option with unit
bits and constraint word list set.
- Option int-constraint-array (4/6) is an int test option with unit mm
+ Option int-constraint-array (4/6) is an int test option with unit mm
and using an array without constraints.
- Option int-constraint-array-constraint-range (5/6) is an int test
- option with unit mm and using an array with a range constraint. Mini-
- mum is 4, maximum 192, and quant is 2.
+ Option int-constraint-array-constraint-range (5/6) is an int test op-
+ tion with unit mm and using an array with a range constraint. Minimum
+ is 4, maximum 192, and quant is 2.
- Option int-constraint-array-constraint-word-list (6/6) is an int test
+ Option int-constraint-array-constraint-word-list (6/6) is an int test
option with unit percent and using an array a word list constraint.
@@ -194,14 +193,14 @@
FIXED TEST OPTIONS
There are 3 fixed test options in total.
- Option fixed (1/3) is a fixed test option with no unit and no con-
+ Option fixed (1/3) is a fixed test option with no unit and no con-
straint set.
- Option fixed-constraint-range (2/3) is a fixed test option with unit
- microsecond and constraint range set. Minimum is -42.17, maximum
+ Option fixed-constraint-range (2/3) is a fixed test option with unit
+ microsecond and constraint range set. Minimum is -42.17, maximum
32767.9999, and quant is 2.0.
- Option fixed-constraint-word-list (3/3) is a Fixed test option with no
+ Option fixed-constraint-word-list (3/3) is a Fixed test option with no
unit and constraint word list set.
@@ -226,15 +225,15 @@
FILES
/usr/local/etc/sane.d/test.conf
- The backend configuration file (see also description of
- SANE_CONFIG_DIR below). The initial values of most of the basic
+ The backend configuration file (see also description of
+ SANE_CONFIG_DIR below). The initial values of most of the basic
SANE options can be configured in this file. A template contain-
- ing all the default values is provided together with this back-
- end. One of the more interesting values may be num-
- ber_of_devices. It can be used to check the frontend's ability
- to show a long list of devices. The config values concerning
- resolution and geometry can be useful to test the handling of
- big file sizes.
+ ing all the default values is provided together with this back-
+ end. One of the more interesting values may be number_of_de-
+ vices. It can be used to check the frontend's ability to show a
+ long list of devices. The config values concerning resolution
+ and geometry can be useful to test the handling of big file
+ sizes.
/usr/local/lib/sane/libsane-test.a
The static library implementing this backend.
@@ -249,20 +248,20 @@
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
+ are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
- uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ uration file is searched in two default directories: first, the
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_TEST
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_TEST=4
@@ -270,12 +269,13 @@
SEE ALSO
- sane(7), http://www.meier-geinitz.de/sane/test-backend/
+ sane(7), scanimage(1), xscanimage(1)
+ http://www.meier-geinitz.de/sane/test-backend/
AUTHOR
- Henning Meier-Geinitz <henning@meier-geinitz.de>
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
diff --git a/man/sane-u12.5.html b/man/sane-u12.5.html
index 7157e4d0..ad18c8e2 100644
--- a/man/sane-u12.5.html
+++ b/man/sane-u12.5.html
@@ -2,7 +2,7 @@
sane-u12.5
-
+
sane-u12.5
@@ -26,9 +26,9 @@
SUPPORTED DEVICES
- The backend is able to support some early Plustek USB scanner based
- their old parport design around the ASIC 98003 and other rebadged Plus-
- tek devices. The following tables will give you a short overview.
+ The backend is able to support some early Plustek USB scanners that
+ based their old parport design around the ASIC 98003 and other rebadged
+ Plustek devices. The following tables will give you a short overview.
If your Plustek scanner has another Product ID, then the device is NOT
supported by this backend.
@@ -53,6 +53,7 @@
CONFIGURATION
To use your scanner with this backend, you need at least two entries in
the configuration file /usr/local/etc/sane.d/u12.conf
+
[usb] vendor-id product-id
device /dev/usbscanner
@@ -75,13 +76,12 @@
b specifies the behaviour when closing the backend, 1 --> switch
lamps off, 0 --> do not change lamp status
- See the u12.conf file for examples.
+ See the u12.conf file for examples.
- Note:
- You have to make sure, that the USB subsystem is loaded correctly and
- you have access to the device-node. For more details see sane-usb (5)
- manpage. You might use sane-find-scanner to check that you have access
- to your device.
+ Note: You have to make sure, that the USB subsystem is loaded correctly
+ and you have access to the device-node. For more details see
+ sane-usb(5) manpage. You might use sane-find-scanner(1) to check that
+ you have access to your device.
Note:
If there's no configuration file, the backend defaults to device auto
@@ -108,17 +108,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_U12
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
Higher debug levels increase the verbosity of the output.
Example: export SANE_DEBUG_U12=10
@@ -126,7 +126,8 @@
SEE ALSO
- sane(7), sane-usb(5), sane-plustek(5),
+ sane(7), sane-usb(5), sane-plustek(5), sane-find-scanner(1), xscanim-
+ age(1), scanimage(1)
/usr/local/share/doc/sane-backends/u12/U12.changes
@@ -137,12 +138,13 @@
Additional info and hints can be obtained from our
Mailing-List archive at:
- http://www.sane-project.org/mailing-lists.html
+ http://www.sane-project.org/mailing-lists.html
- To obtain debug messages from the backend, please set the environment-
- variable SANE_DEBUG_U12 before calling your favorite scan-frontend
- (i.e. xscanimage).
- i.e.: export SANE_DEBUG_U12=20 ; xscanimage
+ To obtain debug messages from the backend, please set the environment-
+ variable SANE_DEBUG_U12 before calling your favorite scan-frontend
+ (i.e. xscanimage(1)), i.e.:
+
+ export SANE_DEBUG_U12=20 ; xscanimage
The value controls the verbosity of the backend.
@@ -151,7 +153,7 @@
KNOWN BUGS & RESTRICTIONS
* The driver is in alpha state, so please don't expect too much!!!
- * When using libusb, it might be, that the backend hangs. In that
+ * When using libusb, it might be, that the backend hangs. In that
case, reconnect the scanner.
14 Jul 2008 sane-u12(5)
diff --git a/man/sane-umax.5.html b/man/sane-umax.5.html
index 8b5d16a9..067d957d 100644
--- a/man/sane-umax.5.html
+++ b/man/sane-umax.5.html
@@ -2,7 +2,7 @@
sane-umax.5
-
+
sane-umax.5
@@ -17,9 +17,9 @@
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 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 xsane(1) online help)!
@@ -34,8 +34,8 @@
CONFIGURATION
- The configuration file for this backend resides in
- /usr/local/etc/sane.d/umax.conf.
+ The configuration file for this backend resides in /usr/lo-
+ cal/etc/sane.d/umax.conf.
Its contents is a list of device names that correspond to UMAX and UMAX
compatible scanners. Empty lines and lines starting with a hash mark
@@ -81,17 +81,16 @@
default min = 32768, max = 131072
Especially the minimum value is very important. If this value
is set too small the backend is not 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
+ the scanner or to do a correct color calibration. This may re-
+ sult 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 out of memory error. The
- default is 32KB, for some scanners it should be increased to
- 64KB.
+ SCSI buffer size and aborts with out of memory error. The de-
+ fault is 32KB, for some scanners it should be increased to 64KB.
scan-lines, preview-lines:
values: 1-65535
default: scan-lines = 40, preview-lines = 10
- define the maximum number of lines that are scanned into one
+ define the maximum number of lines that are scanned into one
buffer
force-preview-bit-rgb:
@@ -103,7 +102,7 @@
values: -1 = auto, 0 = disabled, 1 = enabled
default = -1
dangerous options, needed for some scanners do not changed these
- options until you really know what you do, you may destroy your
+ options until you really know what you do, you may destroy your
scanner when you define wrong values for this options
calibration-full-ccd:
@@ -116,67 +115,67 @@
add an offset width to the calculated with for image/ccd
calibration-bytes-pixel:
- values: -1 = disabled, 0 = not set, 1 = 1 byte/pixel, 2 = 2
+ values: -1 = disabled, 0 = not set, 1 = 1 byte/pixel, 2 = 2
bytes/pixel
use # bytes per pixel for calibration
exposure-time-rgb-bind:
- values: -1 = automatically set by driver - if known, 0 = dis-
+ values: -1 = automatically set by driver - if known, 0 = dis-
abled (own selection for red, green and blue), 1 = enabled (same
values for red, green and blue)
invert-shading-data:
- values: -1 = automatically set by driver - if known, 0 = dis-
+ values: -1 = automatically set by driver - if known, 0 = dis-
abled, 1 = enabled
default = -1
invert shading data before sending it back to the scanner
lamp-control-available:
- values: 0 = automatically set by driver - if known, 1 = avail-
+ values: 0 = automatically set by driver - if known, 1 = avail-
able
default = 0
gamma-lsb-padded:
- values: -1 = automatically set by driver - if known, 0 = gamma
+ values: -1 = automatically set by driver - if known, 0 = gamma
data is msb padded, 1 = gamma data is lsb padded
default = -1
handle-bad-sense-error:
- values: 0 = handle as device busy, 1 = handle as ok, 2 = handle
+ values: 0 = handle as device busy, 1 = handle as ok, 2 = handle
as i/o error, 3 = ignore bad error code - continue sense handler
default = 0
scsi-maxqueue:
values: 1..# (maximum defined at compile time)
default = 2
- 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
+ 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 command queueing you can try to set this value to 1.
- 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.
+ 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(5).
SCSI ADAPTER TIPS
- The ISA-SCSI-adapters that are shipped with some Umax-scanners are not
- supported very well by Linux (I suggest not to use it), the PCI-SCSI-
+ The ISA-SCSI-adapters that are shipped with some Umax-scanners are not
+ supported very well by Linux (I suggest not to use it), the PCI-SCSI-
adapters that come with some Umax-scanners are not supported at all (as
- far as I know). On other platforms these SCSI-adapters are not sup-
- ported. So you typically need to purchase another SCSI-adapter that is
- supported by your platform. See the relevant hardware FAQs and HOWTOs
+ far as I know). On other platforms these SCSI-adapters are not sup-
+ ported. So you typically need to purchase another SCSI-adapter 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 scan-
- ning. 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 sug-
+ The UMAX-scanners do block the SCSI-bus for a few seconds while scan-
+ ning. 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 sug-
gest 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: sane-scsi(5)
@@ -198,10 +197,10 @@
ENVIRONMENT
SANE_DEBUG_UMAX
- 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_UMAX values
+ If the library was compiled with debug support enabled, this en-
+ vironment 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_UMAX values.
Number Remark
0 print important errors (printed each time)
@@ -224,12 +223,12 @@
BUGS
- X-resolutions greater than 600 dpi sometimes make problems
+ X-resolutions greater than 600 dpi sometimes cause problems.
SEE ALSO
- sane(7)
+ sane(7), sane-scsi(5)
@@ -239,7 +238,7 @@
EMAIL-CONTACT
- Oliver.Rauch@Rauch-Domain.DE
+ Oliver.Rauch@Rauch-Domain.DE
14 Jul 2008 sane-umax(5)
diff --git a/man/sane-umax1220u.5.html b/man/sane-umax1220u.5.html
index 05f6b91d..1853143a 100644
--- a/man/sane-umax1220u.5.html
+++ b/man/sane-umax1220u.5.html
@@ -2,7 +2,7 @@
sane-umax1220u.5
-
+
sane-umax1220u.5
@@ -30,7 +30,7 @@
This backend is also able to drive the UMAX Astra 1600U/2000U/2100U.
The 2100U is confirmed to work. For the other scanners no reports have
been received yet. Please contact us and tell us if your scanner works
- (sane-devel@alioth-lists.debian.net).
+ (sane-devel@alioth-lists.debian.net).
@@ -38,9 +38,9 @@
Usually, no manual configuration is necessary. The configuration file
for this backend resides in /usr/local/etc/sane.d/umax1220u.conf.
- Its contents is a list of device names that correspond to UMAX Astra
- scanners. Empty lines and lines starting with a hash mark (#) are
- ignored. A sample configuration file is shown below:
+ Its content is a list of device names that correspond to UMAX Astra
+ scanners. Empty lines and lines starting with a hash mark (#) are ig-
+ nored. A sample configuration file is shown below:
#usb vendor product
usb 0x1606 0x0010
@@ -68,12 +68,12 @@
ENVIRONMENT
SANE_DEBUG_UMAX1220U
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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_UMAX1220U values
+ SANE_DEBUG_UMAX1220U values:
Number Remark
1 print failures
@@ -96,12 +96,12 @@
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 sane_can-
- cel().
+ There is no way to cancel a scan, since the driver ignores sane_can-
+ cel().
- If you try scanning an image which is too small, you will get I/O
- errors. Be sure to adjust the scan area before doing a scan, since by
- default, the scan area is zero.
+ If you try scanning an image which is too small, you will get I/O er-
+ rors. Be sure to adjust the scan area before doing a scan, since by de-
+ fault, the scan area is zero.
@@ -114,19 +114,19 @@
AUTHOR
- Marcio Luis Teixeira <marciot@users.sourceforge.net>
+ Marcio Luis Teixeira <marciot@users.sourceforge.net>
EMAIL-CONTACT
- sane-devel@alioth-lists.debian.net
+ sane-devel@alioth-lists.debian.net
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 SANE_DEBUG_UMAX1220U set to 10 and
+ bugs, please run the backend with SANE_DEBUG_UMAX1220U set to 10 and
attach a copy of the log messages.
14 Jul 2008 sane-umax1220u(5)
diff --git a/man/sane-umax_pp.5.html b/man/sane-umax_pp.5.html
index 96c374c5..10edea91 100644
--- a/man/sane-umax_pp.5.html
+++ b/man/sane-umax_pp.5.html
@@ -2,7 +2,7 @@
sane-umax_pp.5
-
+
sane-umax_pp.5
@@ -39,8 +39,8 @@
The new generation models share a newer version of the 610P ASIC embed-
ded in an EPAT chip. Only parts such as CCD and ADC change from one to
another. They even all reports being UMAX Astra 1220P via IEEE1284.
- There isn't software way to recognize them properly. Under windows,
- model is set by the driver installed, regardless of the hardware.
+ There isn't a software method to recognize them properly. Under win-
+ dows, model is set by the driver installed, regardless of the hardware.
EPP/ECP MODES ONLY
The current version of the backend uses only EPP or ECP mode to
@@ -58,8 +58,8 @@
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 back-
end through the network interface (See saned(8) and sane-net(5)). A
- more relaxed solution (security wise) is to add suid bit to the fron-
- tend (See chmod(1)). The backend drop root privileges as soon as it
+ more relaxed solution (security wise) is to add suid bit to the front-
+ end (See 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.
@@ -78,25 +78,25 @@
autodetect all parallel ports and probe them for scanner,
but does not try direct hardware access
- /dev/ppi0
+ /dev/ppi0
uses *BSD ppi device, depending on the number of avail-
- able parallel port, you have to use /dev/ppi1, /dev/ppi2,
+ able parallel port, you have to use /dev/ppi1, /dev/ppi2,
...
- /dev/parport0
- uses linux ppdev device, depending on the number of
- available parallel port, you have to use /dev/parport1,
- /dev/parport2, ...
+ /dev/parport0
+ uses Linux ppdev device, depending on the number of
+ available parallel port, you have to use /dev/parport1,
+ /dev/parport2, ...
0x378 does direct hardware access on the given address. Usual
values are 0x378, 0x278, 0x3BC In this case, you have to
- run the scanner as root (*BSD and linux), or with
+ run the scanner as root (*BSD and Linux), or with
'IOPL=yes' on OS/2
NOTE: 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 permis-
- sions on the dev/ppi* or /dev/parport* devices.
+ sions on the /dev/ppi* or /dev/parport* devices.
You can rename any device using the
@@ -109,20 +109,20 @@
CONFIGURATION
- Please make sure to edit umax_pp.conf before you use the backend.
+ Please make sure to edit umax_pp.conf before you use the backend.
- The contents of the umax_pp.conf file is a list of options and device
+ The contents of the umax_pp.conf file is a list of options and device
names that correspond to Umax scanners. Empty lines and lines starting
with a hash mark (#) are ignored.
The eight options supported are red-gain, green-gain, blue-gain,
red-offset, green-offset, blue-offset, astra, and buffer.
- Options red-gain , green-gain and blue-gain allow you to adjust the
- sensitivity of your scanner for the given color. Values range from 0
- (lowest gain) to 15 (highest). If the advanced option "Gain" isn't
- checked in the frontend, the backend does automatic gain calibration,
- and do not use user provided values.
+ Options red-gain, green-gain and blue-gain allow you to adjust the sen-
+ sitivity of your scanner for the given color. Values range from 0 (low-
+ est gain) to 15 (highest). If the advanced option "Gain" isn't checked
+ in the frontend, the backend does automatic gain calibration, and do
+ not use user provided values.
Options red-offset , green-offset and blue-offset allow you to adjust
the offset of your scanner for the given color. Values range from 0
@@ -139,9 +139,9 @@
aware that it will prevent scanner model autodetection.
Option buffer allows you to change the size of the scan buffer. The
- size must be specified in bytes. The default value is 2 megabytes.
- Decreasing this value will improve the smoothness of progress bar in
- the frontend, but will stall the scan more often.
+ size must be specified in bytes. The default value is 2 megabytes. De-
+ creasing this value will improve the smoothness of progress bar in the
+ frontend, but will stall the scan more often.
@@ -166,17 +166,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_UMAX_PP
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -216,7 +216,7 @@
AUTHOR
- Stephane Voltz <stef.dev@free.fr>
+ Stephane Voltz <stef.dev@free.fr>
@@ -231,23 +231,24 @@
tion about your scanner to be able to help you...
SANE version
- run "scanimage -V" to determine this
+ Run scanimage -V to determine this
the backend version and your scanner hardware
- run "SANE_DEBUG_UMAX_PP=255 scanimage -L 2>log" as root. If you
- don't get any output from the umax_pp backend, make sure a line
- "umax_pp" is included into your /usr/local/etc/sane.d/dll.conf.
- If your scanner isn't detected, make sure you've defined the
- right port address, or the correct device in your umax_pp.conf.
+ Run SANE_DEBUG_UMAX_PP=255 scanimage -L 2>log as root. If you
+ don't get any output from the sane-umax_pp backend, make sure a
+ line "umax_pp" is included into your /usr/lo-
+ cal/etc/sane.d/dll.conf file. If your scanner isn't detected,
+ make sure you've defined the right port address, or the correct
+ device in your umax_pp.conf file.
the name of your scanner/vendor
also a worthy information. Please also include the optical reso-
- lution and lamp type of your scanner, both can be found in the
+ lution and lamp type of your scanner, both can be found in the
manual of your scanner.
any further comments
if you have comments about the documentation (what could be done
- better), or you think I should know something, please include
+ better), or you think I should know something, please include
it.
14 Jul 2008 sane-umax_pp(5)
diff --git a/man/sane-usb.5.html b/man/sane-usb.5.html
index 5f2085f1..ddad7e47 100644
--- a/man/sane-usb.5.html
+++ b/man/sane-usb.5.html
@@ -2,7 +2,7 @@
sane-usb.5
-
+
sane-usb.5
@@ -18,134 +18,135 @@
DESCRIPTION
This manual page contains information on how to access scanners with a
- USB interface. It focusses on two main topics: getting the scanner
- detected by the operating system kernel and using it with SANE.
+ USB interface. It focuses on two main topics: getting the scanner de-
+ tected by the operating system kernel and using it with SANE.
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 sane-microtek2(5) for details.
+ generic sanei_usb interface. However, there is one exception: USB Scan-
+ ners supported by the sane-microtek2(5) backend need a special USB ker-
+ nel driver.
QUICK START
This is a short HOWTO-like section. For the full details, read the fol-
- lowing sections. The goal of this section is to get the scanner
- detected by sane-find-scanner(1).
+ lowing sections. The goal of this section is to get the scanner de-
+ tected by sane-find-scanner(1).
- Run sane-find-scanner. If it lists your scanner with the correct vendor
- and product ids, you are done. See section SANE ISSUES for details on
- how to go on.
+ Run sane-find-scanner(1). If it lists your scanner with the correct
+ vendor and product ids, you are done. See section SANE ISSUES for de-
+ tails on how to go on.
- sane-find-scanner doesn't list your scanner? Does it work as root? If
- yes, there is a permission issue. See the LIBUSB section for details.
+ sane-find-scanner(1) doesn't list your scanner? Does it work as root?
+ If yes, there is a permission issue. See the LIBUSB section for de-
+ tails.
- Nothing is found even as root? Check that your kernel supports USB and
+ Nothing is found even as root? Check that your kernel supports USB and
that libusb is installed (see section LIBUSB).
USB ACCESS METHODS
- For accessing USB devices, the USB library libusb is used. There used
- to exist another method to access USB devices: the kernel scanner
+ For accessing USB devices, the USB library libusb is used. There used
+ to exist another method to access USB devices: the kernel scanner
driver. The kernel scanner driver method is deprecated and shouldn't be
- used anymore. It may be removed from SANE at any time. In Linux, the
+ used anymore. It may be removed from SANE at any time. In Linux, the
kernel scanner driver has been removed in the 2.6.* kernel series. Only
libusb access is documented in this manual page.
LIBUSB
- SANE can only use libusb 0.1.6 or newer. It needs to be installed at
+ SANE can only use libusb 0.1.6 or newer. It needs to be installed at
build-time. Modern Linux distributions and other operating systems come
with libusb.
- Libusb can only access your scanner if it's not claimed by the kernel
- scanner driver. If you want to use libusb, unload the kernel driver
+ Libusb can only access your scanner if it's not claimed by the kernel
+ scanner driver. If you want to use libusb, unload the kernel driver
(e.g. rmmod scanner under Linux) or disable the driver when compiling a
new kernel. For Linux, your kernel needs support for the USB filesystem
(usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs"
- because the name has changed. This filesystem must be mounted. That's
- done automatically at boot time, if /etc/fstab contains a line like
+ because the name has changed. This filesystem must be mounted. That's
+ done automatically at boot time, if /etc/fstab contains a line like
this:
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 Linux,
- the devices are located in /proc/bus/usb/ or in /dev/bus/usb, if you
- use udev. There are directories named e.g. "001" (the bus name) con-
- taining files "001", "002" etc. (the device files). The right device
- files can be found out by running scanimage -L as root. Setting permis-
- sions with "chmod" is not permanent, however. They will be reset after
- reboot or replugging the scanner.
+ The permissions for the device files used by libusb must be adjusted
+ for user access. Otherwise only root can use SANE devices. For Linux,
+ the devices are located in /proc/bus/usb/ or in /dev/bus/usb, if you
+ use udev. There are directories named e.g. "001" (the bus name) con-
+ taining files "001", "002" etc. (the device files). The right device
+ files can be found out by running: scanimage -L: as root. Setting per-
+ missions with chmod(1) is not permanent, however. They will be reset
+ after reboot or replugging the scanner.
- Usually udev 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
- /usr/local/share/doc/sane-backends/README.linux, tools/README and the
- README in the tools/hotplug directory for more details.
+ Usually 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 /usr/lo-
+ cal/share/doc/sane-backends/README.linux, tools/README and the README
+ in the tools/hotplug directory for more details.
- For the BSDs, the device files used by libusb are named /dev/ugen*.
+ For the BSDs, the device files used by libusb are named /dev/ugen*.
Use chmod to apply appropriate permissions.
SANE ISSUES
- This section assumes that your scanner is detected by sane-find-scan-
- ner. It doesn't make sense to go on, if this is not the case. While
- sane-find-scanner is able to detect any USB scanner, actual scanning
- will only work if the scanner is supported by a SANE backend. Informa-
- tion on the level of support can be found on the SANE webpage
+ This section assumes that your scanner is detected by sane-find-scan-
+ ner(1). It doesn't make sense to go on, if this is not the case. While
+ 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. Informa-
+ tion on the level of support can be found on the SANE webpage
(http://www.sane-project.org/), and the individual backend manpages.
Most backends can detect USB scanners automatically using "usb" config-
- uration file lines. This method allows one to identify scanners by the
- USB vendor and product numbers. The syntax for specifying a scanner
+ uration file lines. This method allows one to identify scanners by the
+ USB vendor and product numbers. The syntax for specifying a scanner
this way is:
usb VENDOR PRODUCT
where VENDOR is the USB vendor id, and PRODUCT is the USB product id of
- the scanner. Both ids are non-negative integer numbers in decimal or
+ 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 sane-find-scanner, looking into the syslog (e.g., /var/log/mes-
- sages) or under Linux by issuing the command "cat
- /proc/bus/usb/devices". This is an example of a config file line:
+ running sane-find-scanner(1), looking into the syslog (e.g.,
+ /var/log/messages) or under Linux by issuing the command cat
+ /proc/bus/usb/devices. This is an example of a config file line:
usb 0x055f 0x0006
- would have the effect that all USB devices in the system with a vendor
- id of 0x55f and a product id of 0x0006 would be probed and recognized
+ would have the effect that all USB devices in the system with a vendor
+ id of 0x55f and a product id of 0x0006 would be probed and recognized
by the backend.
- If your scanner is not detected automatically, it may be necessary to
- edit the appropriate backend configuration file before using SANE for
- the first time. For a detailed description of each backend's configu-
- ration file, please refer to the relevant backend manual page (e.g.
+ If your scanner is not detected automatically, it may be necessary to
+ edit the appropriate backend configuration file before using SANE for
+ the first time. For a detailed description of each backend's configu-
+ ration file, please refer to the relevant backend manual page (e.g.
sane-mustek_usb(5) for Mustek USB scanners).
- Do not create a symlink from /dev/scanner to the USB device because
- this link is used by the SCSI backends. The scanner may be confused if
+ Do not create a symlink from /dev/scanner to the USB device because
+ this link is used by the SCSI backends. The scanner may be confused if
it receives SCSI commands.
ENVIRONMENT
SANE_DEBUG_SANEI_USB
- 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
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for the USB I/O sub-
+ system. 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: export
- SANE_DEBUG_SANEI_USB=4.
+ enable libusb debugging (if available). Example: export SANE_DE-
+ BUG_SANEI_USB=4.
SANE_USB_WORKAROUND
If your scanner does not work when plugged into a USB3 port, try
- setting the environment variable SANE_USB_WORKAROUND to 1. This
- may work around issues which happen with particular kernel ver-
- sions. Example: export SANE_USB_WORKAROUND=1.
+ setting the environment variable SANE_USB_WORKAROUND to 1. This
+ may work around issues which happen with particular kernel ver-
+ sions. Example: export SANE_USB_WORKAROUND=1.
@@ -155,7 +156,7 @@
AUTHOR
- Henning Meier-Geinitz <henning@meier-geinitz.de>
+ Henning Meier-Geinitz <henning@meier-geinitz.de>
14 Jul 2008 sane-usb(5)
diff --git a/man/sane-v4l.5.html b/man/sane-v4l.5.html
index 455cc627..084c657f 100644
--- a/man/sane-v4l.5.html
+++ b/man/sane-v4l.5.html
@@ -2,7 +2,7 @@
sane-v4l.5
-
+
sane-v4l.5
@@ -71,17 +71,17 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SANE_DEBUG_V4L
- If the library was compiled with debug support enabled, this
- environment variable controls the debug level for this backend.
+ If the library was compiled with debug support enabled, this en-
+ vironment 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.
@@ -95,14 +95,14 @@
BUGS:
If more than one video card is present, a crash may occur. Frequency
and geometry selection is missing.
- Send bug reports to the SANE mailing list: sane-devel@alioth-
- lists.debian.net. You must be subscribed to the list to send mail. See
- http://www.sane-project.org/mailing-lists.html for details.
+ Send bug reports to the SANE mailing list: sane-devel@alioth-lists.de-
+ bian.net. You must be subscribed to the list to send mail. See
+ http://www.sane-project.org/mailing-lists.html for details.
SEE ALSO
- sane(7), xcam(1).
+ sane(7), xcam(1)
14 Jul 2008 sane-v4l(5)
diff --git a/man/sane-xerox_mfp.5.html b/man/sane-xerox_mfp.5.html
index 639e86a9..17faebd4 100644
--- a/man/sane-xerox_mfp.5.html
+++ b/man/sane-xerox_mfp.5.html
@@ -2,7 +2,7 @@
sane-xerox_mfp.5
-
+
sane-xerox_mfp.5
@@ -25,22 +25,23 @@
CONFIGURATION
- /usr/local/etc/sane.d/xerox_mfp.conf USB scanners do not need any con-
- figuration.
+ /usr/local/etc/sane.d/xerox_mfp.conf
+ USB scanners do not need any configuration.
- For SCX-4500W in network mode you need to specify
+ For SCX-4500W in network mode you need to specify
tcp host_address [port]
- The host_address is passed through resolver, thus can be a dotted quad
- or a name from /etc/hosts or resolvable through DNS.
+ The host_address is passed through resolver, thus can be a dotted quad
+ or a name from /etc/hosts or resolvable through DNS.
FILES
/usr/local/etc/sane.d/xerox_mfp.conf
- The backend configuration file. By default all scanner
- types/models are enabled, you may want to comment out unwanted.
+ The backend configuration file. By default all scanner
+ types/models are enabled, you may want to comment out unwanted
+ entries.
/usr/local/lib/sane/libsane-xerox_mfp.a
The static library implementing this backend.
@@ -52,11 +53,12 @@
ENVIRONMENT
- SANE_DEBUG_XEROX_MFP If the library was compiled with debug support
- enabled, this environment variable controls the debug level for this
- backend. Higher debug levels increase the verbosity of the output.
+ SANE_DEBUG_XEROX_MFP
+ If the library was compiled with debug support enabled, this en-
+ vironment variable controls the debug level for this backend.
+ Higher debug levels increase the verbosity of the output.
- Example: export SANE_DEBUG_XEROX_MFP=4
+ Example: export SANE_DEBUG_XEROX_MFP=4
@@ -68,18 +70,18 @@
BUGS AND SUPPORT
If you have found a bug or need support please follow open-source way
- of acquiring support via mail-lists http://www.sane-project.org/mail-
- ing-lists.html or SANE bug tracker
- http://www.sane-project.org/bugs.html
+ of acquiring support via mail-lists http://www.sane-project.org/mail-
+ ing-lists.html or SANE bug tracker
+ http://www.sane-project.org/bugs.html.
AUTHORS
- Alex Belkin <abc@telekom.ru>
+ Alex Belkin <abc@telekom.ru>.
Samsung SCX-4500W scan over network support by Alexander Kuznetsov
- <acca(at)cpan.org>
+ <acca(at)cpan.org>.
Color scanning on Samsung M2870 model and Xerox Cognac 3215 & 3225 mod-
- els by Laxmeesh Onkar Markod <m.laxmeesh@samsung.com>
+ els by Laxmeesh Onkar Markod <m.laxmeesh@samsung.com>.
diff --git a/man/sane.7.html b/man/sane.7.html
index aba23e5f..72bb0bee 100644
--- a/man/sane.7.html
+++ b/man/sane.7.html
@@ -2,7 +2,7 @@
sane.7
-
+
sane.7
@@ -43,24 +43,24 @@
SOFTWARE PACKAGES
- The package `sane-backends' contains a lot of backends, documentation,
- networking support, and the command line frontend `scanimage'. The
- frontends `xscanimage', `xcam', and `scanadf' are included in the pack-
- age `sane-frontends'. Both packages can be downloaded from the SANE
- homepage (http://www.sane-project.org/). Information about other fron-
- tends and backends can also be found on the SANE homepage.
+ The package sane-backends contains backends, documentation, networking
+ support, and the command line frontend scanimage(1). The frontends xs-
+ canimage(1), xcam(1), and scanadf(1) are included in the package
+ sane-frontends. Both packages can be downloaded from the SANE homepage
+ (http://www.sane-project.org/). Information about other frontends and
+ backends can also be found on the SANE homepage.
GENERAL INFORMATION
- The following sections provide short descriptions and links to more
- information about several aspects of SANE. A name with a number in
- parenthesis (e.g. `sane-dll(5)') points to a manual page. In this case
- `man 5 sane-dll' will display the page. Entries like
- `/usr/local/share/doc/sane-backends/README' are references to text
- files that were copied to the SANE documentation directory
- (/usr/local/share/doc/sane-backends/) during installation. Everything
- else is a URL to a resource on the web.
+ The following sections provide short descriptions and links to more in-
+ formation about several aspects of SANE. A name with a number in
+ parenthesis (e.g. sane-dll(5)) points to a manual page. In this case
+ man 5 sane-dll will display the page. Entries like /usr/lo-
+ cal/share/doc/sane-backends/README are references to text files that
+ were copied to the SANE documentation directory (/usr/lo-
+ cal/share/doc/sane-backends/) during installation. Everything else is a
+ URL to a resource on the web.
SANE homepage
Information on all aspects of SANE including a tutorial and a link to
@@ -74,15 +74,15 @@
CAN YOU HELP SANE for details. There are lists for specific releases
of SANE, for the current development version and a search engine:
http://www.sane-project.org/sane-supported-devices.html. The lists
- are also installed on your system at /usr/local/share/doc/sane-back-
- ends/.
+ are also installed on your system at /usr/local/share/doc/sane-back-
+ ends/.
SANE mailing list
There is a mailing list for the purpose of discussing the SANE stan-
dard and its implementations: sane-devel. Despite its name, the list
is not only intended for developers, but also for users. There are
- also some more lists for special topics, however, for users,
- sane-devel is the right list. How to subscribe and unsubscribe:
+ also some more lists for special topics. However, for users, sane-de-
+ vel is the right list. How to subscribe and unsubscribe:
http://www.sane-project.org/mailing-lists.html.
SANE IRC channel
@@ -118,316 +118,301 @@
sane-find-scanner
Command-line tool to find SCSI and USB scanners and determine their
- Unix device files. See sane-find-scanner(1).
+ UNIX device files. See sane-find-scanner(1).
- Also, have a look at the sane-frontends package (including xscanimage,
- xcam, and scanadf) and the frontend information page at
+ Also, have a look at the sane-frontends package (which includes xscan-
+ image(1), xcam(1), and scanadf(1)) and the frontend information page at
http://www.sane-project.org/sane-frontends.html.
BACKENDS FOR SCANNERS
abaton
- The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
- (8bit, 256 levels of gray) and the Scan 300/S (black and white,
- untested). See sane-abaton(5) for details.
+ Supports Abaton flatbed scanners such as the Scan 300/GS (8bit, 256
+ levels of gray) and the Scan 300/S (black and white, untested). See
+ sane-abaton(5) for details.
agfafocus
- This backend supports AGFA Focus scanners and the Siemens S9036
- (untested). See sane-agfafocus(5) for details.
+ Supports AGFA Focus scanners and the Siemens S9036 (untested). See
+ sane-agfafocus(5) for details.
apple
- The SANE backend for Apple flatbed scanners supports the following
- scanners: AppleScanner, OneScanner and ColorOneScanner. See
- sane-apple(5) for details.
+ Supports Apple flatbed scanners including the following scanners: Ap-
+ pleScanner, OneScanner and ColorOneScanner. See sane-apple(5) for de-
+ tails.
artec
- The SANE Artec backend supports several Artec/Ultima SCSI flatbed
- scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
- See sane-artec(5) for details.
+ Supports several Artec/Ultima SCSI flatbed scanners as well as the
+ BlackWidow BW4800SP and the Plustek 19200S. See sane-artec(5) for de-
+ tails.
artec_eplus48u
- The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
- re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
- and Trust Easy Webscan 19200. See sane-artec_eplus48u(5) for details.
+ Supports the Artec E+ 48U scanner and re-badged models like Tevion MD
+ 9693, Medion MD 9693, Medion MD 9705 and Trust Easy Webscan 19200.
+ See sane-artec_eplus48u(5) for details.
as6e
- This is a SANE backend for using the Artec AS6E parallel port inter-
- face scanner. See sane-as6e(5) for details.
+ Supports the Artec AS6E parallel port interface scanner. See
+ sane-as6e(5) for details.
avision
- This backend supports several Avision based scanners. This includes
- the original Avision scanners (like AV 630, AV 620, ...) as well as
- the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit-
- subishi and Minolta film-scanners. See sane-avision(5) for details.
+ Supports several Avision based scanners including the original Avi-
+ sion scanners (like AV 630, AV 620, ...) as well as the HP ScanJet
+ 53xx and 74xx series, Fujitsu ScanPartner, some Mitsubishi and Mi-
+ nolta film-scanners. See sane-avision(5) for details.
bh
- The bh backend provides access to Bell+Howell Copiscan II series doc-
- ument scanners. See sane-bh(5) for details.
+ Supports Bell+Howell Copiscan II series document scanners. See
+ sane-bh(5) for details.
canon
- The canon backend supports the CanoScan 300, CanoScan 600, and
- CanoScan 2700F SCSI flatbed scanners. See sane-canon(5) for details.
+ Supports the CanoScan 300, CanoScan 600, and CanoScan 2700F SCSI
+ flatbed scanners. See sane-canon(5) for details.
canon630u
- The canon630u backend supports the CanoScan 630u and 636u USB scan-
- ners. See sane-canon630u(5) for details.
+ Supports the CanoScan 630u and 636u USB scanners. See
+ sane-canon630u(5) for details.
canon_dr
- The canon_dr backend supports the Canon DR-Series ADF SCSI and USB
- scanners. See sane-canon_dr(5) for details.
+ Supports the Canon DR-Series ADF SCSI and USB scanners. See
+ sane-canon_dr(5) for details.
canon_lide70
- The canon_lide70 backend supports the CanoScan LiDE 70 USB scanner.
- See sane-canon_lide70(5) for details.
+ Supports the CanoScan LiDE 70 USB scanner. See sane-canon_lide70(5)
+ for details.
canon_pp
- The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
- N640P parallel port scanners. See sane-canon_pp(5) for details.
+ Supports the CanoScan FB330P, FB630P, N340P and N640P parallel port
+ scanners. See sane-canon_pp(5) for details.
cardscan
- This backend provides support for Corex Cardscan USB scanners. See
- sane-cardscan(5) for details.
+ Support for Corex Cardscan USB scanners. See sane-cardscan(5) for de-
+ tails.
- coolscan
- This is a SANE backend for Nikon Coolscan film-scanners. See
- sane-coolscan(5) for details.
-
- coolscan2
- This is a SANE backend for Nikon Coolscan film-scanners. See
- sane-coolscan2(5) for details.
+ coolscan coolscan2 coolscan3
+ Supports Nikon Coolscan film-scanners. See sane-coolscan(5),
+ sane-coolscan2(5) and sane-coolscan3(5) for details.
epjitsu
- The epjitsu backend provides support for Epson-based Fujitsu USB
- scanners. See sane-epjitsu(5) for details.
+ Supports Epson-based Fujitsu USB scanners. See sane-epjitsu(5) for
+ details.
epson
- The SANE epson backend provides support for Epson SCSI, parallel port
- and USB flatbed scanners. See sane-epson(5) for details.
+ Supports Epson SCSI, parallel port and USB flatbed scanners. See
+ sane-epson(5) for details.
+
+ escl
+ Supports scanners through the eSCL protocol. See sane-escl(5) for de-
+ tails.
fujitsu
- The fujitsu backend provides support for most Fujitsu SCSI and USB,
- flatbed and adf scanners. See sane-fujitsu(5) for details.
+ Supports most Fujitsu SCSI and USB, flatbed and adf scanners. See
+ sane-fujitsu(5) for details.
genesys
- The genesys backend provides support for several scanners based on
- the Genesys Logic GL646, GL841, GL843, GL847 and GL124 chips like the
- Medion 6471 and Hewlett-Packard 2300c.
+ Supports several scanners based on the Genesys Logic GL646, GL841,
+ GL843, GL847 and GL124 chips like the Medion 6471 and Hewlett-Packard
+ 2300c.
See sane-genesys(5) for details.
gt68xx
- The gt68xx backend provides support for scanners based on the
- Grandtech GT-6801 and GT-6816 chips like the Artec Ultima 2000 and
- several Mustek BearPaw CU and TA models. Some Genius, Lexmark,
- Medion, Packard Bell, Plustek, and Trust scanners are also supported.
- See sane-gt68xx(5) for details.
+ Supports scanners based on the Grandtech GT-6801 and GT-6816 chips
+ like the Artec Ultima 2000 and several Mustek BearPaw CU and TA mod-
+ els. Some Genius, Lexmark, Medion, Packard Bell, Plustek, and Trust
+ scanners are also supported. See sane-gt68xx(5) for details.
hp
- The SANE hp backend provides access to Hewlett-Packard ScanJet scan-
- ners which support SCL (Scanner Control Language by HP). See
- sane-hp(5) for details.
+ Supports Hewlett-Packard ScanJet scanners which utilize SCL (Scanner
+ Control Language by HP). See sane-hp(5) for details.
hpsj5s
- The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
- sane-hpsj5s(5) for details.
+ Supports the Hewlett-Packard ScanJet 5S scanner. See sane-hpsj5s(5)
+ for details.
hp3500
- The SANE backend for the Hewlett-Packard ScanJet 3500 series. See
- sane-hp3500(5) for details.
+ Supports the Hewlett-Packard ScanJet 3500 series. See sane-hp3500(5)
+ for details.
hp3900
- The SANE backend for the Hewlett-Packard ScanJet 3900 series. See
- sane-hp3900(5) for details.
+ Supports the Hewlett-Packard ScanJet 3900 series. See sane-hp3900(5)
+ for details.
hp4200
- The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
- sane-hp4200(5) for details.
+ Supports the Hewlett-Packard ScanJet 4200 series. See sane-hp4200(5)
+ for details.
hp5400
- The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
- sane-hp5400(5) for details.
+ Supports the Hewlett-Packard ScanJet 54XXC series. See sane-hp5400(5)
+ for details.
hpljm1005
- The SANE backend for the Hewlett-Packard LaserJet M1005 scanner. See
+ Supports the Hewlett-Packard LaserJet M1005 scanner. See
sane-hpljm1005(5) for details.
hs2p
- The SANE backend for the Ricoh IS450 family of SCSI scanners. See
- sane-hs2p(5) for details.
+ Supports the Ricoh IS450 family of SCSI scanners. See sane-hs2p(5)
+ for details.
ibm
- The SANE backend for some IBM and Ricoh SCSI scanners. See
- sane-ibm(5) for details.
+ Supports some IBM and Ricoh SCSI scanners. See sane-ibm(5) for de-
+ tails.
kodak
- The SANE backend for some large Kodak scanners. See sane-kodak(5) for
- details.
+ Supports some large Kodak scanners. See sane-kodak(5) for details.
kodakaio
- The SANE backend for Kodak AiO printer/scanners. See sane-kodakaio(5)
- for details.
+ Supports Kodak AiO printer/scanners. See sane-kodakaio(5) for de-
+ tails.
kvs1025
- The SANE backend for Panasonic KV-S102xC scanners. See
- sane-kvs1025(5) for details.
+ Supports Panasonic KV-S102xC scanners. See sane-kvs1025(5) for de-
+ tails.
leo
- This backend supports the Leo S3 and the Across FS-1130, which is a
- re-badged LEO FS-1130 scanner. See sane-leo(5) for details.
+ Supports the LEO S3 and the Across FS-1130, which is a re-badged LEO
+ FS-1130 scanner. See sane-leo(5) for details.
lexmark
- This backend supports the Lexmark X1100 series of USB scanners. See
- sane-lexmark(5) for details.
+ Supports the Lexmark X1100 series of USB scanners. See sane-lex-
+ mark(5) for details.
ma1509
- The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
- scanner. See sane-ma1509(5) for details.
+ Supports the Mustek BearPaw 1200F USB flatbed scanner. See
+ sane-ma1509(5) for details.
magicolor
- The magicolor backend supports the KONICA MINOLTA magicolor 1690MF
- multi-function printer/scanner/fax. See sane-magicolor(5) for
- details.
+ Supports the KONICA MINOLTA magicolor 1690MF multi-function
+ printer/scanner/fax. See sane-magicolor(5) for details.
matsushita
- This backend supports some Panasonic KVSS high speed scanners. See
- sane-matsushita(5) for details.
+ Supports some Panasonic KVSS high speed scanners. See sane-mat-
+ sushita(5) for details.
microtek
- The microtek backend provides access to the "second generation"
- Microtek scanners with SCSI-1 command set. See sane-microtek(5) for
- details.
+ Supports "second generation" Microtek scanners with SCSI-1 command
+ set. See sane-microtek(5) for details.
microtek2
- The microtek2 backend provides access to some Microtek scanners with
- a SCSI-2 command set. See sane-microtek2(5) for details.
+ Supports some Microtek scanners with a SCSI-2 command set. See
+ sane-microtek2(5) for details.
mustek
- The SANE mustek backend supports most Mustek SCSI flatbed scanners
- including the Paragon and ScanExpress series and the 600 II N and 600
- II EP (non-SCSI). Some Trust scanners are also supported. See
- sane-mustek(5) for details.
+ Supports most Mustek SCSI flatbed scanners including the Paragon and
+ ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some
+ Trust scanners are also supported. See sane-mustek(5) for details.
mustek_pp
- The mustek_pp backend provides access to Mustek parallel port flatbed
- scanners. See sane-mustek_pp(5) for details.
-
- mustek_usb
- The mustek_usb backend provides access to some Mustek ScanExpress USB
- flatbed scanners. See sane-mustek_usb(5) for details.
-
- mustek_usb2
- The mustek_usb2 backend provides access to scanners using the SQ113
- chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
- sane-mustek_usb2(5) for details.
-
- nec
- The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
- sane-nec(5) for details.
-
- niash
- The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
- 3300c, 3400c, and 4300c USB flatbed scanners. See sane-niash(5) for
- details.
-
- p5
- The SANE backend for Primax PagePartner. See sane-p5(5) for details.
-
- pie
- The pie backend provides access to Pacific Image Electronics (PIE)
- and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
-
- pixma
- The pixma backend supports Canon PIXMA MP series (multi-function
- devices), Canon imageCLASS series (laser devices), Canon MAXIFY
- series and some Canon CanoScan series. See sane-pixma(5) for details.
-
- plustek
- The SANE plustek backend supports USB flatbed scanners that use the
- National Semiconductor LM983[1/2/3] chipset aka Merlin. Scanners
- using this LM983x chips include some models from Plustek, KYE/Genius,
- Hewlett-Packard, Mustek, Umax, Epson, and Canon. See sane-plustek(5)
+ Supports Mustek parallel port flatbed scanners. See sane-mustek_pp(5)
for details.
+ mustek_usb
+ Supports some Mustek ScanExpress USB flatbed scanners. See
+ sane-mustek_usb(5) for details.
+
+ mustek_usb2
+ Supports scanners using the SQ113 chipset like the Mustek BearPaw
+ 2448 TA Pro USB flatbed scanner. See sane-mustek_usb2(5) for details.
+
+ nec
+ Supports the NEC PC-IN500/4C SCSI scanner. See sane-nec(5) for de-
+ tails.
+
+ niash
+ Supports the Agfa Snapscan Touch and the HP ScanJet 3300c, 3400c, and
+ 4300c USB flatbed scanners. See sane-niash(5) for details.
+
+ p5
+ Supports the Primax PagePartner. See sane-p5(5) for details.
+
+ pie
+ Supports Pacific Image Electronics (PIE) and Devcom SCSI flatbed
+ scanners. See sane-pie(5) for details.
+
+ pixma
+ Supports Canon PIXMA MP series (multi-function devices), Canon image-
+ CLASS series (laser devices), Canon MAXIFY series and some Canon
+ CanoScan series. See sane-pixma(5) for details.
+
+ plustek
+ Supports USB flatbed scanners that use the National Semiconductor
+ LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x chips in-
+ clude some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek,
+ Umax, Epson, and Canon. See sane-plustek(5) for details.
+
plustek_pp
- The SANE plustek_pp backend supports Plustek parallel port flatbed
- scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
- P98003 include some models from Plustek, KYE/Genius, Primax. See
- sane-plustek_pp(5) for details.
+ Supports Plustek parallel port flatbed scanners using the Plustek
+ ASIC P96001, P96003, P98001 and P98003, which includes some models
+ from Plustek, KYE/Genius, Primax. See sane-plustek_pp(5) for details.
ricoh
- The ricoh backend provides access to the following Ricoh flatbed
- scanners: IS50 and IS60. See sane-ricoh(5) for details.
+ Supports the Ricoh flatbed scanners IS50 and IS60. See sane-ricoh(5)
+ for details.
ricoh2
- The ricoh2 backend provides access to the following Ricoh flatbed
- scanners: SG-3100SNw, SP-100SU, and SP-111SU. See sane-ricoh2(5) for
- details.
+ Supports the Ricoh flatbed scanners: SG-3100SNw, SP-100SU, and
+ SP-111SU. See sane-ricoh2(5) for details.
s9036
- The s9036 backend provides access to Siemens 9036 flatbed scanners.
- See sane-s9036(5) for details.
+ Supports Siemens 9036 flatbed scanners. See sane-s9036(5) for de-
+ tails.
sceptre
- The sceptre backend provides access to the Sceptre S1200 flatbed
- scanner. See sane-sceptre(5) for details.
-
- sharp
- The SANE sharp backend supports Sharp SCSI scanners. See
- sane-sharp(5) for details.
-
- sm3600
- The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
- scanner. See sane-sm3600(5) for details.
-
- sm3840
- The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
- scanner. See sane-sm3840(5) for details.
-
- snapscan
- The snapscan backend supports AGFA SnapScan flatbed scanners. See
- sane-snapscan(5) for details.
-
- sp15c
- This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
- ner. See sane-sp15c(5) for details.
-
- st400
- The sane-st400 backend provides access to Siemens ST400 and ST800.
- See sane-st400(5) for details.
-
- tamarack
- The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
- ners. See sane-tamarack(5) for details.
-
- teco1 teco2 teco3
- The SANE teco1, teco2 and teco3 backends support some TECO scanners,
- usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
- See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
-
- u12
- The sane-u12 backend provides USB flatbed scanners based on Plustek's
- ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
- bridge chip like the Plustek OpticPro U(T)12. See sane-u12(5) for
+ Supports the Sceptre S1200 flatbed scanner. See sane-sceptre(5) for
details.
+ sharp
+ Supports Sharp SCSI scanners. See sane-sharp(5) for details.
+
+ sm3600
+ Supports the Microtek ScanMaker 3600 USB scanner. See sane-sm3600(5)
+ for details.
+
+ sm3840
+ Supports the Microtek ScanMaker 3840 USB scanner. See sane-sm3840(5)
+ for details.
+
+ snapscan
+ Supports AGFA SnapScan flatbed scanners including some which are re-
+ badged to other brands. See sane-snapscan(5) for details.
+
+ sp15c
+ Supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See
+ sane-sp15c(5) for details.
+
+ st400
+ Supports the Siemens ST400 and ST800. See sane-st400(5) for details.
+
+ tamarack
+ Supports Tamarack Artiscan flatbed scanners. See sane-tamarack(5) for
+ details.
+
+ teco1 teco2 teco3
+ Supports some TECO scanners, usually sold under the Relisys, Trust,
+ Primax, Piotech, Dextra names. See sane-teco1(5), sane-teco2(5) and
+ sane-teco3(5) for details.
+
+ u12
+ Supports USB flatbed scanners based on Plustek's ASIC 98003 (paral-
+ lel-port ASIC) and a GeneSys Logics' USB-parport bridge chip like the
+ Plustek OpticPro U(T)12. See sane-u12(5) for details.
+
umax
- The sane-umax backend provides access to several UMAX-SCSI-scanners
- and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
+ Supports UMAX-SCSI-scanners and some Linotype Hell SCSI-scanners. See
+ sane-umax(5) for details.
umax_pp
- The sane-umax_pp backend provides access to Umax parallel port
- flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
+ Supports Umax parallel port flatbed scanners and the HP 3200C. See
+ sane-umax_pp(5) for details.
umax1200u
- The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
- flatbed scanner (and also the UMAX Astra 2000U, sort of). See
- sane-umax1220u(5) for details.
+ Supports the UMAX Astra 1220U (USB) flatbed scanner (and also the
+ UMAX Astra 2000U, sort of). See sane-umax1220u(5) for details.
xerox_mfp
- The sane-xerox_mfp backend supports multiple Samsung-based Samsung,
- Xerox, and Dell scanners. See sane-xerox_mfp(5) for details.
+ Supports multiple Samsung-based Samsung, Xerox, and Dell scanners.
+ See sane-xerox_mfp(5) for details.
- Also, have a look at the backend information page at
+ Also, have a look at the backend information page at
http://www.sane-project.org/sane-supported-devices.html and the list of
projects in /usr/local/share/doc/sane-backends/PROJECTS.
@@ -435,31 +420,30 @@
BACKENDS FOR DIGITAL CAMERAS
dc210
- Backend for Kodak DC210 Digital Camera. See sane-dc210(5).
+ Supports the Kodak DC210 Digital Camera. See sane-dc210(5).
dc240
- Backend for Kodak DC240 Digital Camera. See sane-dc240(5).
+ Supports the Kodak DC240 Digital Camera. See dc240(5).
dc25
- Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
+ Supports Kodak DC20/DC25 Digital Cameras. See dc25(5).
dmc
- Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5).
+ Supports the Polaroid Digital Microscope Camera. See dmc(5).
gphoto2
- Backend for digital cameras supported by the gphoto2 library package.
- (See http://www.gphoto.org for more information and a list of sup-
- ported cameras.) Gphoto2 supports over 140 different camera models.
- However, please note that more development and testing is needed
- before all of these cameras will be supported by SANE backend. See
- sane-gphoto2(5).
+ Supports digital cameras supported by the gphoto2 library package.
+ (See http://www.gphoto.org for more information and a list of sup-
+ ported cameras.) Gphoto2 supports over 140 different camera models.
+ However, please note that more development and testing is needed be-
+ fore all of these cameras will be supported by SANE backend. See
+ gphoto2(5).
qcam
- Backend for Connectix QuickCam cameras. See sane-qcam(5).
+ Supports Connectix QuickCam cameras. See qcam(5).
stv680
- The sane-stv680 backend provides access to webcams with a stv680
- chip. See sane-stv680(5) for details.
+ Supports webcams with a stv680 chip. See stv680(5) for details.
Also, have a look at the backend information page at
http://www.sane-project.org/sane-supported-devices.html and the list of
@@ -469,75 +453,72 @@
MISCELLANEOUS BACKENDS
dll
- The sane-dll library implements a SANE backend that provides access
- to an arbitrary number of other SANE backends by dynamic loading. See
- sane-dll(5).
+ Implements a SANE backend that provides access to an arbitrary number
+ of other SANE backends by dynamic loading. See sane-dll(5).
net
- The SANE network daemon saned provides access to scanners located on
- different computers in connection with the net backend. See
+ The SANE network daemon saned(8) provides access to scanners located
+ on different computers in connection with the net backend. See
sane-net(5) and saned(8).
pnm
- PNM image reader pseudo-backend. The purpose of this backend is pri-
+ PNM image reader pseudo-backend. The purpose of this backend is pri-
marily to aid in debugging of SANE frontends. See sane-pnm(5).
pint
- Backend for scanners that use the PINT (Pint Is Not Twain) device
- driver. The PINT driver is being actively developed on the OpenBSD
- platform, and has been ported to a few other *nix-like operating sys-
+ Supports scanners that use the PINT (Pint Is Not Twain) device
+ driver. The PINT driver is being actively developed on the OpenBSD
+ platform, and has been ported to a few other *NIX-like operating sys-
tems. See sane-pint(5).
test
- The SANE test backend is for testing frontends and the SANE installa-
- tion. It provides test pictures and various test options. See
- sane-test(5).
+ Tests frontends and the SANE installation. It provides test pictures
+ and various test options. See sane-test(5).
v4l
- The sane-v4l library implements a SANE backend that provides generic
- access to video cameras and similar equipment using the V4L (Video
- for Linux) API. See sane-v4l(5).
+ Provides generic access to video cameras and similar equipment using
+ the V4L (Video for Linux) API. See sane-v4l(5).
- Also, have a look at the backend information page at
+ Also, have a look at the backend information page at
http://www.sane-project.org/sane-supported-devices.html and the list of
projects in /usr/local/share/doc/sane-backends/PROJECTS.
CHANGING THE TOP-LEVEL BACKEND
- By default, all SANE backends (drivers) are loaded dynamically by the
- sane-dll meta backend. If you have any questions about the dynamic
- loading, read sane-dll(5). SANE frontend can also be linked to other
- backends directly by copying or linking a backend to libsane.so in
+ By default, all SANE backends (drivers) are loaded dynamically by the
+ sane-dll meta backend. If you have any questions about the dynamic
+ loading, read sane-dll(5). SANE frontends can also be linked to other
+ backends directly by copying or linking a backend to libsane.so in
/usr/local/lib/sane.
DEVELOPER'S DOCUMENTATION
- It's not hard to write a SANE backend. It can take some time, however.
- You should have basic knowledge of C and enough patience to work
+ It's not hard to write a SANE backend. It can take some time, however.
+ You should have basic knowledge of C and enough patience to work
through the documentation and find out how your scanner works. Appended
is a list of some documents that help to write backends and frontends.
- The SANE standard defines the application programming interface (API)
- that is used to communicate between frontends and backends. It can be
+ The SANE standard defines the application programming interface (API)
+ that is used to communicate between frontends and backends. It can be
found at http://sane-project.gitlab.io/standard/ .
- There is some more information for programmers in
- /usr/local/share/doc/sane-backends/backend-writing.txt. Most of the
- internal SANE routines (sanei) are documented using doxygen:
- http://www.sane-project.org/sanei/. Before a new backend or frontend
- project is started, have a look at /usr/local/share/doc/sane-back-
- ends/PROJECTS for projects that are planned or not yet included into
- the SANE distribution and at our bug-tracking system:
+ There is some more information for programmers in /usr/lo-
+ cal/share/doc/sane-backends/backend-writing.txt. Most of the internal
+ SANE routines (sanei) are documented using doxygen:
+ http://www.sane-project.org/sanei/. Before a new backend or frontend
+ project is started, have a look at /usr/local/share/doc/sane-back-
+ ends/PROJECTS for projects that are planned or not yet included into
+ the SANE distribution and at our bug-tracking system:
http://www.http://www.sane-project.org/bugs.html.
- There are some links on how to find out about the protocol of a scan-
+ There are some links on how to find out about the protocol of a scan-
ner: http://www.meier-geinitz.de/sane/misc/develop.html.
- If you start writing a backend or frontend or any other part of SANE,
- please contact the sane-devel mailing list for coordination so the same
- work isn't done twice.
+ If you start writing a backend or frontend or any other part of SANE,
+ please contact the sane-devel mailing list for coordination so that
+ work is not duplicated.
@@ -549,7 +530,7 @@
The static libraries implementing the backends.
/usr/local/lib/sane/libsane-*.so
- The shared libraries implementing the backends (present on sys-
+ The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
/usr/local/share/doc/sane-backends/*
@@ -559,116 +540,117 @@
PROBLEMS
If your device isn't found but you know that it is supported, make sure
- that it is detected by your operating system. For SCSI and USB scan-
- ners, use the sane-find-scanner tool (see sane-find-scanner(1) for
- details). It prints one line for each scanner it has detected and some
- comments (#). If sane-find-scanner finds your scanner only as root but
- not as normal user, the permissions for the device files are not
- adjusted correctly. If the scanner isn't found at all, the operating
- system hasn't detected it and may need some help. Depending on the type
- of your scanner, read sane-usb(5) or sane-scsi(5). If your scanner (or
- other device) is not connected over the SCSI bus or USB, read the back-
- end's manual page for details on how to set it up.
+ that it is detected by your operating system. For SCSI and USB scan-
+ ners, use the sane-find-scanner(1) utility. It prints one line for
+ each scanner it has detected and some comments (#). If sane-find-scan-
+ ner(1) finds your scanner only as root but not as normal user, the per-
+ missions for the device files are not adjusted correctly. If the scan-
+ ner isn't found at all, the operating system hasn't detected it and may
+ need some help. Depending on the type of your scanner, read sane-usb(5)
+ or sane-scsi(5). If your scanner (or other device) is not connected
+ over the SCSI bus or USB, read the backend's manual page for details on
+ how to set it up.
- Now your scanner is detected by the operating system but not by SANE?
- Try scanimage -L. If the scanner is not found, check that the back-
- end's name is mentioned in /usr/local/etc/sane.d/dll.conf. Some back-
- ends are commented out by default. Remove the comment sign for your
- backend in this case. Also some backends aren't compiled at all if one
- of their prerequisites are missing. Examples include dc210, dc240,
- canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm.
- If you need one of these backends and they aren't available, read the
- build instructions in the README file and the individual manual pages
- of the backends.
+ Is your scanner detected by the operating system but not by SANE? Try
+ scanimage -L. If the scanner is not found, check that the backend's
+ name is mentioned in /usr/local/etc/sane.d/dll.conf. Some backends are
+ commented out by default. Remove the comment sign for your backend in
+ this case. Also some backends aren't compiled at all if one of their
+ prerequisites are missing. Examples include dc210, dc240, canon_pp,
+ hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you
+ need one of these backends and it isn't available, read the build in-
+ structions in the README file and the individual manual pages of the
+ backends.
- Another reason for not being detected by scanimage -L may be a missing
- or wrong configuration in the backend's configuration file. While SANE
- tries to automatically find most scanners, some can't be setup cor-
- rectly without the intervention of the administrator. Also on some
+ Another reason for not being detected by scanimage -L may be a missing
+ or incorrect configuration in the backend's configuration file. While
+ SANE tries to automatically find most scanners, some can't be setup
+ correctly without the intervention of the administrator. Also on some
operating systems auto-detection may not work. Check the backend's man-
ual page for details.
If your scanner is still not found, try setting the various environment
- variables that are available to assist in debugging. The environment
+ variables that are available to assist in debugging. The environment
variables are documented in the relevant manual pages. For example, to
- get the maximum amount of debug information when testing a Mustek SCSI
- scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
- and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L . The
- debug messages for the dll backend tell if the mustek backend was found
- and loaded at all. The mustek messages explain what the mustek backend
- is doing while the SCSI debugging shows the low level handling. If you
+ get the maximum amount of debug information when testing a Mustek SCSI
+ scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
+ and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L. The de-
+ bug messages for the dll backend tell if the mustek backend was found
+ and loaded at all. The mustek messages explain what the mustek backend
+ is doing while the SCSI debugging shows the low level handling. If you
can't find out what's going on by checking the messages carefully, con-
tact the sane-devel mailing list for help (see REPORTING BUGS below).
- Now that your scanner is found by scanimage -L, try to do a scan: scan-
- image >image.pnm. This command starts a scan for the default scanner
- with default settings. All the available options are listed by running
- scanimage --help. If scanning aborts with an error message, turn on
- debugging as mentioned above. Maybe the configuration file needs some
- tuning, e.g. to setup the path to a firmware that is needed by some
- scanners. See the backend's manual page for details. If you can't find
+ Now that your scanner is found by scanimage -L, try to do a scan: scan-
+ image >image.pnm. This command starts a scan for the default scanner
+ with default settings. All the available options are listed by running
+ scanimage --help. If scanning aborts with an error message, turn on
+ debugging as mentioned above. Maybe the configuration file needs some
+ tuning, e.g. to setup the path to a firmware that is needed by some
+ scanners. See the backend's manual page for details. If you can't find
out what's wrong, contact sane-devel.
- To check that the SANE libraries are installed correctly you can use
- the test backend, even if you don't have a scanner or other SANE
- device:
+ To check that the SANE libraries are installed correctly you can use
+ the test backend, even if you don't have a scanner or other SANE de-
+ vice:
- scanimage -d test -T
+ scanimage -d test -T
- You should get a list of PASSed tests. You can do the same with your
+ You should get a list of PASSed tests. You can do the same with your
backend by changing "test" to your backend's name.
- So now scanning with scanimage works and you want to use one of the
- graphical frontends like xsane, xscanimage, or quiteinsane but those
- frontends don't detect your scanner? One reason may be that you
+ So now scanning with scanimage(1) works and you want to use one of the
+ graphical frontends like xsane(1), xscanimage(1), or quiteinsane(1) but
+ those frontends don't detect your scanner? One reason may be that you
installed two versions of SANE. E.g. the version that was installed by
- your distribution in /usr and one you installed from source in
- /usr/local/. Make sure that only one version is installed. Another
- possible reason is, that your system's dynamic loader can't find the
- SANE libraries. For Linux, make sure that /etc/ld.so.conf contains
- /usr/local/lib and does not contain /usr/local/lib/sane. See also the
- documentation of the frontends.
+ your distribution in /usr and one you installed from source in /usr/lo-
+ cal/. Make sure that only one version is installed. Another possible
+ reason is, that your system's dynamic loader can't find the SANE li-
+ braries. For Linux, make sure that /etc/ld.so.conf contains /usr/lo-
+ cal/lib and does not contain /usr/local/lib/sane. See also the docu-
+ mentation of the frontends.
HOW CAN YOU HELP SANE
- We appreciate any help we can get. Please have a look at our web page
+ We appreciate any help we can get. Please have a look at our web page
about contributing to SANE: http://www.sane-project.org/contrib.html
CONTACT
- For reporting bugs or requesting new features, please use our bug-
- tracking system: http://www.sane-project.org/bugs.html. You can also
- contact the author of your backend directly. Usually the email address
- can be found in the /usr/local/share/doc/sane-backends/AUTHORS file or
- the backend's manpage. For general discussion about SANE, please use
+ For reporting bugs or requesting new features, please use our bug-
+ tracking system: http://www.sane-project.org/bugs.html. You can also
+ contact the author of your backend directly. Usually the email address
+ can be found in the /usr/local/share/doc/sane-backends/AUTHORS file or
+ the backend's manpage. For general discussion about SANE, please use
the SANE mailing list sane-devel (see http://www.sane-project.org/mail-
ing-lists.html for details).
SEE ALSO
- saned(8), sane-find-scanner(1), scanimage(1), sane-abaton(5),
- sane-agfafocus(5), sane-apple(5), sane-artec(5),
- sane-artec_eplus48u(5), sane-as6e(5), sane-avision(5), sane-bh(5),
- sane-canon(5), sane-canon630u(5), sane-canon_dr(5), sane-canon_pp(5),
- sane-cardscan(5), sane-coolscan2(5), sane-coolscan(5), sane-dc210(5),
- sane-dc240(5), sane-dc25(5), sane-dll(5), sane-dmc(5), sane-epson(5),
- sane-fujitsu(5), sane-genesys(5), sane-gphoto2(5), sane-gt68xx(5),
- sane-hp(5), sane-hpsj5s(5), sane-hp3500(5), sane-hp3900(5),
- sane-hp4200(5), sane-hp5400(5), sane-hpljm1005(5), sane-ibm(5),
- sane-kodak(5), sane-leo(5), sane-lexmark(5), sane-ma1509(5), sane-mat-
- sushita(5), sane-microtek2(5), sane-microtek(5), sane-mustek(5),
- sane-mustek_pp(5), sane-mustek_usb(5), sane-mustek_usb2(5),
- sane-nec(5), sane-net(5), sane-niash(5), sane-pie(5), sane-pint(5),
- sane-plustek(5), sane-plustek_pp(5), sane-pnm(5), sane-qcam(5),
- sane-ricoh(5), sane-ricoh2(5), sane-s9036(5), sane-sceptre(5),
- sane-scsi(5), sane-sharp(5), sane-sm3600(5), sane-sm3840(5), sane-snap-
- scan(5), sane-sp15c(5), sane-st400(5), sane-stv680(5), sane-tama-
- rack(5), sane-teco1(5), sane-teco2(5), sane-teco3(5), sane-test(5),
- sane-u12(5), sane-umax1220u(5), sane-umax(5), sane-umax_pp(5),
- sane-usb(5), sane-v4l(5), sane-xerox_mfp(5)
+ saned(8), sane-find-scanner(1), scanimage(1), sane-abaton(5), sane-ag-
+ fafocus(5), sane-apple(5), sane-artec(5), sane-artec_eplus48u(5),
+ sane-as6e(5), sane-avision(5), sane-bh(5), sane-canon(5),
+ sane-canon630u(5), sane-canon_dr(5), sane-canon_pp(5), sane-card-
+ scan(5), sane-coolscan(5), sane-coolscan2(5), sane-coolscan3(5),
+ sane-dc210(5), sane-dc240(5), sane-dc25(5), sane-dll(5), sane-dmc(5),
+ sane-epson(5), sane-escl(5), sane-fujitsu(5), sane-genesys(5),
+ sane-gphoto2(5), sane-gt68xx(5), sane-hp(5), sane-hpsj5s(5),
+ sane-hp3500(5), sane-hp3900(5), sane-hp4200(5), sane-hp5400(5),
+ sane-hpljm1005(5), sane-ibm(5), sane-kodak(5), sane-leo(5), sane-lex-
+ mark(5), sane-ma1509(5), sane-matsushita(5), sane-microtek2(5),
+ sane-microtek(5), sane-mustek(5), sane-mustek_pp(5),
+ sane-mustek_usb(5), sane-mustek_usb2(5), sane-nec(5), sane-net(5),
+ sane-niash(5), sane-pie(5), sane-pint(5), sane-plustek(5), sane-plus-
+ tek_pp(5), sane-pnm(5), sane-qcam(5), sane-ricoh(5), sane-ricoh2(5),
+ sane-s9036(5), sane-sceptre(5), sane-scsi(5), sane-sharp(5),
+ sane-sm3600(5), sane-sm3840(5), sane-snapscan(5), sane-sp15c(5),
+ sane-st400(5), sane-stv680(5), sane-tamarack(5), sane-teco1(5),
+ sane-teco2(5), sane-teco3(5), sane-test(5), sane-u12(5),
+ sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane-usb(5),
+ sane-v4l(5), sane-xerox_mfp(5)
diff --git a/man/saned.8.html b/man/saned.8.html
index fca8e2b5..da26ab4d 100644
--- a/man/saned.8.html
+++ b/man/saned.8.html
@@ -2,7 +2,7 @@
saned.8
-
+
saned.8
@@ -17,8 +17,8 @@
SYNOPSIS
- saned [ -a [ username ] ] [ -u username ] [ -b address ] [ -l ] [ -D ]
- [ -o ] [ -d n ] [ -e ] [ -h ]
+ saned [ -a [ username ] ] [ -u username ] [ -b address ] [ -p port ] [
+ -l ] [ -D ] [ -o ] [ -d n ] [ -e ] [ -h ]
@@ -31,13 +31,15 @@
OPTIONS
The -l flag requests that saned run in standalone daemon mode. In this
- mode, saned will listen for incoming client connections; inetd is not
- required for saned operations in this mode. The -b flag tells saned to
- bind to the address given. The -u flag requests that saned drop root
- privileges and run as the user (and group) associated with username
- after binding. The -D flag will request saned to detach from the con-
- sole and run in the background. The flag -a is equivalent to the com-
- bination of -l -B -u username options.
+ mode, saned will listen for incoming client connections; inetd(8) is
+ not required for saned operations in this mode. The -b flag tells saned
+ to bind to the address given. The -p flags tells saned to listen on
+ the port given. A value of 0 tells saned to pick an unused port. The
+ default is the sane-port (6566). The -u flag requests that saned drop
+ root privileges and run as the user (and group) associated with user-
+ name after binding. The -D flag will request saned to detach from the
+ console and run in the background. The flag -a is equivalent to the
+ combination of -l -B -u username options.
The -d flag sets the level of saned debug output. When compiled with
debugging enabled, this flag may be followed by a number to request
@@ -53,44 +55,45 @@
The -h flag displays a short help message.
- If saned is run from other programs such as inetd, xinetd and systemd,
- check that program's documentation on how to pass command-line options.
+ If saned is run from other programs such as inetd(8), xinetd(8) and
+ systemd(1), check that program's documentation on how to pass command-
+ line options.
CONFIGURATION
First and foremost: saned is not intended to be exposed to the internet
or other non-trusted networks. Make sure that access is limited by tcp-
- wrappers and/or a firewall setup. Don't depend only on saned's own
- authentication. Don't run saned as root if it's not necessary. And do
- not install saned as setuid root.
+ wrappers and/or a firewall setup. Don't depend only on saned's own au-
+ thentication. Don't run saned as root if it's not necessary. And do not
+ install saned as setuid root.
- The saned.conf configuration file contains both options for the daemon
+ The saned.conf configuration file contains both options for the daemon
and the access list.
data_portrange = min_port - max_port
- 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
+ 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 saned server is sitting behind a firewall. If that firewall
- is a Linux machine, we strongly recommend using the Netfilter
+ is a Linux machine, we strongly recommend using the Netfilter
nf_conntrack_sane module instead.
data_connect_timeout = timeout
- Specify the time in milliseconds that 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 backend. Specify zero to have the old behavior. The
- default is 4000ms.
+ Specify the time in milliseconds that 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 backend. Specify zero to have the old behavior. The de-
+ fault is 4000ms.
- The access list is a list of host names, IP addresses or IP subnets
- (CIDR notation) that are permitted to use local SANE devices. IPv6
- addresses must be enclosed in brackets, and should always be specified
- in their compressed form. Connections from localhost are always permit-
- ted. Empty lines and lines starting with a hash mark (#) are ignored. A
- line containing the single character ``+'' is interpreted to match any
- hostname. This allows any remote machine to use your scanner and may
+ The access list is a list of host names, IP addresses or IP subnets
+ (CIDR notation) that are permitted to use local SANE devices. IPv6 ad-
+ dresses must be enclosed in brackets, and should always be specified in
+ their compressed form. Connections from localhost are always permitted.
+ Empty lines and lines starting with a hash mark (#) are ignored. A line
+ containing the single character ``+'' is interpreted to match any host-
+ name. This allows any remote machine to use your scanner and may
present a security risk, so this shouldn't be used unless you know what
you're doing.
@@ -106,20 +109,21 @@
[::1]
[2001:db8:185e::42:12]/64
- The case of the host names does not matter, so AHost.COM is considered
+ The case of the host names does not matter, so AHost.COM is considered
identical to ahost.com.
SERVER DAEMON CONFIGURATION
For saned to work properly in its default mode of operation, it is also
- necessary to add the appropriate configuration for (x)inetd or systemd.
- (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.
+ necessary to add the appropriate configuration for xinetd(8), inetd(8)
+ or systemd(1) (see below). Note that your inetd(8) must support IPv6
+ if you want to connect to saned over IPv6; xinetd(8), openbsd-inetd(8)
+ and systemd(1) are known to support IPv6, check the documentation for
+ your inetd(8) daemon.
- In the sections below the configuration for inetd, xinetd and systemd
- are described in more detail.
+ In the sections below the configuration for inetd(8), xinetd(8) and
+ systemd(1) are described in more detail.
For the configurations below it is necessary to add a line of the fol-
lowing form to /etc/services:
@@ -132,7 +136,7 @@
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 inetd(8) configuration file
(/etc/inetd.conf)
The configuration line normally looks like this:
@@ -141,12 +145,12 @@
saned
However, if your system uses tcpd(8) for additional security screening,
- you may want to disable saned access control by putting ``+'' in
- saned.conf and use a line of the following form in /etc/inetd.conf
- instead:
+ you may want to disable saned access control by putting ``+'' in
+ saned.conf and use a line of the following form in /etc/inetd.conf in-
+ stead:
- sane-port stream tcp nowait saned.saned /usr/sbin/tcpd
- /usr/local/sbin/saned
+ sane-port stream tcp nowait saned.saned /usr/sbin/tcpd /usr/lo-
+ cal/sbin/saned
Note that both examples assume that there is a saned group and a saned
user. If you follow this example, please make sure that the access
@@ -157,8 +161,8 @@
XINETD CONFIGURATION
- If xinetd is installed on your system instead of inetd the following
- example for /etc/xinetd.conf may be helpful:
+ If xinetd(8) is installed on your system instead of inetd(8) the fol-
+ lowing example for /etc/xinetd.conf may be helpful:
# default: off
# description: The sane server accepts requests
@@ -177,21 +181,21 @@
SYSTEMD CONFIGURATION
- Saned can be compiled with explicit systemd support. This will allow
- logging debugging information to be forwarded to the systemd journal.
- The systemd support requires compilation with the systemd-devel package
- installed on the system. this is the preferred option.
+ saned can be compiled with explicit systemd(1)support.This will allow
+ logging debugging information to be forwarded to the systemd(1) jour-
+ nal. The systemd(1) support requires compilation with the systemd-devel
+ package installed on the system. this is the preferred option.
- Saned can be used wih systemd without the systemd integration compiled
- in, but then logging of debug information is not supported.
+ saned can be used with systemd(1) without the systemd(1) integration
+ compiled in, but then logging of debug information is not supported.
- The systemd configuration is different for the 2 options, so both are
- described below.
+ The systemd(1) configuration is different for the 2 options, so both
+ are described below.
Systemd configuration for saned with systemd support compiled in
- for the systemd configuration we need to add 2 configuration files in
+ For systemd(1) configuration we need to add 2 configuration files in
/etc/systemd/system.
The first file we need to add here is called saned.socket. It shall
@@ -231,29 +235,29 @@
Also=saned.socket
You need to set an environment variable for SANE_CONFIG_DIR pointing to
- the directory where 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.
+ the directory where saned can find its configuration files. you will
+ have to remove the # on the last line and set the variables for the de-
+ sired debugging information if required. Multiple variables can be set
+ by separating the assignments by spaces as shown in the example above.
- Unlike (x)inetd , systemd allows debugging output from backends set
- using SANE_DEBUG_XXX to be captured. See the man-page for your backend
- to see what options are supported. With the service unit as described
- above, the debugging output is forwarded to the system log.
+ Unlike xinetd(8) and inetd(8), systemd(1) allows debugging output from
+ backends set using SANE_DEBUG_XXX to be captured. See the man-page for
+ your backend to see what options are supported. With the service unit
+ as described above, the debugging output is forwarded to the system
+ log.
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
+ This configuration will also work when saned is compiled WITH sys-
+ temd(1)integrationsupport,butitdoesnotallowdebugging information to be
logged.
- for systemd configuration for saned, we need to add 2 configuration
+ For systemd(1) configuration for saned, we need to add 2 configuration
files in /etc/systemd/system.
The first file we need to add here is called saned.socket. It is iden-
- tical to the version for systemd with the support compiled in. It
+ tical to the version for systemd(1) with the support compiled in. It
shall have the following contents:
[Unit]
@@ -267,8 +271,8 @@
[Install]
WantedBy=sockets.target
- The second file to be added is saned@.service This one differes from
- the sersion with systemd integration compiled in:
+ The second file to be added is saned@.service This one differs from the
+ version with systemd(1) integration compiled in:
[Unit]
Description=Scanner Service
@@ -315,19 +319,19 @@
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration 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 directo-
- ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:"
- would result in directories "tmp/config", ".", and
- "/usr/local/etc/sane.d" being searched (in this order).
+ current working directory (".") and then in /usr/lo-
+ cal/etc/sane.d. If the value of the environment variable ends
+ with the directory separator character, then the default direc-
+ tories are searched after the explicitly specified directories.
+ For example, setting SANE_CONFIG_DIR to "/tmp/config:" would re-
+ sult in directories tmp/config, ., and /usr/local/etc/sane.d be-
+ ing searched (in this order).
SEE ALSO
sane(7), scanimage(1), xscanimage(1), xcam(1), sane-dll(5),
- sane-net(5), sane-"backendname"(5)
+ sane-net(5), sane-"backendname"(5), inetd(8), xinetd(8), systemd(1),
http://www.penguin-breeder.org/?page=sane-net
diff --git a/man/scanimage.1.html b/man/scanimage.1.html
index e6790c74..d2f407aa 100644
--- a/man/scanimage.1.html
+++ b/man/scanimage.1.html
@@ -2,7 +2,7 @@
scanimage.1
-
+
scanimage.1
@@ -28,13 +28,13 @@
DESCRIPTION
- scanimage is a command-line interface to control image acquisition
- devices such as flatbed scanners or cameras. The device is controlled
+ scanimage is a command-line interface to control image acquisition de-
+ vices such as flatbed scanners or cameras. The device is controlled
via command-line options. After command-line processing, scanimage
normally proceeds to acquire an image. The image data is written to
standard output in one of the PNM (portable aNyMaP) formats (PBM for
- black-and-white images, PGM for grayscale images, and PPM for color
- images), TIFF format (black-and-white, grayscale or color), PNG format,
+ black-and-white images, PGM for grayscale images, and PPM for color im-
+ ages), TIFF format (black-and-white, grayscale or color), PNG format,
or JPEG format (compression level 75). scanimage accesses image acqui-
sition devices through the SANE (Scanner Access Now Easy) interface and
can thus support any device for which there exists a SANE backend (try
@@ -64,10 +64,10 @@
OPTIONS
Parameters are separated by a blank from single-character options (e.g.
- -d epson) and by a "=" from multi-character options (e.g.
- --device-name=epson).
+ -d epson) and by a "=" from multi-character options (e.g. --de-
+ vice-name=epson).
- The -d or --device-name options must be followed by a SANE device-name
+ The -d or --device-name options must be followed by a SANE device-name
like `epson:/dev/sg0' or `hp:/dev/usbscanner0'. A (partial) list of
available devices can be obtained with the --list-devices option (see
below). If no device-name is specified explicitly, scanimage reads a
@@ -76,7 +76,7 @@
device.
The --format format option selects how image data is written to stan-
- dard output or the file specified by the --output-file option. format
+ dard output or the file specified by the --output-file option. format
can be pnm, tiff, png, or jpeg. If --format is not specified, PNM is
written by default.
@@ -92,64 +92,62 @@
is by its full device name. You may need to consult your system admin-
istrator to find out the names of such devices.
- The -f or --formatted-device-list option works similar to
- --list-devices, but requires a format string. scanimage replaces the
- placeholders %d %v %m %t %i %n with the device name, vendor name, model
- name, scanner type, an index number and newline respectively. The com-
- mand
+ The -f or --formatted-device-list option works similar to --list-de-
+ vices, but requires a format string. scanimage replaces the placehold-
+ ers %d %v %m %t %i %n with the device name, vendor name, model name,
+ scanner type, an index number and newline respectively. The command
- scanimage -f " scanner number %i device %d is a %t, model %m,
+ scanimage -f " scanner number %i device %d is a %t, model %m,
produced by %v "
will produce something like:
- scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
+ scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
model JX250 SCSI, produced by SHARP
- The --batch* options provide the features for scanning documents using
- document feeders. --batch [format] 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 format is not specified, the default of
- out%d.pnm (or out%d.tif for --format tiff, out%d.png for --format png
- or out%d.jpg for -- format jpeg) will be used. This option is incom-
- patible with the --output-path option. format is given as a printf
- style string with one integer parameter. --batch-start start selects
- the page number to start naming files with. If this option is not
- given, the counter will start at 1. --batch-count count specifies the
- number of pages to attempt to scan. If not given, scanimage will con-
- tinue scanning until the scanner returns a state other than OK. Not
- all scanners with document feeders signal when the ADF is empty, use
- this command to work around them. With --batch-increment increment you
- can change the amount that the number in the filename is incremented
- by. Generally this is used when you are scanning double-sided docu-
- ments on a single-sided document feeder. A specific command is pro-
- vided to aid this: --batch-double will automatically set the increment
- to 2. --batch-prompt will ask for pressing RETURN before scanning a
- page. This can be used for scanning multiple pages without an automatic
- document feeder.
+ The --batch* options provide the features for scanning documents using
+ document feeders. --batch [format] 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 format is not specified, the default of
+ out%d.pnm (or out%d.tif for --format tiff, out%d.png for --format png
+ or out%d.jpg for --format jpeg) will be used. This option is incompat-
+ ible with the --output-path option. format is given as a printf style
+ string with one integer parameter. --batch-start start selects the
+ page number to start naming files with. If this option is not given,
+ the counter will start at 1. --batch-count count specifies the number
+ of pages to attempt to scan. If not given, scanimage will continue
+ scanning until the scanner returns a state other than OK. Not all
+ scanners with document feeders signal when the ADF is empty, use this
+ command to work around them. With --batch-increment increment you can
+ change the amount that the number in the filename is incremented by.
+ Generally this is used when you are scanning double-sided documents on
+ a single-sided document feeder. A specific command is provided to aid
+ this: --batch-double will automatically set the increment to 2.
+ --batch-prompt will ask for pressing RETURN before scanning a page.
+ This can be used for scanning multiple pages without an automatic docu-
+ ment feeder.
- The --accept-md5-only option only accepts user authorization requests
- that support MD5 security. The SANE network daemon (saned) is capable
+ The --accept-md5-only option only accepts user authorization requests
+ that support MD5 security. The SANE network daemon (saned) is capable
of doing such requests. See saned(8).
- The -p or --progress option requests that scanimage prints a progress
- counter. It shows how much image data of the current image has already
+ The -p or --progress option requests that scanimage prints a progress
+ counter. It shows how much image data of the current image has already
been received by scanimage (in percent).
- The -o or --output-file option requests that scanimage saves the scan-
- ning output to the given path. This option is incompatible with the
- --batch option. The program will try to guess --format from the file
- name. If that is not possible, it will print an error message and
- exit.
+ The -o or --output-file option requests that scanimage saves the scan-
+ ning output to the given path. This option is incompatible with the
+ --batch option. The program will try to guess --format from the file
+ name. If that is not possible, it will print an error message and exit.
- The -n or --dont-scan option requests that scanimage only sets the
- options provided by the user but doesn't actually perform a scan. This
+ The -n or --dont-scan option requests that scanimage only sets the op-
+ tions provided by the user but doesn't actually perform a scan. This
option can be used to e.g. turn off the scanner's lamp (if supported by
the backend).
The -T or --test option requests that scanimage performs a few simple
sanity tests to make sure the backend works as defined by the SANE API
- (in particular the sane_read function is exercised by this test).
+ (in particular the sane_read() function is exercised by this test).
The -A or --all-options option requests that scanimage lists all avail-
able options exposed the backend, including button options. The infor-
@@ -172,7 +170,7 @@
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 DEBUG variable for the dll backend can be
- used. Example: SANE_DEBUG_DLL=3 scanimage -L.
+ used. Example: SANE_DEBUG_DLL=3 scanimage -L .
As you might imagine, much of the power of scanimage comes from the
fact that it can control any SANE backend. Thus, the exact set of com-
@@ -180,12 +178,12 @@
To see the options for a device named dev, invoke scanimage via a com-
mand-line of the form:
- scanimage --help --device-name dev
+ scanimage --help --device-name dev
The documentation for the device-specific options printed by --help is
best explained with a few examples:
- -l 0..218mm [0]
+ -l 0..218mm [0]
Top-left x position of scan area.
The description above shows that option -l expects an option
@@ -194,7 +192,7 @@
ends provide similar geometry options for top-left y position
(-t), width (-x) and height of scan-area (-y).
- --brightness -100..100% [0]
+ --brightness -100..100% [0]
Controls the brightness of the acquired image.
The description above shows that option --brightness expects an
@@ -202,17 +200,17 @@
in square brackets indicates that the current option value is 0
percent.
- --default-enhancements
+ --default-enhancements
Set default values for enhancement controls.
The description above shows that option --default-enhancements
has no option value. It should be thought of as having an imme-
- diate effect at the point of the command-line at which it
- appears. For example, since this option resets the --brightness
+ diate effect at the point of the command-line at which it ap-
+ pears. For example, since this option resets the --brightness
option, the option-pair --brightness 50 --default-enhancements
would effectively be a no-op.
- --mode Lineart|Gray|Color [Gray]
+ --mode Lineart|Gray|Color [Gray]
Selects the scan mode (e.g., lineart or color).
The description above shows that option --mode accepts an argu-
@@ -223,56 +221,56 @@
case of the spelling doesn't matter. For example, option set-
ting --mode col is identical to --mode Color.
- --custom-gamma[=(yes|no)] [inactive]
- Determines whether a builtin or a custom gamma-table
- should be used.
+ --custom-gamma[=(yes|no)] [inactive]
+ Determines whether a builtin or a custom gamma-table should be
+ used.
- The description above shows that option --custom-gamma expects
+ The description above shows that option --custom-gamma expects
either no option value, a "yes" string, or a "no" string. Spec-
- ifying the option with no value is equivalent to specifying
- "yes". The value in square-brackets indicates that the option
- is not currently active. That is, attempting to set the option
- would result in an error message. The set of available options
- typically depends on the settings of other options. For exam-
- ple, the --custom-gamma table might be active only when a
+ ifying the option with no value is equivalent to specifying
+ "yes". The value in square-brackets indicates that the option
+ is not currently active. That is, attempting to set the option
+ would result in an error message. The set of available options
+ typically depends on the settings of other options. For exam-
+ ple, the --custom-gamma table might be active only when a
grayscale or color scan-mode has been requested.
- Note that the --help option is processed only after all other
- options have been processed. This makes it possible to see the
- option settings for a particular mode by specifying the appro-
- priate mode-options along with the --help option. For example,
+ Note that the --help option is processed only after all other
+ options have been processed. This makes it possible to see the
+ option settings for a particular mode by specifying the appro-
+ priate mode-options along with the --help option. For example,
the command-line:
scanimage --help --mode color
- would print the option settings that are in effect when the
+ would print the option settings that are in effect when the
color-mode is selected.
- --gamma-table 0..255,...
+ --gamma-table 0..255,...
Gamma-correction table. In color mode this option
equally affects the red, green, and blue channels
simultaneously (i.e., it is an intensity gamma table).
- The description above shows that option --gamma-table expects
+ The description above shows that option --gamma-table expects
zero or more values in the range 0 to 255. For example, a legal
- value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
- it's cumbersome to specify long vectors in this form, the same
- can be expressed by the abbreviated form "[0]3-[9]12". What
- this means is that the first vector element is set to 3, the
+ value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
+ it's cumbersome to specify long vectors in this form, the same
+ can be expressed by the abbreviated form "[0]3-[9]12". What
+ this means is that the first vector element is set to 3, the
9-th element is set to 12 and the values in between are interpo-
- lated linearly. Of course, it is possible to specify multiple
- such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
- is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
- gamma4scanimage can be used to generate such gamma tables (see
+ lated linearly. Of course, it is possible to specify multiple
+ such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
+ is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
+ gamma4scanimage can be used to generate such gamma tables (see
gamma4scanimage(1) for details).
- --filename <string> [/tmp/input.ppm]
+ --filename <string> [/tmp/input.ppm]
The filename of the image to be loaded.
- The description above is an example of an option that takes an
+ The description above is an example of an option that takes an
arbitrary string value (which happens to be a filename). Again,
the value in brackets show that the option is current set to the
- filename /tmp/input.ppm.
+ filename /tmp/input.ppm.
@@ -284,7 +282,7 @@
FILES
/usr/local/etc/sane.d
- This directory holds various configuration files. For details,
+ This directory holds various configuration files. For details,
please refer to the manual pages listed below.
~/.sane/pass
@@ -292,12 +290,11 @@
user:password:resource
- 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
- --accept-md5-only option to avoid server-side attacks. The
- resource may contain any character but is limited to 127 charac-
- ters.
+ scanimage uses this information to answer user authorization re-
+ quests automatically. The file must have 0600 permissions or
+ stricter. You should use this file in conjunction with the --ac-
+ cept-md5-only option to avoid server-side attacks. The resource
+ may contain any character but is limited to 127 characters.
@@ -310,7 +307,7 @@
AUTHOR
David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
many others. For questions and comments contact the sane-devel mail-
- inglist (see http://www.sane-project.org/mailing-lists.html).
+ inglist (see http://www.sane-project.org/mailing-lists.html).