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

Update for sane-backends-1.0.29 

Fixes #25.
merge-requests/4/merge
Olaf Meeuwissen 2020-03-29 14:47:02 +09:00
rodzic 57982bd5b1
commit 543070deb2
98 zmienionych plików z 2567 dodań i 2164 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

2
man/gamma4scanimage.1.html
Wyświetl plik

@ -43,7 +43,7 @@
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‐
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.
<B>maxout</B> defines the maximum output value. Take a look at the output of

34
man/sane-abaton.5.html
Wyświetl plik

@ -26,13 +26,13 @@
If you own a Abaton scanner other than the ones listed above that works
with this backend, or if you own an Abaton scanner that does not work
with this backend, please contact <I>sane-devel@alioth-lists.debian.net</I>
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‐
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.
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.
@ -60,7 +60,7 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>abaton.conf</I> file is a list of device names that
correspond to Abaton scanners. Empty lines and lines starting with a
hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what consti‐
hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what consti-
tutes a valid device name.
@ -84,19 +84,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_ABATON</B>
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.
@ -127,7 +127,7 @@
<B>Implement</B> <B>non-blocking</B> <B>support</B>
<B>Finish</B> <B>reverse-engineering</B> <B>the</B> <B>MacOS</B> <B>driver</B>
This will allow me to add support for other models with reason‐
This will allow me to add support for other models with reason-
able confidence that it will work, as well as to fully exploit
the information returned by the INQUIRY command.

35
man/sane-agfafocus.5.html
Wyświetl plik

@ -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 <I>sane-devel@alioth-lists.debian.net</I>.
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
@ -50,7 +50,7 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor‐
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
@ -61,8 +61,8 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>agfafocus.conf</I> 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
@ -89,24 +89,23 @@
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‐
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‐
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
<B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
"tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
"tmp/config", ".", and "/etc/sane.d" being searched (in this or-
der).
<B>SANE_DEBUG_AGFAFOCUS</B>
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:
Number Remark
0 print important errors (printed each time)
1 print errors
2 print sense
@ -144,9 +143,9 @@
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
@ -157,15 +156,15 @@
<H2>TODO</H2><PRE>
<B>More</B> <B>scanners?</B>
The AGFA ACS and ARCUS scanners are similar to the FOCUS scan‐
The AGFA ACS and ARCUS scanners are similar to the FOCUS scan-
ners. The driver could probably be extended to support these
scanners without too many changes. I do not have access to such
scanners, and cannot add support for it. However, if you are in
possession of such a scanner, I could be helpful in adding sup‐
possession of such a scanner, I could be helpful in adding sup-
port for these scanners.
The AGFA HORIZON scanners are SCSI-2 scanners, and it would
probably be easier to support these scanners in a SCSI-2 compli‐
probably be easier to support these scanners in a SCSI-2 compli-
ant backend.
@ -176,7 +175,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Ingo Schneider and Karl Anders Øygard.
Ingo Schneider and Karl Anders <B>O</B>ygard.
10 Jul 2008 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
</PRE>

175
man/sane-apple.5.html
Wyświetl plik

@ -28,10 +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
<I>sane-devel@alioth-lists.debian.net</I>. 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 <I>sane-devel@alioth-lists.de-</I>
<I>bian.net</I>. See http://www.sane-project.org/mailing-lists.html for de-
tails on how to subscribe to sane-devel.
</PRE>
@ -40,30 +39,30 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that corâ€<C3A2>
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The <I>apple.conf</I> file is a list of options and device names that correâ€<C3A2>
spond to Apple scanners. Empty lines and lines starting with a hash
mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what constitutes
The <I>apple.conf</I> file is a list of options and device names that corre-
spond to Apple scanners. Empty lines and lines starting with a hash
mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> 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 apply just to the most recently mentioned device. Note that
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!
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
SCSI scanners are typically delivered with an ISA SCSI adapter. Unforâ€<EFBFBD>
tunately, that adapter is not worth much since it is not interrupt
SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
tunately, that adapter is not worth much since it is not interrupt
driven. It is sometimes possible to get the supplied card to work, but
without an interrupt line, scanning will put so much load on the system
that it becomes almost unusable for other tasks.
@ -72,7 +71,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/apple.conf</I>
The backend configuration file (see also description of
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-apple.a</I>
@ -86,33 +85,33 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable is list of directories where SANE
looks for the configuration file. Under UNIX directory names
are separated by a colon (`:'), under OS/2 by a semi-colon
(`;'). If SANE_CONFIG_DIR is not set, SANE defaults to searchâ€<C3A2>
ing the current working directory (".") and then /etc/sane.d.
If the value of $SANE_CONFIG_DIR ends with the separator characâ€<EFBFBD>
ter, the default directories are searched after the directory
list. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in that order).
This environment variable is list of directories where SANE
looks for the configuration file. Under UNIX directory names
are separated by a colon (`:'), under OS/2 by a semi-colon
(`;'). If SANE_CONFIG_DIR is not set, SANE defaults to 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in that order).
<B>SANE_DEBUG_APPLE</B>
Controls the debug level. A value of 255 prints all debug outâ€<EFBFBD>
put. Smaller values reduce verbosity. Requires a library comâ€<C3A2>
Controls the debug level. A value of 255 prints all debug out-
put. Smaller values reduce verbosity. Requires a library com-
piled with debug support.
</PRE>
<H2>CURRENT STATUS</H2><PRE>
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â€<C3A2>
canner) I can only develop/test for the AppleScanner effectively. Howâ€<EFBFBD>
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.
Most of the functionality is there. At least OneScanner should scan at
the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
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
could be actually usable. The ColorOneScanner needs more work. AppleSâ€<C3A2>
could be actually usable. The ColorOneScanner needs more work. AppleS-
canner is of course almost fully supported.
@ -127,85 +126,85 @@
Cannot up/download halftone patterns or calibration vectors.
<B>ColorOneScanner</B>
Cannot up/download halftone patterns, calibration vectors, cusâ€<EFBFBD>
tom Color Correction Tables (CCT) and of course custom gamma
tables.
Cannot up/download halftone patterns, calibration vectors, cus-
tom Color Correction Tables (CCT) and of course custom gamma ta-
bles.
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
Some capabilities are missing.
The above functionalities are missing because I don't have the hardware
to experiment on. Another reason is my lack of understanding as to how
or if the SANE API provide means to describe any array type besides
or if the SANE API provide means to describe any array type besides
gamma.
</PRE>
<H2>UNSUPPORTED FEATURES</H2><PRE>
The following "features" will never be supported, at least while I
The following "features" will never be supported, at least while I
maintain the sane-apple backend.
<B>NoHome</B> <B>(AppleScanner)</B>
The scanner lamp stays on and the carriage assembly remains
The scanner lamp stays on and the carriage assembly remains
where it stops at the end of the scan. After two minutes, if the
scanner does not receive another SCAN command, the lamp goes off
and the carriage returns to the home position.
<B>Compression</B> <B>(AppleScanner)</B>
The Scanner can compress data with CCITT Group III one dimenâ€<C3A2>
The Scanner can compress data with CCITT Group III one dimen-
sional algorithm (fax) and the Skip White Line algorithm.
<B>Multiple</B> <B>Windows</B> <B>(AppleScanner)</B>
AppleScanner may support multiple windows. It would be a cool
feature and a challenge for me to code if it could intermix difâ€<EFBFBD>
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.
AppleScanner may support multiple windows. It would be a cool
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 im-
possible.
<B>Scan</B> <B>Direction</B> <B>(OneScanner)</B>
It controls the scan direction. (?)
<B>Status/Reset</B> <B>Button</B> <B>(OneScanner)</B>
This option controls the status of the button on the OneScanner
This option controls the status of the button on the OneScanner
model. You can also reset the button status by software.
</PRE>
<H2>BUGS</H2><PRE>
SANE backend bugs are divided in two classes. We have <B>GUI</B> bugs and
SANE backend bugs are divided in two classes. We have <B>GUI</B> bugs and
<B>scanner</B> <B>specific</B> bugs.
We know we have a GUI bug when a parameter is not showing up when it
should (active) or vice versa. Finding out which parameters are active
across various Apple modes and models from the documentation
<B>ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher</B>â€<B>â</B>€<EFBFBD>
<B>als_Documentation/</B> 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.
We know we have a GUI bug when a parameter is not showing up when it
should (active) or vice versa. Finding out which parameters are active
across various Apple modes and models from the documentation <B>ftp://ft-</B>
<B>pdev.info.apple.com/devworld/Technical_Documentation/Peripherals_Docu-</B>
<B>mentation/</B> 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
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
scan area should be a byte multiple. In another place it says that the
scan area should be a byte multiple. In another place it says that the
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 <B>SANE</B>
API violations.
Other sources of bugs are due to scsi communication, scsi connects and
disconnects. However the classical bugs are still there. So you may en-
counter buffer overruns, null pointers, memory corruption and <B>SANE</B> API
violations.
<B>SIGSEGV</B> <B>on</B> <B>SliceBars</B>
When you try to modify the scan area from the slice bar you have
a nice little cute core dump. I don't know why. If you select
the scan area from the preview window or by hand typing the numâ€<EFBFBD>
a nice little cute core dump. I don't know why. If you select
the scan area from the preview window or by hand typing the num-
bers everything is fine. The SIGSEGV happens deep in gtk library
(gdk). I really cannot debug it.
<B>Options</B> <B>too</B> <B>much</B>
It is possible, especially for the ColorOneScanner, for the
It is possible, especially for the ColorOneScanner, for the
backend's options panel to extend beyond your screen. It happens
with mine and I am running my X Server at 1024x768. What can I
with mine and I am running my X Server at 1024x768. What can I
say? Try smaller fonts in the X server, or virtual screens.
<B>Weird</B> <B>SCSI</B> <B>behaviour</B>
@ -213,35 +212,35 @@
&gt;&gt; OS: FreeBSD 2.2.6
&gt;&gt; CC: egcs-1.02
Just wanted to follow up on this... I recently changed my SCSI
card from the Adaptec 2940UW to a dual-channel Symbios 786
chipset. When I started up SANE with your driver, I managed to
Just wanted to follow up on this... I recently changed my SCSI
card from the Adaptec 2940UW to a dual-channel Symbios 786
chipset. When I started up SANE with your driver, I managed to
scan line art drawings okay, but Gray16 scans led to a stream of
SCSI error messages on the console, ultimately hanging with a
message saying the scanner wasn't releasing the SCSI bus. This
may be that the Symbios is simply less tolerant of ancient hardâ€<EFBFBD>
SCSI error messages on the console, ultimately hanging with a
message saying the scanner wasn't releasing the SCSI bus. This
may be that the Symbios is simply less tolerant of ancient hard-
ware, or may be bugs in your driver or in SANE itself...
</PRE>
<H2>DEBUG</H2><PRE>
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.
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 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
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.
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 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, COLORONESCANNER.
If you encounter a SCSI bus error or trimmed and/or displaced images
If you encounter a SCSI bus error or trimmed and/or displaced images
please set the environment variable SANE_DEBUG_SANEI_SCSI to 255 before
sending me the report.
@ -249,7 +248,7 @@
</PRE>
<H2>TODO</H2><PRE>
<B>Non</B> <B>Blocking</B> <B>Support</B>
Make sane-apple a non blocking backend. Properly support
Make sane-apple a non blocking backend. Properly support
<B>sane_set_io_mode</B> and <B>sane_get_select_fd</B>
<B>Scan</B> Make scanning possible for all models in all supported modes.
@ -264,8 +263,8 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The sane-apple backend was written not entirely from scratch by Milon
Firikis. It is mostly based on the mustek backend from David Mosberger
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
11 Jul 2008 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>

30
man/sane-artec.5.html
Wyświetl plik

@ -44,7 +44,7 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>artec.conf</I> file are a list of device names that
correspond to Artec scanners. Empty lines and lines starting with a
hash mark (#) are ignored. See <I>sane-scsi(5)</I> on details of what consti‐
hash mark (#) are ignored. See <I>sane-scsi(5)</I> on details of what consti-
tutes a valid device name.
Sample file:
@ -79,7 +79,7 @@
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
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
(&gt;= 2.2.0) kernels using the generic NCR5380 support. You must pass
the following boot argument to the kernel: "dtc3181e=0x2c0,0"
@ -107,24 +107,23 @@
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‐
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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_ARTEC</B>
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_ARTEC values
Number Remark
0 print important errors
1 print errors
2 print sense
@ -139,12 +138,9 @@
11 print called sane-procedures
12 print sane infos
13 print sane option-control messages
50 print verbose data/debug messages
== 100 print software RGB calibration data
== 101 print raw data from scanner to artec.data.raw file
== 128 print out all messages
Example: export SANE_DEBUG_ARTEC=13
@ -152,7 +148,7 @@
</PRE>
<H2>BUGS</H2><PRE>
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

32
man/sane-artec_eplus48u.5.html
Wyświetl plik

@ -19,19 +19,19 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-artec_eplus48u</B> 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
<I>http://www.sane-project.org/sane-supported-devices.html</I>.
This is ALPHA software. Especially if you test new or untested scan‐
This is ALPHA software. Especially if you test new or untested scan-
ners, keep your hand at the scanner's plug and unplug it, if the head
bumps at the end of the scan area.
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‐
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
@ -51,10 +51,10 @@
</PRE>
<H2>FIRMWARE FILE</H2><PRE>
You need a firmware file for your scanner. That's a small file contain‐
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.
You can find it on the installation CD that was provided by the manu‐
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
Windows-driver is installed on your computer, then you can also find
the firmware file under c:\windows\system32\drivers.
@ -129,19 +129,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_ARTEC_EPLUS48U</B>
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

12
man/sane-as6e.5.html
Wyświetl plik

@ -12,23 +12,23 @@
</PRE>
<H2>NAME</H2><PRE>
sane-as6e - SANE backend for using the Artec AS6E parallel port inter‐
sane-as6e - SANE backend for using the Artec AS6E parallel port inter-
face scanner.
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-as6e</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-as6e</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to Artec AS6E flatbed scanner. <B>It</B> <B>requires</B>
<B>the</B> <B>as6edriver</B> <B>program</B> <B>in</B> <B>order</B> <B>to</B> <B>operate.</B> The as6edriver program is
<B>not</B> included with the SANE package. It can be found at
<B>http://as6edriver.sourceforge.net.</B> See the as6edriver documentation
for technical information.
The <I>as6edriver</I> program must be in the path for executables ($PATH).
Especially if you run <I>saned</I> (the SANE network scanning daemon), take
care to setup the path for <I>inetd</I> or <I>xinetd</I> correctly or place the pro‐
gram in a directory that is in the path.
The <I>as6edriver</I> program must be in the path for executables ($PATH). Es-
pecially if you run <I>saned</I> (the SANE network scanning daemon), take care
to setup the path for <I>inetd</I> or <I>xinetd</I> correctly or place the program in
a directory that is in the path.
</PRE>

50
man/sane-avision.5.html
Wyświetl plik

@ -12,7 +12,7 @@
</PRE>
<H2>NAME</H2><PRE>
sane-avision - SANE backend for original Avision and Avision OEM scan‐
sane-avision - SANE backend for original Avision and Avision OEM scan-
ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film
scanners.
@ -26,7 +26,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-avision</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to various Avision scanners and the Avi‐
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
@ -38,8 +38,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/avision.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/avision.conf</I>.
Its contents is a list of device names that correspond to Avision and
Avision compatible scanners and backend-options. Empty lines and lines
@ -47,13 +47,11 @@
is shown below:
# this is a comment
option force-a4
option force-a3
option skip-adf
option disable-gamma-table
option disable-calibration
#scsi Vendor Model Type Bus Channel ID LUN
scsi AVISION
scsi HP
@ -77,8 +75,8 @@
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.
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
@ -88,7 +86,7 @@
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
@ -105,15 +103,15 @@
Where <I>scsi-spec</I> 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‐
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 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
by the scanner, for example "HP" or "AVISION". See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
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‐
USB devices such as the HP 53xx, HP 74xx or Minolta film-scan-
ners.
<I>usb-spec</I> is the USB device name, the vendor/product ID pair or the name
@ -123,7 +121,7 @@
The program <I>sane-find-scanner</I> helps to find out the correct scsi or usb
device name.
A list with supported devices is built into the avision backend so nor‐
A list with supported devices is built into the avision backend so nor-
mally specifying an ID should not be necessary.
@ -147,19 +145,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_AVISION</B>
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. The
debug level 7 is the author's preferred value to debug backend
problems.
@ -175,12 +173,12 @@
</PRE>
<H2>MAINTAINER</H2><PRE>
René Rebe
Ren<B>e</B> Rebe
</PRE>
<H2>AUTHOR</H2><PRE>
René Rebe and Meino Christian Cramer
Ren<B>e</B> Rebe and Meino Christian Cramer
11 Jul 2008 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
</PRE>

154
man/sane-bh.5.html
Wyświetl plik

@ -19,10 +19,10 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-bh</B> library implements a SANE (Scanner Access Now Easy) backend
that provides access to Bell+Howell Copiscan II series document scanâ€<EFBFBD>
that provides access to Bell+Howell Copiscan II series document scan-
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â€<EFBFBD>
the entire series is consistent the backend should work for the follow-
ing scanner models.
COPISCAN II 6338 Duplex Scanner with ACE
@ -49,8 +49,8 @@
these features as possible.
The main technical reference used in writing this backend is the <B>Bell</B>
<B>and</B> <B>Howell</B> <B>Copiscan</B> <B>II</B> <B>Remote</B> <B>SCSI</B> <B>Controller</B> <B>(RSC)</B> <B>OEM</B> <B>Technical</B> <B>Man</B>â€<B>â</B>€<EFBFBD>
<B>ual</B> <B>Version</B> <B>1.5.</B> The Linux SCSI programming HOWTO, the SANE API docuâ€<EFBFBD>
<B>and</B> <B>Howell</B> <B>Copiscan</B> <B>II</B> <B>Remote</B> <B>SCSI</B> <B>Controller</B> <B>(RSC)</B> <B>OEM</B> <B>Technical</B> <B>Man-</B>
<B>ual</B> <B>Version</B> <B>1.5.</B> The Linux SCSI programming HOWTO, the SANE API docu-
mentation, and SANE source code were also extremely valuable resources.
The latest backend release, additional information and helpful hints
@ -73,11 +73,11 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>bh.conf</I> file is a list of device names that correâ€<EFBFBD>
The contents of the <I>bh.conf</I> file is a list of device names that corre-
spond to Bell+Howell scanners. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what
constitutes a valid device name. Additionally, options can be speciâ€<EFBFBD>
fied; these lines begin with the word "option". Each option is
described in detail below. Empty lines and lines starting with a hash
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.
@ -89,11 +89,11 @@
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,
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
options. These frames are never sent in preview mode.
frames are generated based on the compression and barcode op-
tions. These frames are never sent in preview mode.
<B>fake-inquiry</B>
This option is used for debugging purposes and its use is not
@ -123,19 +123,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_BH</B>
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.
@ -149,57 +149,57 @@
detected. The SANE frontend <B>scanadf</B> is a command line frontend
that supports multi-page scans. It has been used successfully
with this backend. The SANE frontend <B>xsane</B> is an improved GUI
frontend by Oliver Rauch. Support for multi-page scans is
included in xsane version 0.35 and above.
frontend by Oliver Rauch. Support for multi-page scans is in-
cluded in xsane version 0.35 and above.
<B>Duplex</B> <B>scanning</B>
Some models, such as the COPISCAN II 6338, support duplex scanâ€<EFBFBD>
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 <B>--duplex</B>
option). The front and back page images are delivered consecuâ€<C3A2>
This backend supports duplex scanning (with the <B>--duplex</B> op-
tion). The front and back page images are delivered consecu-
tively as if they were separately scanned pages.
<B>Hardware</B> <B>compression</B>
The scanner is capable of compressing the data into several
industry standard formats (CCITT G3, CCITT G3-2D, CCITT G4).
This results in increased performance as less data is passed
from the scanner to the host over the SCSI bus. The backend
supports these compression formats via the <B>--g31d,</B> <B>--g32d,</B>
<B>--g42d</B> options, respectively. Many SANE frontends are not
equipped to deal with these formats, however. The SANE frontend
<B>scanadf</B> supports these optional frame formats. The compressed
image data is written directly to a file and can then be proâ€<C3A2>
cessed by a scan-script using the <B>--scan-script</B> option. Examâ€<C3A2>
ples of this are given on the scanadf homepage.
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 <B>--g31d,</B> <B>--g32d,</B> <B>--g42d</B> op-
tions, respectively. Many SANE frontends are not equipped to
deal with these formats, however. The SANE frontend <B>scanadf</B>
supports these optional frame formats. The compressed image
data is written directly to a file and can then be processed by
a scan-script using the <B>--scan-script</B> option. Examples of this
are given on the scanadf homepage.
<B>Automatic</B> <B>Border</B> <B>Detection</B>
The scanner can automatically detect the paper size and adjust
the scanning window geometry appropriately. The backend supâ€<EFBFBD>
the scanning window geometry appropriately. The backend sup-
ports this useful feature with the <B>--autoborder</B> option. It is
enabled by default.
<B>Batch</B> <B>Mode</B> <B>Scanning</B>
The batch scan mode allows for maximum throughput. The Set Winâ€<EFBFBD>
The batch scan mode allows for maximum throughput. The Set Win-
dow parameters must remain constant during the entire batch.
<B>Icon</B> <B>Generation</B>
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.
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.
<B>Multiple</B> <B>Sections</B>
Multiple sections (scanning sub-windows) can be defined for the
front and back pages. Each section can have different characâ€<EFBFBD>
teristics (e.g. geometry, compression). The sections are
returned as if they were separately scanned images. Additionâ€<EFBFBD>
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.
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.
<B>Support</B> <B>Barcode/Patchcode</B> <B>Decoding</B>
The RSC unit can recognize Bar and Patch Codes of various types
@ -208,7 +208,7 @@
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â€<EFBFBD>
on the content of this text frame as well as some barcode decod-
ing examples can be found on the backend homepage.
@ -219,12 +219,12 @@
a time. While the code generally supports this as well, the
<B>--barcode-search-bar</B> 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.
comma separated list of barcode type codes could be added to ad-
dress this.
<B>Scanning</B> <B>a</B> <B>fixed</B> <B>number</B> <B>of</B> <B>pages</B> <B>in</B> <B>batch</B> <B>mode</B>
The separation of front and back end functionality in SANE
presents a problem in supporting the 'cancel batch' functionalâ€<EFBFBD>
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
@ -238,8 +238,8 @@
<B>Revision</B> <B>1.2</B> <B>Patch</B> <B>detector</B>
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
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.
@ -248,8 +248,8 @@
<B>Scan</B> <B>Mode</B> <B>Options:</B>
<B>--preview[=(yes|no)]</B> <B>[no]</B>
Request a preview-quality scan. When preview is set to yes
image compression is disabled and the image is delivered in a
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.
<B>--mode</B> <B>lineart|halftone</B> <B>[lineart]</B>
@ -300,8 +300,8 @@
<B>--source</B> <B>Automatic</B> <B>Document</B> <B>Feeder|Manual</B> <B>Feed</B> <B>Tray</B> <B>[Automatic</B> <B>Document</B>
<B>Feeder]</B>
Selects the scan source (such as a document feeder). This
option is provided to allow multiple image scans with xsane; it
Selects the scan source (such as a document feeder). This op-
tion is provided to allow multiple image scans with xsane; it
has no other purpose.
<B>--batch[=(yes|no)]</B> <B>[no]</B>
@ -328,20 +328,20 @@
on the scanner model.
<B>--check-adf[=(yes|no)]</B> <B>[no]</B>
Check ADF Status prior to starting scan using the OBJECT POSIâ€<EFBFBD>
Check ADF Status prior to starting scan using the OBJECT POSI-
TION command. Note that this feature requires RSC firmware
level 1.5 or higher and dip switch 4 must be in the on position.
NOTE: This option has not been tested extensively and may proâ€<EFBFBD>
NOTE: This option has not been tested extensively and may pro-
duce undesirable results.
<B>Enhancement:</B>
<B>--control-panel[=(yes|no)]</B> <B>[yes]</B>
Enables the scanner's control panel for selecting image enhanceâ€<EFBFBD>
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.
Enables the scanner's control panel for selecting image enhance-
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.
<B>--ace-function</B> <B>-4..4</B> <B>[3]</B>
Specify the Automatic Contrast Enhancement (ACE) Function.
@ -416,13 +416,13 @@
<B>--barcode-search-timeout</B> <B>20..65535us</B> <B>[10000]</B>
Sets the timeout for barcode searching in milliseconds. When
the timeout expires, the decoder will stop trying to decode barâ€<EFBFBD>
the timeout expires, the decoder will stop trying to decode bar-
codes.
<B>--section</B> <B>&lt;string&gt;</B> <B>[]</B>
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):
<B>&lt;width&gt;x&lt;height&gt;+&lt;top-left-x&gt;+&lt;top-left-y&gt;[:functioncode...]</B>
@ -457,7 +457,7 @@
<B>g32d</B> - use Group 3 2 dimensions image compression
<B>g42d</B> - use Group 4 2 dimensions image compression
If you omit a compression functioncode, the full page compression setâ€<EFBFBD>
If you omit a compression functioncode, the full page compression set-
ting is used. If you specify multiple compression functioncodes, only
the last one is used.
@ -472,7 +472,7 @@
Specifies the maximum number of bars in a Bar/Patch code.
<B>--barcode-contrast</B> <B>0..6</B> <B>[3]</B>
Specifies the image contrast used in decoding. Use higher valâ€<EFBFBD>
Specifies the image contrast used in decoding. Use higher val-
ues when there are more white pixels in the code.
<B>--barcode-patchmode</B> <B>0..1</B> <B>[0]</B>
@ -486,8 +486,8 @@
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
<I>sane-devel@alioth-lists.debian.net</I>.
send a report detailing the conditions surrounding the bug to <I>sane-de-</I>
<I>vel@alioth-lists.debian.net</I>.
</PRE>
@ -498,7 +498,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
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â€<EFBFBD>
backend by Feico W. Dillema and the bnhscan program by Sean Reifschnei-
der of tummy.com ltd. Some 8000 enhancements added by Mark Temple.
10 Jul 2008 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>

22
man/sane-canon.5.html
Wyświetl plik

@ -29,16 +29,16 @@
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
information.
the manual pages for sane-canon_pp and sane-canon630u for further in-
formation.
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 &lt;mpd@rzg.mpg.de&gt;; for questions concerning the FB620 and
@ -53,8 +53,8 @@
and blue). It is recommended to use the automatic exposure controls of
the frontend xsane 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-&gt;Enhance-&gt;Sharpen" at about 40
@ -88,8 +88,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_CANON</B>
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

34
man/sane-canon630u.5.html
Wyświetl plik

@ -26,7 +26,7 @@
Color scanning is supported at 75, 150, 300, and 600 dpi, and gamma and
analog gain are adjustable.
TESTERS ARE WELCOME. Send your bug reports and comments to Nathan Rutâ€<EFBFBD>
TESTERS ARE WELCOME. Send your bug reports and comments to Nathan Rut-
man &lt;nthn1@yahoo.com&gt;
@ -36,7 +36,7 @@
correspond to Canon USB scanners. Empty lines and lines starting with
a hash mark (#) are ignored. Only one device name can be listed in
<I>canon630u.conf</I>. The program <I>sane-find-scanner</I> helps to find out the
correct device. Under Linux, such a device name could be <I>/dev/usb/scanâ</I>€<EFBFBD>
correct device. Under Linux, such a device name could be <I>/dev/usb/scan-</I>
<I>ner0</I> for example. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
This product-specific scanner driver uses the lower-level kernel USB
@ -52,15 +52,15 @@
driver. So things like the calibration procedure I kind of made up; it
seems to work for my scanner. If you have complaints, let me know.
This driver requires the ability to send USB Control Messages, availâ€<EFBFBD>
This driver requires the ability to send USB Control Messages, avail-
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
seems to be a hardware specific issue, although I don't know what ex-
actly 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 &gt; /dev/null"
version from /var/log/messages, and the output from "SANE_DE-
BUG_CANON630U=12 scanimage &gt; /dev/null"
</PRE>
@ -88,19 +88,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_CANON630U</B>
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:

38
man/sane-canon_dr.5.html
Wyświetl plik

@ -20,8 +20,8 @@
The <B>sane-canon_dr</B> library implements a SANE (Scanner Access Now Easy)
backend which provides access to some Canon DR-series scanners.
This document describes backend version 51, which shipped with SANE
1.0.25.
This document describes backend version 57, which shipped with SANE
1.0.28.
</PRE>
@ -30,7 +30,7 @@
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‐
This backend may support other Canon scanners. The best way to deter-
mine level of support is to test the scanner directly, or to collect a
trace of the windows driver in action. Please contact the author for
help or with test results.
@ -38,7 +38,7 @@
In general, the larger machines (DR-4000 and up) which have been tested
use a fairly complete protocol, with hardware support for many modes,
resolutions and features. The smaller machines have many limitations,
like missing horizontal resolutions, missing binary mode, always scan‐
like missing horizontal resolutions, missing binary mode, always scan-
ning full-width, etc. There is code in the backend to address these
problems, but there seems to be no way to detect if they are required,
so they must be hard-coded.
@ -67,17 +67,17 @@
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‐
Other options will be available based on the capabilities of the scan-
ner: enhancement, compression, buttons and sensors, etc.
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
@ -89,12 +89,12 @@
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‐
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.
may be settable only when another option has been set, and that ad-
vanced options may be hidden by some frontend programs.
</PRE>
@ -144,7 +144,7 @@
"option model-name [string of text]"
"option version-name [string of text]"
These options can be used collectively to override the values
provided by the scanner, or to provide the values when the scan‐
provided by the scanner, or to provide the values when the scan-
ner cannot.
"option padded-read [0|1]"
@ -181,8 +181,8 @@
<H2>KNOWN ISSUES</H2><PRE>
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.
be enabled. Many machines have not been tested. Their protocol is un-
known.
</PRE>
@ -192,10 +192,10 @@
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‐
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‐
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum-
melen, Thanos Diacakis and Junren Shi for testing and feedback.

58
man/sane-canon_pp.5.html
Wyświetl plik

@ -32,12 +32,12 @@
No USB scanners are supported and there are no plans to support them in
the future. Other projects are working on support for USB scanners.
See the <B>PROJECTS</B> 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.
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‐
back is still appreciated. Please send any bug reports to the main‐
it as reliable as possible, it will not always work as expected. Feed-
back is still appreciated. Please send any bug reports to the main-
tainers as listed on the web page (listed in <B>SEE</B> <B>ALSO</B> below).
@ -49,7 +49,7 @@
On Linux 2.4 kernels this will be of the form <I>parport0</I> or older (2.2
and before) kernels may produce names like <I>0x378</I> (the base address of
your port) or simply <I>0</I> depending on your module configuration. Check
the contents of <I>/proc/parport</I> if it exists. If you don't want to spec‐
the contents of <I>/proc/parport</I> 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.
@ -71,11 +71,11 @@
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‐
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 <B>init_mode</B> <I>&lt;AUTO|FB620P|FB630P&gt;</I> <I>[portname]</I> defines which initial‐
Option <B>init_mode</B> <I>&lt;AUTO|FB620P|FB630P&gt;</I> <I>[portname]</I> 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
this may cause problems on multi-scanner systems. You may have as many
@ -88,7 +88,7 @@
Option <B>force_nibble</B> 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‐
issue of ECP mode being reported to work by the library, then not work-
ing.
@ -121,19 +121,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_CANON_PP</B>
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
@ -150,8 +150,8 @@
<B>Descreen</B> <B>Mode</B>
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.
an anti-aliasing filter. Again, it seems to be implemented en-
tirely in software, so GIMP is your best bet for now.
<B>Gamma</B> <B>Tables</B>
This is under investigation, but for now only a simple gamma
@ -165,10 +165,10 @@
configuration file to include <B>force_nibble</B> , 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
@ -180,7 +180,7 @@
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‐
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
@ -192,13 +192,13 @@
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
and blue coloured items will appear darker than normal. For high-accu‐
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.
<B>FB620P/FB320P</B> <B>Caveats</B>
These models can not be reset in the same way as the others. The win‐
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!
@ -219,7 +219,7 @@
This backend is primarily the work of Simon Krix (Reverse Engineering),
and Matthew Duggan (SANE interface).
Many thanks to Kevin Easton for his comments and help, and Kent A. Sig‐
Many thanks to Kevin Easton for his comments and help, and Kent A. Sig-
norini for his help with the N340P.
11 Jul 2008 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>

8
man/sane-cardscan.5.html
Wyświetl plik

@ -21,7 +21,7 @@
backend which provides access to the Corex CardScan 800c &amp; 600c small-
format scanners.
The backend supports only grayscale and color modes and media of (theo‐
The backend supports only grayscale and color modes and media of (theo-
retically) infinite length.
This backend may support other scanners. The best way to determine
@ -58,12 +58,12 @@
Some systems use a kernel driver to access usb scanners. This
method is untested.
Additionally, there are two configuration options that control the pro‐
Additionally, there are two configuration options that control the pro-
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)

6
man/sane-config.1.html
Wyświetl plik

@ -34,7 +34,7 @@
option at the same time):
<B>--version</B>
Print the currently installed version of libsane on the stan‐
Print the currently installed version of libsane on the stan-
dard output.
<B>--help</B> <B>OPTION</B>
@ -45,8 +45,8 @@
<B>SANE</B> frontend to libsane.
<B>--ldflags</B>
Print the linker flags that are necessary to link a <B>SANE</B> fron‐
tend to libsane.
Print the linker flags that are necessary to link a <B>SANE</B> front-
end to libsane.
<B>--cflags</B>
Print the compiler flags that are necessary to compile a <B>SANE</B>

14
man/sane-coolscan.5.html
Wyświetl plik

@ -35,8 +35,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/coolscan.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/coolscan.conf</I>.
Its contents is a list of device names that correspond to Nikon
Coolscan scanners. Empty lines and lines starting with a hash mark (#)
@ -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.
</PRE>
@ -77,8 +77,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN</B>
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
@ -93,7 +93,7 @@
</PRE>
<H2>BUGS</H2><PRE>
The autofocus command does not work with some SCSI card/driver combina‐
The autofocus command does not work with some SCSI card/driver combina-
tions
The gamma table is not implemented for the LS1000 yet.

52
man/sane-coolscan2.5.html
Wyświetl plik

@ -20,9 +20,9 @@
The <B>sane-coolscan2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Nikon Coolscan film scanners. Some
functions of this backend should be considered <B>beta-quality</B> 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
day. Please report any strange behaviour to the maintainer of the back‐
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.
At present, the following scanners are known to work with this backend:
@ -42,15 +42,15 @@
</PRE>
<H2>OPTIONS</H2><PRE>
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 or through GUI elements in xs-
canimage or xsane.
Valid command line options and their syntax can be listed by using
scanimage --help -d coolscan2:&lt;interface&gt;:&lt;device&gt;
where &lt;interface&gt; and &lt;device&gt; 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.
@ -66,15 +66,15 @@
start the frontend).
<I>--subframe</I> <I>&lt;x&gt;</I>
This option shifts the scan window by the specified amount
(default unit is mm).
This option shifts the scan window by the specified amount (de-
fault unit is mm).
<I>--infrared=yes/no</I>
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‐
perform a batch scan with batch-count=2 to obtain the IR infor-
mation.
<I>--depth</I> <I>&lt;n&gt;</I>
@ -88,7 +88,7 @@
<I>--autofocus</I>
Perform autofocus operation. Unless otherwise specified by the
other options ( <I>--focus-on-centre</I> and friends), focusing is per‐
other options ( <I>--focus-on-centre</I> and friends), focusing is per-
formed on the centre of the selected scan area.
<I>--ae-wb</I>
@ -98,7 +98,7 @@
each channel separately.
<I>--exposure</I>
Multiply all exposure times with this value. This allows expo‐
Multiply all exposure times with this value. This allows expo-
sure correction without modifying white balance.
<I>--load</I> Load the next slide when using the slide loader.
@ -118,7 +118,7 @@
<H2>CONFIGURATION FILE</H2><PRE>
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‐
supported connection types SCSI, USB, and IEEE 1394, the default con-
figuration file supplied with the SANE distribution should work without
being edited.
@ -126,7 +126,7 @@
all entries are case-sensitive:
<I>blank</I> <I>or</I> <I>starting</I> <I>with</I> <I>a</I> <I>'#'</I> <I>character</I>
These lines are ignored, thus '#' can be used to include com‐
These lines are ignored, thus '#' can be used to include com-
ments.
<I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
@ -158,8 +158,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN2</B>
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.
@ -171,12 +171,12 @@
</PRE>
<H2>BUGS</H2><PRE>
Currently, the SANE protocol does not allow automatically updating
options whenever the hardware changes. Thus the number of choices for
the <B>--frame</B> 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
<B>--frame</B> 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
@ -184,14 +184,14 @@
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.
</PRE>
<H2>AUTHORS</H2><PRE>
The backend is written and maintained by András Major
(andras@users.sourceforge.net).
The backend is written and maintained by Andr<B>a</B>s Major (an-
dras@users.sourceforge.net).
11 Jul 2008 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
</PRE>

48
man/sane-coolscan3.5.html
Wyświetl plik

@ -20,8 +20,8 @@
The <B>sane-coolscan3</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Nikon Coolscan film scanners. Some
functions of this backend should be considered <B>beta-quality</B> 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,22 +35,22 @@
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.
</PRE>
<H2>OPTIONS</H2><PRE>
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 or through GUI elements in xs-
canimage or xsane.
Valid command line options and their syntax can be listed by using
scanimage --help -d coolscan3:&lt;interface&gt;:&lt;device&gt;
where &lt;interface&gt; and &lt;device&gt; 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.
@ -66,15 +66,15 @@
start the frontend).
<I>--subframe</I> <I>&lt;x&gt;</I>
This option shifts the scan window by the specified amount
(default unit is mm).
This option shifts the scan window by the specified amount (de-
fault unit is mm).
<I>--infrared=yes/no</I>
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‐
perform a batch scan with batch-count=2 to obtain the IR infor-
mation.
<I>--depth</I> <I>&lt;n&gt;</I>
@ -88,7 +88,7 @@
<I>--autofocus</I>
Perform autofocus operation. Unless otherwise specified by the
other options ( <I>--focus-on-centre</I> and friends), focusing is per‐
other options ( <I>--focus-on-centre</I> and friends), focusing is per-
formed on the centre of the selected scan area.
<I>--ae-wb</I>
@ -98,7 +98,7 @@
each channel separately.
<I>--exposure</I>
Multiply all exposure times with this value. This allows expo‐
Multiply all exposure times with this value. This allows expo-
sure correction without modifying white balance.
<I>--load</I> Load the next slide when using the slide loader.
@ -118,7 +118,7 @@
<H2>CONFIGURATION FILE</H2><PRE>
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‐
supported connection types SCSI, USB, and IEEE 1394, the default con-
figuration file supplied with the SANE distribution should work without
being edited.
@ -126,7 +126,7 @@
all entries are case-sensitive:
<I>blank</I> <I>or</I> <I>starting</I> <I>with</I> <I>a</I> <I>'#'</I> <I>character</I>
These lines are ignored, thus '#' can be used to include com‐
These lines are ignored, thus '#' can be used to include com-
ments.
<I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
@ -158,8 +158,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_COOLSCAN3</B>
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.
@ -171,12 +171,12 @@
</PRE>
<H2>BUGS</H2><PRE>
Currently, the SANE protocol does not allow automatically updating
options whenever the hardware changes. Thus the number of choices for
the <B>--frame</B> 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
<B>--frame</B> 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
@ -191,7 +191,7 @@
</PRE>
<H2>AUTHORS</H2><PRE>
coolscan3 written by A. Zummo (a.zummo@towertech.it), based heavily on
coolscan2 written by András Major (andras@users.sourceforge.net).
coolscan2 written by Andr<B>a</B>s Major (andras@users.sourceforge.net).
11 Jul 2008 <B><A HREF="sane-coolscan3.5.html">sane-coolscan3(5)</A></B>
</PRE>

24
man/sane-dc210.5.html
Wyświetl plik

@ -18,13 +18,13 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc210</B> 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!!
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con‐
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
@ -34,7 +34,7 @@
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‐
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
115200.
@ -80,15 +80,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DC210</B>
If the library was compiled with debugging support enabled, this

30
man/sane-dc240.5.html
Wyświetl plik

@ -18,13 +18,13 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc240</B> 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!!
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con‐
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
@ -36,7 +36,7 @@
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
@ -80,15 +80,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DC240</B>
If the library was compiled with debugging support enabled, this
@ -114,9 +114,9 @@
</PRE>
<H2>BUGS</H2><PRE>
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.

28
man/sane-dc25.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dc25</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-dc25</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to Kodak DC20 and DC25 cameras. At present,
only the DC25 has been tested, but since the code is based on a DC20
interface program, it is likely to work for that model also.
@ -25,7 +25,7 @@
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con‐
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
@ -35,15 +35,15 @@
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‐
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
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:
@ -74,15 +74,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DC25</B>
If the library was compiled with debugging support enabled, this
@ -106,7 +106,7 @@
Known bugs/limitations are:
I haven't figured out how to trigger an option reload following a
"scan." This causes problems when a new picture is snapped for exam‐
"scan." This causes problems when a new picture is snapped for exam-
ple, the slider that is used to select the picture from the camera may
not be updated immediately.

55
man/sane-dll.5.html
Wyświetl plik

@ -17,14 +17,14 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dll</B> library implements a SANE (Scanner Access Now Easy) backâ€<EFBFBD>
The <B>sane-dll</B> 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 <B>sane-dll</B>
library is built or, on systems that support dynamic loading of shared
These backends may either be pre-loaded at the time the <B>sane-dll</B> 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â€<EFBFBD>
adding support for a new backend simply involves installing the rele-
vant library in <I>/usr/local/lib/sane</I> and adding an entry to the <I>dll.conf</I>
configuration file. In other words, no applications need to be modiâ€<EFBFBD>
configuration file. In other words, no applications need to be modi-
fied or recompiled to add support for new devices.
@ -45,8 +45,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dll.conf</I> 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
@ -61,17 +61,17 @@
They shall follow the format conventions as apply for <I>dll.conf.</I>
Note that backends that were pre-loaded when building this library do
not have to be listed in this configuration file. That is, if a backâ€<EFBFBD>
not have to be listed in this configuration file. That is, if a back-
end was preloaded, then that backend will always be present, regardless
of whether it's listed in the configuration file or not.
The list of preloaded backends is determined by macro <B>PRELOADABLE_BACK</B>â€<B>â</B>€<EFBFBD>
The list of preloaded backends is determined by macro <B>PRELOADABLE_BACK-</B>
<B>ENDS</B> in file backend/Makefile.in of the SANE source code distribution.
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 <I>dll.aliases</I>. It can contain
entries of the form
Aliases are defined in the config file <I>dll.aliases</I>. 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.
</PRE>
@ -101,7 +100,7 @@
The list of aliased or hidden backends.
<I>/usr/local/etc/sane.d/dll.conf</I>
The backend configuration file (see also description of
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/lib/sane/libsane-dll.a</I>
@ -117,21 +116,21 @@
<B>SANE_CONFIG_DIR</B>
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DLL</B>
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

30
man/sane-dmc.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-dmc</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-dmc</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to the Polaroid Digital Microscope Camera.
@ -27,7 +27,7 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre‐
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a generic SCSI
device or a symlink to such a device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
@ -35,7 +35,7 @@
</PRE>
<H2>IMAGING MODES</H2><PRE>
The Polaroid DMC supports a number of imaging modes. This driver sup‐
The Polaroid DMC supports a number of imaging modes. This driver sup-
ports five of the imaging modes:
<B>Full</B> <B>Frame</B>
@ -76,7 +76,7 @@
shutter speed is quantized in units of 32 microseconds.
<B>White</B> <B>Balance</B>
You can choose one of "Daylight", "Incandescent" or "Fluores‐
You can choose one of "Daylight", "Incandescent" or "Fluores-
cent" white balances. This setting more-or-less corresponds to
the "Color Temperature" settings on Polaroid's Windows and Mac
software.
@ -84,7 +84,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>dmc.conf</I> file is a list of device names that corre‐
The contents of the <I>dmc.conf</I> file is a list of device names that corre-
spond to DMC scanners. Empty lines and lines starting with a hash mark
(#) are ignored. A sample configuration file is shown below:
@ -113,19 +113,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_DMC</B>
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.

28
man/sane-epjitsu.5.html
Wyświetl plik

@ -26,11 +26,11 @@
<H2>HARDWARE SUPPORT</H2><PRE>
These scanners are fairly limited, only supporting a couple of modes
and resolutions, and always scanning full width. The backend supports
missing modes (binary, grayscale) and intermediate resolutions in soft‐
missing modes (binary, grayscale) and intermediate resolutions in soft-
ware, but provides only minimal scan area controls. See <B>KNOWN</B> <B>ISSUES.</B>
This backend may support other scanners. If physical inspection reveals
an Epson chipset, please contact the author for instructions on col‐
an Epson chipset, please contact the author for instructions on col-
lecting a USB trace under Windows to verify.
@ -38,8 +38,8 @@
<H2>OPTIONS</H2><PRE>
A limited effort has been made to expose the standard options to the
API. This allows a frontend to set resolution, color mode, and choose
the ADF setting. The epjitsu backend supports the following basic
options for most scanners:
the ADF setting. The epjitsu backend supports the following basic op-
tions for most scanners:
source s
Selects the source for the scan. Options may include "Flatbed",
@ -51,19 +51,19 @@
resolution, y-resolution
Controls scan resolution. Setting --resolution also sets
--y-resolution, though this behavior is overridden by some fron‐
tends.
--y-resolution, though this behavior is overridden by some
frontends.
Other options will be available based on the capabilities of the scan‐
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.
may appear only when another option has been set, and that advanced op-
tions may be hidden by the frontend.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
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‐
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
the frontend starts. If the configuration file is missing, the backend
@ -81,13 +81,13 @@
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.
<B>Note:</B> This firmware is a copyrighted work of Fujitsu, so cannot be pro‐
<B>Note:</B> This firmware is a copyrighted work of Fujitsu, so cannot be pro-
vided by the backend or the author. Please do not ask.
<B>Note:</B> These scanners REQUIRE a firmware file to function. See the sup‐
<B>Note:</B> These scanners REQUIRE a firmware file to function. See the sup-
plied configuration file for more detail.
<B>Note:</B> This option may appear multiple times in the configuration file.

80
man/sane-epson.5.html
Wyświetl plik

@ -19,10 +19,10 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-epson</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Epson flatbed scanners. Some functions
of this backend should be considered <B>beta-quality</B> software! Most func‐
of this backend should be considered <B>beta-quality</B> 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‐
day. Please report any strange behavior to the maintainer of the back-
end.
At present, the following scanners are known to work with this backend:
@ -61,7 +61,7 @@
</PRE>
<H2>OPTIONS</H2><PRE>
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in pro‐
line options to programs like scanimage or through GUI elements in pro-
grams like xscanimage or xsane.
Valid command line options and their syntax can be listed by using
@ -79,18 +79,18 @@
The <I>--depth</I> 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 <I>--halftoning</I> 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".
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 <I>--dropout</I> switch selects the so called dropout color. Valid
options are None, Red, Green and Blue. The default is None. The
@ -111,7 +111,7 @@
The <I>--gamma-correction</I> switch controls the scanner's internal
gamma correction. Valid options are "Default", "User defined",
"High density printing" "Low density printing" and "High con‐
"High density printing" "Low density printing" and "High con-
trast printing".
The <I>--color-correction</I> switch controls the scanner's internal
@ -122,7 +122,7 @@
The <I>--resolution</I> 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‐
be displayed using the "--help -d epson" parameters to scanim-
age.
The <I>--mirror</I> option controls the way the image is scanned. By
@ -134,13 +134,13 @@
speed up the scan if this option is supported.
The <I>--auto-area-segmentation</I> 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".
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 <I>--gamma-table</I> parameter can be used to download a user
defined gamma table. The option takes 256 values from the range
The <I>--gamma-table</I> 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.
@ -161,7 +161,7 @@
defined color correction. Values are specified as integers in
the range -127..127.
The <I>--preview</I> option requests a preview scan. The frontend soft‐
The <I>--preview</I> option requests a preview scan. The frontend soft-
ware automatically selects a low resolution. Valid options are
"yes" and "no". The default is "no".
@ -170,17 +170,17 @@
the default is "no".
The geometry options <I>-l</I> <I>-t</I> <I>-x</I> <I>-y</I> 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 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 <I>--quick-format</I> 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 <I>--source</I> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <I>--source</I> option selects the scan source. Valid options de-
pend on the installed options. The default is "Flatbed".
The <I>--auto-eject</I> option will eject a page after scanning from
the document feeder.
@ -192,10 +192,10 @@
The <I>--focus-position</I> 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‐
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‐
option is only functional for selected scanners, all other scan-
ners will ignore this option.
@ -204,8 +204,8 @@
The configuration file /usr/local/etc/sane.d/epson.conf specifies the
device(s) that the backend will use. Possible connection types are:
<I>SCSI</I> This is the default, and if nothing else is specified the back‐
end software will open a given path as SCSI device. More infor‐
<I>SCSI</I> 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
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
Usually SCSI scanners are configured with a line "scsi EPSON" in
@ -241,14 +241,14 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSON</B>
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.
<B>SANE_DEBUG_EPSON_SCSI</B>
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.
<B>SANE_EPSON_CMD_LVL</B>
@ -274,16 +274,16 @@
</PRE>
<H2>UNSUPPORTED DEVICES</H2><PRE>
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‐
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).
The Perfection 600, Perfection 650, Perfection 660, Perfection 1250 and
Perfection 1260 are not supported by this backend.

96
man/sane-epson2.5.html
Wyświetl plik

@ -19,15 +19,15 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-epson2</B> 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 <B>sane-epson</B> and <B>sane-epson2</B> 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
<I>dll.conf</I> or perhaps by commenting out the options in <I>epson.conf</I> or
<I>epson2.conf.</I>
Because <B>sane-epson</B> and <B>sane-epson2</B> 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
<I>dll.conf</I> or perhaps by commenting out the options in <I>epson.conf</I> or <I>ep-</I>
<I>son2.conf.</I>
At present, the following scanners are known to work with this backend:
@ -101,7 +101,7 @@
</PRE>
<H2>OPTIONS</H2><PRE>
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in pro‐
line options to programs like scanimage or through GUI elements in pro-
grams like xscanimage or xsane.
Valid command line options and their syntax can be listed by using
@ -119,18 +119,18 @@
The <I>--depth</I> 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 <I>--halftoning</I> 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".
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 <I>--dropout</I> switch selects the so called dropout color. Valid
options are None, Red, Green and Blue. The default is None. The
@ -151,7 +151,7 @@
The <I>--gamma-correction</I> switch controls the scanner's internal
gamma correction. Valid options are "Default", "User defined",
"High density printing" "Low density printing" and "High con‐
"High density printing" "Low density printing" and "High con-
trast printing".
The <I>--color-correction</I> switch controls the scanner's internal
@ -162,7 +162,7 @@
The <I>--resolution</I> 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‐
be displayed using the "--help -d epson" parameters to scanim-
age.
The <I>--threshold</I> switch selects the minimum brightness to get a
@ -173,10 +173,10 @@
Valid options are "yes" and "no". The default is "no".
The <I>--auto-area-segmentation</I> 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".
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 <I>--red-gamma-table</I> parameter can be used to download a user
defined gamma table for the red channel. The valid options are
@ -199,17 +199,17 @@
defined color correction. Values are specified as integers in
the range -127..127.
The <I>--preview</I> option requests a preview scan. The frontend soft‐
The <I>--preview</I> 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 <I>-l</I> <I>-t</I> <I>-x</I> <I>-y</I> 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 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 <I>--source</I> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <I>--source</I> option selects the scan source. Valid options de-
pend on the installed options. The default is "Flatbed".
The <I>--auto-eject</I> option will eject a page after scanning from
the document feeder.
@ -221,10 +221,10 @@
The <I>--focus-position</I> 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‐
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‐
option is only functional for selected scanners, all other scan-
ners will ignore this option.
The <I>--bay</I> option selects which bay to scan
@ -239,8 +239,8 @@
The configuration file /usr/local/etc/sane.d/epson2.conf specifies the
device(s) that the backend will use. Possible connection types are:
<I>SCSI</I> This is the default, and if nothing else is specified the back‐
end software will open a given path as SCSI device. More infor‐
<I>SCSI</I> 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
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
Usually SCSI scanners are configured with a line "scsi EPSON" in
@ -280,21 +280,21 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSON2</B>
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.
<B>SANE_DEBUG_EPSON2_SCSI</B>
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.
<B>SANE_DEBUG_EPSON2_NET</B>
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.
<B>SANE_EPSON2_CMD_LVL</B>
This allows one to override the function or command level that
@ -319,16 +319,16 @@
</PRE>
<H2>UNSUPPORTED DEVICES</H2><PRE>
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‐
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).
</PRE>

22
man/sane-epsonds.5.html
Wyświetl plik

@ -35,8 +35,8 @@
The <I>--depth</I> 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.
@ -44,16 +44,16 @@
The <I>--resolution</I> 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‐
be displayed using the "--help -d epson" parameters to scanim-
age.
The geometry options <I>-l</I> <I>-t</I> <I>-x</I> <I>-y</I> 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 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 <I>--source</I> option selects the scan source. Valid options
depend on the installed options. The default is "Flatbed".
The <I>--source</I> option selects the scan source. Valid options de-
pend on the installed options. The default is "Flatbed".
The <I>--eject</I> option ejects the sheet in the ADF.
@ -89,10 +89,10 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_EPSONDS</B>
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‐
Smaller levels reduce verbosity. Values around 11-16 will usu-
allybe enough for a bug report.

70
man/sane-escl.5.html 100644
Wyświetl plik

@ -0,0 +1,70 @@
<HTML>
<HEAD>
<TITLE>sane-escl.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-escl.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-escl.5.html">sane-escl(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-escl.5.html">sane-escl(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-escl - SANE backend for eSCL scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-escl</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to eSCL protocol scanners.
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 <I>https://support.apple.com/en-us/HT201311</I>. While
these devices are expected to work, your mileage may vary.
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/escl.conf</I>
The backend configuration file.
<I>/usr/local/lib/sane/libsane-escl.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-escl.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_ESCL</B>
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.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>
</PRE>
<H2>AUTHORS</H2><PRE>
Touboul Nathane, Thierry HUCHARD
14 Dec 2019 <B><A HREF="sane-escl.5.html">sane-escl(5)</A></B>
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>

82
man/sane-find-scanner.1.html
Wyświetl plik

@ -17,74 +17,76 @@
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>sane-find-scanner</B> [<B>-h</B>|<B>-?</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<B>-F</B> <I>filename</I>] [<I>devname</I>]
<B>sane-find-scanner</B> [<B>-?</B>|<B>-h</B>|<B>--help</B>] [<B>-v</B>] [<B>-q</B>] [<B>-p</B>] [<B>-f</B>] [<B>-F</B> <I>filename</I>] [<I>de-</I>
<I>vname</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>sane-find-scanner</B> is a command-line tool to find SCSI and USB scanners
and determine their Unix device files. Its primary aim is to make sure
<B>sane-find-scanner</B> is a command-line tool to find SCSI and USB scanners
and determine their Unix device files. Its primary aim is to make sure
that scanners can be detected by SANE backends.
For <B>SCSI</B> scanners, it checks the default generic SCSI device files
(e.g., <I>/dev/sg0</I>) and <I>/dev/scanner</I>. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "proces‐
sor" (some old HP scanners seem to send "processor"). So
For <B>SCSI</B> scanners, it checks the default generic SCSI device files
(e.g., <I>/dev/sg0</I>) and <I>/dev/scanner</I>. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "proces-
sor" (some old HP scanners seem to send "processor"). So
<B>sane-find-scanner</B> will find any SCSI scanner connected to those default
device files even if it isn't supported by any SANE backend.
For <B>USB</B> scanners, first the USB kernel scanner device files (e.g.
<I>/dev/usb/scanner0</I>), <I>/dev/usb/scanner</I>, and <I>/dev/usbscanner</I>) are tested.
The files are opened and the vendor and device ids are determined, if
the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module
or the FreeBSD or OpenBSD uscanner driver. After that test,
<B>sane-find-scanner</B> 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. <B>sane-find-scanner</B> also tries to find out the
type of USB chip used in the scanner. If detected, it will be printed
For <B>USB</B> scanners, first the USB kernel scanner device files (e.g.
<I>/dev/usb/scanner0</I>), <I>/dev/usb/scanner</I>, and <I>/dev/usbscanner</I>) are tested.
The files are opened and the vendor and device ids are determined, if
the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module
or the FreeBSD or OpenBSD uscanner driver. After that test,
<B>sane-find-scanner</B> 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. <B>sane-find-scanner</B> 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. <B>sane-find-scanner</B> will even find USB
scanners, that are not supported by any SANE backend.
<B>sane-find-scanner</B> won't find most parallel port scanners, or scanners
connected to proprietary ports. Some <B>parallel</B> <B>port</B> scanners may be
detected by <B>sane-find-scanner</B> <B>-p.</B> At the time of writing this will
only detect Mustek parallel port scanners.
<B>sane-find-scanner</B> won't find most parallel port scanners, or scanners
connected to proprietary ports. Some <B>parallel</B> <B>port</B> scanners may be de-
tected by <B>sane-find-scanner</B> <B>-p.</B> At the time of writing this will only
detect Mustek parallel port scanners.
</PRE>
<H2>OPTIONS</H2><PRE>
<B>-h,</B> <B>-?</B> Prints a short usage message.
<B>-?,</B> <B>-h,</B> <B>--help</B>
Prints a short usage message.
<B>-v</B> Verbose output. If used once, <B>sane-find-scanner</B> shows every
device name and the test result. If used twice, SCSI inquiry
information and the USB device descriptors are also printed.
<B>-v</B> Verbose output. If used once, <B>sane-find-scanner</B> shows every de-
vice name and the test result. If used twice, SCSI inquiry in-
formation and the USB device descriptors are also printed.
<B>-q</B> Be quiet. Print only the devices, no comments.
<B>-p</B> Probe parallel port scanners.
<B>-f</B> Force opening all explicitly given devices as SCSI and USB
devices. That's useful if <B>sane-find-scanner</B> is wrong in deter‐
mining the device type.
<B>-f</B> Force opening all explicitly given devices as SCSI and USB de-
vices. That's useful if <B>sane-find-scanner</B> is wrong in determin-
ing the device type.
<B>-F</B> <B>filename</B>
filename is a file that contains USB descriptors in the format
of /proc/bus/usb/devices as used by Linux. <B>sane-find-scanner</B>
tries to identify the chipset(s) of all USB scanners found in
such a file. This option is useful for developers when the out‐
filename is a file that contains USB descriptors in the format
of /proc/bus/usb/devices as used by Linux. <B>sane-find-scanner</B>
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
itself isn't.
<B>devname</B> Test device file "devname". No other devices are checked if
devname is given.
<B>devname</B> Test device file "devname". No other devices are checked if de-
vname is given.
</PRE>
<H2>EXAMPLE</H2><PRE>
<B>sane-find-scanner</B> <B>-v</B>
Check all SCSI and USB devices for available scanners and print a line
Check all SCSI and USB devices for available scanners and print a line
for every device file.
<B>sane-find-scanner</B> <B>/dev/scanner</B>
@ -96,7 +98,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>,
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>,
<B><A HREF="xsane.1.html">xsane(1)</A></B>, <B>sane-"backendname"</B>(5)
@ -107,11 +109,11 @@
</PRE>
<H2>SUPPORTED PLATFORMS</H2><PRE>
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven‐
USB support is limited to Linux (kernel, libusb), FreeBSD (kernel,
libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven-
dor and device ids only works with Linux or libusb.
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
SCSI support is available on Irix, EMX, Linux, Next, AIX, Solaris,
FreeBSD, NetBSD, OpenBSD, and HP-UX.

36
man/sane-fujitsu.5.html
Wyświetl plik

@ -20,20 +20,20 @@
The <B>sane-fujitsu</B> library implements a SANE (Scanner Access Now Easy)
backend which provides access to most Fujitsu flatbed and ADF scanners.
This document describes backend version 133, which shipped with SANE
1.0.26.
This document describes backend version 134, which shipped with SANE
1.0.28.
</PRE>
<H2>SUPPORTED HARDWARE</H2><PRE>
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
for details.
This backend may support other Fujitsu scanners. The best way to deter‐
This backend may support other Fujitsu scanners. The best way to deter-
mine level of support is to test the scanner directly, or to collect a
trace of the windows driver in action. Please contact the author for
help or with test results.
@ -52,7 +52,7 @@
ScanPartner M3096EX fi-4010CU
SP-Jr M3097E+/DE S300/S300M
SP-10/10C M3099A/EH/EX S1300/S1100
SP-15C/300C fi-60F
SP-15C/300C fi-60F/65F
SP-600C/620C fi-5015C
SP-2x/3x
@ -71,8 +71,8 @@
resolution, y-resolution
Controls scan resolution. Setting --resolution also sets
--y-resolution, though this behavior is overridden by some fron‐
tends.
--y-resolution, though this behavior is overridden by some
frontends.
tl-x, tl-y, br-x, br-y
Sets scan area upper left and lower right coordinates. These are
@ -82,23 +82,23 @@
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‐
Other options will be available based on the capabilities of the scan-
ner: machines with IPC or DTC will have additional enhancement options,
those with CMP will have compression options, those with a printer will
have a group of endorser options.
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.
may be settable only when another option has been set, and that ad-
vanced options may be hidden by some frontend programs.
</PRE>
@ -134,7 +134,7 @@
The only configuration option supported is "buffer-size=xxx", allowing
you to set the number of bytes in the data buffer to something other
than the compiled-in default, 65536 (64K). Some users report that their
scanner will "hang" mid-page, or fail to transmit the image if the buf‐
scanner will "hang" mid-page, or fail to transmit the image if the buf-
fer is not large enough.
Note: This option may appear multiple times in the configuration file.

90
man/sane-genesys.5.html
Wyświetl plik

@ -30,7 +30,7 @@
Plustek OpticBook 3600
Pentax DSmobile 600
Syscan/Ambir DocketPORT 467/485/487/665/685
Visioneer OneTouch 7100/Strobe XP100 (rev3)/XP200/XP300/Roadwar‐
Visioneer OneTouch 7100/Strobe XP100 (rev3)/XP200/XP300/Roadwar-
rior
Xerox Travel Scanner 100, OneTouch 2400
@ -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.
@ -94,7 +94,7 @@
positive values to increase it.
<B>--disable-interpolation</B> <B>yes|no</B>
When using high resolutions where the horizontal resolu‐
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.
@ -114,31 +114,31 @@
is still done with lamp on.
<B>--clear-calibration</B>
Clear calibration cache data, triggering a new calibra‐
Clear calibration cache data, triggering a new calibra-
tion for the device when the next scan will happen.
<B>--calibration-file</B>
Specify the calibration file name to use. At least the
directory containing the file must exist, since it won't be cre‐
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.
<B>--expiration-time</B>
Specify the time (in minutes) a cached calibration is
considered valid. If older than the given value, a new calibra‐
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.
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.
<B>--swcrop</B>
Requests the driver to detect the extremities of the paper
@ -158,15 +158,15 @@
pixels.
<B>--swderotate[=(yes|no)]</B> <B>[no]</B>
Request driver to detect and correct 90 degree image
rotation.
Request driver to detect and correct 90 degree image ro-
tation.
</PRE>
<H2>SYSTEM ISSUES</H2><PRE>
This backend needs libusb-0.1.6 or later installed, and hasn't tested
in other configuration than a linux kernel 2.6.9 or higher. However, it
should work any system with libusb where the SANE package can be com‐
should work any system with libusb where the SANE package can be com-
piled. For setting permissions and general USB information look at
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
@ -202,19 +202,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_GENESYS</B>
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
@ -225,23 +225,23 @@
functions common to all genesys ASICs.
<B>SANE_DEBUG_GENESYS_GL646</B>
This environment variable controls the debug level for the spe‐
This environment variable controls the debug level for the spe-
cific GL646 code part.
<B>SANE_DEBUG_GENESYS_GL841</B>
This environment variable controls the debug level for the spe‐
This environment variable controls the debug level for the spe-
cific GL841 code part.
<B>SANE_DEBUG_GENESYS_GL843</B>
This environment variable controls the debug level for the spe‐
This environment variable controls the debug level for the spe-
cific GL843 code part.
<B>SANE_DEBUG_GENESYS_GL847</B>
This environment variable controls the debug level for the spe‐
This environment variable controls the debug level for the spe-
cific GL847 code part.
<B>SANE_DEBUG_GENESYS_GL124</B>
This environment variable controls the debug level for the spe‐
This environment variable controls the debug level for the spe-
cific GL124 code part.
Example (full and highly verbose output for gl646):
@ -282,7 +282,7 @@
Oliver Rauch
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
Gerhard Jaeger &lt;gerhard@gjaeger.de&gt;
Stéphane Voltz &lt;stef.dev@free.fr&gt;
St<B>e</B>phane Voltz &lt;stef.dev@free.fr&gt;
Philipp Schmid &lt;philipp8288@web.de&gt;
Pierre Willenbrock &lt;pierre@pirsoft.dnsalias.org&gt;
Alexey Osipov &lt;simba@lerlan.ru&gt; for HP2400 final support
@ -290,9 +290,9 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
Powersaving isn't implemented for gl646 based scanner. Dynamic (emu‐
lated from gray data and with dithering) isn't enabled for gl646 scan‐
ners. Hardware lineart is limited up to 600 dpi for gl847 based scan‐
Powersaving isn't implemented for gl646 based scanner. Dynamic (emu-
lated from gray data and with dithering) isn't enabled for gl646 scan-
ners. Hardware lineart is limited up to 600 dpi for gl847 based scan-
ners, due to the way image sensors are built.
This backend will be much slower if not using libusb-1.0. So be sure
@ -302,8 +302,8 @@
</PRE>
<H2>BUGS</H2><PRE>
For the LiDE 200, the scanned data at 4800 dpi is obtained "as is" from
sensor. It seems the windows driver does some digital processing to
improve it, which is not implemented in the backend.
sensor. It seems the windows driver does some digital processing to im-
prove it, which is not implemented in the backend.
4 Jul 2012 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
</PRE>

30
man/sane-gphoto2.5.html
Wyświetl plik

@ -23,14 +23,14 @@
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'.
</PRE>
<H2>DEVICE NAMES</H2><PRE>
The current version of the backend only allows one camera to be con‐
The current version of the backend only allows one camera to be con-
nected. The device name is always "0".
@ -38,10 +38,10 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>gphoto2.conf</I> 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
printed.
@ -56,7 +56,7 @@
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:
@ -89,15 +89,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_GPHOTO2</B>
If the library was compiled with debugging support enabled, this

56
man/sane-gt68xx.5.html
Wyświetl plik

@ -44,23 +44,23 @@
<H2>LIBUSB ISSUES</H2><PRE>
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â€<EFBFBD>
found by sane-find-scanner without further actions. For setting permis-
sions and general USB information looks at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
</PRE>
<H2>FIRMWARE FILE</H2><PRE>
You need a firmware file for your scanner. That's a small file containâ€<EFBFBD>
ing software that will be uploaded to the scanner's memory. It's usuâ€<EFBFBD>
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. It's usu-
ally named *.usb, e.g. <I>PS1fw.usb</I>. It comes on the installation CD
that was provided by the manufacturer, but it may be packaged together
with the installation program in an .exe file. For Mustek scanners, the
file can be downloaded from the gt68xx backend homepage. For other
scanners, check the CD for .usb files. If you only find *.cab files,
try cabextract to unpack. If everything else fails, you must install
the Windows driver and get the firmware from there (usually in the <I>winâ</I>€<EFBFBD>
the Windows driver and get the firmware from there (usually in the <I>win-</I>
<I>dows/system</I> or <I>system32</I> directories). Put that firmware file into
<I>/usr/local/share/sane/gt68xx/</I>. Make sure that it's readable by everyâ€<EFBFBD>
<I>/usr/local/share/sane/gt68xx/</I>. Make sure that it's readable by every-
one.
@ -80,7 +80,7 @@
Option <B>override</B> is used to override the default model parameters.
That's necessary for some scanners that use the same vendor/product ids
but are different. For these scanners there are already commented out
override lines in the configuration file. <B>override</B> <B>mustek-scanex</B>â€<B>â</B>€<EFBFBD>
override lines in the configuration file. <B>override</B> <B>mustek-scanex-</B>
<B>press-1200-ub-plus</B> is necessary for the Mustek Scanexpress 1200 UB
Plus, the Medion/Lifetec/Tevion LT 9452, and the Trust Compact Scan USB
19200. <B>override</B> <B>artec-ultima-2000</B> is used for the Artec Ultima 2000,
@ -96,18 +96,18 @@
create this directory. If you want to place the firmware files at a
different path, use a <B>firmware</B> line.
The <B>vendor</B> and <B>model</B> options are not absolutely necessary but for conâ€<EFBFBD>
The <B>vendor</B> and <B>model</B> options are not absolutely necessary but for con-
venience. Quite a lot of scanners from different manufacturers share
the same vendor/product ids so you can set the "correct" name here.
The <B>afe</B> 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 <I>gt68xx.conf</I>. The option has six
parameters: red offset, red gain, green offset, green gain, blue offâ€<EFBFBD>
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 <I>gt68xx.conf</I>. 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:
@ -139,19 +139,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_GT68XX</B>
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.
@ -184,11 +184,11 @@
Support for buttons is missing.
More detailed bug information is available at the gt68xx backend homeâ€<EFBFBD>
More detailed bug information is available at the gt68xx backend home-
page <I>http://www.meier-geinitz.de/sane/gt68xx-backend/</I>. Please contact
us if you find a bug or missing feature:
&lt;sane-devel@alioth-lists.debian.net&gt;. Please send a debug log if your
scanner isn't detected correctly (see SANE_DEBUG_GT68XX above).
us if you find a bug or missing feature: &lt;sane-devel@alioth-lists.de-
bian.net&gt;. Please send a debug log if your scanner isn't detected cor-
rectly (see SANE_DEBUG_GT68XX above).
13 Jul 2008 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
</PRE>

117
man/sane-hp.5.html
Wyświetl plik

@ -45,13 +45,13 @@
PhotoSmart C5100A R029,R030,R032 SCSI
Support for models 5100C/5200C connected to the parallel port requires
the ppSCSI driver available at <I>http://cyberelk.net/tim/parâ</I>€<EFBFBD>
<I>port/ppscsi.html</I> and <I>http://penguin-breeder.org/kernel/download/</I>.
the ppSCSI driver available at <I>http://cyberelk.net/tim/parport/pp-</I>
<I>scsi.html</I> and <I>http://penguin-breeder.org/kernel/download/</I>.
Support for models 5200C/62X0C/63X0C connected to the USB require the
kernel scanner driver or libusb. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for more details.
The "hp" backend no longer supports OfficeJet multi-function peripherâ€<EFBFBD>
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
<I>http://hpoj.sourceforge.net</I>
@ -73,12 +73,12 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that correâ€<EFBFBD>
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. For SCSI scanners the special device name must
be a generic SCSI device or a symlink to such a device. Under Linux,
such a device name could be <I>/dev/sga</I> or <I>/dev/sg2</I>, for example. If the
special device name contains "usb", "uscanner" or "ugen", it is assumed
that the scanner is connected by USB. For the HP ScanJet Plus the speâ€<EFBFBD>
that the scanner is connected by USB. For the HP ScanJet Plus the spe-
cial device name must be the device that corresponds to the parallel
interface card that was shipped with the scanner. That is <I>/dev/hpscan</I>.
A special driver is required for this card. See
@ -95,24 +95,24 @@
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 <B>connect-scsi</B>, <B>connect-device</B>,
<B>enable-image-buffering</B>, and <B>dumb-read</B>.
Supported options are <B>connect-scsi</B>, <B>connect-device</B>, <B>enable-im-</B>
<B>age-buffering</B>, and <B>dumb-read</B>.
Option <B>connect-scsi</B> specifies that the scanner is connected to the sysâ€<EFBFBD>
Option <B>connect-scsi</B> 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 <B>connect-device</B> 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
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â€<EFBFBD>
"usb", "uscanner" or "ugen", it is not necessary to specify option con-
nect-device.
Option <B>enable-image-buffering</B> stores the scanned image in memory before
@ -120,10 +120,10 @@
moving scanner lamp.
Option <B>dumb-read</B> can be used to work around problems with "Error during
device I/O". These problems may occur with certain SCSI-to-USB convertâ€<EFBFBD>
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.
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 de-
vices which are working correctly. Otherwise startup of frontends and
changing parameters might be slower.
A sample configuration file is shown below:
@ -149,11 +149,10 @@
that support dynamic loading).
<I>$HOME/.sane/calib-hp:&lt;device&gt;.dat</I>
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'.
</PRE>
@ -161,25 +160,25 @@
<B>SANE_CONFIG_DIR</B>
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_HP</B>
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.
<B>SANE_HOME_HP</B>
Only used for OS/2 and along with use of HP PhotoSmart Photoâ€<C3A2>
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,42 +187,42 @@
<B>SANE_HP_KEEPOPEN_USB</B>
<B>SANE_HP_KEEPOPEN_DEVICE</B>
For each type of connection (connect-scsi, connect-usb, conâ€<C3A2>
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.
<B>SANE_HP_RDREDO</B>
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.
</PRE>
<H2>BUGS</H2><PRE>
<B>HP</B> <B>PhotoSmart</B> <B>PhotoScanner</B>
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â€<C3A2>
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.
<B>Automatic</B> <B>Document</B> <B>Feeder</B> <B>(ADF)</B>
For use of the ADF with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, 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 <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, 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â€<EFBFBD>
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 <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>. Try <B><A HREF="xsane.1.html">xsane(1)</A></B>.
<B>Immediate</B> <B>actions</B>
Some actions in <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> (i.e. unload, select media, caliâ€<EFBFBD>
brate) have an immediate effect on the scanner without starting
Some actions in <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> (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.
@ -231,17 +230,17 @@
<H2>TODO</H2><PRE>
<B>HP</B> <B>PhotoSmart</B> <B>PhotoScanner</B>
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â€<C3A2>
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.
<B>Data</B> <B>widths</B> <B>greater</B> <B>than</B> <B>8</B> <B>bits</B>
Custom gamma table does not work.
<B>Parallel</B> <B>scanner</B> <B>support</B>
Beside the ScanJet Plus which came with its own parallel interâ€<C3A2>
face card, currently only the HP ScanJet 5100C/5200C are supâ€<C3A2>
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).
@ -252,7 +251,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
PhotoScanner support by Peter Kirchgessner.
13 Jul 2008 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>

4
man/sane-hp3500.5.html
Wyświetl plik

@ -51,8 +51,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_HP3500</B> If the library was compiled with debug support
enabled, this environment variable controls the debug level for this
<B>SANE_DEBUG_HP3500</B> 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

28
man/sane-hp3900.5.html
Wyświetl plik

@ -33,7 +33,7 @@
UMAX Astra 4900/4950 RTS8822L-01H *
BenQ 5550 RTS8823L-01E *
More details can be found on the hp3900 backend homepage <I>http://sourceâ</I>€<EFBFBD>
More details can be found on the hp3900 backend homepage <I>http://source-</I>
<I>forge.net/projects/hp3900-series/</I>.
This is ALPHA software. Keep your hand at the scanner's plug and unplug
@ -52,8 +52,8 @@
The contents of the <I>hp3900.conf</I> 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 <B>usb</B> <B>vendor_id</B> <B>product_id</B>
scanner. Empty lines and lines starting with a hash mark (#) are ig-
nored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp3900.conf</I>. "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
@ -80,19 +80,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/etc/sane.d" being
searched (in this order).
<B>SANE_DEBUG_HP3900</B>
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
@ -101,7 +101,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>,
<I>http://sourceforge.net/projects/hp3900-series/</I> <I>http://jkdsoftware.dynâ</I>€<EFBFBD>
<I>http://sourceforge.net/projects/hp3900-series/</I> <I>http://jkdsoftware.dyn-</I>
<I>dns.org/drupal/?q=es/books/151</I>

28
man/sane-hp4200.5.html
Wyświetl plik

@ -44,8 +44,8 @@
The contents of the <I>hp4200.conf</I> 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 <B>usb</B> <B>vendor_id</B> <B>product_id</B>
scanner. Empty lines and lines starting with a hash mark (#) are ig-
nored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp4200.conf</I>. "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
@ -72,19 +72,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_HP4200</B>
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
@ -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 <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>
</PRE>

26
man/sane-hp5400.5.html
Wyświetl plik

@ -45,8 +45,8 @@
The contents of the <I>hp5400.conf</I> 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 <B>usb</B> <B>vendor_id</B> <B>product_id</B>
scanner. Empty lines and lines starting with a hash mark (#) are ig-
nored. The scanners are autodetected by <B>usb</B> <B>vendor_id</B> <B>product_id</B>
statements which are already included into <I>hp5400.conf</I>. "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
@ -73,19 +73,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_HP5400</B>
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
@ -100,7 +100,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Martijn van Oosterhout &lt;kleptog@svana.org&gt;, Thomas Soumarmon
&lt;soumarmt@nerim.net&gt;. Manpage by Henning Meier-Geinitz &lt;hen‐
&lt;soumarmt@nerim.net&gt;. Manpage by Henning Meier-Geinitz &lt;hen-
ning@meier-geinitz.de&gt;.

253
man/sane-hp5590.5.html
Wyświetl plik

@ -19,65 +19,268 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-hp5590</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Hewlett-Packard Work‐
backend that provides access to the following Hewlett-Packard Work-
group/Document scanners:
ScanJet 4500C
ScanJet 4570C
ScanJet 5500C
ScanJet 5550C
ScanJet 5590
ScanJet 7650
<B>o</B> ScanJet 4500C
<B>o</B> ScanJet 4570C
<B>o</B> ScanJet 5500C
<B>o</B> ScanJet 5550C
<B>o</B> ScanJet 5590
<B>o</B> ScanJet 7650
If you own a scanner other than the ones listed above that works with
this backend, please let us know this by sending the scanner's exact
model name and the USB vendor and device ids (e.g. from
<I>/proc/bus/usb/devices</I>, <I>sane-find-scanner</I> or syslog) to us. Even if the
model name and the USB vendor and device ids (e.g. from
<I>/sys/bus/usb/devices</I>, <I>sane-find-scanner</I> or syslog) to us. Even if the
scanner's name is only slightly different from the models mentioned
above, please let us know.
</PRE>
<H2>CONFIGURATION</H2><PRE>
None required.
<H2>OPTIONS</H2><PRE>
The options the backend supports can either be selected through command
line options to programs like scanimage or through GUI elements in <I>xs-</I>
<I>canimage</I> or <I>xsane</I>. Valid command line options and their syntax can be
listed by using:
scanimage --help -d hp5590:interface:device
where <I>interface</I> and <I>device</I> specify the device in question, as in the
configuration file. Add <I>--all-options</I> 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:
scanimage -L
to list all devices recognized by your SANE installation.
</PRE>
<H2>DEVICE SPECIFIC OPTIONS</H2><PRE>
<B>-l</B> <I>n</I> Top-left X position of scan area in <B>mm</B>. Allowed range: 0 ..
215.889.
<B>-t</B> <I>n</I> Top-left Y position of scan area in <B>mm</B>. Allowed range: 0 ..
297.699.
<B>-x</B> <I>n</I> X width of scan-area in <B>mm</B>. Allowed range: 0 .. 215.889.
<B>-y</B> <I>n</I> Y height of scan-area in <B>mm</B>. Allowed range: 0 .. 297.699.
By default, the maximum size will be scanned.
<B>--mode</B> <I>mode</I>
Select color mode. <I>mode</I> must be one of: "Color", "Color (48
bits)", "Gray", "Lineart".
<B>o</B> "Color" - Scanning is done with 3 * 8 bit RGB color values per
pixel.
<B>o</B> "Color (48 bits)" - Scanning is done with 3 * 16 bit RGB color
values per pixel.
<B>o</B> "Gray" - Scanning is done with 1 * 8 bit gray value per pixel.
<B>o</B> "Lineart" - Scanning is done with 1 bit black and white value
per pixel.
<B>--source</B> <I>source</I>
Select the source for scanning. <I>source</I> must be one of:
"Flatbed", "ADF", "ADF Duplex", "TMA Slides", "TMA Negatives".
<B>o</B> "Flatbed" - Scan document on the flat document glass.
<B>o</B> "ADF" - Scan frontsides of documents with automatic document
feeder.
<B>o</B> "ADF Duplex" - Scan front- and backsides of documents with au-
tomatic document feeder. Note, the backside images must be
rotated in a separate post process step.
<B>o</B> "TMA Slides" - Slide scanning with transparent media adapter.
(Not fully supported by hp5590 backend).
<B>o</B> "TMA Negatives" - Negative film scanning with transparent me-
dia adapter. (Not fully supported by hp5590 backend).
<B>--resolution</B> <I>res</I>
Set the resolution of the scanned image in <B>dpi</B>. <I>res</I> must be one
of: 100, 200, 300, 600, 1200, 2400.
Default settings: Lineart, Flatbed, 100dpi.
<B>--extend-lamp-timeout[=yes|no]</B>
Extend lamp timeout period. no = 15 minutes, yes = 1 hour.
(Default: no)
<B>--wait-for-button[=yes|no]</B>
Wait for button press before scanning starts. (Default: no)
<B>--preview[=yes|no]</B>
Request a preview-quality scan. (Default: no)
<B>--hide-eop-pixel[=yes|no]</B>
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.
<B>--trailing-lines-mode</B> <I>mode</I>
Filling mode of trailing lines after end of page when automatic
document feeder (ADF) is used. <I>mode</I> must be one of: "last",
"raw", "raster", "white", "black", "color". (Default: "last")
<B>o</B> "last" = repeat the last scan line (recommended),
<B>o</B> "raw" = read raw scan data (not recommended),
<B>o</B> "raster" = generate black and white pixel pattern,
<B>o</B> "white" = white pixels,
<B>o</B> "black" = black pixels,
<B>o</B> "color" = RGB or gray colored pixels (see next option).
<B>--trailing-lines-color</B> <I>n</I>
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.
</PRE>
<H2>READ OUT OPTIONS</H2><PRE>
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 <I>flatbed</I> and <I>ADF</I> mode, or triggering prost processing tasks
after scanning.
<B>--button-pressed</B>
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".
<B>--color-led</B>
Get the state of the color LED indicators. The state is either
"color" or "black_white".
<B>--counter-value</B>
Get the counter value as shown on LCD. The value is in the
range of 1 .. 99.
<B>--doc-in-adf</B>
Get the state of the document-available indicator of the auto-
matic document feeder (ADF). The state is either "yes" or "no".
</PRE>
<H2>HINTS FOR USERS OF SCANBD</H2><PRE>
<I>Scanbd</I> is a scanner button daemon, which can read scanner buttons and
trigger scan actions.
Do not use the old <I>scanbuttond</I> 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 <I>hp5590</I> backend.
This example shows a minimum configuration file and the corresponding
script file for scanbd to be included in <I>scanbd.conf</I>.
<B>o</B> <B>hp5590.conf</B>
device hp5590 {
# Device matching
filter = "^hp5590.*"
desc = "HP5590 Scanner Family"
# Read out counter value and store in environment variable.
function function_lcd_counter {
filter = "^counter-value.*"
desc = "hp5590: LCD counter"
env = "SCANBD_FUNCTION_LCD_COUNTER"
}
# Run scan script when button is pressed.
action do-scan {
filter = "^button-pressed.*"
desc = "hp5590: Scan button pressed"
script = "scan_action.script"
string-trigger {
from-value = "none"
to-value = "scan"
}
}
}
<B>o</B> <B>scan_action.script</B>
#!/bin/bash
echo device = $SCANBD_DEVICE
echo action = $SCANBD_ACTION
echo counter = $SCANBD_FUNCTION_LCD_COUNTER
scanfile="$HOME/tmp/scans/scan-$(date +%s).pnm"
case $SCANBD_ACTION in
do-scan)
scanimage -d "$SCANBD_DEVICE" &gt; "$scanfile"
;;
*)
echo Warning: Unknown scanbd action: "$SCANBD_ACTION"
;;
esac
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-hp5590.a</I>
<I>@LIBDIR@/libsane-hp5590.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-hp5590.so</I>
<I>@LIBDIR@/libsane-hp5590.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>ENVIRONMENT</H2><PRE>
If the library was compiled with debug support enabled, this environ-
ment variable controls the debug level for this backend.
<B>SANE_DEBUG_HP5590</B>
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. See
used levels below.
Level 10 - generic processing
Level 20 - verbose backend messages
Level 40 - HP5590 high-level commands
Level 50 - HP5590 low-level (USB-in-USB) commands
Higher debug levels increase the verbosity of the output:
Example:
10 - generic processing
20 - verbose backend messages
40 - HP5590 high-level commands
50 - HP5590 low-level (USB-in-USB) commands
<B>Example:</B>
export SANE_DEBUG_HP5590=50
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>,
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Ilia Sotnikov &lt;hostcc@gmail.com&gt;
<H2>AUTHORS</H2><PRE>
Ilia Sotnikov &lt;hostcc@gmail.com&gt;.
13 Jul 2008 <B><A HREF="sane-hp5590.5.html">sane-hp5590(5)</A></B>
</PRE>

2
man/sane-hpljm1005.5.html
Wyświetl plik

@ -53,7 +53,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Philippe Rétornaz &lt;couriousous@mandriva.org&gt;
Philippe R<B>e</B>tornaz &lt;couriousous@mandriva.org&gt;
13 Jul 2008 <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>
</PRE>

24
man/sane-hpsj5s.5.html
Wyświetl plik

@ -27,12 +27,12 @@
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
is due to dependence on the libieee1284 library. If your system sup-
ports libieee1284 too, this backend should work. If you ported li-
bieee1284 for your platform, please let me know. Your system should
support <B>EPP</B> (or <B>EPP+ECP</B> ) 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‐
support scanners not only at daisy-chain position 0, but anywhere. Sup-
port for multiple scanners could be implemented too.
Current version implements only gray scale scanning. True Color and B/W
@ -90,15 +90,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SEE</B> <B>ALSO</B>
<B><A HREF="sane.7.html">sane(7)</A></B>

64
man/sane-hs2p.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-hs2p</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-hs2p</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to the Ricoh IS450 family of scanners. Should
also work with the IS420, IS410, and IS430 scanners, but these are
untested. Please contact the maintainer or the sane-devel mailing list
@ -34,7 +34,7 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor‐
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. The program <I>sane-find-scanner</I> helps to find
out the correct device. Under Linux, such a device name could be
<I>/dev/sg0</I> or <I>/dev/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
@ -42,7 +42,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>hs2p.conf</I> file is a list of device names that cor‐
The contents of the <I>hs2p.conf</I> file is a list of device names that cor-
respond to SCSI scanners. Empty lines and lines starting with a hash
mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what constitutes
a valid device name.
@ -68,30 +68,30 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_HS2P</B>
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.
</PRE>
<H2>CURRENT STATUS</H2><PRE>
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
supported. Pre-set gamma tables and halftone patterns are supported, as
features are supported, except for those features requiring the op-
tional IPU. Scanning from the flatbed or ADF (either simplex or duplex)
is supported. Lineart, halftone, 4-bit gray, and 8-bit gray are sup-
ported. 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
relative white setting. Printing with the optional endorser also is
@ -100,27 +100,27 @@
</PRE>
<H2>PLANNED FUNCTIONALITY</H2><PRE>
This scanner can scan from the ADF in continuous simplex mode. Sur‐
prisingly, many scanners scan an entire document from the ADF into mem‐
This scanner can scan from the ADF in continuous simplex mode. Sur-
prisingly, many scanners scan an entire document from the ADF into mem-
ory before ejecting the sheet. Thus if the document is too long, the
scanner cannot hold the entire image data in memory. But if the scan‐
scanner cannot hold the entire image data in memory. But if the scan-
ner would send its image data when its memory got full, and then read
the next buffer's worth of data, continuous scanning could be achieved.
</PRE>
<H2>MISSING FUNCTIONALITY</H2><PRE>
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.
</PRE>

26
man/sane-ibm.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-ibm</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-ibm</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to the IBM 2456 and the Ricoh IS-410, IS-420,
and IS-430 flatbed scanners. Support for the IS-410 and IS-430 is
untested. Please contact the maintainer or the sane-devel mailing list
@ -34,7 +34,7 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor‐
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. The program <I>sane-find-scanner</I> helps to find
out the correct device. Under Linux, such a device name could be
<I>/dev/sg0</I> or <I>/dev/sga</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
@ -42,7 +42,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>ibm.conf</I> file is a list of device names that corre‐
The contents of the <I>ibm.conf</I> file is a list of device names that corre-
spond to SCSI scanners. Empty lines and lines starting with a hash
mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what constitutes
a valid device name.
@ -68,19 +68,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_IBM</B>
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.

10
man/sane-kodak.5.html
Wyświetl plik

@ -69,9 +69,9 @@
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
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 op-
tions may be settable only when another option has been set, and that
advanced options may be hidden by some frontend programs.
@ -100,7 +100,7 @@
The only configuration option supported is "buffer-size=xxx", allowing
you to set the number of bytes in the data buffer to something other
than the compiled-in default, 32768 (32K). Some users report that their
scanner will "hang" mid-page, or fail to transmit the image if the buf‐
scanner will "hang" mid-page, or fail to transmit the image if the buf-
fer is not large enough.
Note: This option may appear multiple times in the configuration file.
@ -129,7 +129,7 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
Most hardware options are either not supported or not exposed for con‐
Most hardware options are either not supported or not exposed for con-
trol by the user, including: multifeed detection, image compression,
autocropping, endorser, iThresholding, multi-stream, etc.

4
man/sane-kodakaio.5.html
Wyświetl plik

@ -21,7 +21,7 @@
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‐
This document describes backend version 2.4, which is the first candi-
date for incorporation in sane-backends.
@ -52,7 +52,7 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
Most hardware options are either not supported or not exposed for con‐
Most hardware options are either not supported or not exposed for con-
trol by the user, including: multifeed detection, image compression
etc.

2
man/sane-kvs1025.5.html
Wyświetl plik

@ -25,7 +25,7 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
This document was written by the SANE project, which has no information
regarding the capabilities or reliability of the backend. All informa‐
regarding the capabilities or reliability of the backend. All informa-
tion contained here is suspect.

4
man/sane-kvs20xx.5.html
Wyświetl plik

@ -12,7 +12,7 @@
</PRE>
<H2>NAME</H2><PRE>
sane-kvs20xx - SANE backend for Panasonic KV-S20xxC USB/SCSI ADF scan‐
sane-kvs20xx - SANE backend for Panasonic KV-S20xxC USB/SCSI ADF scan-
ners.
@ -26,7 +26,7 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
This document was written by the SANE project, which has no information
regarding the capabilities or reliability of the backend. All informa‐
regarding the capabilities or reliability of the backend. All informa-
tion contained here is suspect.

8
man/sane-kvs40xx.5.html
Wyświetl plik

@ -12,7 +12,7 @@
</PRE>
<H2>NAME</H2><PRE>
sane-kvs40xx - SANE backend for Panasonic KV-S40xxC USB/SCSI ADF scan‐
sane-kvs40xx - SANE backend for Panasonic KV-S40xxC USB/SCSI ADF scan-
ners.
@ -26,11 +26,11 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
This document was written by the SANE project, which has no information
regarding the capabilities or reliability of the backend. All informa‐
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.
</PRE>

20
man/sane-leo.5.html
Wyświetl plik

@ -17,8 +17,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-leo</B> library implements a SANE (Scanner Access Now Easy) back‐
end that provides access to some LEO SCSI flatbed scanners. This back‐
The <B>sane-leo</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to some LEO SCSI flatbed scanners. This back-
end should be considered <B>beta-quality</B> software! LEO scanners were also
sold under the Across Technologies brand.
@ -30,10 +30,10 @@
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 or through GUI elements in xs-
canimage or xsane.
If you have any strange behavior, please report to the backend main‐
If you have 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
@ -43,11 +43,11 @@
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev‐
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.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso‐
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 300, in increments of 1.
<B>Geometry</B> <B>options</B>
@ -106,8 +106,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_LEO</B>
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.
@ -115,7 +115,7 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple‐
However they are only software adjustments. This backend only imple-
ments what the scanner can support.

20
man/sane-lexmark.5.html
Wyświetl plik

@ -37,10 +37,10 @@
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 or through GUI elements in xs-
canimage or xsane.
If you have any strange behavior, please report to the backend main‐
If you have 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
@ -49,10 +49,10 @@
<B>Scan</B> <B>Mode</B> <B>Options</B>
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Color</I>, <I>Gray</I> and <I>Lineart</I> The default mode is Color. The Lin‐
eart mode is black and white only (1 bit). Grayscale will pro‐
are <I>Color</I>, <I>Gray</I> and <I>Lineart</I> The default mode is Color. The Lin-
eart mode is black and white only (1 bit). Grayscale will pro-
duce 256 levels of gray (8 bits). Color mode allows for over 16
million different colors produced from 24 bits of color informa‐
million different colors produced from 24 bits of color informa-
tion.
<B>--resolution</B>
@ -78,8 +78,8 @@
<B>--threshold</B>
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.
</PRE>
@ -110,7 +110,7 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple‐
However they are only software adjustments. This backend only imple-
ments what the scanner can support. For instance, shading correction
(vertical stripes due to sensor variation across its width) is done in
software. Head park position is also detected by software. The data
@ -133,7 +133,7 @@
The backend was originally written by Fred Odendaal.
<I>http://ca.geocities.com/freshshelf@rogers.com/</I>
The new version is currently developed by Stéphane Voltz.
The new version is currently developed by St<B>e</B>phane Voltz.
<I>http://stef.dev.free.fr/sane/lexmark</I>
X74 support was written by Torsten Houwaart (&lt;ToHo@gmx.de&gt;)

38
man/sane-ma1509.5.html
Wyświetl plik

@ -36,8 +36,8 @@
the operating system. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> 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
<I>/proc/bus/usb/devices</I> or syslog) to me.
@ -48,7 +48,7 @@
<I>special</I>
Where <I>special</I> is a path-name for the special device that corresponds to
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scanâ</I>€<EFBFBD>
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scan-</I>
<I>ner0</I> or <I>libusb:001:002</I>, for example.
@ -61,13 +61,13 @@
Instead of using the device name, the scanner can be autodetected by
<B>usb</B> <B>vendor_id</B> <B>product_id</B> statements which are already included into
<I>ma1509.conf</I>. This is only supported with Linux 2.4.8 and higher and
all systems that support libsub. "vendor_id" and "product_id" are hexaâ€<EFBFBD>
decimal numbers that identify the scanner. If this doesn't work, a
device name must be placed in <I>ma1509.conf</I> as described above.
all systems that support libsub. "vendor_id" and "product_id" are hexa-
decimal numbers that identify the scanner. If this doesn't work, a de-
vice name must be placed in <I>ma1509.conf</I> as described above.
To set the time the lamp needs for warm-up, use <B>option</B> <B>warmup-time</B> in
<I>ma1509.conf</I>. The time is given in seconds after the option. The
default is 30 seconds.
<I>ma1509.conf</I>. The time is given in seconds after the option. The de-
fault is 30 seconds.
</PRE>
@ -90,19 +90,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MA1509</B>
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.
@ -124,7 +124,7 @@
Transparency adapter and automatic document feeder is not supported yet
No support for "high-speed" mode (jpeg)
More detailed bug information is available at the MA-1509 backend homeâ€<EFBFBD>
More detailed bug information is available at the MA-1509 backend home-
page <I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
13 Jul 2008 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>

22
man/sane-magicolor.5.html
Wyświetl plik

@ -67,25 +67,25 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "/tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MAGICOLOR</B>
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‐
variable before calling your favorite frontend (e.g. xscanim-
age).
Example: SANE_DEBUG_MAGICOLOR=65 xscanimage

26
man/sane-matsushita.5.html
Wyświetl plik

@ -18,7 +18,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-matsushita</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some Panasonic KV-SS high speed scan‐
backend that provides access to some Panasonic KV-SS high speed scan-
ners. This backend is stable.
At present, the following scanners are known to work with this backend:
@ -32,12 +32,12 @@
KV-S2045C (*)
KV-S2065L (*)
(*) WARNING: None of the advanced options of these scanners are avail‐
able (ie no color, no high resolution, no automatic cropping). Basi‐
(*) WARNING: None of the advanced options of these scanners are avail-
able (ie no color, no high resolution, no automatic cropping). Basi-
cally, the driver does no more than what it does for the KV-SS25. I
don't have access to such scanners, and thus cannot add these options.
Other Panasonic high speed scanners may or may not work with that back‐
Other Panasonic high speed scanners may or may not work with that back-
end.
Valid command line options and their syntax can be listed by using
@ -61,8 +61,8 @@
<B>Geometry</B>
<B>--paper-size</B> <B>A4|...|Legal|Letter</B> <B>[A4]</B>
options selects the area to scan. It adjust the <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
options accordingly. It does not need to be the real size of the
options selects the area to scan. It adjust the <B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B> op-
tions accordingly. It does not need to be the real size of the
paper.
<B>-l</B> <B>-t</B> <B>-x</B> <B>-y</B>
@ -83,7 +83,7 @@
<B>--automatic-threshold</B>
automatically sets brightness, contrast, white level, gamma,
noise reduction and image emphasis. These options are not avail‐
noise reduction and image emphasis. These options are not avail-
able when automatic-threshold is in use.
<B>--halftone-pattern</B>
@ -130,8 +130,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_MATSUSHITA</B>
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,8 +154,8 @@
<B>Duplex</B> <B>mode</B>
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.
</PRE>
@ -165,8 +165,8 @@
A scanadf 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"
</PRE>

30
man/sane-microtek.5.html
Wyświetl plik

@ -18,7 +18,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-microtek</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the "second generation" Microtek scan‐
backend that provides access to the "second generation" Microtek scan-
ners. At present, the following hardware is known to work with this
backend:
@ -66,7 +66,7 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre‐
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a generic SCSI
device or a symlink to such a device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
@ -83,10 +83,10 @@
/dev/sge
The configuration file may also contain the special tokens <I>norealcal</I> or
<I>noprecal.</I> <I>norealcal</I> will disable the use of magic, undocumented scan‐
<I>noprecal.</I> <I>norealcal</I> will disable the use of magic, undocumented scan-
ner calibration commands which are known to work on the E6, but may not
work with other models. <I>noprecal</I> will disable logic which tries to
avoid scanner precalibration. This logic would only have been acti‐
avoid scanner precalibration. This logic would only have been acti-
vated if the magic calibration code was turned off.
@ -110,15 +110,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MICROTEK</B>
If the library was compiled with debugging support enabled, this
@ -143,7 +143,7 @@
Brightness and contrast broken.
The 600GS is grayscale only, and will lock up if you select
color. (Unfortunately, the 600GS and 600ZS are indistinguish‐
color. (Unfortunately, the 600GS and 600ZS are indistinguish-
able by software.)
i.e. don't complain about these --- but if brightness and/or contrast
@ -162,8 +162,8 @@
setenv SANE_DEBUG_MICROTEK 128
More general comments, suggestions, and inquiries about frontends or
SANE should go to <B>sane-devel@alioth-lists.debian.net</B>, the SANE Develop‐
ers mailing list. Have a look at http://www.sane-project.org/mail‐
SANE should go to <B>sane-devel@alioth-lists.debian.net</B>, 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 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>

50
man/sane-microtek2.5.html
Wyświetl plik

@ -24,7 +24,7 @@
are reported to work well, others not. New development versions of this
backend can be obtained from <B>http://karstenfestag.gmxhome.de</B>
There exists a different backend for Microtek scanners with SCSI-1 com‐
There exists a different backend for Microtek scanners with SCSI-1 com-
mand set. Refer to <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for details.
And there is work in progress for the ScanMaker 3600. See
@ -62,7 +62,7 @@
Additional information can be found at <B>http://www.sane-project.org/</B>.
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‐
or may not work with SANE! Because equal scanners are sold under dif-
ferent names in different countries your model may be equivalent to one
of the above.
@ -79,7 +79,7 @@
If you try your scanner for the first time keep an eye on it. If it
gets commands that it doesn't understand the scanhead may go beyond the
scan area. The scanner then makes strange noises. In this case immedi‐
scan area. The scanner then makes strange noises. In this case immedi-
ately switch off the scanner or disconnect its power cable to prevent
damages!
@ -87,22 +87,22 @@
it is working please tell the author about it. It would be nice if you
add a logfile to this information (creation of the logfile: see below).
If your scanner is not working properly you also should create a log‐
If your scanner is not working properly you also should create a log-
file and send it to the author. He will use the information to improve
the backend and possibly make your scanner work.
How to create the logfile?
- put the line
"option dump 2" into your <I>microtek2.conf</I> file or change the
existing "option dump" to "2"
"option dump 2" into your <I>microtek2.conf</I> 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&gt;scan.log &gt;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.
</PRE>
@ -115,7 +115,7 @@
Color, grayscale, halftone and lineart scans.
Highlight, midtone, shadow, contrast, brightness, exposure time con‐
Highlight, midtone, shadow, contrast, brightness, exposure time con-
trol, gamma correction, threshold (dependent of the scan mode and the
scanner capabilities)
@ -131,7 +131,7 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre‐
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a generic SCSI
device or a symlink to such a device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I> for example.
@ -139,8 +139,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/microtek2.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/microtek2.conf</I>.
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 &lt;n&gt; and option strip-height &lt;n&gt;, 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 &lt;n&gt; and option strip-height &lt;n&gt;, 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 &lt;n&gt;
option strip-height &lt;n&gt;
@ -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 <I>microtek2.conf</I> 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,10 +189,10 @@
sized scan area.
The following options enable or disable additional frontend options. If
an option is set to &lt;on&gt; an appropriate option will appear in the fron‐
tend.
an option is set to &lt;on&gt; an appropriate option will appear in the
frontend.
<I>option</I> <I>no-backtrack-option</I> <I>&lt;on/off&gt;</I> prevents the scanner head from mov‐
<I>option</I> <I>no-backtrack-option</I> <I>&lt;on/off&gt;</I> prevents the scanner head from mov-
ing backwards between the read commands. This speeds up scanning. Try
it.
@ -213,7 +213,7 @@
<I>option</I> <I>colorbalance-adjust</I> <I>&lt;on/off&gt;</I> Some scanners (e.g. Phantom 330CX
and 636CX) need to have corrected the color balance. If this option is
enabled you get advanced options where you can balance the colors. And
you will have a button to use the values that the firmware of the scan‐
you will have a button to use the values that the firmware of the scan-
ner provides.
A sample configuration file is shown below:
@ -265,11 +265,11 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_MICROTEK2</B>
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

92
man/sane-mustek.5.html
Wyświetl plik

@ -31,7 +31,7 @@
Paragon MFS-8000SP
Paragon MFS-1200SP, MFS-12000SP
ScanExpress 6000SP
ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scanâ€<EFBFBD>
ScanExpress 12000SP, 12000SP Plus, Paragon 1200 III SP, Scan-
Magic 9636S, 9636S Plus
Paragon 1200 LS
ScanExpress A3 SP
@ -48,38 +48,38 @@
More details can be found on the Mustek SCSI backend homepage
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
Don't mix up MFS (Paragon), Pro and ScanExpress models! They're comâ€<EFBFBD>
Don't mix up MFS (Paragon), Pro and ScanExpress models! They're com-
pletely different. Check the exact model name!
Note that most of the above scanners come with a SCSI interface. The
only non-SCSI scanners that have some support at this point is the 600
II N and 600 II EP scanners. The former one comes with its own parallel
port adapter (i.e., it does <I>not</I> attach to the printer port). Both scanâ€<EFBFBD>
port adapter (i.e., it does <I>not</I> attach to the printer port). Both scan-
ners use the SCSI protocol internally, too. More info on how to use
these parallel port scanners can be found below in section <B>PARALLEL</B>
<B>PORT</B> <B>SCANNERS</B>. Other parallel port scanners are not supported by this
backend but you may be successful using the Mustek parallel port backâ€<EFBFBD>
end mustek_pp, see <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>. USB scanners are also not supâ€<EFBFBD>
backend but you may be successful using the Mustek parallel port back-
end mustek_pp, see <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>. USB scanners are also not sup-
ported by this backend but the ma1509, mustek_usb, gt68xx, and plustek
backends include support for some of them, see <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, and <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>.
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
the <I>/usr/local/share/doc/sane-backends/PROBLEMS</I> file.
If you own a Mustek (or Trust) scanner other than the ones listed above
that works with this backend, please let us know by sending the scanâ€<EFBFBD>
that works with this backend, please let us know by sending the scan-
ner's exact model name (look at the front and back of the scanner) and
a debug output to <I>sane-devel@alioth-lists.debian.net</I>. You can get the
debug output by setting the environment variable <B>SANE_DEBUG_MUSTEK</B> 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
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
<I>http://www.sane-project.org/mailing-lists.html</I> for details.
@ -89,29 +89,29 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that corâ€<EFBFBD>
Where <I>special</I> 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 <B>PARALLEL</B> <B>PORT</B> <B>SCANNERS</B> below).
For SCSI scanners, the special device name must be a generic SCSI
device or a symlink to such a device. The program <I>sane-find-scanner</I>
For SCSI scanners, the special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sg0</I> or <I>/dev/sg3</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
could be <I>/dev/sg0</I> or <I>/dev/sg3</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>mustek.conf</I> file is a list of options and device
names that correspond to Mustek scanners. Empty lines and lines startâ€<EFBFBD>
names that correspond to Mustek scanners. Empty lines and lines start-
ing with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of
what constitutes a valid device name.
The supported options are <B>linedistance-fix</B>, <B>lineart-fix</B>, <B>legal-size</B>,
<B>buffersize</B>, <B>blocksize</B>, <B>strip-height</B>, <B>disable-double-buffering</B>, <B>dis</B>â€<B>â</B>€<EFBFBD>
<B>buffersize</B>, <B>blocksize</B>, <B>strip-height</B>, <B>disable-double-buffering</B>, <B>dis-</B>
<B>able-backtracking</B>, and <B>force-wait</B>.
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!
@ -122,13 +122,13 @@
Turning on this option usually fixes the problem.
Option <B>lineart-fix</B> is positional and works around a timing problem that
seems to exist with certain MFS-12000SP scanners. The problem maniâ€<EFBFBD>
seems to exist with certain MFS-12000SP scanners. The problem mani-
fests itself in dropped lines when scanning in lineart mode. Turning
on this option should fix the problem but may slow down scanning a bit.
Option <B>legal-size</B> is positional and sets the size of the scan area to
Legal format. Set this option if you own a Paragon 12000 LS. It can't
be distinguished by software from a ScanExpress 12000 SP (ISO A4 forâ€<EFBFBD>
be distinguished by software from a ScanExpress 12000 SP (ISO A4 for-
mat).
Option <B>buffersize</B> is a positional option that overrides the default
@ -141,18 +141,18 @@
have to change that value, too. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
Option <B>blocksize</B> is a positional option that overrides the default
value set for the maximum amount of data scanned in one block. The bufâ€<EFBFBD>
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 <B>strip-height</B> 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â€<C3A2>
outs and/or timeouts with other devices on the same SCSI bus. Unfortuâ€<C3A2>
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.
@ -162,7 +162,7 @@
first few cm are repeated over and over again in your image.
Option <B>disable-backtracking</B> is a positional option. If set, the scanner
will not move back its slider after each SCSI buffer is filled (`backâ€<EFBFBD>
will not move back its slider after each SCSI buffer is filled (`back-
tracking'). Setting this option will lead to faster scans but may also
produce horizontal stripes. This option doesn't work with every scanner
(only some of the paragon models can modify backtracking).
@ -170,7 +170,7 @@
Finally, <B>force-wait</B> is a global option. If set, the backend will wait
until the device is ready before sending the inquiry command. Further
more the backend will force the scan slider to return to its starting
position (not implemented for all scanners). This option may be necesâ€<EFBFBD>
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).
@ -190,7 +190,7 @@
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
You need a SCSI adapter for the SCSI scanners. Even if the connector is
the same as that of parallel port scanners, connecting it to the comâ€<EFBFBD>
the same as that of parallel port scanners, connecting it to the com-
puters parallel port will NOT work.
Mustek SCSI scanners are typically delivered with an ISA SCSI adapter.
@ -200,13 +200,13 @@
load on the system, that it becomes almost unusable for other tasks.
If you already have a working SCSI controller in your system, you
should consider that Mustek scanners do not support the SCSI-2 disconâ€<EFBFBD>
should consider that Mustek scanners do not support the SCSI-2 discon-
nect/reconnect protocol and hence tie up the SCSI bus while a scan is
in progress. This means that no other SCSI device on the same bus can
be accessed while a scan is in progress.
Because the Mustek-supplied adapter is not worth much and because
Mustek scanners do not support the SCSI-2 disconnect/reconnect protoâ€<EFBFBD>
Mustek scanners do not support the SCSI-2 disconnect/reconnect proto-
col, it is recommended to install a separate (cheap) SCSI controller
for Mustek scanners. For example, ncr810 based cards are known to work
fine and cost as little as fifty US dollars.
@ -217,8 +217,8 @@
driver- and platform-specific information.
The ScanExpress models have sometimes trouble with high resolution
color mode. If you encounter sporadic corrupted images (parts dupliâ€<EFBFBD>
cated or shifted horizontally) kill all other applications before scanâ€<EFBFBD>
color mode. If you encounter sporadic corrupted images (parts dupli-
cated or shifted horizontally) kill all other applications before scan-
ning and (if sufficient memory is available) disable swapping.
Details on how to get the Mustek SCSI adapters and other cards running
@ -233,7 +233,7 @@
scanner does not connected to the printer parallel port).
These scanners can be configured by listing the port number of the
adapter or the parallel port in the mustek.conf file. Valid port numâ€<EFBFBD>
adapter or the parallel port in the mustek.conf file. Valid port num-
bers for the 600 II N are <I>0x26b</I>, <I>0x2ab</I>, <I>0x2eb</I>, <I>0x22b</I>, <I>0x32b</I>, <I>0x36b</I>,
<I>0x3ab</I>, <I>0x3eb</I>. For the 600 II EP use one of these: <I>parport0</I>, <I>parport1</I>,
<I>parport2</I>, <I>0x378</I>, <I>0x278</I>, <I>0x3bc</I>. Pick one that doesn't conflict with the
@ -281,19 +281,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MUSTEK</B>
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
@ -331,7 +331,7 @@
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â€<EFBFBD>
More detailed bug information is available at the Mustek backend home-
page: <I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
13 Jul 2008 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>

111
man/sane-mustek_pp.5.html
Wyświetl plik

@ -70,7 +70,7 @@
driver. They seem to be solved now.
(**) Problems have been reported in the past for the MD/LT9850 type
(striped scans, head moving in wrong direction at some resoluâ€<EFBFBD>
(striped scans, head moving in wrong direction at some resolu-
tions). It is not known whether the current version of the
driver still has these problems.
@ -80,8 +80,8 @@
(***) Possibly, the engine_delay parameter has to be set to 1 ms for
accurate engine movements.
Please note that this backend is still under construction. Certain modâ€<EFBFBD>
els are currently not supported and some may never be because the comâ€<EFBFBD>
Please note that this backend is still under construction. Certain mod-
els are currently not supported and some may never be because the com-
munication protocol is still unknown (eg., SE 12000 P).
Some scanners work faster when <B>EPP/ECP</B> is enabled in the BIOS. EPP mode
@ -93,7 +93,7 @@
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 <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). Note also that the backend
<I>does</I> <I>not</I> support <I>parport</I> <I>sharing</I>, i.e. if you try printing while scanâ€<EFBFBD>
<I>does</I> <I>not</I> support <I>parport</I> <I>sharing</I>, 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 <I>sane-musteka4s2</I> backend. You can only enable one of them in your
@ -114,23 +114,23 @@
where
<B>&lt;name&gt;</B> is an arbitrary name for the device, optionally enclosed by douâ€<EFBFBD>
<B>&lt;name&gt;</B> is an arbitrary name for the device, optionally enclosed by dou-
ble quotes, for instance "LifeTec 9350".
<B>&lt;port</B> <B>name&gt;</B> is the name of the parallel port to which the device is
connected. In case libieee1284 is used for communication with
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par</B>â€<B>â</B>€<EFBFBD>
the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
<B>port1</B>, and <B>parport2</B>.
In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>, or
<B>0x3BC</B>. 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 <I>(old</I> <I>setup)</I>, port ad-
dresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>, or <B>0x3BC</B>.
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 <B>*</B> to
probe for your scanner.
@ -145,17 +145,17 @@
<B>Choosing</B> <B>the</B> <B>wrong</B> <B>driver</B> <B>can</B> <B>damage</B> <B>your</B> <B>scanner!</B>
Especially, using the 1200CP settings on a 600CP can be harmful.
If the scanner starts making a loud noise, turn it off immediâ€<EFBFBD>
If the scanner starts making a loud noise, turn it off immedi-
ately !!!
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not danâ€<EFBFBD>
Using the cis600 driver on a 1200CP or a 1200CP+ is probably not dan-
gerous. The cis1200+ driver also works for the 1200CP, and using the
cis1200 driver on a 1200CP+ will typically result in scans that cover
only half of the width of the scan area (also not dangerous).
If unsure about the exact model of your OEM version, check the optical
resolution in the manual or on the box: the 600CP has a maximum optical
resolution of 300x600 DPI, whereas the 1200CP and 1200CP+ have a maxiâ€<EFBFBD>
resolution of 300x600 DPI, whereas the 1200CP and 1200CP+ have a maxi-
mum optical resolution of 600x1200 DPI.
Examples:
@ -166,16 +166,16 @@
scanner Mustek_600IIIEP * ccd300
If in doubt which port you have to use, or whether your scanner is
detected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all configâ€<EFBFBD>
ured ports.
If in doubt which port you have to use, or whether your scanner is de-
tected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all configured
ports.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <B>mustek_pp.conf</B> 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â€<EFBFBD>
lines starting with a hash mark (#) are ignored. Options have the fol-
lowing format:
<I>option</I> <I>&lt;name&gt;</I> <I>[&lt;value&gt;]</I>
@ -187,7 +187,7 @@
<B>Common</B> <B>options</B>
<B>bw</B> <B>&lt;value&gt;</B>
Black/white discrimination value to be used during lineart scanâ€<EFBFBD>
Black/white discrimination value to be used during lineart scan-
ning. Pixel values below this value are assumed to be black,
values above are assumed to be white.
Default value: 127
@ -199,10 +199,10 @@
<B>CIS</B> <B>driver</B> <B>options</B>
<B>top_adjust</B> <B>&lt;value&gt;</B>
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
@ -229,15 +229,15 @@
Under normal circumstances, it is sufficient for the driver to
wait for the scanner signaling that the engine is stable, before
a new engine command can be transmitted. In rare cases, certain
scanners and/or parallel port chipsets appear to prevent reliâ€<EFBFBD>
scanners and/or parallel port chipsets appear to prevent reli-
able detection of the engine state. As a result, engine commands
are transmitted too soon and the movement of the scanner head
becomes unreliable. Inaccuracies ranging up to 10 cm over the
whole vertical scan range have been reported. To work around
this problem, the engine_delay option can be set. If it is set,
the driver waits an additional amount of time after every engine
command, equal to the engine_delay parameter, expressed in milâ€<EFBFBD>
liseconds. It practice an engine_delay of 1 ms is usually suffiâ€<EFBFBD>
command, equal to the engine_delay parameter, expressed in mil-
liseconds. It practice an engine_delay of 1 ms is usually suffi-
cient. The maximum delay is 100 ms.
Note that every additional ms of delay can add up to 14 seconds
@ -349,19 +349,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MUSTEK_PP</B>
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.
@ -411,37 +411,36 @@
</PRE>
<H2>BUGS</H2><PRE>
Too many... please send bug reports to
<I>sane-devel@alioth-lists.debian.net</I> (note that you have to subscribe
first to the list before you can send emails... see
http://www.sane-project.org/mailing-lists.html)
Too many... please send bug reports to <I>sane-devel@alioth-lists.de-</I>
<I>bian.net</I> (note that you have to subscribe first to the list before you
can send emails... see http://www.sane-project.org/mailing-lists.html)
</PRE>
<H2>BUG REPORTS</H2><PRE>
If something doesn't work, please contact us (Jochen for the CCD scanâ€<EFBFBD>
ners, Eddy for the CIS scanners). But we need some information about
If something doesn't work, please contact us (Jochen for the CCD scan-
ners, Eddy for the CIS scanners). But we need some information about
your scanner to be able to help you...
<I>SANE</I> <I>version</I>
run "scanimage -V" to determine this
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
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
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/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.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical resoâ€<EFBFBD>
lution and lamp type of your scanner, both can be found in the
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.
<I>any</I> <I>further</I> <I>comments</I>
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.
13 Jul 2008 <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>

36
man/sane-mustek_usb.5.html
Wyświetl plik

@ -53,7 +53,7 @@
<I>special</I>
Where <I>special</I> is a path-name for the special device that corresponds to
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scanâ</I>€<EFBFBD>
a USB scanner. With Linux, such a device name could be <I>/dev/usb/scan-</I>
<I>ner0</I> or <I>/dev/usbscanner1</I>, for example.
For FreeBSD use <I>/dev/uscanner0</I>.
@ -61,8 +61,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>mustek</I><B>_</B><I>usb.conf</I> file is a list of options and
device names that correspond to Mustek USB scanners. Empty lines and
The contents of the <I>mustek</I><B>_</B><I>usb.conf</I> 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 <I>mustek</I><B>_</B><I>usb.conf</I>, it must be followed by a line containing the
keyword <B>option</B> and an option specifying the scanner type. The following
@ -116,19 +116,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_MUSTEK_USB</B>
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
@ -146,8 +146,8 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
<B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B>sane-plus-</B>
<B><A HREF="tek.5.html">tek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
<I>/usr/local/share/doc/sane-backends/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
<I>/usr/local/share/doc/sane-backends/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>
@ -156,7 +156,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
This backend is based on the Mustek 1200ub backend from Mustek, mainâ€<EFBFBD>
This backend is based on the Mustek 1200ub backend from Mustek, main-
tained by Tom Wang.
@ -169,10 +169,10 @@
In earlier versions this backend failed when it was loaded the second
time in some configurations. The only choice was to replug the scanner
in this case. The backend uses a workaround for that bug now but it's
only tested on Linux. Reports for other operating systems are appreciâ€<EFBFBD>
only tested on Linux. Reports for other operating systems are appreci-
ated.
More detailed bug information is available at the Mustek backend homeâ€<EFBFBD>
More detailed bug information is available at the Mustek backend home-
page <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
13 Jul 2008 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>

14
man/sane-mustek_usb2.5.html
Wyświetl plik

@ -20,7 +20,7 @@
The <B>sane-mustek_usb2</B> library implements a SANE (Scanner Access Now
Easy) backend that provides access to USB flatbed scanners based on the
Service &amp; Quality SQ113 chipset. At the moment, only the Mustek BearPaw
2448 TA Pro is supported. It's planned to add support for other scan‐
2448 TA Pro is supported. It's planned to add support for other scan-
ners that are based on the SQ113 and maybe SQ11 chip. For more details,
see the mustek_usb2 backend homepage:
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>.
@ -30,10 +30,10 @@
at the end of the scan area.
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‐
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 <I>sane-find-scanner</I> or syslog) to me. Even if the scanner's
name is only slightly different from the models already listed as sup‐
name is only slightly different from the models already listed as sup-
ported, please let me know.
@ -41,7 +41,7 @@
<H2>LIBUSB ISSUES</H2><PRE>
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‐
found by sane-find-scanner without further actions. For setting permis-
sions and general USB information looks at <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
@ -58,8 +58,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_MUSTEK_USB2</B>
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
@ -81,7 +81,7 @@
</PRE>
<H2>BUGS</H2><PRE>
Please contact me if you find a bug or missing feature: &lt;hen‐
Please contact me if you find a bug or missing feature: &lt;hen-
ning@meier-geinitz.de&gt;. Please send a debug log if your scanner isn't
detected correctly (see SANE_DEBUG_MUSTEK_USB2 above).

6
man/sane-nec.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-nec</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-nec</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to NEC SCSI scanners. This backend should be
considered <B>alpha-quality</B> software! In the current state it is known to
work with PC-IN500/4C scanners. Another MultiReader scanner series is
@ -52,8 +52,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_NEC</B>
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.

46
man/sane-net.5.html
Wyświetl plik

@ -17,10 +17,10 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-net</B> library implements a SANE (Scanner Access Now Easy) backâ€<EFBFBD>
The <B>sane-net</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to image acquisition devices through a network
connection. This makes it possible to control devices attached to a
remote host and also provides a means to grant users access to proâ€<EFBFBD>
remote host and also provides a means to grant users access to pro-
tected resources.
@ -52,7 +52,7 @@
Timeout (in seconds) for the initial connection to the <I>saned</I>
server. This will prevent the backend from blocking for several
minutes trying to connect to an unresponsive <I>saned</I> host (network
outage, host down, ...). The environment variable <B>SANE_NET_TIME</B>â€<B>â</B>€<EFBFBD>
outage, host down, ...). The environment variable <B>SANE_NET_TIME-</B>
<B>OUT</B> can also be used to specify the timeout at runtime.
Empty lines and lines starting with a hash mark (#) are ignored. Note
@ -66,19 +66,19 @@
::1
The above list of hosts can be extended at run-time using environment
variable <B>SANE_NET_HOSTS</B>. This environment variable is a colon-sepaâ€<EFBFBD>
rated list of hostnames or IP addresses that should be contacted in
addition to the hosts mentioned in the configuration file. For examâ€<EFBFBD>
ple, a user could set the environment variable to the string:
variable <B>SANE_NET_HOSTS</B>. 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 <I>new.scanner.com</I> , <I>[::1]</I> , <I>192.168.0.2</I> and <I>scanâ</I>€<EFBFBD>
To request that hosts <I>new.scanner.com</I> , <I>[::1]</I> , <I>192.168.0.2</I> and <I>scan-</I>
<I>ner.univ.edu</I> are contacted in addition to the hosts listed above.
For this backend to function properly, it is also necessary to define
the <B>sane-port</B> service in <I>/etc/services</I>. The <B>sane</B> service should be
defined using a line of the following form:
the <B>sane-port</B> service in <I>/etc/services</I>. The <B>sane</B> service should be de-
fined using a line of the following form:
sane-port 6566/tcp # SANE network scanner daemon
@ -103,18 +103,18 @@
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the configâ€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_NET_HOSTS</B>
A colon-separated list of host names or IP addresses to be conâ€<EFBFBD>
A colon-separated list of host names or IP addresses to be con-
tacted by this backend.
<B>SANE_NET_TIMEOUT</B>
@ -122,16 +122,16 @@
for the initial connection request.
<B>SANE_DEBUG_NET</B>
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.
</PRE>
<H2>BUGS</H2><PRE>
If saned has timed out, the net backend may loop with authorization
requests.
If saned has timed out, the net backend may loop with authorization re-
quests.
</PRE>

6
man/sane-niash.5.html
Wyświetl plik

@ -56,15 +56,15 @@
If you use a
Hewlett-Packard Scanjet 3400c or
Hewlett-Packard Scanjet 4300c
together with Linux kernel <B>2.6</B>, kernel version <B>2.6.8</B> or newer is neces‐
together with Linux kernel <B>2.6</B>, kernel version <B>2.6.8</B> or newer is neces-
sary.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_NIASH</B>
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

38
man/sane-p5.5.html
Wyświetl plik

@ -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.
<B>EPP/ECP</B> <B>MODES</B> <B>ONLY</B> The current version of the backend uses only EPP or
ECP mode to communicate with the scanner. It is recommended that you
@ -80,19 +80,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_P5</B>
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.
@ -114,13 +114,13 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Stéphane Voltz &lt;stef.dev@free.fr&gt;
St<B>e</B>phane Voltz &lt;stef.dev@free.fr&gt;
</PRE>
<H2>CREDITS</H2><PRE>
Support for the Prima PagePartner has been made possible thank to an
hardware donation by Sébastien Lange.
hardware donation by S<B>e</B>bastien Lange.
</PRE>
@ -135,13 +135,13 @@
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
run "SANE_DEBUG_P5=255 scanimage -L 2&gt;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.
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.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso‐
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.

4
man/sane-pie.5.html
Wyświetl plik

@ -17,8 +17,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pie</B> library implements a SANE (Scanner Access Now Easy) back‐
end that provides access to PIE, Devcom and AdLib SCSI flatbed scan‐
The <B>sane-pie</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to PIE, Devcom and AdLib SCSI flatbed scan-
ners.
At present, the following scanners should work with this backend:

22
man/sane-pieusb.5.html
Wyświetl plik

@ -12,8 +12,8 @@
</PRE>
<H2>NAME</H2><PRE>
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
</PRE>
@ -45,7 +45,7 @@
after each scan.
However, for best results, it is recommended to do a preview for every
slide since this sets gamma, brightness, and contrast to optimal valâ€<EFBFBD>
slide since this sets gamma, brightness, and contrast to optimal val-
ues.
Attention: SANE does not have an automatic landscape/portrait detection
@ -55,13 +55,13 @@
</PRE>
<H2>DIRT REMOVAL</H2><PRE>
If available, pieusb supports infrared scans for dirt detection and
removal. This must be enabled via the 'Clean image' setting.
If available, pieusb supports infrared scans for dirt detection and re-
moval. This must be enabled via the 'Clean image' setting.
</PRE>
<H2>KNOWN PROBLEMS</H2><PRE>
The pieusb backend supports dirt removal based on infrared scan inforâ€<EFBFBD>
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
@ -72,8 +72,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PIEUSB</B>
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.
@ -111,13 +111,13 @@
</PRE>
<H2>CONTACT AND BUG-REPORTS</H2><PRE>
Please send any information and bug-reports to:
<B>Klaus</B> <B>K</B>Ã<B>Ã</B>ƒÂ<B>Â</B>¤<B>mpf</B> <B>&lt;kkaempf@suse.com&gt;</B>
<B>Klaus</B> <B>KAxmpf</B> <B>&lt;kkaempf@suse.com&gt;</B>
</PRE>
<H2>AUTHORS</H2><PRE>
The pieusb backend is based on work by Jan Vleeshouwers, Michael Rickâ€<EFBFBD>
mann, and Klaus Kämpf
The pieusb backend is based on work by Jan Vleeshouwers, Michael Rick-
mann, and Klaus K<B>Ax</B>mpf
10 Aug 2015 <B><A HREF="sane-pieusb.5.html">sane-pieusb(5)</A></B>
</PRE>

42
man/sane-pint.5.html
Wyświetl plik

@ -17,11 +17,11 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pint</B> 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.
The <B>sane-pint</B> library implements a SANE (Scanner Access Now Easy) back-
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 <B><A HREF="ioctl.2.html">ioctl(2)</A></B> interface to many different
scanner types. However, this backend has only been tested with flatbed
@ -30,8 +30,8 @@
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
<I>sane-devel@alioth-lists.debian.net</I>. Have a look at
send a mail with the relevant information for your scanner to <I>sane-de-</I>
<I>vel@alioth-lists.debian.net</I>. Have a look at
http://www.sane-project.org/mailing-lists.html concerning subscription
to sane-devel.
@ -42,7 +42,7 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre‐
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the scanner. The special device name must be a PINT device
or a symlink to such a device. For example, under NetBSD or OpenBSD,
such a device name could be <I>/dev/ss0</I> or <I>/dev/scan0</I>.
@ -79,19 +79,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_PINT</B>
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.
@ -103,7 +103,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Gordon Matzigkeit, adapted from existing backends written by David Mos‐
Gordon Matzigkeit, adapted from existing backends written by David Mos-
berger.
@ -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

306
man/sane-pixma.5.html
Wyświetl plik

@ -21,17 +21,19 @@
The <B>sane-pixma</B> 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:
PIXMA MG2100, MG2200, MG2400, MG2500, MG2900, MG3100, MG3200
PIXMA MG3500, MG3600, MG4200, MG5100, MG5200, MG5300, MG5400
PIXMA MG5500, MG5600, MG5700, MG6100, MG6200, MG6300, MG6400
PIXMA MG7100, MG7500, MG7700, MG8200
PIXMA E510
PIXMA G2000, G2010, G2100
PIXMA MG2100, MG2200, MG2400, MG2500, MG2900, MG3000, MG3100
PIXMA MG3200, MG3500, MG3600, MG4200, MG5100, MG5200, MG5300
PIXMA MG5400, MG5500, MG5600, MG5700, MG6100, MG6200, MG6300
PIXMA MG6400, MG7100, MG7500, MG7700, MG8200
PIXMA MP140, MP150, MP160, MP170, MP180, MP190
PIXMA MP210, MP220, MP230, MP240, MP250, MP260, MP270, MP280
PIXMA MP360, MP370, MP390
@ -44,17 +46,22 @@
PIXMA MX300, MX310, MX330, MX340, MX350, MX360, MX370
PIXMA MX410, MX420, MX470, MX510, MX520, MX530, MX700, MX720
PIXMA MX850, MX860, MX870, MX882, MX885, MX890, MX920, MX7600
PIXMA TS3100, TS5000, TS6100, TS6200, TS8000, TS8200
PIXUS MP10
imageCLASS MF634Cdw, MF733Cdw
imageCLASS MF3110, MF3240, MF4010, MF4018
imageCLASS MF4120, MF4122, MF4140, MF4150
imageCLASS MF4270, MF4350d, MF4370dn, MF4380dn
imageCLASS MF4410, MF4430, MF4570dw, MF4660, MF4690
imageCLASS MF5730, MF5770, MF6550, MPC200, D420, D480, D530
i-SENSYS MF230, MF240, MF3010, MF4320d, MF4330d, MF4500, MF4700
i-SENSYS MF4800, MF6100, MF8200C, MF8300
imageRUNNER 1020/1024/1025
imageCLASS MF5730, MF5770, MF6550, MPC200
imageCLASS D420, D480, D530, D570
i-SENSYS MF210, MF230, MF240, MF620, MF630, MF640, MF645C, MF730
i-SENSYS MF731/733, MF741/743, MF3010, MF4320d, MF4330d, MF4500
i-SENSYS MF4700, MF4800, MF6100, MF8030, MF8200C, MF8300
imageRUNNER 1020/1024/1025, 1133
CanoScan 8800F, 9000F, 9000F Mark II
MAXIFY MB5000 (ADF is not working)
CanoScan LiDE 300, 400
MAXIFY MB2000, MB2100, MB2300, MB2700, MB5000, MB5400
The following models are not well tested and/or the scanner sometimes
hangs and must be switched off and on.
@ -62,114 +69,128 @@
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, E510, E560, E600, E610
PIXMA MG3000, MG4100, MG6500, MG6600, MG6800, MG6900, MG8100
PIXMA E400, E410, E460, E470, E480, E500, E560, E600, E610
PIXMA E3100, E3300, E4200
PIXMA MG4100, MG6500, MG6600, MG6800, MG6900, MG8100
PIXMA MP375R, MP493, MP495, MP740
PIXMA MX320, MX390, MX430, MX450, MX490, MX710
PIXMA G3000
PIXMA TS9000, TS800, TS6000, TS5000
PIXUS MP5
imageCLASS MF810/820, MF5630, MF5650, MF5750, MF8030, MF8170c
imageCLASS MPC190
imageRUNNER 1133
i-SENSYS MF210, MF220, MF5880dn, MF5900, MF6680dn, MF8500C
MAXIFY MB2000, MB2300, MB5300
PIXMA G3000, G3010, G4000, G4010, G6000, G6080
PIXMA TR4500, TR7500, TR7530, TR8500, TR8530, TR8580, TR9530
PIXMA TS5100, TS6000, TS6130, TS6180, TS6230, TS6280, TS6300
PIXMA TS6330, TS6380, TS7330, TS8100, TS8130, TS8180, TS8230
PIXMA TS8280,, TS8300, TS8330, TS8380, TS9000, TS9100, TS9180
PIXMA TS9500, TS9580
PIXUS MP5, XK50, XK60, XK70, XK80
imageCLASS 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 MB5100, 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 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.
</PRE>
<H2>OPTIONS</H2><PRE>
Besides "well-known" options (e.g. resolution, mode etc.) pixma backend
also provides the following options, i.e. the options might change in
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
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.
<I>adf-wait</I>
This option enables and sets the time in seconds waiting for a
document inserted into the <B>Automatic</B> <B>Document</B> <B>Feeder</B>. The maxi‐
This option enables and sets the time in seconds waiting for a
document inserted into the <B>Automatic</B> <B>Document</B> <B>Feeder</B>. The maxi-
mum allowed waiting time is 3600 sec (= 1 hour).
<I>button-controlled</I>
This option can be used by applications (like <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and
<B><A HREF="scanimage.1.html">scanimage(1)</A></B>) 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 <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and
<B><A HREF="scanimage.1.html">scanimage(1)</A></B>) 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.)
<I>button-update</I> <I>(deprecated)</I>
(write only) In the past this option was required to be set to
force reading of the button status for <I>button-1</I> and <I>button-2.</I>
The <B>sane-pixma</B> no longer requires this option to be used: if no
fresh data is available, it will be now requested automatically
(write only) In the past this option was required to be set to
force reading of the button status for <I>button-1</I> and <I>button-2.</I>
The <B>sane-pixma</B> 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.
<I>button-1</I> <I>button-2</I>
(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.
<I>original</I>
(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
= A4, 2 = Letter, 8 = 10x15, 9 = 13x18, b = auto. Not all scan‐
be scanned if the scanner provides that data. Known values of
type: 1 = document, 2 = foto, 5 = film. Known values of size: 1
= A4, 2 = Letter, 8 = 10x15, 9 = 13x18, b = auto. Not all scan-
ners can provide this data.
<I>target</I> (read only) Returns the value of the target of the scan opera‐
<I>target</I> (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,
3 = PDF, 4 = Compact PDF. For some scanners this value is equiv‐
alent to the number of the pressed button. Not all scanners can
= 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
provide this data.
<I>scan-resolution</I>
(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.
@ -184,28 +205,32 @@
that support dynamic loading).
<I>/usr/local/etc/sane.d/pixma.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below). The file contains an optional list of
networked scanners. Normally only scanners that cannot be auto-
detected because they are on a different subnet shall be listed
here. If your OS does not allow enumeration of interfaces (i.e.
it does not support the getifaddrs() function) you also may need
to add your scanner here as well.
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>Scanners</I> <I>shall</I> <I>be</I> <I>listed</I> <I>in</I> <I>the</I> <I>configuraton</I> <I>file</I> <I>as</I> <I>follows:</I>
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
well.
<I>Scanners</I> <I>shall</I> <I>be</I> <I>listed</I> <I>in</I> <I>the</I> <I>configuration</I> <I>file</I> <I>as</I> <I>follows:</I>
<I>&lt;method&gt;://&lt;host&gt;[:port][/timeout=&lt;value&gt;]</I>
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
@ -213,20 +238,31 @@
Define scanners each on a new line.
More globally applicable tinmeouts can be set using the bjnp-
timeout parameter as folllows:
More globally applicable timeouts can be set using the bjnp-
timeout parameter as follows:
<I>bjnp-timeout=&lt;value&gt;</I>
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
explicitely 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 settng 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 the first non-commented line contains <B>networking=no</B>
all networking will be disabled. This will cause all
further statements in the configuration file to be ig-
nored.
- A line that contains <B>auto_detection=no</B> will cause auto-
detection to be skipped. Explicitely defined network
scanners will still be probed.
</PRE>
<H2>USB SUPPORT</H2><PRE>
@ -236,54 +272,61 @@
</PRE>
<H2>NETWORKING SUPPORT</H2><PRE>
The pixma backend supports network scanners using the so called Canon
BJNP protocol and MFNP protocol. Both IPv4 and IPv6 are supported, but
IPv6 is as yet untested with MFNP. Please report your results on the
mailing list.
BJNP and MFNP protocols.
Configuration is normally not required. The pixma backend will auto-
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.
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.
If your scanner can not be auto-detected, you can add it to the pixma
If your scanner can not be auto-detected, you can add it to the pixma
configuration file (see above).
</PRE>
<H2>FIREWALLING FOR NETWORKED SCANNERS</H2><PRE>
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.
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 de-
scribed 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.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PIXMA</B>
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
@ -293,10 +336,10 @@
21 full dump USB traffic
<B>SANE_DEBUG_BJNP</B>
If the library was compiled with debug support enabled, this
environment variable controls the debug level for the <B>BJNP</B> <B>and</B>
<B>MFNP</B> 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 <B>BJNP</B> <B>and</B>
<B>MFNP</B> 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)
@ -306,28 +349,27 @@
5 Print full protocol contents
<B>PIXMA_EXPERIMENT</B>
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.
<B>SANE_CONFIG_DIR</B>
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 <B>SANE_CONFIG_DIR</B> 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 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <I>http://home.arcor.de/wittawat/pixma/,</I>
<I>http://mp610.blogspot.com/</I>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>,
In case of trouble with a recent Pixma model, try the latest code for
the pixma backend, available in the Sane git repository at:
@ -345,7 +387,7 @@
not be able to write subdrivers for models we don't have. See also the
project homepage.
20 May 2017 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
28 Dec 2019 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
</PRE>
<HR>
<ADDRESS>

50
man/sane-plustek.5.html
Wyświetl plik

@ -19,14 +19,14 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-plustek</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to USB flatbed scanners based on National
Semiconductor Merlin chipsets (LM9831, 9832 and 9833). If you're lookâ€<EFBFBD>
Semiconductor Merlin chipsets (LM9831, 9832 and 9833). If you're look-
ing for parallel-port support for Plustek scanner please refer to the
<B>sane-plustek_pp</B> backend.
</PRE>
<H2>SUPPORTED DEVICES</H2><PRE>
The Backend is able to support USB scanner based on the National Semiâ€<EFBFBD>
The Backend is able to support USB scanner based on the National Semi-
conductor chipsets LM9831, LM9832 and LM9833. The following tables show
various devices which are currently reported to work. If your Plustek
scanner has another Product ID, then the device is <B>NOT</B> supported by
@ -155,7 +155,7 @@
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
<I>device</I> <I>/dev/usbscanner</I>
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usbâ</I>€<EFBFBD>
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
<I>scanner</I>) has to be interpreted as USB scanner device. If vendor- and
product-id has not been specified, the backend tries to detect this by
its own. If device is set to <I>auto</I> then the next matching device is
@ -166,8 +166,8 @@
<B>The</B> <B>Options:</B>
option warmup t
<I>t</I> specifies the warmup period in seconds, if set to -1, the
automatic warmup function will be used
<I>t</I> specifies the warmup period in seconds, if set to -1, the au-
tomatic warmup function will be used
option lampOff t
<I>t</I> is the time in seconds for switching off the lamps in standby
@ -195,7 +195,7 @@
option altCalibration b
<I>b</I> 0 --&gt; use standard calibration routines,
1 --&gt; use alternate calibration (only non Plustek devices, stanâ€<EFBFBD>
1 --&gt; use alternate calibration (only non Plustek devices, stan-
dard for CIS devices)
option skipFine b
@ -254,7 +254,7 @@
option green_offset go
option blue_gain b
option blue_offset bo
<I>r</I> <I>g</I> <I>b</I> <I>ro</I> <I>go</I> <I>bo</I> These values can be used to set the gain and offâ€<EFBFBD>
<I>r</I> <I>g</I> <I>b</I> <I>ro</I> <I>go</I> <I>bo</I> These values can be used to set the gain and off-
set values of the AFE for each channel. The range is between 0
and 63. -1 means autocalibration.
@ -289,19 +289,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_PLUSTEK</B>
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
@ -311,7 +311,6 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>,
<I>/usr/local/share/doc/sane-backends/plustek/Plustek-USB.changes</I>
<I>http://www.gjaeger.de/scanner/plustek/</I>
</PRE>
@ -323,17 +322,14 @@
Mailing-List archive at:
<B>http://www.sane-project.org/mailing-lists.html</B>
or directly from the projects' homepage at:
<B>http://www.gjaeger.de/scanner/plustek/</B>
To obtain debug messages from the backend, please set the environment-
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I> before calling your favorite scan-frontend
(i.e. xscanimage).
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>xscanimage</B>
(i.e. scanimage).
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK=20</B> <B>;</B> <B>scanimage</B>
The value controls the verbosity of the backend. Please note, that valâ€<EFBFBD>
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â€<EFBFBD>
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.
@ -346,7 +342,7 @@
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â€<EFBFBD>
* 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
@ -354,7 +350,7 @@
* Negative/Slide scanning quality is poor.
13 Feb 2013 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
03 Nov 2017 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
</PRE>
<HR>
<ADDRESS>

124
man/sane-plustek_pp.5.html
Wyświetl plik

@ -12,7 +12,7 @@
</PRE>
<H2>NAME</H2><PRE>
sane-plustek_pp - SANE backend for Plustek parallel port flatbed scanâ€<EFBFBD>
sane-plustek_pp - SANE backend for Plustek parallel port flatbed scan-
ners
@ -20,9 +20,9 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-plustek_pp</B> 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â€<EFBFBD>
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 plustek_pp backend code - see also sec-
tion <B>BUILDING</B> <B>THE</B> <B>KERNEL</B> <B>MODULE</B> for further information.
@ -77,8 +77,8 @@
<B>ARIES</B> <B>SCANNERS</B>
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:
--------------------------- -------------- ------------
@ -87,7 +87,7 @@
<B>BrightScan</B> <B>SCANNERS</B>
There's one scanner sold as BrightScan OpticPro Scanner, this is also a
rebadged Plustek device. The following table will show the relationâ€<EFBFBD>
rebadged Plustek device. The following table will show the relation-
ship:
Model: Remarks:
@ -98,15 +98,15 @@
</PRE>
<H2>DEVICE NAMES</H2><PRE>
This backend works in two modes, the so called "direct-mode" and the
"kernel-mode". In direct-mode, the user-space backend is used, in kerâ€<EFBFBD>
"kernel-mode". In direct-mode, the user-space backend is used, in ker-
nel-mode, you should have a kernel-module named pt_drv loaded. This
backends default device is:
<I>0x378</I>
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
@ -154,25 +154,25 @@
<I>m</I> = 0 default: no override
<I>m</I> = 1 OpticPro 9630PL override (works if OP9630 has been
detected) forces legal size (14")
<I>m</I> = 1 OpticPro 9630PL override (works if OP9630 has been de-
tected) forces legal size (14")
<I>m</I> = 2 Primax 4800Direct override (works if OP600 has been
detected) swaps red/green color
<I>m</I> = 2 Primax 4800Direct override (works if OP600 has been de-
tected) swaps red/green color
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been
detected) disables backends transparency/negative capaâ€<C3A2>
bilities
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been de-
tected) disables backends transparency/negative capabili-
ties
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been
detected) disables backends transparency/negative capaâ€<C3A2>
bilities
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been de-
tected) disables backends transparency/negative capabili-
ties
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been
detected) enables A3 scanning
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been de-
tected) enables A3 scanning
<I>m</I> = 6 OpticPro 4800P override (works if OP600 has been
detected) swaps red/green color
<I>m</I> = 6 OpticPro 4800P override (works if OP600 has been de-
tected) swaps red/green color
<I>m</I> = 7 Primax 4800Direct 30bit override (works if OP4830 has
been detected)
@ -194,7 +194,7 @@
that the kernelsources need to be configured correctly. Refer to your
distributions manual on how this is done. As root user, try
<I>./MakeModule.sh</I>
the script will try and get all necessary information about your runâ€<EFBFBD>
the script will try and get all necessary information about your run-
ning kernel and will lead you through the whole installation process.
<B>Note:</B> <B>Installing</B> <B>and</B> <B>loading</B> <B>the</B> <B>can</B> <B>only</B> <B>be</B> <B>done</B> <B>as</B> superuser.
@ -204,20 +204,20 @@
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 <B>/etc/modules.conf</B> <B>(kernel</B> <B>&lt;</B> <B>2.6.x)</B> or <B>/etc/mod</B>â€<B>â</B>€<EFBFBD>
the options to the file <B>/etc/modules.conf</B> <B>(kernel</B> <B>&lt;</B> <B>2.6.x)</B> or <B>/etc/mod-</B>
<B>probe.conf</B> <B>(kernel</B> <B>&gt;=</B> <B>2.6.x)</B>
<B>The</B> <B>Options:</B>
lampoff=lll
The value <I>lll</I> tells the driver, after how many seconds to
switch-off the lamp(s). The default value is 180. 0 will disâ€<EFBFBD>
switch-off the lamp(s). The default value is 180. 0 will dis-
able this feature.
<B>HINT:</B> Do not use a value that is too small, because often
switching on/off the lamps will reduce their lifetime.
port=ppp
<I>ppp</I> specifies the port base address, where the scanner is conâ€<EFBFBD>
nected to. The default value is 0x378, which is normally a stanâ€<EFBFBD>
<I>ppp</I> specifies the port base address, where the scanner is con-
nected to. The default value is 0x378, which is normally a stan-
dard.
warmup=www
@ -233,32 +233,32 @@
delayed functions, 0 --&gt; use the non-delayed ones
forceMode=fm
<I>fm</I> specifies port mode which should be used, 0 --&gt; autodetecâ€<EFBFBD>
<I>fm</I> specifies port mode which should be used, 0 --&gt; autodetec-
tion, 1 --&gt; use SPP mode and 2 --&gt; use EPP mode
mov=m
<I>m</I> = 0 default: no override
<I>m</I> = 1 OpticPro 9630PL override (works if OP9630 has been
detected) forces legal size (14")
<I>m</I> = 1 OpticPro 9630PL override (works if OP9630 has been de-
tected) forces legal size (14")
<I>m</I> = 2 Primax 4800Direct override (works if OP600 has been
detected) swaps red/green color
<I>m</I> = 2 Primax 4800Direct override (works if OP600 has been de-
tected) swaps red/green color
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been
detected) disables backends transparency/negative capaâ€<C3A2>
bilities
<I>m</I> = 3 OpticPro 9636 override (works if OP9636 has been de-
tected) disables backends transparency/negative capabili-
ties
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been
detected) disables backends transparency/negative capaâ€<C3A2>
bilities
<I>m</I> = 4 OpticPro 9636P override (works if OP9636 has been de-
tected) disables backends transparency/negative capabili-
ties
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been
detected) enables A3 scanning
<I>m</I> = 5 OpticPro A3I override (works if OP12000 has been de-
tected) enables A3 scanning
<I>m</I> = 6 OpticPro 4800P override (works if OP600 has been
detected) swaps red/green color
<I>m</I> = 6 OpticPro 4800P override (works if OP600 has been de-
tected) swaps red/green color
<I>m</I> = 7 Primax 4800Direct 30bit override (works if OP4830 has
been detected)
@ -281,16 +281,16 @@
The current driver works best, when the parallel port has been set to
EPP-mode. When detecting any other mode such as ECP or PS/2 the driver
tries to set to a faster, supported mode. If this fails, it will use
the SPP mode, as this mode should work with all Linux supported paralâ€<EFBFBD>
the SPP mode, as this mode should work with all Linux supported paral-
lel ports. If in doubt, enter your BIOS and set it to any mode except
ECP.
Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
adapter card. This card is <B>not</B> supported by the driver.
The ASIC 96001/3 based models have sometimes trouble with high resoluâ€<EFBFBD>
tion modes. If you encounter sporadic corrupted images (parts dupliâ€<EFBFBD>
cated or shifted horizontally) kill all other applications before scanâ€<EFBFBD>
The ASIC 96001/3 based models have sometimes trouble with high resolu-
tion modes. If you encounter sporadic corrupted images (parts dupli-
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.
@ -321,19 +321,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_PLUSTEK_PP</B>
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
@ -343,7 +343,6 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>,
<I>/usr/local/share/doc/sane-backends/plustek/Plustek-PARPORT.changes</I>
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>
</PRE>
@ -355,12 +354,9 @@
Mailing-List archive at:
<B>http://www.sane-project.org/mailing-lists.html</B>
or directly from the projects' homepage at:
<B>http://www.gjaeger.de/scanner/plustek_pp/</B>
To obtain debug messages from the backend, please set the environment-
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I><B>_</B><I>PP</I> before calling your favorite scan-fronâ€<C3A2>
tend (i.e. xscanimage).
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>PLUSTEK</I><B>_</B><I>PP</I> before calling your favorite scan-front-
end (i.e. xscanimage).
<B>i.e.:</B> <B>export</B> <B>SANE_DEBUG_PLUSTEK_PP=20</B> <B>;</B> <B>xscanimage</B>
The value controls the verbosity of the backend.

16
man/sane-pnm.5.html
Wyświetl plik

@ -17,11 +17,11 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pnm</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-pnm</B> 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
PBM bitmap files, PGM grayscale files, and PPM pixmap files). The pur-
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,16 +48,16 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PNM</B>
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.
</PRE>
<H2>BUGS</H2><PRE>
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
If the pnm backend is installed and saned is used to allow users on re-
mote 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

22
man/sane-qcam.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-qcam</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-qcam</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access Connectix QuickCam cameras.
@ -71,19 +71,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_QCAM</B>
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.

28
man/sane-ricoh.5.html
Wyświetl plik

@ -31,11 +31,11 @@
<I>special</I>
Where <I>special</I> 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 <I>sane-find-scanner</I>
to a SCSI scanner. The special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
</PRE>
@ -58,19 +58,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_RICOH</B>
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

81
man/sane-ricoh2.5.html 100644
Wyświetl plik

@ -0,0 +1,81 @@
<HTML>
<HEAD>
<TITLE>sane-ricoh2.5</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="../images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>sane-ricoh2.5</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B>
</PRE>
<H2>NAME</H2><PRE>
sane-ricoh2 - SANE backend for Ricoh flatbed scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-ricoh2</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Ricoh flatbed scanners:
SG-3110SFNw
SG-3100SNw
SP-100SU
SP-111SU (SP-112SU)
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/lib/sane/libsane-ricoh2.a</I>
The static library implementing this backend.
<I>/usr/local/lib/sane/libsane-ricoh2.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
</PRE>
<H2>OPTIONS</H2><PRE>
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.
The following options are supported by ricoh2:
<B>--mode</B> <B>color|gray</B>
Color or grayscale mode.
<B>--resolution</B> <B>300|600</B>
DPI resolution.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_RICOH2</B>
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.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
Stanislav Yuzvinsky
04 Sep 2019 <B><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B>
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>

18
man/sane-rts8891.5.html
Wyświetl plik

@ -30,10 +30,10 @@
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 or through GUI elements in xs-
canimage or xsane.
If you have any strange behavior, please report to the backend main‐
If you have 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
@ -45,8 +45,8 @@
are <I>R</I> <I>Color</I> <I>,</I> <I>Gray</I> and <I>Lineart</I> 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.
<B>--resolution</B>
selects the resolution for a scan. The horizontal and vertical
@ -71,8 +71,8 @@
<B>--threshold</B>
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.
</PRE>
@ -138,7 +138,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
This backend has been developed by Stéphane Voltz.
This backend has been developed by St<B>e</B>phane Voltz.
<I>http://stef.dev.free.fr/sane/rts8891</I>
@ -146,7 +146,7 @@
<H2>CREDITS</H2><PRE>
Many thanks go to:
Laurent Fournier who donated me a HP4470c. Vladimir Sysoev and
"TheUnruly Squash" for the time they spent recording USB activ‐
"TheUnruly Squash" for the time they spent recording USB activ-
ity and testing the experimental version on HP4400 models.
8 Dec 2008 <B><A HREF="sane-rts8891.5.html">sane-rts8891(5)</A></B>

28
man/sane-s9036.5.html
Wyświetl plik

@ -28,11 +28,11 @@
<I>special</I>
Where <I>special</I> 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 <I>sane-find-scanner</I>
to a SCSI scanner. The special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
</PRE>
@ -55,19 +55,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_S9036</B>
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

18
man/sane-sceptre.5.html
Wyświetl plik

@ -28,15 +28,15 @@
--------------------------- -------------------
Sceptre VividScan S1200 SCSI
The make of this scanner is KINPO, so other scanners from that manufac‐
The make of this scanner is KINPO, so other scanners from that manufac-
turer may also work (eg. the S600).
</PRE>
<H2>OPTIONS</H2><PRE>
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 or through GUI elements in xs-
canimage or xsane.
Valid command line options and their syntax can be listed by using
scanimage --help -d sceptre
@ -46,9 +46,9 @@
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Lineart,</I> <I>Halftone,</I> <I>Gray</I> <I>and</I> <I>Color.</I> 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.
levels of gray (8 bits). Color will produce a 24 bits color im-
age. The scanner supports 30 bits internally but it only exports
24.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do several
@ -60,7 +60,7 @@
<B>--gamma-correction</B>
controls the scanner internal gamma correction. Valid options
are "Default", "User defined", "High density printing" "Low den‐
are "Default", "User defined", "High density printing" "Low den-
sity printing" and "High contrast printing".
<B>--custom-gamma</B>
@ -116,8 +116,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SCEPTRE</B>
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.

86
man/sane-scsi.5.html
Wyświetl plik

@ -23,15 +23,15 @@
</PRE>
<H2>GENERAL INFO</H2><PRE>
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, <B>/dev/sg4</B> or <B>/dev/sge</B> is such a generic SCSI device). It is cus‐
Linux, <B>/dev/sg4</B> or <B>/dev/sge</B> is such a generic SCSI device). It is cus-
tomary to create a symlink from <B>/dev/scanner</B> to the generic SCSI device
that the scanner is connected to. In this case, the configuration file
simply lists the line <B>/dev/scanner</B>. For a detailed description of each
backend's configuration file, please refer to the relevant backend man‐
backend's configuration file, please refer to the relevant backend man-
ual page (e.g., <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for Epson scanners, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> for HP
scanners, etc.).
@ -52,7 +52,7 @@
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‐
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
@ -77,20 +77,20 @@
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
On some platforms (e.g., OpenStep), SANE device names take a special
form. This is explained below in the relevant platform-specific sec‐
form. This is explained below in the relevant platform-specific sec-
tion.
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 <B>/dev/sg0</B>, then the following two commands would
set the permission correctly:
@ -112,7 +112,7 @@
<H2>FREEBSD INFO</H2><PRE>
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 <I>/dev/scanner</I> to the appro‐
/dev/xpt0. Instead, you can also set a link <I>/dev/scanner</I> to the appro-
priate /dev/uk device.
Adaptec AHA1542CF
@ -143,7 +143,7 @@
</PRE>
<H2>LINUX INFO</H2><PRE>
First, make sure your kernel has SCSI generic support enabled. In
``make xconfig'', this shows up under ``SCSI support-&gt;SCSI generic sup‐
``make xconfig'', this shows up under ``SCSI support-&gt;SCSI generic sup-
port''.
To keep scanning times to a minimum, it is strongly recommended to use
@ -152,13 +152,13 @@
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
<B>SANE_SG_BUFFERSIZE</B> 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
request larger scsi buffers. If a backend does not automatically re-
quest a larger scsi buffer, set the environment variable
<B>SANE_SG_BUFFERSIZE</B> 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
@ -184,8 +184,8 @@
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.
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
@ -197,10 +197,10 @@
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.
@ -223,31 +223,31 @@
ISA SCSI card
This card is supplied by Mustek (and other vendors). It's
supported since Linux 2.2. The SCSI cards are supported
by the module g_NCR5380. It's necessary to tell the ker‐
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.
and therefore while a scan is in progress, the system be-
comes almost unusable. You may change the values of the
USLEEP macros in drivers/scsi/g_NCR5380.c. Some documen-
tation is in this file and NCR5380.c.
NCR/Symbios 810
For some scanners it may be necessary to disable discon‐
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‐
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
too low when scanning large area. If you get messages of
the form ``restart (ncr dead ?)'' in your /var/log/mes‐
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-&gt;latetime&gt;10)'' in file ncr53c8xx.c (nor‐
line ``if (np-&gt;latetime&gt;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
rebuild the kernel/module and try again.
@ -255,8 +255,8 @@
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
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
@ -281,12 +281,12 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SANEI_SCSI</B>
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.
<B>SANE_SCSICMD_TIMEOUT</B>
sets the timeout value for SCSI commands in seconds. Overriding

76
man/sane-sharp.5.html
Wyświetl plik

@ -49,7 +49,7 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that corâ€<EFBFBD>
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. The special device name must be a generic
SCSI device or a symlink to such a device. Under Linux, such a device
name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
@ -65,7 +65,7 @@
<B>Color</B> (8 bit RGB scans).
The default value is <B>Color.</B>
<B>Halftone</B> <B>Pattern</B> (parameter <B>--halftone-pattern</B> for scanimage). Availâ€<EFBFBD>
<B>Halftone</B> <B>Pattern</B> (parameter <B>--halftone-pattern</B> for scanimage). Avail-
able only for the JX-330 series scanners. Possible settings:
<B>none</B>
<B>Dither</B> <B>Bayer</B>
@ -80,11 +80,11 @@
<B>Flatbed</B>
<B>Automatic</B> <B>Document</B> <B>Feeder</B>
<B>Transparency</B> <B>Adapter</B>
If an ADF or a transparency adapter is installed, using it is the
default selection.
If an ADF or a transparency adapter is installed, using it is the de-
fault selection.
<B>Custom</B> <B>Gamma</B> (parameter <B>--custom-gamma</B> for scanimage). This option
determines whether a builtin or a custom gamma-table is used. Possible
<B>Custom</B> <B>Gamma</B> (parameter <B>--custom-gamma</B> for scanimage). This option de-
termines whether a builtin or a custom gamma-table is used. Possible
settings:
<B>yes</B> enables custom gamma tables
<B>no</B> enables a built gamma table
@ -94,7 +94,7 @@
<B>1.0</B>
<B>2.2</B>
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â€<EFBFBD>
correction; for these scanner, a gamma table is downloaded to the scan-
ner by the backend.)
<B>Gamma</B> <B>Table</B> (parameter <B>--gamma-table</B> for scanimage). Allowed values:
@ -106,9 +106,9 @@
values: 0..255; 256 numbers must be defined. The default values are 0,
1, 2, .. 255 (i.e., gamma == 1).
<B>Green</B> <B>Gamma</B> <B>Table</B> (parameter <B>--green-gamma-table</B> for scanimage).
Allowed values: 0..255; 256 numbers must be defined. The default valâ€<EFBFBD>
ues are 0, 1, 2, .. 255 (i.e., gamma == 1).
<B>Green</B> <B>Gamma</B> <B>Table</B> (parameter <B>--green-gamma-table</B> for scanimage). Al-
lowed values: 0..255; 256 numbers must be defined. The default values
are 0, 1, 2, .. 255 (i.e., gamma == 1).
<B>Blue</B> <B>Gamma</B> <B>Table</B> (parameter <B>--blue-gamma-table</B> for scanimage). Allowed
values: 0..255; 256 numbers must be defined. The default values are 0,
@ -124,7 +124,7 @@
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â€<EFBFBD>
xscanimage, or xsane. With scanimage, enter one of the following com-
mands:
<I>scanimage</I> <I>-d</I> <I>sharp</I> <I>--source</I> <I>"Automatic</I> <I>Document</I> <I>Feeder"</I> <I>--help</I>
@ -139,9 +139,9 @@
Top-left x position of scan area (parameter <B>-l</B> for scanimage);
Top-left y position of scan area (parameter <B>-t</B> for scanimage);
bottom right x position of scan area (parameter <B>-x</B> for scanimâ€<EFBFBD>
bottom right x position of scan area (parameter <B>-x</B> for scanim-
age);
bottom right y position of scan area (parameter <B>-y</B> for scanimâ€<EFBFBD>
bottom right y position of scan area (parameter <B>-y</B> for scanim-
age);
<B>Edge</B> <B>emphasis</B> (parameter <B>--Edge</B> <B>emphasis</B> for scanimage). This option is
@ -199,16 +199,16 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>sharp.conf</I> file is a list of options and device
names that correspond to Sharp scanners. Empty lines and lines beginâ€<EFBFBD>
names that correspond to Sharp scanners. Empty lines and lines begin-
ning with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details
about device names.
Lines setting an option start with the key word <B>option,</B> followed by the
option's name and the option's value. At present, three options are
defined: <B>buffers,</B> <B>buffersize,</B> and <B>readqueue.</B>
option's name and the option's value. At present, three options are de-
fined: <B>buffers,</B> <B>buffersize,</B> and <B>readqueue.</B>
Options defined at the start of <I>sharp.conf</I> apply to all devices;
options defined after a device name apply to this device.
Options defined at the start of <I>sharp.conf</I> apply to all devices; op-
tions defined after a device name apply to this device.
The options <B>buffers</B> and <B>readqueue</B> are only significant if the backend
has been compiled so that for each scan a second process is forked
@ -222,14 +222,14 @@
allowed is 2.
<B>option</B> <B>buffersize</B> defines the size of one buffer. Since each buffer is
filled with a single read command sent to the scanner, its size is limâ€<EFBFBD>
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
or 256 kB is recommended for scan resolutions of 300 dpi and above.
<B>option</B> <B>readqueue</B> defines how many read commands to be sent to the scanâ€<EFBFBD>
<B>option</B> <B>readqueue</B> 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, <B>option</B> <B>read</B>â€<B>â</B>€<EFBFBD>
commands only for for Linux. For other operating systems, <B>option</B> <B>read-</B>
<B>queue</B> should be set to 0. For Linux, <B>option</B> <B>readqueue</B> should be set to
2. Larger values than 2 for <B>option</B> <B>readqueue</B> are not reasonable in most
cases. <B>option</B> <B>buffers</B> should be greater than <B>option</B> <B>readqueue.</B>
@ -238,7 +238,7 @@
</PRE>
<H2>Performance Considerations</H2><PRE>
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â€<EFBFBD>
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.
That means that the backend must read the data as fast as possible from
the scanner in order to avoid carriage stops.
@ -274,9 +274,9 @@
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.
For Linux, the usage of the SG driver version 2.1.36 or above is recomâ€<EFBFBD>
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
@ -288,15 +288,15 @@
scanner. If you have enough memory available, you can increase <B>option</B>
<B>buffers,</B> 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â€<EFBFBD>
ing of the data is too slow, set the environment variable
<B>SANE_DEBUG_SHARP</B> to 1. When a scan is finished, the backend writes the
line "buffer full conditions: <I>nn"</I> to stderr. If <I>nn</I> is zero, carriage
stops are caused by too slow responses of the backend or too much
"traffic" on the SCSI bus. If <I>nn</I> is greater than zero, the backend had
to wait <I>nn</I> times until a buffer has been processed by the frontend.
(Please note that <B>option</B> <B>buffers</B> must be greater than <B>option</B> <B>readqueue</B>
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 <B>SANE_DE-</B>
<B>BUG_SHARP</B> to 1. When a scan is finished, the backend writes the line
"buffer full conditions: <I>nn"</I> to stderr. If <I>nn</I> is zero, carriage stops
are caused by too slow responses of the backend or too much "traffic"
on the SCSI bus. If <I>nn</I> is greater than zero, the backend had to wait <I>nn</I>
times until a buffer has been processed by the frontend. (Please note
that <B>option</B> <B>buffers</B> must be greater than <B>option</B> <B>readqueue</B> in order to
get useful output for "buffer full conditions".)
</PRE>
@ -315,8 +315,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SHARP</B>
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.
@ -360,10 +360,10 @@
</PRE>
<H2>CREDITS</H2><PRE>
The Sharp backend is based on the Canon backend written by Helmut Koeâ€<EFBFBD>
The Sharp backend is based on the Canon backend written by Helmut Koe-
berle
Parts of this man page are a plain copy of <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mosâ€<EFBFBD>
Parts of this man page are a plain copy of <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mos-
berger-Tang, Andreas Czechanowski and Andreas Bolsch
11 Jul 2008 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>

4
man/sane-sm3600.5.html
Wyświetl plik

@ -73,8 +73,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SM3600</B>
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.

8
man/sane-sm3840.5.html
Wyświetl plik

@ -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 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> and <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
There exist backends for Microtek scanners with SCSI command set. Re-
fer to <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> and <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
There also exists a Microtek 3600 series driver, see <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> for
details.
@ -82,8 +82,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SM3840</B>
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.

24
man/sane-snapscan.5.html
Wyświetl plik

@ -53,7 +53,7 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>snapscan.conf</I> file is a list of device names that
correspond to SnapScan scanners. Empty lines and lines starting with a
hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what consti‐
hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what consti-
tutes a valid device name.
@ -77,19 +77,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_SNAPSCAN</B>
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.
@ -109,7 +109,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Kevin Charter, Franck Schneider, Michel Roelofs, Emmanuel Blot, Mikko
Tyolajarvi, David Mosberger-Tang, Wolfgang Goeller, Petter Reinholdt‐
Tyolajarvi, David Mosberger-Tang, Wolfgang Goeller, Petter Reinholdt-
sen, Gary Plewa, Sebastien Sable, Oliver Schwartz and Mikael Magnusson.
Man page by Henning Meier-Geinitz (mostly based on the web pages and
source code).

38
man/sane-st400.5.html
Wyświetl plik

@ -18,7 +18,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-st400</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Siemens ST400 flatbed scanners and com‐
backend that provides access to Siemens ST400 flatbed scanners and com-
patibles. At present, the following scanners are supported by this
backend:
@ -30,7 +30,7 @@
The Siemens ST/Highscan series includes several more models, e.g. the
ST300 and ST600. If you own one of these scanners, or a scanner other
than the ones listed above that works with this backend, please let us
know by sending the scanner's model name, SCSI ID, and firmware revi‐
know by sending the scanner's model name, SCSI ID, and firmware revi-
sion to <I>sane-devel@alioth-lists.debian.net</I>. Have a look at
http://www.sane-project.org/mailing-lists.html concerning subscription
to sane-devel.
@ -42,7 +42,7 @@
<I>special</I>
Where <I>special</I> is either the path-name for the special device that cor‐
Where <I>special</I> is either the path-name for the special device that cor-
responds to a SCSI scanner. For SCSI scanners, the special device name
must be a generic SCSI device or a symlink to such a device. Under
Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
@ -51,7 +51,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>st400.conf</I> file is a list of device names that cor‐
The contents of the <I>st400.conf</I> file is a list of device names that cor-
respond to Siemens scanners. Empty lines and lines starting with a
hash mark (#) are ignored. A sample configuration file is shown below:
@ -66,7 +66,7 @@
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
driver with other scanner models, add an appropriate line to the con‐
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:
@ -93,19 +93,19 @@
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‐
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‐
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
<B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
"tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
"tmp/config", ".", and "/etc/sane.d" being searched (in this or-
der).
<B>SANE_DEBUG_ST400</B>
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,25 +118,25 @@
</PRE>
<H2>BUGS</H2><PRE>
Currently, the backend does not check if the attached device really is
a ST400. It will happily accept everything that matches the configura‐
tion entries. This makes it easy to test the backend with other scan‐
ners: Just add an appropriate line to the configuration file. The con‐
a ST400. It will happily accept everything that matches the configura-
tion entries. This makes it easy to test the backend with other scan-
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.
The ST400 answers on all eight SCSI LUNs. Normally this is not a prob‐
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
seeing multiple instances of the scanner in a device list, either dis‐
seeing multiple instances of the scanner in a device list, either dis-
able LUNs in your SCSI setup or change the entry in the configuration
file to match LUN 0 only.
</PRE>
<H2>DEBUG</H2><PRE>
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

10
man/sane-stv680.5.html
Wyświetl plik

@ -19,8 +19,8 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-stv680</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to some STV680 cameras. This backend
should be considered <B>beta-quality</B> software! STV680 cameras are sold
under various brands like Aiptek. This backend may or may not support
should be considered <B>beta-quality</B> 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:
@ -123,8 +123,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_STV680</B>
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.
@ -132,7 +132,7 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple‐
However they are only software adjustments. This backend only imple-
ments what the webcam can support.

30
man/sane-tamarack.5.html
Wyświetl plik

@ -18,7 +18,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-tamarack</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to the following Tamarack flatbed scan‐
backend that provides access to the following Tamarack flatbed scan-
ners:
Artiscan 6000C
@ -33,11 +33,11 @@
<I>special</I>
Where <I>special</I> 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 <I>sane-find-scanner</I>
to a SCSI scanner. The special device name must be a generic SCSI de-
vice or a symlink to such a device. The program <I>sane-find-scanner</I>
helps to find out the correct device. Under Linux, such a device name
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for
details.
could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for de-
tails.
</PRE>
@ -60,19 +60,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_TAMARACK</B>
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

14
man/sane-teco1.5.html
Wyświetl plik

@ -55,8 +55,8 @@
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 or through GUI elements in xs-
canimage or xsane.
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
@ -69,11 +69,11 @@
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev‐
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.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso‐
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 600, in increments of 1.
<B>Geometry</B> <B>options</B>
@ -132,8 +132,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO1</B>
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.
@ -141,7 +141,7 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple‐
However they are only software adjustments. This backend only imple-
ments what the scanner can support.

34
man/sane-teco2.5.html
Wyświetl plik

@ -52,8 +52,8 @@
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 or through GUI elements in xs-
canimage, xsane, quiteinsane or kooka.
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
@ -76,10 +76,10 @@
Color selects the resolution for a scan. The scanner can do only
the resolutions listed.
All values with ydpi &gt; 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‐
All values with ydpi &gt; 300 (300 x 600) or 600 (600 x 1200) re-
sult 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%
@ -110,26 +110,26 @@
table for the blue channel. The table must be 256 bytes long.
<B>--white-level-r</B>
(VM3564, VM356A, VM3575 and VM6575 only) Selects what red radi‐
(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‐
sheets by changing the calibration value loaded into the scan-
ner. Scale 0..64 in steps of 1.
<B>--white-level-g</B>
(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‐
(VM3564, VM356A, VM3575 and VM6575 only) Selects what green ra-
diance 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.
<B>--white-level-b</B>
(VM3564, VM356A, VM3575 and VM6575 only) Selects what blue radi‐
(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‐
sheets by changing the calibration value loaded into the scan-
ner. Scale 0..64 in steps of 1.
<B>--preview</B>
requests a preview scan. The resolution used for that scan is 50
dpi (for VM356A and VM6575 75 dpi) and the scan area is the max‐
dpi (for VM356A and VM6575 75 dpi) and the scan area is the max-
imum allowed. The scan mode is user selected. The default is
"no".
@ -153,8 +153,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO2</B>
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.
@ -168,7 +168,7 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple‐
However they are only software adjustments. This backend only imple-
ments what the scanner can support.

14
man/sane-teco3.5.html
Wyświetl plik

@ -38,8 +38,8 @@
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 or through GUI elements in xs-
canimage or xsane.
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
@ -52,11 +52,11 @@
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
are <I>Black</I> <I>&amp;</I> <I>White</I> , <I>Grayscale</I> and <I>Color</I> The Black &amp; White mode
is black and white only (1 bit). Grayscale will produce 256 lev‐
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.
<B>--resolution</B>
selects the resolution for a scan. The scanner can do all reso‐
selects the resolution for a scan. The scanner can do all reso-
lutions between 1 and 1200, in increments of 1.
<B>Geometry</B> <B>options</B>
@ -110,8 +110,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_TECO3</B>
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,7 +119,7 @@
</PRE>
<H2>LIMITATIONS</H2><PRE>
The windows TWAIN driver has many more options than this SANE backend.
However they are only software adjustments. This backend only imple‐
However they are only software adjustments. This backend only imple-
ments what the scanner can support.

105
man/sane-test.5.html
Wyświetl plik

@ -17,18 +17,18 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-test</B> library implements a SANE (Scanner Access Now Easy) backâ€<EFBFBD>
The <B>sane-test</B> library implements a SANE (Scanner Access Now Easy) back-
end that allows testing the SANE installation and SANE frontends. It
provides access to a (nearly) unlimited number of virtual devices.
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 <B>sane-test</B> 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 <B>sane-test</B> 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
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'.
@ -91,7 +91,7 @@
Option <B>read-delay</B> enables delaying data to the frontend.
Option <B>read-delay-duration</B> selects the number of microseconds the backâ€<EFBFBD>
Option <B>read-delay-duration</B> selects the number of microseconds the back-
ends waits after each transfer of a buffer. This option is useful to
find timing-related bugs, especially if used over the network.
@ -103,8 +103,8 @@
pixels that are "lost" at the end of each line. That means, lines are
padded with unused data.
Option <B>fuzzy-parameters</B> selects that fuzzy (inexact) parameters are
returned as long as the scan hasn't been started. This option can be
Option <B>fuzzy-parameters</B> 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).
@ -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 <B>bool-hard-select</B> (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 <B>bool-hard-select</B> (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 <B>bool-soft-detect</B> (4/6) is a bool test option that has soft
detect (and advanced) capabilities. That means the option is read-
only.
Option <B>bool-soft-detect</B> (4/6) is a bool test option that has soft de-
tect (and advanced) capabilities. That means the option is read-only.
Option <B>bool-soft-select-soft-detect-emulated</B> (5/6) is a Bool test
option that has soft select, soft detect, and emulated (and advanced)
capabilities.
Option <B>bool-soft-select-soft-detect-emulated</B> (5/6) is a Bool test op-
tion that has soft select, soft detect, and emulated (and advanced) ca-
pabilities.
Option <B>bool-soft-select-soft-detect-auto</B> (6/6) is a Bool test option
that has soft select, soft detect, and automatic (and advanced) capaâ€<C3A2>
Option <B>bool-soft-select-soft-detect-auto</B> (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 @@
<H2>INT TEST OPTIONS</H2><PRE>
There are 6 int test options in total.
Option <B>int</B> (1/6) is an int test option with no unit and no constraint
Option <B>int</B> (1/6) is an int test option with no unit and no constraint
set.
Option <B>int-constraint-range</B> (2/6) is an int test option with unit pixel
and constraint range set. Minimum is 4, maximum 192, and quant is 2.
Option <B>int-constraint-word-list</B> (3/6) is an int test option with unit
Option <B>int-constraint-word-list</B> (3/6) is an int test option with unit
bits and constraint word list set.
Option <B>int-constraint-array</B> (4/6) is an int test option with unit mm
Option <B>int-constraint-array</B> (4/6) is an int test option with unit mm
and using an array without constraints.
Option <B>int-constraint-array-constraint-range</B> (5/6) is an int test
option with unit mm and using an array with a range constraint. Miniâ€<C3A2>
mum is 4, maximum 192, and quant is 2.
Option <B>int-constraint-array-constraint-range</B> (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 <B>int-constraint-array-constraint-word-list</B> (6/6) is an int test
Option <B>int-constraint-array-constraint-word-list</B> (6/6) is an int test
option with unit percent and using an array a word list constraint.
@ -194,14 +193,14 @@
<H2>FIXED TEST OPTIONS</H2><PRE>
There are 3 fixed test options in total.
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no conâ€<C3A2>
Option <B>fixed</B> (1/3) is a fixed test option with no unit and no con-
straint set.
Option <B>fixed-constraint-range</B> (2/3) is a fixed test option with unit
microsecond and constraint range set. Minimum is -42.17, maximum
Option <B>fixed-constraint-range</B> (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 <B>fixed-constraint-word-list</B> (3/3) is a Fixed test option with no
Option <B>fixed-constraint-word-list</B> (3/3) is a Fixed test option with no
unit and constraint word list set.
@ -226,15 +225,15 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/test.conf</I>
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below). The initial values of most of the basic
SANE options can be configured in this file. A template containâ€<EFBFBD>
ing all the default values is provided together with this backâ€<EFBFBD>
end. One of the more interesting values may be <B>num</B>â€<B>â</B>€<EFBFBD>
<B>ber_of_devices</B>. 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.
The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> 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 <B>number_of_de-</B>
<B>vices</B>. 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.
<I>/usr/local/lib/sane/libsane-test.a</I>
The static library implementing this backend.
@ -249,20 +248,20 @@
<B>SANE_CONFIG_DIR</B>
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_TEST</B>
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

30
man/sane-u12.5.html
Wyświetl plik

@ -18,7 +18,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-u12</B> library implements a SANE (Scanner Access Now Easy) backâ€<EFBFBD>
The <B>sane-u12</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides access to USB flatbed scanners based on Plusteks'
ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
bridge chip.
@ -27,7 +27,7 @@
</PRE>
<H2>SUPPORTED DEVICES</H2><PRE>
The backend is able to support some early Plustek USB scanner based
their old parport design around the ASIC 98003 and other rebadged Plusâ€<EFBFBD>
their old parport design around the ASIC 98003 and other rebadged Plus-
tek devices. The following tables will give you a short overview.
If your Plustek scanner has another Product ID, then the device is <B>NOT</B>
@ -56,7 +56,7 @@
<I>[usb]</I> <I>vendor-id</I> <I>product-id</I>
<I>device</I> <I>/dev/usbscanner</I>
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usbâ</I>€<EFBFBD>
<I>[usb]</I> tells the backend, that the following devicename (here <I>/dev/usb-</I>
<I>scanner</I>) has to be interpreted as USB scanner device. If vendor- and
product-id has not been specified, the backend tries to detect this by
its own. If device is set to <I>auto</I> then the next matching device is
@ -106,19 +106,19 @@
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â€<EFBFBD>
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â€<EFBFBD>
ries. For example, setting <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_U12</B>
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
@ -128,7 +128,6 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
<I>/usr/local/share/doc/sane-backends/u12/U12.changes</I>
<I>http://www.gjaeger.de/scanner/u12/</I>
</PRE>
@ -140,9 +139,6 @@
Mailing-List archive at:
<B>http://www.sane-project.org/mailing-lists.html</B>
or directly from the projects' homepage at:
<B>http://www.gjaeger.de/scanner/u12/</B>
To obtain debug messages from the backend, please set the environment-
variable <I>SANE</I><B>_</B><I>DEBUG</I><B>_</B><I>U12</I> before calling your favorite scan-frontend
(i.e. xscanimage).

74
man/sane-umax.5.html
Wyświetl plik

@ -25,7 +25,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-umax</B> library implements a SANE backend that provides access to
several UMAX-SCSI-scanners and some Linotye Hell SCSI-scanners, paral‐
several UMAX-SCSI-scanners and some Linotye Hell SCSI-scanners, paral-
lel- and USB-scanners are not (and probably will never be) supported!
<B>I</B> <B>suggest</B> <B>you</B> <B>hold</B> <B>one</B> <B>hand</B> <B>on</B> <B>the</B> <B>power-button</B> <B>of</B> <B>the</B> <B>scanner</B> <B>while</B>
@ -34,8 +34,8 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The configuration file for this backend resides in
<I>/usr/local/etc/sane.d/umax.conf</I>.
The configuration file for this backend resides in <I>/usr/lo-</I>
<I>cal/etc/sane.d/umax.conf</I>.
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
@ -61,12 +61,10 @@
option lamp-control-available 0
option gamma-lsb-padded 0
/dev/sge
#scsi Vendor Model Type Bus Channel ID LUN
# The following scanner supports lamp control
option lamp-control-available 1
scsi UMAX * Scanner * * * * *
# scanner on /dev/scanner does not support lamp control
option lamp-control-available 0
/dev/scanner
@ -74,7 +72,7 @@
execute-request-sense:
values: 0 = disabled, 1 = enabled
default = 0
If set to 1 umax_do_request_sense is called in umax_do_calibra‐
If set to 1 umax_do_request_sense is called in umax_do_calibra-
tion. This can hang the system (but has been enabled until this
version)
@ -83,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:
@ -105,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:
@ -118,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
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.
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
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: <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
@ -200,13 +197,12 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_UMAX</B>
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_UMAX values
Number Remark
0 print important errors (printed each time)
1 print errors
2 print sense

17
man/sane-umax1220u.5.html
Wyświetl plik

@ -39,8 +39,8 @@
for this backend resides in <I>/usr/local/etc/sane.d/umax1220u.conf</I>.
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:
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,15 +68,14 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_UMAX1220U</B>
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
Number Remark
1 print failures
2 print information
3 print high-level function calls
@ -97,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‐
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.
</PRE>

50
man/sane-umax_pp.5.html
Wyświetl plik

@ -12,7 +12,7 @@
</PRE>
<H2>NAME</H2><PRE>
sane-umax_pp - SANE backend for Umax Astra parallel port flatbed scan‐
sane-umax_pp - SANE backend for Umax Astra parallel port flatbed scan-
ners
@ -36,7 +36,7 @@
300x600 for 610P. In color and gray levels, there is a software lineart
mode.
The new generation models share a newer version of the 610P ASIC embed‐
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,
@ -56,10 +56,10 @@
<I>with</I> <I>ppdev</I> <I>support.</I>
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‐
needs to run as root. To allow user access to the scanner run the back-
end through the network interface (See <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). A
more relaxed solution (security wise) is to add suid bit to the fron‐
tend (See <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drop root privileges as soon as it
more relaxed solution (security wise) is to add suid bit to the front-
end (See <B><A HREF="chmod.1.html">chmod(1)</A></B>). The backend drop root privileges as soon as it
can, right after gaining direct access to IO ports, which lessen risks
when being root.
@ -79,7 +79,7 @@
but does not try direct hardware access
/dev/ppi0
uses *BSD ppi device, depending on the number of avail‐
uses *BSD ppi device, depending on the number of avail-
able parallel port, you have to use /dev/ppi1, /dev/ppi2,
...
@ -95,7 +95,7 @@
<B>NOTE:</B> 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‐
devices may not be available for all users. You have to change permis-
sions on the dev/ppi* or /dev/parport* devices.
You can rename any device using the
@ -130,7 +130,7 @@
Option <B>astra</B> allows you to change the model of your scanner. Current
auto detection is based on side effects on scanning when using 1220P
command set on other models, so it may fail on unknown hardware combi‐
command set on other models, so it may fail on unknown hardware combi-
nation. Valid values are 610, 1220, 1600 and 2000. It is useful only
when autodetection fails to detect properly your scanner model. If your
scanner work properly but is reported wrongly, let it be that way. The
@ -139,9 +139,9 @@
aware that it will prevent scanner model autodetection.
Option <B>buffer</B> 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.
</PRE>
@ -164,19 +164,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_UMAX_PP</B>
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,18 +216,18 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Stéphane Voltz &lt;stef.dev@free.fr&gt;
St<B>e</B>phane Voltz &lt;stef.dev@free.fr&gt;
</PRE>
<H2>CREDITS</H2><PRE>
Support for the 610P has been made possible thank to an hardware dona‐
Support for the 610P has been made possible thank to an hardware dona-
tion by William Stuart.
</PRE>
<H2>BUG REPORTS</H2><PRE>
If something doesn't work, please contact me. But I need some informa‐
If something doesn't work, please contact me. But I need some informa-
tion about your scanner to be able to help you...
<I>SANE</I> <I>version</I>
@ -241,7 +241,7 @@
right port address, or the correct device in your umax_pp.conf.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso‐
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.

50
man/sane-usb.5.html
Wyświetl plik

@ -18,8 +18,8 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
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 focusses 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
@ -29,9 +29,9 @@
</PRE>
<H2>QUICK START</H2><PRE>
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 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
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 de-
tected by <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
Run sane-find-scanner. If it lists your scanner with the correct vendor
and product ids, you are done. See section <B>SANE</B> <B>ISSUES</B> for details on
@ -74,18 +74,18 @@
The permissions for the device files used by libusb must be adjusted
for user access. Otherwise only root can use SANE devices. For <I>Linux</I>,
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‐
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‐
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.
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.
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 <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
Use chmod to apply appropriate permissions.
@ -93,14 +93,14 @@
</PRE>
<H2>SANE ISSUES</H2><PRE>
This section assumes that your scanner is detected by sane-find-scan‐
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‐
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
(<I>http://www.sane-project.org/</I>), and the individual backend manpages.
Most backends can detect USB scanners automatically using "usb" config‐
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
this way is:
@ -110,9 +110,9 @@
where <I>VENDOR</I> is the USB vendor id, and <I>PRODUCT</I> is the USB product id of
the scanner. Both ids are non-negative integer numbers in decimal or
hexadecimal format. The correct values for these fields can be found by
running 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, looking into the syslog (e.g., /var/log/mes-
sages) or under Linux by issuing the command "cat /proc/bus/usb/de-
vices". This is an example of a config file line:
usb 0x055f 0x0006
@ -122,7 +122,7 @@
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‐
the first time. For a detailed description of each backend's configu-
ration file, please refer to the relevant backend manual page (e.g.
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for Mustek USB scanners).
@ -134,12 +134,18 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_SANEI_USB</B>
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.
<B>SANE_USB_WORKAROUND</B>
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.
</PRE>

33
man/sane-v4l.5.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-v4l</B> library implements a SANE (Scanner Access Now Easy) back‐
The <B>sane-v4l</B> library implements a SANE (Scanner Access Now Easy) back-
end that provides generic access to video cameras and similar equipment
using the V4L (Video for Linux) API.
@ -32,7 +32,7 @@
<I>special</I>
Where <I>special</I> is the UNIX path-name for the special device that corre‐
Where <I>special</I> is the UNIX path-name for the special device that corre-
sponds to the v4l device. The special device name must be a v4l device
or a symlink to such a device. For example, such a device name could
be <I>/dev/video0</I> or <I>/dev/bttv0</I>.
@ -40,7 +40,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>v4l.conf</I> file is a list of device names that corre‐
The contents of the <I>v4l.conf</I> file is a list of device names that corre-
spond to v4l devices. Empty lines and lines starting with a hash mark
(#) are ignored. A sample configuration file is shown below:
@ -69,19 +69,19 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
<B>SANE_DEBUG_V4L</B>
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,10 +95,9 @@
<H2>BUGS:</H2><PRE>
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.
</PRE>

10
man/sane-xerox_mfp.5.html
Wyświetl plik

@ -25,7 +25,7 @@
</PRE>
<H2>CONFIGURATION</H2><PRE>
<I>/usr/local/etc/sane.d/xerox</I><B>_</B><I>mfp.conf</I> USB scanners do not need any con‐
<I>/usr/local/etc/sane.d/xerox</I><B>_</B><I>mfp.conf</I> USB scanners do not need any con-
figuration.
For SCX-4500W in network mode you need to specify
@ -52,8 +52,8 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_XEROX_MFP</B> If the library was compiled with debug support
enabled, this environment variable controls the debug level for this
<B>SANE_DEBUG_XEROX_MFP</B> 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_XEROX_MFP=4
@ -68,7 +68,7 @@
</PRE>
<H2>BUGS AND SUPPORT</H2><PRE>
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‐
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
@ -78,7 +78,7 @@
Alex Belkin &lt;abc@telekom.ru&gt;
Samsung SCX-4500W scan over network support by Alexander Kuznetsov
&lt;acca(at)cpan.org&gt;
Color scanning on Samsung M2870 model and Xerox Cognac 3215 &amp; 3225 mod‐
Color scanning on Samsung M2870 model and Xerox Cognac 3215 &amp; 3225 mod-
els by Laxmeesh Onkar Markod &lt;m.laxmeesh@samsung.com&gt;

199
man/sane.7.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>SANE</B> is an application programming interface (API) that provides stanâ€<EFBFBD>
<B>SANE</B> is an application programming interface (API) that provides stan-
dardized access to any raster image scanner hardware. The standardized
interface makes it possible to write just one driver for each scanner
device instead of one driver for each scanner and application.
@ -37,7 +37,7 @@
<H2>TERMINOLOGY</H2><PRE>
An application that uses the <B>SANE</B> interface is called a <B>SANE</B> <B>frontend.</B>
A driver that implements the <B>SANE</B> interface is called a <B>SANE</B> <B>backend.</B>
A <B>meta</B> <B>backend</B> provides some means to manage one or more other backâ€<EFBFBD>
A <B>meta</B> <B>backend</B> provides some means to manage one or more other back-
ends.
@ -54,14 +54,14 @@
</PRE>
<H2>GENERAL INFORMATION</H2><PRE>
The following sections provide short descriptions and links to more
information about several aspects of <B>SANE.</B> A name with a number in
The following sections provide short descriptions and links to more in-
formation about several aspects of <B>SANE.</B> A name with a number in
parenthesis (e.g. `<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>') points to a manual page. In this case
`<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like
`<I>/usr/local/share/doc/sane-backends/sane.tex</I>' are references to text
files that were copied to the <B>SANE</B> documentation directory
(<I>/usr/local/share/doc/sane-backends/</I>) during installation. Everything
else is a URL to a resource on the web.
`<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like `<I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/sane.tex</I>' are references to text files that
were copied to the <B>SANE</B> documentation directory (<I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/</I>) during installation. Everything else is a
URL to a resource on the web.
<B>SANE</B> <B>homepage</B>
Information on all aspects of SANE including a tutorial and a link to
@ -75,28 +75,28 @@
CAN YOU HELP SANE for details. There are lists for specific releases
of SANE, for the current development version and a search engine:
<I>http://www.sane-project.org/sane-supported-devices.html</I>. The lists
are also installed on your system at /usr/local/share/doc/sane-backâ€<EFBFBD>
are also installed on your system at /usr/local/share/doc/sane-back-
ends/.
<B>SANE</B> <B>mailing</B> <B>list</B>
There is a mailing list for the purpose of discussing the SANE stanâ€<EFBFBD>
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:
<I>http://www.sane-project.org/mailing-lists.html</I>.
<B>SANE</B> <B>IRC</B> <B>channel</B>
The IRC (Internet Relay Chat) channel #sane can be found on the
Freenode network (irc.freenode.net). It's for discussing <B>SANE</B> probâ€<EFBFBD>
Freenode network (irc.freenode.net). It's for discussing <B>SANE</B> prob-
lems, talking about development and general <B>SANE</B> related chatting.
Before asking for help, please read the other documentation mentioned
in this manual page. The channel's topic is also used for announceâ€<EFBFBD>
in this manual page. The channel's topic is also used for announce-
ments of problems with SANE infrastructure (mailing lists, web
server, etc.).
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
Look at <I>/usr/local/share/doc/sane-backends/README</I> and the os-depenâ€<EFBFBD>
Look at <I>/usr/local/share/doc/sane-backends/README</I> and the os-depen-
dent README files for information about compiling and installing
<B>SANE.</B>
@ -114,7 +114,7 @@
Command-line frontend. See <B><A HREF="scanimage.1.html">scanimage(1)</A></B>.
<B>saned</B>
<B>SANE</B> network daemon that allows remote clients to access image acquiâ€<EFBFBD>
<B>SANE</B> network daemon that allows remote clients to access image acqui-
sition devices available on the local host. See <B><A HREF="saned.8.html">saned(8)</A></B>.
<B>sane-find-scanner</B>
@ -139,8 +139,8 @@
<B>apple</B>
The SANE backend for Apple flatbed scanners supports the following
scanners: AppleScanner, OneScanner and ColorOneScanner. See
<B><A HREF="sane-apple.5.html">sane-apple(5)</A></B> for details.
scanners: AppleScanner, OneScanner and ColorOneScanner. See <B>sane-ap-</B>
<B><A HREF="ple.5.html">ple(5)</A></B> for details.
<B>artec</B>
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
@ -153,17 +153,17 @@
and Trust Easy Webscan 19200. See <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> for details.
<B>as6e</B>
This is a SANE backend for using the Artec AS6E parallel port interâ€<EFBFBD>
This is a SANE backend for using the Artec AS6E parallel port inter-
face scanner. See <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B> for details.
<B>avision</B>
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â€<EFBFBD>
the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit-
subishi and Minolta film-scanners. See <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> for details.
<B>bh</B>
The bh backend provides access to Bell+Howell Copiscan II series docâ€<EFBFBD>
The bh backend provides access to Bell+Howell Copiscan II series doc-
ument scanners. See <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B> for details.
<B>canon</B>
@ -171,7 +171,7 @@
CanoScan 2700F SCSI flatbed scanners. See <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B> for details.
<B>canon630u</B>
The canon630u backend supports the CanoScan 630u and 636u USB scanâ€<EFBFBD>
The canon630u backend supports the CanoScan 630u and 636u USB scan-
ners. See <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B> for details.
<B>canon_dr</B>
@ -192,7 +192,7 @@
<B>coolscan2</B>
This is a SANE backend for Nikon Coolscan film-scanners. See
<B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
<B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B> for details.
<B>epjitsu</B>
The epjitsu backend provides support for Epson-based Fujitsu USB
@ -220,7 +220,7 @@
See <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> for details.
<B>hp</B>
The SANE hp backend provides access to Hewlett-Packard ScanJet scanâ€<EFBFBD>
The SANE hp backend provides access to Hewlett-Packard ScanJet scan-
ners which support SCL (Scanner Control Language by HP). See
<B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> for details.
@ -282,17 +282,17 @@
<B>magicolor</B>
The magicolor backend supports the KONICA MINOLTA magicolor 1690MF
multi-function printer/scanner/fax. See <B><A HREF="sane-magicolor.5.html">sane-magicolor(5)</A></B> for
details.
multi-function printer/scanner/fax. See <B><A HREF="sane-magicolor.5.html">sane-magicolor(5)</A></B> for de-
tails.
<B>matsushita</B>
This backend supports some Panasonic KVSS high speed scanners. See
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B> for details.
<B>microtek</B>
The microtek backend provides access to the "second generation"
Microtek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for
details.
The microtek backend provides access to the "second generation" Mi-
crotek scanners with SCSI-1 command set. See <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B> for de-
tails.
<B>microtek2</B>
The microtek2 backend provides access to some Microtek scanners with
@ -334,14 +334,14 @@
and Devcom SCSI flatbed scanners. See <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B> for details.
<B>pixma</B>
The pixma backend supports Canon PIXMA MP series (multi-function
devices). See <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B> or <I>http://home.arcor.de/wittawat/pixma/</I>
for details.
The pixma backend supports Canon PIXMA MP series (multi-function de-
vices), Canon imageCLASS series (laser devices), Canon MAXIFY series
and some Canon CanoScan series. See <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B> for details.
<B>plustek</B>
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,
National Semiconductor LM983[1/2/3] chipset aka Merlin. Scanners us-
ing this LM983x chips include some models from Plustek, KYE/Genius,
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
for details.
@ -355,6 +355,11 @@
The ricoh backend provides access to the following Ricoh flatbed
scanners: IS50 and IS60. See <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B> for details.
<B>ricoh2</B>
The ricoh2 backend provides access to the following Ricoh flatbed
scanners: SG-3100SNw, SP-100SU, and SP-111SU. See <B><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B> for
details.
<B>s9036</B>
The s9036 backend provides access to Siemens 9036 flatbed scanners.
See <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B> for details.
@ -380,7 +385,7 @@
<B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B> for details.
<B>sp15c</B>
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scanâ€<EFBFBD>
This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
ner. See <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B> for details.
<B>st400</B>
@ -388,7 +393,7 @@
See <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B> for details.
<B>tamarack</B>
The SANE tamarack backend supports Tamarack Artiscan flatbed scanâ€<EFBFBD>
The SANE tamarack backend supports Tamarack Artiscan flatbed scan-
ners. See <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B> for details.
<B>teco1</B> <B>teco2</B> <B>teco3</B>
@ -399,8 +404,8 @@
<B>u12</B>
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 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> for
details.
bridge chip like the Plustek OpticPro U(T)12. See <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B> for de-
tails.
<B>umax</B>
The sane-umax backend provides access to several UMAX-SCSI-scanners
@ -440,18 +445,18 @@
<B>gphoto2</B>
Backend for digital cameras supported by the gphoto2 library package.
(See <I>http://www.gphoto.org</I> for more information and a list of supâ€<EFBFBD>
(See <I>http://www.gphoto.org</I> 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 <B>SANE</B> backend. See
However, please note that more development and testing is needed be-
fore all of these cameras will be supported by <B>SANE</B> backend. See
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
<B>qcam</B>
Backend for Connectix QuickCam cameras. See <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>.
<B>stv680</B>
The sane-stv680 backend provides access to webcams with a stv680 chip.
See <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B> for details.
The sane-stv680 backend provides access to webcams with a stv680
chip. See <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B> for details.
Also, have a look at the backend information page at
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
@ -471,17 +476,17 @@
<B><A HREF="sane-net.5.html">sane-net(5)</A></B> and <B><A HREF="saned.8.html">saned(8)</A></B>.
<B>pnm</B>
PNM image reader pseudo-backend. The purpose of this backend is priâ€<EFBFBD>
PNM image reader pseudo-backend. The purpose of this backend is pri-
marily to aid in debugging of <B>SANE</B> frontends. See <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>.
<B>pint</B>
Backend for scanners that use the <B>PINT</B> (Pint Is Not Twain) device
driver. The <B>PINT</B> driver is being actively developed on the OpenBSD
platform, and has been ported to a few other *nix-like operating sysâ€<EFBFBD>
platform, and has been ported to a few other *nix-like operating sys-
tems. See <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>.
<B>test</B>
The <B>SANE</B> test backend is for testing frontends and the <B>SANE</B> installaâ€<EFBFBD>
The <B>SANE</B> test backend is for testing frontends and the <B>SANE</B> installa-
tion. It provides test pictures and various test options. See
<B><A HREF="sane-test.5.html">sane-test(5)</A></B>.
@ -513,21 +518,21 @@
The <B>SANE</B> standard defines the application programming interface (API)
that is used to communicate between frontends and backends. It can be
found at <I>/usr/local/share/doc/sane-backends/sane.ps</I> (if latex is
installed on your system) and on the <B>SANE</B> website:
found at <I>/usr/local/share/doc/sane-backends/sane.ps</I> (if latex is in-
stalled on your system) and on the <B>SANE</B> website:
<I>http://www.sane-project.org/html/</I> (HTML), or
<I>http://www.sane-project.org/sane.ps</I> (Postscript).
There is some more information for programmers in
<I>/usr/local/share/doc/sane-backends/backend-writing.txt</I>. Most of the
internal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
There is some more information for programmers in <I>/usr/lo-</I>
<I>cal/share/doc/sane-backends/backend-writing.txt</I>. Most of the internal
<B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
project is started, have a look at <I>/usr/local/share/doc/sane-backâ</I>€<EFBFBD>
project is started, have a look at <I>/usr/local/share/doc/sane-back-</I>
<I>ends/PROJECTS</I> for projects that are planned or not yet included into
the <B>SANE</B> distribution and at our bug-tracking system:
<I>http://www.http://www.sane-project.org/bugs.html</I>.
There are some links on how to find out about the protocol of a scanâ€<EFBFBD>
There are some links on how to find out about the protocol of a scan-
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
If you start writing a backend or frontend or any other part of <B>SANE,</B>
@ -544,31 +549,31 @@
The static libraries implementing the backends.
<I>/usr/local/lib/sane/libsane-*.so</I>
The shared libraries implementing the backends (present on sysâ€<EFBFBD>
The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
<I>/usr/local/share/doc/sane-backends/*</I>
<B>SANE</B> documentation: The standard, READMEs, text files for backâ€<EFBFBD>
<B>SANE</B> documentation: The standard, READMEs, text files for back-
ends etc.
</PRE>
<H2>PROBLEMS</H2><PRE>
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â€<EFBFBD>
ners, use the <B>sane-find-scanner</B> tool (see <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> for
details). It prints one line for each scanner it has detected and some
that it is detected by your operating system. For SCSI and USB scan-
ners, use the <B>sane-find-scanner</B> tool (see <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B> for de-
tails). It prints one line for each scanner it has detected and some
comments (#). If <B>sane-find-scanner</B> 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 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> or <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>. If your scanner (or
other device) is not connected over the SCSI bus or USB, read the backâ€<EFBFBD>
not as normal user, the permissions for the device files are not ad-
justed correctly. If the scanner isn't found at all, the operating sys-
tem hasn't detected it and may need some help. Depending on the type of
your scanner, read <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> or <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>. 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.
Now your scanner is detected by the operating system but not by <B>SANE</B>?
Try <B>scanimage</B> <B>-L</B>. If the scanner is not found, check that the backâ€<EFBFBD>
end's name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. Some backâ€<EFBFBD>
Try <B>scanimage</B> <B>-L</B>. If the scanner is not found, check that the back-
end's name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. 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,
@ -579,10 +584,10 @@
Another reason for not being detected by <B>scanimage</B> <B>-L</B> may be a missing
or wrong configuration in the backend's configuration file. While <B>SANE</B>
tries to automatically find most scanners, some can't be setup corâ€<EFBFBD>
rectly without the intervention of the administrator. Also on some
operating systems auto-detection may not work. Check the backend's manâ€<EFBFBD>
ual page for details.
tries to automatically find most scanners, some can't be setup cor-
rectly without the intervention of the administrator. Also on some op-
erating systems auto-detection may not work. Check the backend's manual
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
@ -593,10 +598,10 @@
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
can't find out what's going on by checking the messages carefully, conâ€<EFBFBD>
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 <B>scanimage</B> <B>-L</B>, try to do a scan: <B>scan</B>â€<B>â</B>€<EFBFBD>
Now that your scanner is found by <B>scanimage</B> <B>-L</B>, try to do a scan: <B>scan-</B>
<B>image</B> <B>&gt;image.pnm</B>. This command starts a scan for the default scanner
with default settings. All the available options are listed by running
<B>scanimage</B> <B>--help</B>. If scanning aborts with an error message, turn on
@ -606,8 +611,8 @@
out what's wrong, contact sane-devel.
To check that the <B>SANE</B> libraries are installed correctly you can use
the test backend, even if you don't have a scanner or other <B>SANE</B>
device:
the test backend, even if you don't have a scanner or other <B>SANE</B> de-
vice:
<B>scanimage</B> <B>-d</B> <I>test</I> <B>-T</B>
@ -616,14 +621,14 @@
So now scanning with <B>scanimage</B> works and you want to use one of the
graphical frontends like <B>xsane</B>, <B>xscanimage</B>, or <B>quiteinsane</B> but those
frontends don't detect your scanner? One reason may be that you
installed two versions of <B>SANE</B>. E.g. the version that was installed by
your distribution in <I>/usr</I> and one you installed from source in
<I>/usr/local/</I>. Make sure that only one version is installed. Another
possible reason is, that your system's dynamic loader can't find the
<B>SANE</B> libraries. For Linux, make sure that <I>/etc/ld.so.conf</I> contains
<I>/usr/local/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See also the
documentation of the frontends.
frontends don't detect your scanner? One reason may be that you in-
stalled two versions of <B>SANE</B>. E.g. the version that was installed by
your distribution in <I>/usr</I> and one you installed from source in <I>/usr/lo-</I>
<I>cal/</I>. Make sure that only one version is installed. Another possible
reason is, that your system's dynamic loader can't find the <B>SANE</B> li-
braries. For Linux, make sure that <I>/etc/ld.so.conf</I> contains <I>/usr/lo-</I>
<I>cal/lib</I> and does <B>not</B> contain <I>/usr/local/lib/sane</I>. See also the docu-
mentation of the frontends.
</PRE>
@ -639,32 +644,32 @@
contact the author of your backend directly. Usually the email address
can be found in the <I>/usr/local/share/doc/sane-backends/AUTHORS</I> file or
the backend's manpage. For general discussion about SANE, please use
the <B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mailâ</I>€<EFBFBD>
the <B>SANE</B> mailing list sane-devel (see <I>http://www.sane-project.org/mail-</I>
<I>ing-lists.html</I> for details).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>,
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>,
<B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>, <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>,
<B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>, <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>,
<B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>,
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>, <B>sane-ag-</B>
<B><A HREF="fafocus.5.html">fafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>,
<B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>, <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>,
<B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>, <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B>sane-card-</B>
<B><A HREF="scan.5.html">scan(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>,
<B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>, <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>,
<B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>, <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>,
<B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B>,
<B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>, <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>, <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>,
<B><A HREF="sane-kodak.5.html">sane-kodak(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
<B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>,
<B><A HREF="sane-kodak.5.html">sane-kodak(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-mat-</B>
<B><A HREF="sushita.5.html">sushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>,
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>,
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>, <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>,
<B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>,
<B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>,
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>,
<B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>,
<B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>,
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>,
<B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>, <B><A HREF="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B>
<B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-ricoh2.5.html">sane-ricoh2(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>, <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>,
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B>sane-snap-</B>
<B><A HREF="scan.5.html">scan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>, <B>sane-tama-</B>
<B><A HREF="rack.5.html">rack(5)</A></B>, <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>,
<B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>,
<B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>, <B><A HREF="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B>
</PRE>
@ -674,7 +679,7 @@
Meier-Geinitz. Quite a lot of text was taken from the <B>SANE</B> standard,
several man pages, and README files.
14 Jul 2008 <B><A HREF="sane.7.html">sane(7)</A></B>
03 Jan 2020 <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<HR>
<ADDRESS>

157
man/saned.8.html
Wyświetl plik

@ -17,45 +17,53 @@
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>saned</B> <B>[</B> <B>-a</B> <I>[</I> <I>username</I> <I>]</I> <B>|</B> <B>-d</B> <I>[</I> <I>n</I> <I>]</I> <B>|</B> <B>-s</B> <I>[</I> <I>n</I> <I>]</I> <B>|</B> <B>-h</B> <B>]</B>
<B>saned</B> <B>[</B> <B>-a</B> <I>[</I> <I>username</I> <I>]</I> <B>]</B> <B>[</B> <B>-u</B> <I>username</I> <B>]</B> <B>[</B> <B>-b</B> <I>address</I> <B>]</B> <B>[</B> <B>-l</B> <B>]</B> <B>[</B> <B>-D</B> <B>]</B>
<B>[</B> <B>-o</B> <B>]</B> <B>[</B> <B>-d</B> <I>n</I> <B>]</B> <B>[</B> <B>-e</B> <B>]</B> <B>[</B> <B>-h</B> <B>]</B>
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>saned</B> is the SANE (Scanner Access Now Easy) daemon that allows remote
clients to access image acquisition devices available on the local
<B>saned</B> is the SANE (Scanner Access Now Easy) daemon that allows remote
clients to access image acquisition devices available on the local
host.
</PRE>
<H2>OPTIONS</H2><PRE>
The <B>-a</B> flag requests that <B>saned</B> run in standalone daemon mode. In this
mode, <B>saned</B> will detach from the console and run in the background,
listening for incoming client connections; <B>inetd</B> is not required for
<B>saned</B> operations in this mode. If the optional <B>username</B> is given after
<B>-a</B> , <B>saned</B> will drop root privileges and run as this user (and group).
The <B>-l</B> flag requests that <B>saned</B> run in standalone daemon mode. In this
mode, <B>saned</B> will listen for incoming client connections; <B>inetd</B> is not
required for <B>saned</B> operations in this mode. The <B>-b</B> flag tells <B>saned</B> to
bind to the <I>address</I> given. The <B>-u</B> flag requests that <B>saned</B> drop root
privileges and run as the user (and group) associated with <I>username</I> af-
ter binding. The <B>-D</B> flag will request <B>saned</B> to detach from the console
and run in the background. The flag <B>-a</B> is equivalent to the combina-
tion of <B>-l</B> <B>-B</B> <B>-u</B> <I>username</I> options.
The <B>-d</B> and <B>-s</B> flags request that <B>saned</B> run in debug mode (as opposed to
<B><A HREF="inetd.8.html">inetd(8)</A></B> daemon mode). In this mode, <B>saned</B> explicitly waits for a con‐
nection request. When compiled with debugging enabled, these flags may
be followed by a number to request debug info. The larger the number,
the more verbose the debug output. E.g., <B>-d128</B> will request printing
of all debug info. Debug level 0 means no debug output at all. The
default value is 2. If flag <B>-d</B> is used, the debug messages will be
printed to stderr while <B>-s</B> requests using syslog.
The <B>-d</B> flag sets the level of <B>saned</B> debug output. When compiled with
debugging enabled, this flag may be followed by a number to request
more or less debug info. The larger the number, the more verbose the
debug output. E.g., <B>-d128</B> will request output of all debug info. A
level of 0 produces no output at all. The default value is 2.
If <B>saned</B> is run from inetd, xinetd or systemd, no option can be given.
The <B>-e</B> flag will divert <B>saned</B> debug output to stderr instead of the
syslog default.
The <B>-o</B> flag requests that <B>saned</B> exits after the first client discon-
nects. This is useful for debugging.
The <B>-h</B> flag displays a short help message.
If <B>saned</B> is run from other programs such as inetd, xinetd and systemd,
check that program's documentation on how to pass command-line options.
</PRE>
<H2>CONFIGURATION</H2><PRE>
First and foremost: <B>saned</B> 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 <B>saned</B>'s own
authentication. Don't run <B>saned</B> as root if it's not necessary. And do
<B>not</B> install <B>saned</B> as setuid root.
or other non-trusted networks. Make sure that access is limited by tcp-
wrappers and/or a firewall setup. Don't depend only on <B>saned</B>'s own au-
thentication. Don't run <B>saned</B> as root if it's not necessary. And do <B>not</B>
install <B>saned</B> as setuid root.
The <I>saned.conf</I> configuration file contains both options for the daemon
and the access list.
@ -68,13 +76,21 @@
is a Linux machine, we strongly recommend using the Netfilter
<I>nf</I><B>_</B><I>conntrack</I><B>_</B><I>sane</I> module instead.
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
<B>data_connect_timeout</B> = <I>timeout</I>
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 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.
@ -90,7 +106,7 @@
[::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.
@ -98,50 +114,50 @@
<H2>SERVER DAEMON CONFIGURATION</H2><PRE>
For <B>saned</B> to work properly in its default mode of operation, it is also
necessary to add the appropriate configuration for <I>(x)inetd</I> <I>or</I> <I>systemd.</I>
(see below). Note that your inetd must support IPv6 if you want to
connect to saned over IPv6 ; xinetd, openbsd-inetd and systemd are
(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.
In the sections below the configuration for <I>inetd,</I> <I>xinetd</I> and <I>systemd</I>
In the sections below the configuration for <I>inetd,</I> <I>xinetd</I> and <I>systemd</I>
are described in more detail.
For the configurations below it is necessary to add a line of the fol‐
For the configurations below it is necessary to add a line of the fol-
lowing form to <I>/etc/services</I>:
sane-port 6566/tcp # SANE network scanner daemon
The official IANA short name for port 6566 is "sane-port". The older
The official IANA short name for port 6566 is "sane-port". The older
name "sane" is now deprecated.
</PRE>
<H2>INETD CONFIGURATION</H2><PRE>
It is required to add a single line to the inetd configuration file
It is required to add a single line to the inetd configuration file
<I>(/etc/inetd.conf)</I>
The configuration line normally looks like this:
sane-port stream tcp nowait saned.saned /usr/local/sbin/saned
sane-port stream tcp nowait saned.saned /usr/local/sbin/saned
saned
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security screening,
you may want to disable saned access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
instead:
you may want to disable saned access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I> 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 <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
the scanner (the program generally needs read and write access to scan‐
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
the scanner (the program generally needs read and write access to scan-
ner devices).
</PRE>
<H2>XINETD CONFIGURATION</H2><PRE>
If xinetd is installed on your system instead of inetd the following
If xinetd is installed on your system instead of inetd the following
example for <I>/etc/xinetd.conf</I> may be helpful:
# default: off
@ -161,24 +177,24 @@
</PRE>
<H2>SYSTEMD CONFIGURATION</H2><PRE>
Saned can be compiled with explicit systemd support. This will allow
logging debugging information to be forwarded to the systemd journal.
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 used wih systemd without the systemd integration compiled
Saned can be used wih systemd without the systemd integration compiled
in, but then logging of debug information is not supported.
The systemd configuration is different for the 2 options, so both are
The systemd configuration is different for the 2 options, so both are
described below.
</PRE>
<H2>Systemd configuration for saned with systemd support compiled in</H2><PRE>
for the systemd configuration we need to add 2 configuration files in
for the systemd configuration we need to add 2 configuration files in
<I>/etc/systemd/system.</I>
The first file we need to add here is called <I>saned.socket.</I> It shall
The first file we need to add here is called <I>saned.socket.</I> It shall
have the following contents:
[Unit]
@ -192,7 +208,7 @@
[Install]
WantedBy=sockets.target
The second file to be added is <I>saned@.service</I> with the following con‐
The second file to be added is <I>saned@.service</I> with the following con-
tents:
[Unit]
@ -215,15 +231,14 @@
Also=saned.socket
You need to set an environment variable for <B>SANE_CONFIG_DIR</B> 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 <I>(x)inetd</I> , systemd allows debugging output from backends set
using <B>SANE_DEBUG_XXX</B> to be captured. See the man-page for your backend
to see what options are supported. With the service unit as described
Unlike <I>(x)inetd</I> , systemd allows debugging output from backends set us-
ing <B>SANE_DEBUG_XXX</B> 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.
@ -236,7 +251,7 @@
for systemd configuration for saned, we need to add 2 configuration
files in <I>/etc/systemd/system.</I>
The first file we need to add here is called <I>saned.socket.</I> It is iden‐
The first file we need to add here is called <I>saned.socket.</I> It is iden-
tical to the version for systemd with the support compiled in. It
shall have the following contents:
@ -297,15 +312,15 @@
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‐
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 <B>SANE_CONFIG_DIR</B> 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 <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would re-
sult in directories "tmp/config", ".", and "/usr/lo-
cal/etc/sane.d" being searched (in this order).
</PRE>
@ -319,7 +334,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
20 Apr 2009 <B><A HREF="saned.8.html">saned(8)</A></B>
29 Sep 2017 <B><A HREF="saned.8.html">saned(8)</A></B>
</PRE>
<HR>
<ADDRESS>

193
man/scanimage.1.html
Wyświetl plik

@ -21,23 +21,24 @@
<I>profile</I>] [<B>-L</B>|<B>--list-devices</B>] [<B>-f</B>|<B>--formatted-device-list</B> <I>format</I>]
[<B>-b</B>|<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</I>]
[<B>--batch-increment</B> <I>increment</I>] [<B>--batch-double</B>] [<B>--accept-md5-only</B>]
[<B>-p</B>|<B>--progress</B>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>] [<B>-A</B>|<B>--all-options</B>]
[<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>] [<B>-B</B>|<B>--buffer-size</B> [=<I>size</I>]] [<B>-V</B>|<B>--version</B>]
[<I>device-specific-options</I>]
[<B>-p</B>|<B>--progress</B>] [<B>-o</B>|<B>--output-file</B>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>]
[<B>-A</B>|<B>--all-options</B>] [<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>] [<B>-B</B>|<B>--buffer-size</B>
[=<I>size</I>]] [<B>-V</B>|<B>--version</B>] [<I>device-specific-options</I>]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>scanimage</B> is a command-line interface to control image acquisition
devices such as flatbed scanners or cameras. The device is controlled
<B>scanimage</B> 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, <B>scanimage</B>
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) or in TIFF (black-and-white, grayscale or color). <B>scanimage</B>
accesses image acquisition devices through the <B>SANE</B> (Scanner Access Now
Easy) interface and can thus support any device for which there exists
a <B>SANE</B> backend (try <B>apropos</B> <I>sane-</I> to get a list of available backends).
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. <B>scanimage</B> accesses image acquisition devices through
the <B>SANE</B> (Scanner Access Now Easy) interface and can thus support any
device for which there exists a <B>SANE</B> backend (try <B>apropos</B> <I>sane-</I> to get
a list of available backends).
</PRE>
@ -50,7 +51,7 @@
scanimage &gt;image.pnm
To scan 100x100 mm to the file image.tiff (-x and -y may not be availâ€<C3A2>
To scan 100x100 mm to the file image.tiff (-x and -y may not be avail-
able with all devices):
scanimage -x 100 -y 100 --format=tiff &gt;image.tiff
@ -63,20 +64,21 @@
</PRE>
<H2>OPTIONS</H2><PRE>
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 <B>-d</B> or <B>--device-name</B> options must be followed by a <B>SANE</B> device-name
like `<I>epson:/dev/sg0</I>' or `<I>hp:/dev/usbscanner0</I>'. A (partial) list of
available devices can be obtained with the <B>--list-devices</B> option (see
below). If no device-name is specified explicitly, <B>scanimage</B> reads a
The <B>-d</B> or <B>--device-name</B> options must be followed by a <B>SANE</B> device-name
like `<I>epson:/dev/sg0</I>' or `<I>hp:/dev/usbscanner0</I>'. A (partial) list of
available devices can be obtained with the <B>--list-devices</B> option (see
below). If no device-name is specified explicitly, <B>scanimage</B> reads a
device-name from the environment variable <B>SANE_DEFAULT_DEVICE</B>. If this
variable is not set, <B>scanimage</B> will attempt to open the first available
device.
The <B>--format</B> <I>format</I> option selects how image data is written to stanâ€<C3A2>
dard output. <I>format</I> can be <B>pnm</B> or <B>tiff.</B> If <B>--format</B> is not used, PNM
is written.
The <B>--format</B> <I>format</I> option selects how image data is written to stan-
dard output or the file specified by the --output-file option. <I>format</I>
can be <B>pnm</B>, <B>tiff</B>, <B>png</B>, or <B>jpeg</B>. If <B>--format</B> is not specified, PNM is
written by default.
The <B>-i</B> or <B>--icc-profile</B> option is used to include an ICC profile into a
TIFF file.
@ -84,77 +86,85 @@
The <B>-L</B> or <B>--list-devices</B> option requests a (partial) list of devices
that are available. The list is not complete since some devices may be
available, but are not listed in any of the configuration files (which
are typically stored in directory <I>/etc/sane.d</I>). This is particularly
the case when accessing scanners through the network. If a device is
not listed in a configuration file, the only way to access it is by its
full device name. You may need to consult your system administrator to
find out the names of such devices.
are typically stored in directory <I>/usr/local/etc/sane.d</I>). This is par-
ticularly the case when accessing scanners through the network. If a
device is not listed in a configuration file, the only way to access it
is by its full device name. You may need to consult your system admin-
istrator to find out the names of such devices.
The <B>-f</B> or <B>--formatted-device-list</B> option works similar to
<B>--list-devices</B>, but requires a format string. <B>scanimage</B> replaces the
placeholders <B>%d</B> <B>%v</B> <B>%m</B> <B>%t</B> <B>%i</B> <B>%n</B> with the device name, vendor name, model
name, scanner type, an index number and newline respectively. The comâ€<C3A2>
mand
The <B>-f</B> or <B>--formatted-device-list</B> option works similar to <B>--list-de-</B>
<B>vices</B>, but requires a format string. <B>scanimage</B> replaces the placehold-
ers <B>%d</B> <B>%v</B> <B>%m</B> <B>%t</B> <B>%i</B> <B>%n</B> with the device name, vendor name, model name,
scanner type, an index number and newline respectively. The command
<B>scanimage</B> <B>-f</B> <I>â</I>€œ <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
<I>produced</I> <I>by</I> <I>%v</I> <I>â</I>€<EFBFBD>
<B>scanimage</B> <B>-f</B> <I>"</I> <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
<I>produced</I> <I>by</I> <I>%v</I> <I>"</I>
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 <B>--batch*</B> options provide the features for scanning documents using
document feeders. <B>--batch</B> [<I>format</I>] is used to specify the format of
the filename that each page will be written to. Each page is written
out to a single file. If <I>format</I> is not specified, the default of
out%d.pnm (or out%d.tif for --format tiff) will be used. <I>format</I> is
given as a printf style string with one integer parameter.
<B>--batch-start</B> <I>start</I> selects the page number to start naming files with.
If this option is not given, the counter will start at 1.
<B>--batch-count</B> <I>count</I> 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 <B>--batch-increment</B> <I>increment</I> 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: <B>--batch-double</B>
will automatically set the increment to 2. <B>--batch-prompt</B> will ask for
pressing RETURN before scanning a page. This can be used for scanning
multiple pages without an automatic document feeder.
The <B>--batch*</B> options provide the features for scanning documents using
document feeders. <B>--batch</B> [<I>format</I>] is used to specify the format of
the filename that each page will be written to. Each page is written
out to a single file. If <I>format</I> 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. <I>format</I> is given as a printf
style string with one integer parameter. <B>--batch-start</B> <I>start</I> selects
the page number to start naming files with. If this option is not
given, the counter will start at 1. <B>--batch-count</B> <I>count</I> 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 <B>--batch-increment</B> <I>increment</I> 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: <B>--batch-double</B> will automatically set the increment
to 2. <B>--batch-prompt</B> will ask for pressing RETURN before scanning a
page. This can be used for scanning multiple pages without an automatic
document feeder.
The <B>--accept-md5-only</B> option only accepts user authorization requests
that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
The <B>--accept-md5-only</B> option only accepts user authorization requests
that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
of doing such requests. See <B><A HREF="saned.8.html">saned(8)</A></B>.
The <B>-p</B> or <B>--progress</B> option requests that <B>scanimage</B> prints a progress
counter. It shows how much image data of the current image has already
The <B>-p</B> or <B>--progress</B> option requests that <B>scanimage</B> prints a progress
counter. It shows how much image data of the current image has already
been received by <B>scanimage</B> (in percent).
The <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> only sets the
options provided by the user but doesn't actually perform a scan. This
The <B>-o</B> or <B>--output-file</B> option requests that <B>scanimage</B> 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 <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> 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 <B>-T</B> or <B>--test</B> option requests that <B>scanimage</B> performs a few simple
sanity tests to make sure the backend works as defined by the <B>SANE</B> API
The <B>-T</B> or <B>--test</B> option requests that <B>scanimage</B> performs a few simple
sanity tests to make sure the backend works as defined by the <B>SANE</B> API
(in particular the <B>sane_read</B> function is exercised by this test).
The <B>-A</B> or <B>--all-options</B> option requests that <B>scanimage</B> lists all availâ€<EFBFBD>
able options exposed the backend, including button options. The inforâ€<EFBFBD>
The <B>-A</B> or <B>--all-options</B> option requests that <B>scanimage</B> lists all avail-
able options exposed the backend, including button options. The infor-
mation is printed on standard output and no scan will be done.
The <B>-h</B> or <B>--help</B> options request help information. The information is
The <B>-h</B> or <B>--help</B> options request help information. The information is
printed on standard output and in this case, no attempt will be made to
acquire an image.
The <B>-v</B> or <B>--verbose</B> options increase the verbosity of the operation of
<B>scanimage.</B> The option may be specified repeatedly, each time increasâ€<EFBFBD>
The <B>-v</B> or <B>--verbose</B> options increase the verbosity of the operation of
<B>scanimage.</B> The option may be specified repeatedly, each time increas-
ing the verbosity level.
The <B>-B</B> or <B>--buffer-size</B> changes the input buffer size from 32KB to the
number kB specified or 1M.
The <B>-B</B> option without argument changes the input buffer size from the
default 32KB to 1MB. For finer grained control, use <B>--buffer-size=</B>
followed by the number of KB.
The <B>-V</B> or <B>--version</B> option requests that <B>scanimage</B> prints the program
and package name, the version number of the <B>SANE</B> distribution that it
@ -164,9 +174,9 @@
used. Example: SANE_DEBUG_DLL=3 scanimage -L.
As you might imagine, much of the power of <B>scanimage</B> comes from the
fact that it can control any <B>SANE</B> backend. Thus, the exact set of comâ€<EFBFBD>
fact that it can control any <B>SANE</B> backend. Thus, the exact set of com-
mand-line options depends on the capabilities of the selected device.
To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a comâ€<EFBFBD>
To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a com-
mand-line of the form:
<B>scanimage</B> <B>--help</B> <B>--device-name</B> <I>dev</I>
@ -178,8 +188,8 @@
Top-left x position of scan area.
The description above shows that option <B>-l</B> expects an option
value in the range from 0 to 218 mm. The value in square brackâ€<EFBFBD>
ets indicates that the current option value is 0 mm. Most backâ€<EFBFBD>
value in the range from 0 to 218 mm. The value in square brack-
ets indicates that the current option value is 0 mm. Most back-
ends provide similar geometry options for top-left y position
(-t), width (-x) and height of scan-area (-y).
@ -195,21 +205,21 @@
Set default values for enhancement controls.
The description above shows that option <B>--default-enhancements</B>
has no option value. It should be thought of as having an immeâ€<EFBFBD>
diate effect at the point of the command-line at which it
appears. For example, since this option resets the <B>--brightness</B>
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 ap-
pears. For example, since this option resets the <B>--brightness</B>
option, the option-pair <B>--brightness</B> <B>50</B> <B>--default-enhancements</B>
would effectively be a no-op.
--mode Lineart|Gray|Color [Gray]
Selects the scan mode (e.g., lineart or color).
The description above shows that option <B>--mode</B> accepts an arguâ€<EFBFBD>
The description above shows that option <B>--mode</B> accepts an argu-
ment that must be one of the strings <B>Lineart</B>, <B>Gray</B>, or <B>Color</B>.
The value in the square bracket indicates that the option is
currently set to <B>Gray</B>. For convenience, it is legal to abbreviâ€<EFBFBD>
currently set to <B>Gray</B>. For convenience, it is legal to abbrevi-
ate the string values as long as they remain unique. Also, the
case of the spelling doesn't matter. For example, option setâ€<EFBFBD>
case of the spelling doesn't matter. For example, option set-
ting <B>--mode</B> <B>col</B> is identical to <B>--mode</B> <B>Color</B>.
--custom-gamma[=(yes|no)] [inactive]
@ -217,18 +227,18 @@
should be used.
The description above shows that option <B>--custom-gamma</B> expects
either no option value, a "yes" string, or a "no" string. Specâ€<EFBFBD>
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â€<EFBFBD>
typically depends on the settings of other options. For exam-
ple, the <B>--custom-gamma</B> table might be active only when a
grayscale or color scan-mode has been requested.
Note that the <B>--help</B> 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â€<EFBFBD>
option settings for a particular mode by specifying the appro-
priate mode-options along with the <B>--help</B> option. For example,
the command-line:
@ -248,7 +258,7 @@
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â€<EFBFBD>
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
@ -272,7 +282,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d</I>
<I>/usr/local/etc/sane.d</I>
This directory holds various configuration files. For details,
please refer to the manual pages listed below.
@ -281,30 +291,29 @@
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â€<C3A2>
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.
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B>xcam(1)</B>, <B>xsane(1)</B>,
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B>xcam(1)</B>, <B>xsane(1)</B>,
<B><A HREF="scanadf.1.html">scanadf(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B>sane-"backendname"</B>(5)
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
many others. For questions and comments contact the sane-devel mailâ€<C3A2>
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).
</PRE>
<H2>BUGS</H2><PRE>
For vector options, the help output currently has no indication as to
For vector options, the help output currently has no indication as to
how many elements a vector-value should have.
10 Jul 2008 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>