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

updates for sane-backends 1.0.24

merge-requests/1/head
m. allan noah 2013-09-30 22:17:11 -04:00
rodzic 3c651aaa43
commit 7f6bd48a06
24 zmienionych plików z 18780 dodań i 963 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

27
index.html
Wyświetl plik

@ -36,21 +36,19 @@
<td valign=top bgcolor="#e0e0ff" width="300">
<h3>Latest News</h3>
<p>
<strong>2012-08-19:</strong>
<a href="source.html">SANE-Backends-1.0.23</a> has been released. Changes since 1.0.22:
<strong>2013-09-30:</strong>
<a href="source.html">SANE-Backends-1.0.24</a> has been released. Changes since 1.0.23:
</p>
<ul>
<li>New backends: kvs40xx (Panasonic KV-S40xx), kodakaio (Kodak AiO ESP and Hero)</li>
<li>Significant enhancements to several backends</li>
<li>30 new scanner models supported</li>
<li>V4L support improvements</li>
<li>Improvements for builds on multiple platforms</li>
<li>Improved udev rules</li>
<li>Updated software deskew algorithm</li>
<li>Documentation updates</li>
<li>Bugfixes</li>
</ul>
<b>Note:</b> Due to problems with file downloads at alioth, the sane-backends source tarball has been divided into multiple parts. Directions for assembling these are provided in README.txt with <a href="source.html">the downloads</a>.
<li>Significant enhancements to pixma, genesys, kodakaio, fujitsu, canon_dr.
<li>Minor updates, bugfixes or scanners added in several backends.
<li>Added new testsuite
<li>51 new scanner models supported.
<li>USB support improvements.
<li>Improved build system (mingw64, bug fixes, default pthread on Linux).
<li>Documentation updates.
<li>Bugfixes.
</ul>
</td>
<td valign=top>
@ -82,8 +80,5 @@
<a href="imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>

27
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 37, which shipped with SANE
1.0.22.
This document describes backend version 41, which shipped with SANE
1.0.24.
</PRE>
@ -152,14 +152,20 @@
bytes. Enable this option if the scanner fails to respond to
commands.
Note: 'option' lines may appear multiple times in the configuration
file. They only apply to scanners discovered by the next 'scsi/usb'
"option duplex-offset [integer]"
Some scanners pad the upper edge of one side of a duplex scan.
There is some variation in the amount of padding. Modify this
option if your unit shows an unwanted band of image data on only
one side.
Note: 'option' lines may appear multiple times in the configuration
file. They only apply to scanners discovered by the next 'scsi/usb'
line.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
The backend uses a single environment variable, SANE_DEBUG_CANON_DR,
The backend uses a single environment variable, SANE_DEBUG_CANON_DR,
which enables debugging output to stderr. Valid values are:
5 Errors
@ -173,9 +179,9 @@
</PRE>
<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
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.
@ -188,7 +194,8 @@
HPrint hprint.com.br provided funding and testing for DR-2510 support
Stone-IT www.stone-it.com provided funding for DR-2010 and DR-2050 sup‐
port
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum‐
Gerhard Pfeffer provided access and testing for P-208 and P-215
Special thanks to: Alejandro Imass, Andre Shimakawa, Martijn van Brum‐
melen, Thanos Diacakis and Junren Shi for testing and feedback.
@ -201,7 +208,7 @@
<H2>AUTHOR</H2><PRE>
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
26 Jan 2011 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
16 Sep 2013 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -54,6 +54,12 @@
pnm
mustek
It is also possible to add a file in <I>/etc/sane.d/dll.d</I> that contains
the list of backends to be added. Backends mentioned in a file included
in this directory will be added before any backends listed in <I>dll.conf.</I>
Files in <I>/etc/sane.d/dll.d</I> can be freely named. 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‐
end was preloaded, then that backend will always be present, regardless
@ -147,7 +153,6 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
13 Jul 2008 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
</PRE>
<HR>

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

@ -62,12 +62,12 @@
</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‐
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
will not work.
The configuration file "/etc/sane.d/epjitsu.conf" is used to tell the
backend how to look for scanners, and provide options controlling the
operation of the backend. This file is read each time the frontend asks
the backend for a list of scanners, generally only when the frontend
starts. If the configuration file is missing, the backend will not
work.
Scanners can be specified in the configuration file in two ways:

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

@ -20,28 +20,29 @@
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 111, which shipped with SANE
1.0.23.
This document describes backend version 117, which shipped with SANE
1.0.24.
</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, and the USB
ScanSnap S5xx/S15xx scanners are supported. Please see the list at
http://www.sane-project.org/sane-supported-devices.html for details.
series, the SCSI fi-series, most of the USB fi-series, the USB ScanSnap
S5xx/S15xx, and the USB iX5xx 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‐
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
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.
</PRE>
<H2>UNSUPPORTED HARDWARE</H2><PRE>
The following scanners are known NOT to work with this backend, either
because they have a non-fujitsu chipset, or an unsupported interface
The following scanners are known NOT to work with this backend, either
because they have a non-fujitsu chipset, or an unsupported interface
type. Some of these scanners may be supported by another backend.
--------------------------------------
@ -60,15 +61,15 @@
Effort has been made to expose all hardware options, including:
source s
Selects the source for the scan. Options may include "Flatbed",
Selects the source for the scan. Options may include "Flatbed",
"ADF Front", "ADF Back", "ADF Duplex".
mode m
Selects the mode for the scan. Options may include "Lineart",
Selects the mode for the scan. Options may include "Lineart",
"Halftone", "Gray", and "Color".
resolution, y-resolution
Controls scan resolution. Setting --resolution also sets
Controls scan resolution. Setting --resolution also sets
--y-resolution, though this behavior is overridden by some fron‐
tends.
@ -77,32 +78,32 @@
renamed t, l, x, y by some frontends.
page-width, page-height
Sets paper size. Used by scanner to determine centering of scan
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
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.
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
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.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
The configuration file "fujitsu.conf" is used to tell the backend how
to look for scanners, and provide options controlling the operation of
The configuration file "fujitsu.conf" is used to tell the backend how
to look for scanners, and provide options controlling the operation of
the backend. This file is read each time the frontend asks the backend
for a list of scanners, generally only when the frontend starts. If the
configuration file is missing, the backend will be unable to locate any
@ -111,43 +112,43 @@
Scanners can be specified in the configuration file in 4 ways:
"scsi FUJITSU"
Requests backend to search all scsi busses in the system for a
Requests backend to search all scsi busses in the system for a
device which reports itself to be a scanner made by 'FUJITSU'.
"scsi /dev/sg0" (or other scsi device file)
Requests backend to open the named scsi device. Only useful if
you have multiple compatible scanners connected to your system,
and need to specify one. Probably should not be used with the
Requests backend to open the named scsi device. Only useful if
you have multiple compatible scanners connected to your system,
and need to specify one. Probably should not be used with the
other "scsi" line above.
"usb 0x04c5 0x1042" (or other vendor/product ids)
Requests backend to search all usb busses in the system for a
device which uses that vendor and product id. The device will
Requests backend to search all usb busses in the system for a
device which uses that vendor and product id. The device will
then be queried to determine if it is a Fujitsu scanner.
"usb /dev/usb/scanner0" (or other device file)
Some systems use a kernel driver to access usb scanners. This
Some systems use a kernel driver to access usb scanners. This
method is untested.
The only configuration option supported is "buffer-size=xxx", allowing
you to set the number of bytes in the data buffer to something other
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‐
fer is not large enough.
Note: This option may appear multiple times in the configuration file.
It only applies to scanners discovered by 'scsi/usb' lines that follow
Note: This option may appear multiple times in the configuration file.
It only applies to scanners discovered by 'scsi/usb' lines that follow
this option.
Note: The backend does not place an upper bound on this value, as some
users required it to be quite large. Values above the default are not
Note: The backend does not place an upper bound on this value, as some
users required it to be quite large. Values above the default are not
recommended, and may crash your OS or lockup your scsi card driver. You
have been warned.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
which enables debugging output to stderr. Valid values are:
5 Errors
@ -162,17 +163,14 @@
</PRE>
<H2>KNOWN ISSUES</H2><PRE>
Flatbed units may fail to scan at maximum area, particularly at high
Flatbed units may fail to scan at maximum area, particularly at high
resolution.
Any model that does not support VPD during inquiry will not function
Any model that does not support VPD during inquiry will not function
until an override is added to the backend.
CCITT Fax compression used by older scanners is not supported.
Hardware automatic paper width detection (aka auto-cropping) is not
supported.
JPEG output is supported by the backend, but not by the SANE protocol,
so is disabled in this release. It can be enabled if you rebuild from
source.
@ -211,6 +209,10 @@
Fujitsu Computer Products of America, Inc.
www.fcpa.com
iX500 support funded by:
Prefix Computer Services
www.prefixservice.com
</PRE>
<H2>SEE ALSO</H2><PRE>
@ -218,12 +220,11 @@
<B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
30 Jan 2011 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
17 Sep 2013 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -74,6 +74,16 @@
white point. Pixels whith brightness below that value will be
scanned as black.
<B>--brightness</B> <B>value</B>
-100..100 (in steps of 1). Set the brightness enhancement.
0 for no enhancement, negative values to decrease brigthness,
and positive values to increase it.
<B>--contrast</B> <B>value</B>
-100..100 (in steps of 1). Set the contrast enhancement. 0
for no enhancement, negative values to decrease contrast, and
positive values to increase it.
<B>--disable-interpolation</B> <B>yes|no</B>
When using high resolutions where the horizontal resolu‐
tion is smaller than vertical resolution, data is expanded by
@ -94,26 +104,37 @@
The lamp will be turned off during the scan. Calibration
is still done with lamp on.
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
<B>--clear-calibration</B>
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‐
ated. This allow to handle the case of several identical devices
that would otherwise use the same calibration data. This option
is disabled if the backend is ran as root.
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.
<B>--swcrop</B>
Requests the driver to detect the extremities of the paper
Requests the driver to detect the extremities of the paper
within the larger image, and crop the empty edges.
<B>--swdeskew</B>
Requests the driver to detect the rotation of the paper
Requests the driver to detect the rotation of the paper
within the larger image, and counter the rotation.
<B>--swdespeck</B> <B>--despeck</B> <B>X</B>
Requests the driver to find and remove dots of X diameter
or smaller from the image, and fill the space with the average
Requests the driver to find and remove dots of X diameter
or smaller from the image, and fill the space with the average
surrounding color.
<B>--swskip</B> <B>0..100%</B> <B>(in</B> <B>steps</B> <B>of</B> <B>1)</B> <B>[0]</B>
@ -121,34 +142,34 @@
pixels.
<B>--swderotate[=(yes|no)]</B> <B>[no]</B>
Request driver to detect and correct 90 degree image
Request driver to detect and correct 90 degree image
rotation.
</PRE>
<H2>SYSTEM ISSUES</H2><PRE>
This backend needs libusb-0.1.6 or later installed, and hasn't tested
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‐
piled. For setting permissions and general USB information look at
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>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
The contents of the <I>genesys.conf</I> file is a list of usb lines containing
vendor and product ids that correspond to USB scanners. The file can
also contain option lines. 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> statements which are already included into <I>genesys.conf</I>.
"vendor_id" and "product_id" are hexadecimal numbers that identify the
vendor and product ids that correspond to USB scanners. The file can
also contain option lines. 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> statements which are already included into <I>genesys.conf</I>.
"vendor_id" and "product_id" are hexadecimal numbers that identify the
scanner.
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d/genesys.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/lib/sane/libsane-genesys.a</I>
@ -164,23 +185,23 @@
<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
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
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
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).
<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
environment 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
debug level is set to 1 or higher, some debug options become
available that are normally hidden. Handle them with care. This
will print messages related to core genesys functions.
<B>SANE_DEBUG_GENESYS_LOW</B>
@ -188,23 +209,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):
@ -213,10 +234,9 @@
export SANE_DEBUG_GENESYS_GL646=255
</PRE>
<H2>CREDITS</H2><PRE>
Jack McGill for donating several sheetfed and flatbed scanners, which
Jack McGill for donating several sheetfed and flatbed scanners, which
made possible to add support for them in the genesys backend:
Hewlett-Packard HP3670
Visioneer Strobe XP100 (rev3)/XP200/XP300/Roadwarrior
@ -225,10 +245,10 @@
Syscan/Ambir DocketPORT 467/485/487/665/685
Xerox Travel Scanner 100, Onetouch 2400
cncsolutions (http://www.cncsolutions.com.br) sponsored and supported
cncsolutions (http://www.cncsolutions.com.br) sponsored and supported
the work on the Panasonic KV-SS080.
Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE
Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE
700F.
@ -250,19 +270,19 @@
</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
This backend will be much slower if not using libusb-1.0. So be sure
that sane-backends is built with the --enable-libusb_1_0 option.
</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
sensor. It seems the windows driver does some digital processing to
improve it, which is not implemented in the backend.
4 Jul 2012 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>

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

@ -162,7 +162,7 @@
<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-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
<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-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<I>/usr/doc/sane-1.0.22git/gt68xx/gt68xx.CHANGES</I>
<I>/usr/doc/sane-1.0.24/gt68xx/gt68xx.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/gt68xx</I>

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

@ -70,7 +70,7 @@
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/doc/sane-1.0.23git/PROBLEMS</I> file.
the <I>/usr/doc/sane-1.0.24/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‐
@ -311,7 +311,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(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>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<I>/usr/doc/sane-1.0.23git/mustek/mustek.CHANGES</I>
<I>/usr/doc/sane-1.0.24/mustek/mustek.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>

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

@ -7,7 +7,7 @@
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B> File Formats Manual <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
</PRE>

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

@ -148,8 +148,8 @@
<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>sane-plus</B>â€<B>â</B>€<EFBFBD>
<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/doc/sane-1.0.22git/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
<I>/usr/doc/sane-1.0.22git/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
<I>/usr/doc/sane-1.0.24/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
<I>/usr/doc/sane-1.0.24/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>

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

@ -69,7 +69,7 @@
<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>, <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-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
<I>/usr/doc/sane-1.0.23git/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
<I>/usr/doc/sane-1.0.24/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>

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

@ -12,21 +12,25 @@
</PRE>
<H2>NAME</H2><PRE>
<B>sane-pixma</B> - SANE backend for Canon PIXMA Multi-Functions Printers
E, MG, MP, MX, ImageCLASS, imageRunner and I-SENSYS series
and for Canon CanoScan Flatbed/TPU Scanners
sane-pixma - SANE backend for Canon Multi-Function Printers and
CanoScan Scanners
</PRE>
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pixma</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Canon PIXMA multi-function devices
(All-in-one printers). The backend implements both USB interface and
Network LAN interface using Canon's BJNP protocol. Currently, the folâ€<C3A2>
lowing models work with this backend:
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 USB inter‐
face and network interface using Canon's BJNP protocol. The network
interface supports scanners over IPv4 as well as IPv6.
Currently, the following models work with this backend:
PIXMA MG2100, MG3100, MG4200, MG5100, MG5200, MG5300
PIXMA MG6100, MG6200, MG6300, MG8200
PIXMA MP140, MP150, MP160, MP170, MP180, MP190
PIXMA MP210, MP220, MP240, MP250, MP260, MP270, MP280
PIXMA MP210, MP220, MP230, MP240, MP250, MP260, MP270, MP280
PIXMA MP360, MP370, MP390
PIXMA MP450, MP460, MP470, MP480, MP490
PIXMA MP500, MP510, MP520, MP530, MP540, MP550, MP560
@ -34,16 +38,17 @@
PIXMA MP700, MP710, MP730, PIXMA MP750 (no grayscale)
PIXMA MP800, MP800R, MP810, MP830
PIXMA MP960, MP970, MP980, MP990
PIXMA MX300, MX310, MX330, MX340, MX350, MX360
PIXMA MX300, MX310, MX330, MX340, MX350, MX360, MX370
PIXMA MX420, MX700, MX7600
PIXMA MX850, MX860, MX870, MX882, MX885
ImageCLASS MF3110, MF3240, MF4010, MF4018
ImageCLASS MF4120, MF4122, MF4140, MF4150
ImageCLASS MF4270, MF4350d, MF4370dn, MF4380dn
ImageCLASS MF4410, MF4660, MF4690
ImageCLASS MF5770, MF6550, D480
I-SENSYS MF4320d, MF4330d
CanoScan 8800F, 9000F
PIXMA MX850, MX860, MX870, MX882, MX885, MX890
imageCLASS MF3110, MF3240, MF4010, MF4018
imageCLASS MF4120, MF4122, MF4140, MF4150
imageCLASS MF4270, MF4350d, MF4370dn, MF4380dn
imageCLASS MF4410, MF4430, MF4660, MF4690, MF4770n
imageCLASS MF5730, MF5770, MF6550, D420, D480
i-SENSYS MF3010, MF4320d, MF4330d, MF4550d
imageRUNNER 1020/1024/1025
CanoScan 8800F, 9000F, 9000F Mark II
The following models are not well tested and/or the scanner sometimes
hangs and must be switched off and on.
@ -56,30 +61,26 @@
declared in the backend so that they get recognized and activated.
Feedback in the sane-devel mailing list welcome.
PIXMA MG2100, MG3100, MG4100, MG5100, MG5200, MG5300
PIXMA MG6100, MG6200, MG8100, MG8200
PIXMA E500, E510, E600, E610
PIXMA MG2200, MG2400, MG2500, MG3200, MG4100, MG5400, MG5500
PIXMA MG6400, MG6500, MG7100, MG8100
PIXMA MP375R, MP493, MP495, MP740
PIXMA MX320, MX410
ImageCLASS MF5630, MF5650, MF5730, MF5750, MF8030, MF8170c
imageRunner iR1020, iR1024, iR1025
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. Snoop logs are required to further
investigate, please contact the sane-devel mailing list.
PIXMA E500, E600
PIXMA MX370, MX430, MX510, MX710, MX890
PIXMA MX320, MX390, MX410, MX430, MX450, MX510, MX520
PIXMA MX710, MX720, MX920
imageCLASS MF4570dw, MF5630, MF5650, MF5750, MF8030, MF8170c
imageRUNNER 1133
i-SENSYS MF5880dn, MF6680dn
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â€<C3A2>
* 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.
* 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‐
@ -91,7 +92,7 @@
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 every situaâ€<C3A2>
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‐
formances.
@ -102,26 +103,56 @@
Besides "well-known" options (e.g. resolution, mode etc.) pixma backend
also provides the following options for button handling, 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.
<I>button-controlled</I>
This option can be used in combination with <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and <B>scan</B>â€<B>â</B>€<EFBFBD>
<B><A HREF="image.1.html">image(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 scanâ€<C3A2>
ner, 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
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.)
<I>button-update</I> <I>button-1</I> <I>button-2</I>
These options are interesting for developers. To check button
status: (1) set <I>button-1</I> and <I>button-2</I> to zero, (2) set <I>button-</I>
<I>update</I> (Its type is SANE_TYPE_BUTTON.), (3) get <I>button-1</I> and
<I>button-2</I>. If the result is not zero, the corresponding button
was pressed.
<I>button-update</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
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
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‐
ners can provide this data.
<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
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
dpi, 3 = 300 dpi, 4 = 600 dpi. Not all scanners can provide this
data.
</PRE>
@ -144,8 +175,10 @@
<I>bjnp://&lt;host&gt;</I>
where host is the hostname or IP address of the scanner, e.g.
bjnp://10.0.1.4 or bjnp://myscanner.mydomain.org. Define each
scanner on a new line.
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. Define each scan‐
ner on a new line.
</PRE>
@ -156,9 +189,11 @@
</PRE>
<H2>NETWORKING SUPPORT</H2><PRE>
The pixma backend supports network scanners using the so called Canon
BJNP protocol. 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.
BJNP protocol. Both IPv4 and IPv6 are supported.
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
configuration file (see above).
@ -172,14 +207,16 @@
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 interfaces). The broadcast is sent
FROM port 8612 TO port 8612 on the broadcast address of each interface.
The outgoing packets will be allowed by the rule described above.
OS allows for enumeration of all netowrk interfaces). The broadcast is
sent FROM port 8612 TO port 8612 on the broadcast address of each
interface. The outgoing packets will be allowed by the rule described
above.
Responses from the scanner are sent back to the computer TO port 8612.
Connection tracking however does not see a match as the response does
not come from the broadcast address but from the scanners own address.
You will therefore have to allow incoming packets TO port 8612 on your
computer.
For automatic detection of your scanner, you will therefore have to
allow incoming packets TO port 8612 on your computer.
So in short: open the firewall for all traffic from your computer to
port 8612 AND to port 8612 to your computer.
@ -193,15 +230,27 @@
<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.
Higher value increases the verbosity.
environment variable controls the debug level for this backend
itself. 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)
2 print informational messages
3 print debug-level messages
11 dump USB/BJNP traffics
21 full dump USB/BJNP traffic
11 dump USB traffic
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> net‐
work protocol for this backend. Higher value increases the ver‐
bosity and includes the information printed at the lower levels.
0 print nothing (default)
1 Print error and warning messages (recommended)
2 Print high level function tracing information
3 Print more detailed protocol tracing information
4 Print protocol headers
5 Print full protocol contents
<B>PIXMA_EXPERIMENT</B>
Setting to a non-zero value will enable the support for experi‐
@ -243,7 +292,7 @@
not be able to write subdrivers for models we don't have. See also the
project homepage.
31 Jul 2012 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
24 Sep 2013 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -117,6 +117,7 @@
USB Model: ASIC: Properties: Prod-ID
----------------------------------------------------------
Q-Scan USB001 LM9832 300x600dpi 42bit 512Kb 0x1000
Q-Scan USB201 LM9832 300x600dpi 42bit 512Kb 0x2000
Vendor Visioneer - ID: 0x04A7
----------------------------------------------------------
@ -309,7 +310,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>, <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/doc/sane-1.0.22git/plustek/Plustek-USB.changes</I>
<I>/usr/doc/sane-1.0.24/plustek/Plustek-USB.changes</I>
<I>http://www.gjaeger.de/scanner/plustek/</I>
@ -353,7 +354,7 @@
* Negative/Slide scanning quality is poor.
25 Aug 2008 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
13 Feb 2013 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
</PRE>
<HR>
<ADDRESS>

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

@ -342,7 +342,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>,
<I>/usr/doc/sane-1.0.23git/plustek/Plustek-PARPORT.changes</I>
<I>/usr/doc/sane-1.0.24/plustek/Plustek-PARPORT.changes</I>
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>

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

@ -127,7 +127,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>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
<I>/usr/doc/sane-1.0.23git/u12/U12.changes</I>
<I>/usr/doc/sane-1.0.24/u12/U12.changes</I>
<I>http://www.gjaeger.de/scanner/u12/</I>

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

@ -84,8 +84,8 @@
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/doc/sane-1.0.23git/README.linux, tools/README and the README in
the tools/hotplug directory for more details.
/usr/doc/sane-1.0.24/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.

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

@ -58,48 +58,47 @@
information 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/doc/sane-1.0.23git/sane.tex</I>' are references to text files
that were copied to the <B>SANE</B> documentation directory
(<I>/usr/local/doc/sane-1.0.23git/</I>) during installation. Everything else
is a URL to a resource on the web.
`<I>/usr/doc/sane-1.0.24/sane.tex</I>' are references to text files that were
copied to the <B>SANE</B> documentation directory (<I>/usr/doc/sane-1.0.24/</I>) dur‐
ing 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
the SANE FAQ can be found on the SANE homepage:
the SANE FAQ can be found on the SANE homepage:
<I>http://www.sane-project.org/</I>.
<B>SANE</B> <B>device</B> <B>lists</B>
The <B>SANE</B> device lists contain information about the status of <B>SANE</B>
support for a specific device. If your scanner is not listed there
The <B>SANE</B> device lists contain information about the status of <B>SANE</B>
support for a specific device. If your scanner is not listed there
(either supported or unsupported), please contact us. See section HOW
CAN YOU HELP SANE for details. There are lists for specific releases
of SANE, for the current development version and a search engine:
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/doc/sane-1.0.23git/.
are also installed on your system at /usr/doc/sane-1.0.24/.
<B>SANE</B> <B>mailing</B> <B>list</B>
There is a mailing list for the purpose of discussing the SANE stanâ€<C3A2>
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
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:
sane-devel 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â€<C3A2>
lems, talking about development and general <B>SANE</B> related chatting.
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‐
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â€<C3A2>
ments of problems with SANE infrastructure (mailing lists, web
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/doc/sane-1.0.23git/README</I> and the os-dependent
README files for information about compiling and installing <B>SANE.</B>
Look at <I>/usr/doc/sane-1.0.24/README</I> and the os-dependent README files
for information about compiling and installing <B>SANE.</B>
<B>SCSI</B> <B>configuration</B>
For information about various systems and SCSI controllers see
For information about various systems and SCSI controllers see
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
<B>USB</B> <B>configuration</B>
@ -116,10 +115,10 @@
sition devices available on the local host. See <B><A HREF="saned.8.html">saned(8)</A></B>.
<B>sane-find-scanner</B>
Command-line tool to find SCSI and USB scanners and determine their
Command-line tool to find SCSI and USB scanners and determine their
Unix device files. See <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>.
Also, have a look at the <B>sane-frontends</B> package (including <B>xscanimage</B>,
Also, have a look at the <B>sane-frontends</B> package (including <B>xscanimage</B>,
<B>xcam</B>, and <B>scanadf</B>) and the frontend information page at
<I>http://www.sane-project.org/sane-frontends.html</I>.
@ -128,36 +127,36 @@
<H2>BACKENDS FOR SCANNERS</H2><PRE>
<B>abaton</B>
The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
(8bit, 256 levels of gray) and the Scan 300/S (black and white,
(8bit, 256 levels of gray) and the Scan 300/S (black and white,
untested). See <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B> for details.
<B>agfafocus</B>
This backend supports AGFA Focus scanners and the Siemens S9036
This backend supports AGFA Focus scanners and the Siemens S9036
(untested). See <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B> for details.
<B>apple</B>
The SANE backend for Apple flatbed scanners supports the following
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.
<B>artec</B>
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
See <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B> for details.
<B>artec_eplus48u</B>
The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
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â€<C3A2>
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â€<C3A2>
This backend supports several Avision based scanners. This includes
the original Avision scanners (like AV 630, AV 620, ...) as well as
the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit‐
subishi and Minolta film-scanners. See <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B> for details.
<B>bh</B>
@ -165,23 +164,23 @@
ument scanners. See <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B> for details.
<B>canon</B>
The canon backend supports the CanoScan 300, CanoScan 600, and
The canon backend supports the CanoScan 300, CanoScan 600, and
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â€<C3A2>
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>
The canon_dr backend supports the Canon DR-Series ADF SCSI and USB
The canon_dr backend supports the Canon DR-Series ADF SCSI and USB
scanners. See <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B> for details.
<B>canon_pp</B>
The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
N640P parallel port scanners. See <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B> for details.
<B>cardscan</B>
This backend provides support for Corex Cardscan USB scanners. See
This backend provides support for Corex Cardscan USB scanners. See
<B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B> for details.
<B>coolscan</B>
@ -189,11 +188,11 @@
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B> for details.
<B>coolscan2</B>
This is a SANE backend for Nikon Coolscan film-scanners. See
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>epjitsu</B>
The epjitsu backend provides support for Epson-based Fujitsu USB
The epjitsu backend provides support for Epson-based Fujitsu USB
scanners. See <B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B> for details.
<B>epson</B>
@ -201,57 +200,57 @@
and USB flatbed scanners. See <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for details.
<B>fujitsu</B>
The fujitsu backend provides support for most Fujitsu SCSI and USB,
The fujitsu backend provides support for most Fujitsu SCSI and USB,
flatbed and adf scanners. See <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B> for details.
<B>genesys</B>
The genesys backend provides support for several scanners based on
The genesys backend provides support for several scanners based on
the Genesys Logic GL646, GL841, GL843, GL847 and GL124 chips like the
Medion 6471 and Hewlett-Packard 2300c.
See <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B> for details.
<B>gt68xx</B>
The gt68xx backend provides support for scanners based on the
Grandtech GT-6801 and GT-6816 chips like the Artec Ultima 2000 and
several Mustek BearPaw CU and TA models. Some Genius, Lexmark,
The gt68xx backend provides support for scanners based on the
Grandtech GT-6801 and GT-6816 chips like the Artec Ultima 2000 and
several Mustek BearPaw CU and TA models. Some Genius, Lexmark,
Medion, Packard Bell, Plustek, and Trust scanners are also supported.
See <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.
<B>hpsj5s</B>
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B> for details.
<B>hp3500</B>
The SANE backend for the Hewlett-Packard ScanJet 3500 series. See
The SANE backend for the Hewlett-Packard ScanJet 3500 series. See
<B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B> for details.
<B>hp3900</B>
The SANE backend for the Hewlett-Packard ScanJet 3900 series. See
The SANE backend for the Hewlett-Packard ScanJet 3900 series. See
<B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B> for details.
<B>hp4200</B>
The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
<B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B> for details.
<B>hp5400</B>
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B> for details.
<B>hpljm1005</B>
The SANE backend for the Hewlett-Packard LaserJet M1005 scanner. See
The SANE backend for the Hewlett-Packard LaserJet M1005 scanner. See
<B>sane-hpljm1005(5)</B> for details.
<B>hs2p</B>
The SANE backend for the Ricoh IS450 family of SCSI scanners. See
The SANE backend for the Ricoh IS450 family of SCSI scanners. See
<B><A HREF="sane-hs2p.5.html">sane-hs2p(5)</A></B> for details.
<B>ibm</B>
The SANE backend for some IBM and Ricoh SCSI scanners. See
The SANE backend for some IBM and Ricoh SCSI scanners. See
<B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B> for details.
<B>kodak</B>
@ -263,43 +262,43 @@
for details.
<B>kvs1025</B>
The SANE backend for Panasonic KV-S102xC scanners. See
The SANE backend for Panasonic KV-S102xC scanners. See
<B><A HREF="sane-kvs1025.5.html">sane-kvs1025(5)</A></B> for details.
<B>leo</B>
This backend supports the Leo S3 and the Across FS-1130, which is a
This backend supports the Leo S3 and the Across FS-1130, which is a
re-badged LEO FS-1130 scanner. See <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B> for details.
<B>lexmark</B>
This backend supports the Lexmark X1100 series of USB scanners. See
This backend supports the Lexmark X1100 series of USB scanners. See
<B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B> for details.
<B>ma1509</B>
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
scanner. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details.
<B>magicolor</B>
The magicolor backend supports the KONICA MINOLTA magicolor 1690MF
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.
<B>matsushita</B>
This backend supports some Panasonic KVSS high speed scanners. See
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
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.
<B>microtek2</B>
The microtek2 backend provides access to some Microtek scanners with
The microtek2 backend provides access to some Microtek scanners with
a SCSI-2 command set. See <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B> for details.
<B>mustek</B>
The SANE mustek backend supports most Mustek SCSI flatbed scanners
The SANE mustek backend supports most Mustek SCSI flatbed scanners
including the Paragon and ScanExpress series and the 600 II N and 600
II EP (non-SCSI). Some Trust scanners are also supported. See
II EP (non-SCSI). Some Trust scanners are also supported. See
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for details.
<B>mustek_pp</B>
@ -311,111 +310,111 @@
flatbed scanners. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B> for details.
<B>mustek_usb2</B>
The mustek_usb2 backend provides access to scanners using the SQ113
chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
The mustek_usb2 backend provides access to scanners using the SQ113
chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
<B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B> for details.
<B>nec</B>
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
<B><A HREF="sane-nec.5.html">sane-nec(5)</A></B> for details.
<B>niash</B>
The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
3300c, 3400c, and 4300c USB flatbed scanners. See <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B> for
3300c, 3400c, and 4300c USB flatbed scanners. See <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B> for
details.
<B>p5</B>
The SANE backend for Primax PagePartner. See <B><A HREF="sane-p5.5.html">sane-p5(5)</A></B> for details.
<B>pie</B>
The pie backend provides access to Pacific Image Electronics (PIE)
The pie backend provides access to Pacific Image Electronics (PIE)
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>
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.
<B>plustek</B>
The SANE plustek backend supports USB flatbed scanners that use the
The SANE plustek backend supports USB flatbed scanners that use the
National Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners
using this LM983x chips include some models from Plustek, KYE/Genius,
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
Hewlett-Packard, Mustek, Umax, Epson, and Canon. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
for details.
<B>plustek_pp</B>
The SANE plustek_pp backend supports Plustek parallel port flatbed
The SANE plustek_pp backend supports Plustek parallel port flatbed
scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
P98003 include some models from Plustek, KYE/Genius, Primax. See
P98003 include some models from Plustek, KYE/Genius, Primax. See
<B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B> for details.
<B>ricoh</B>
The ricoh backend provides access to the following Ricoh flatbed
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>s9036</B>
The s9036 backend provides access to Siemens 9036 flatbed scanners.
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.
<B>sceptre</B>
The sceptre backend provides access to the Sceptre S1200 flatbed
The sceptre backend provides access to the Sceptre S1200 flatbed
scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> for details.
<B>sharp</B>
The SANE sharp backend supports Sharp SCSI scanners. See
The SANE sharp backend supports Sharp SCSI scanners. See
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B> for details.
<B>sm3600</B>
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
scanner. See <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B> for details.
<B>sm3840</B>
The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
scanner. See <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B> for details.
<B>snapscan</B>
The snapscan backend supports AGFA SnapScan flatbed scanners. See
The snapscan backend supports AGFA SnapScan flatbed scanners. See
<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â€<C3A2>
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>
The sane-st400 backend provides access to Siemens ST400 and ST800.
The sane-st400 backend provides access to Siemens ST400 and ST800.
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â€<C3A2>
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>
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
The SANE teco1, teco2 and teco3 backends support some TECO scanners,
usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
See <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B> and <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B> for details.
<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
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.
<B>umax</B>
The sane-umax backend provides access to several UMAX-SCSI-scanners
The sane-umax backend provides access to several UMAX-SCSI-scanners
and some Linotype Hell SCSI-scanners. See <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B> for details.
<B>umax_pp</B>
The sane-umax_pp backend provides access to Umax parallel port
The sane-umax_pp backend provides access to Umax parallel port
flatbed scanners and the HP 3200C. See <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B> for details.
<B>umax1200u</B>
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
flatbed scanner (and also the UMAX Astra 2000U, sort of). See
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
flatbed scanner (and also the UMAX Astra 2000U, sort of). See
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B> for details.
Also, have a look at the backend information page at
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
projects in <I>/usr/local/doc/sane-1.0.23git/PROJECTS</I>.
projects in <I>/usr/doc/sane-1.0.24/PROJECTS</I>.
</PRE>
@ -434,10 +433,10 @@
<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â€<C3A2>
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
(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
<B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>.
<B>qcam</B>
@ -447,79 +446,78 @@
The sane-st680 backend provides access to webcams with a stv680 chip.
See <B><A HREF="sane-st680.5.html">sane-st680(5)</A></B> for details.
Also, have a look at the backend information page at
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
projects in <I>/usr/local/doc/sane-1.0.23git/PROJECTS</I>.
projects in <I>/usr/doc/sane-1.0.24/PROJECTS</I>.
</PRE>
<H2>MISCELLANEOUS BACKENDS</H2><PRE>
<B>dll</B>
The sane-dll library implements a <B>SANE</B> backend that provides access
The sane-dll library implements a <B>SANE</B> backend that provides access
to an arbitrary number of other <B>SANE</B> backends by dynamic loading. See
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>.
<B>net</B>
The <B>SANE</B> network daemon saned provides access to scanners located on
different computers in connection with the net backend. See
The <B>SANE</B> network daemon saned provides access to scanners located on
different computers in connection with the net backend. See
<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â€<C3A2>
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
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‐
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‐
tion. It provides test pictures and various test options. See
tion. It provides test pictures and various test options. See
<B><A HREF="sane-test.5.html">sane-test(5)</A></B>.
<B>v4l</B>
The sane-v4l library implements a <B>SANE</B> backend that provides generic
access to video cameras and similar equipment using the <B>V4L</B> (Video
The sane-v4l library implements a <B>SANE</B> backend that provides generic
access to video cameras and similar equipment using the <B>V4L</B> (Video
for Linux) API. See <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B><B>.</B>
Also, have a look at the backend information page at
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
projects in <I>/usr/local/doc/sane-1.0.23git/PROJECTS</I>.
projects in <I>/usr/doc/sane-1.0.24/PROJECTS</I>.
</PRE>
<H2>CHANGING THE TOP-LEVEL BACKEND</H2><PRE>
By default, all <B>SANE</B> backends (drivers) are loaded dynamically by the
<B>sane-dll</B> meta backend. If you have any questions about the dynamic
loading, read <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>. <B>SANE</B> frontend can also be linked to other
backends directly by copying or linking a backend to <B>libsane.so</B> in
<I>/usr/local/lib/sane</I>.
By default, all <B>SANE</B> backends (drivers) are loaded dynamically by the
<B>sane-dll</B> meta backend. If you have any questions about the dynamic
loading, read <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>. <B>SANE</B> frontend can also be linked to other
backends directly by copying or linking a backend to <B>libsane.so</B> in
<I>/usr/lib/sane</I>.
</PRE>
<H2>DEVELOPER'S DOCUMENTATION</H2><PRE>
It's not hard to write a <B>SANE</B> backend. It can take some time, however.
You should have basic knowledge of C and enough patience to work
It's not hard to write a <B>SANE</B> backend. It can take some time, however.
You should have basic knowledge of C and enough patience to work
through the documentation and find out how your scanner works. Appended
is a list of some documents that help to write backends and frontends.
The <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/doc/sane-1.0.23git/sane.ps</I> (if latex is installed
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).
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/doc/sane-1.0.24/sane.ps</I> (if latex is installed 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/doc/sane-1.0.23git/backend-writing.txt</I>. Most of the interâ€<C3A2>
nal <B>SANE</B> routines (<B>sanei</B>) are documented using doxygen:
<I>/usr/doc/sane-1.0.24/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/doc/sane-1.0.23git/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>.
project is started, have a look at <I>/usr/doc/sane-1.0.24/PROJECTS</I> for
projects that are planned or not yet included into the <B>SANE</B> distribu‐
tion 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‐
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
@ -531,17 +529,17 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/usr/local/etc/sane.d/*.conf</I>
<I>/etc/sane.d/*.conf</I>
The backend configuration files.
<I>/usr/local/lib/sane/libsane-*.a</I>
<I>/usr/lib/sane/libsane-*.a</I>
The static libraries implementing the backends.
<I>/usr/local/lib/sane/libsane-*.so</I>
<I>/usr/lib/sane/libsane-*.so</I>
The shared libraries implementing the backends (present on sys‐
tems that support dynamic loading).
<I>/usr/local/doc/sane-1.0.23git/*</I>
<I>/usr/doc/sane-1.0.24/*</I>
<B>SANE</B> documentation: The standard, READMEs, text files for back‐
ends etc.
@ -562,14 +560,14 @@
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‐
end's name is mentioned in <I>/usr/local/etc/sane.d/dll.conf</I>. Some backâ€<C3A2>
ends are commented out by default. Remove the comment sign for your
backend in this case. Also some backends aren't compiled at all if one
of their prerequisites are missing. Examples include dc210, dc240,
canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm.
If you need one of these backends and they aren't available, read the
build instructions in the <B>README</B> file and the individual manual pages
of the backends.
end's name is mentioned in <I>/etc/sane.d/dll.conf</I>. Some backends are
commented out by default. Remove the comment sign for your backend in
this case. Also some backends aren't compiled at all if one of their
prerequisites are missing. Examples include dc210, dc240, canon_pp,
hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you
need one of these backends and they aren't available, read the build
instructions in the <B>README</B> file and the individual manual pages of the
backends.
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>
@ -631,10 +629,10 @@
For reporting bugs or requesting new features, please use our bug-
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
contact the author of your backend directly. Usually the email address
can be found in the <I>/usr/local/doc/sane-1.0.23git/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>
<I>ing-lists.html</I> for details).
can be found in the <I>/usr/doc/sane-1.0.24/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/mailing-lists.html</I> for
details).
</PRE>
@ -664,9 +662,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger-Tang and many many more (see
<I>/usr/local/doc/sane-1.0.23git/AUTHORS</I> for details). This man page was
written by Henning Meier-Geinitz. Quite a lot of text was taken from
the <B>SANE</B> standard, several man pages, and README files.
<I>/usr/doc/sane-1.0.24/AUTHORS</I> for details). This man page was written
by Henning 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>
</PRE>

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

@ -17,7 +17,7 @@
</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>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>
</PRE>
@ -36,15 +36,17 @@
<B>-a</B> , <B>saned</B> will drop root privileges and run as this user (and group).
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> mode). In this mode, <B>saned</B> explicitly waits for a connection
request. When compiled with debugging enabled, these flags may be fol‐
lowed 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.
<B><A HREF="inetd.8.html">inetd(8)</A></B> daemon mode). In this mode, <B>saned</B> explicitly waits for a conâ€<EFBFBD>
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.
If <B>saned</B> is run from inetd or xinetd, no option can be given.
If <B>saned</B> is run from inetd, xinetd or systemd, no option can be given.
The <B>-h</B> flag displays a short help message.
</PRE>
@ -93,33 +95,53 @@
</PRE>
<H2>INETD CONFIGURATION</H2><PRE>
<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 a configuration line to <I>/etc/inetd.conf</I>. Note that
your inetd must support IPv6 if you want to connect to saned over IPv6
; xinetd and openbsd-inetd are known to support IPv6, check the docu‐
mentation for your inetd daemon.
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
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>
are described in more detail.
For the configurations below it is necessary to add a line of the folâ€<C3A2>
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
name "sane" is now deprecated.
</PRE>
<H2>INETD CONFIGURATION</H2><PRE>
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/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:
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:
sane-port stream tcp nowait saned.saned /usr/sbin/tcpd
/usr/sbin/saned
sane-port stream tcp nowait saned.saned /usr/sbin/tcpd
/usr/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‐
ner devices).
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 scanner devices).
</PRE>
<H2>XINETD CONFIGURATION</H2><PRE>
If xinetd is installed on your system instead of inetd the following
example for xinetd.conf may be helpful:
example for <I>/etc/xinetd.conf</I> may be helpful:
# default: off
# description: The sane server accepts requests
@ -135,24 +157,60 @@
server = /usr/sbin/saned
}
Finally, it is also necessary to add a line of the following form to
<I>/etc/services</I>:
sane-port 6566/tcp # SANE network scanner daemon
</PRE>
<H2>SYSTEMD CONFIGURATION</H2><PRE>
for systemd we need to add 2 configuation files in <I>/etc/systemd/system.</I>
The official IANA short name for port 6566 is "sane-port". The older
name "sane" is now deprecated.
The first file we need to add here is called <I>saned.socket.</I> It shall
have the following contents:
[Unit]
Description=saned incoming socket
[Socket]
ListenStream=6566
Accept=yes
MaxConnections=1
[Install]
WantedBy=sockets.target
The second file to be added is <I>saned@.service</I> with the following conâ€<C3A2>
tents:
[Unit]
Description=Scanner Service
Requires=saned.socket
[Service]
ExecStart=/usr/sbin/saned
User=saned
Group=saned
StandardInput=null
StandardOutput=syslog
StandardError=syslog
# Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255
Is you need to set an environment variable for saned like <B>SANE_CON</B>â€<B>â</B>€<EFBFBD>
<B>FIG_DIR</B> you will have to remove the # on the last line and set the
variable appropriately. 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_&lt;backend_name&gt;</B> to be captured. With the service unit as
described above, the debugging output is forwarded to the system log.
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/hosts.equiv</I>
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
and its use is not recommended.
<I>/etc/sane.d/saned.conf</I>
Contains a list of hosts permitted to access local SANE devices
Contains a list of hosts permitted to access local SANE devices
(see also description of <B>SANE_CONFIG_DIR</B> below).
<I>/etc/sane.d/saned.users</I>
@ -160,8 +218,8 @@
user:password:backend
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
The server uses MD5 hashing if supported by the client.
@ -170,15 +228,15 @@
<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
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
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â€<C3A2>
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
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).

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

@ -19,7 +19,7 @@
<H2>SYNOPSIS</H2><PRE>
<B>scanimage</B> [<B>-d</B>|<B>--device-name</B> <I>dev</I>] [<B>--format</B> <I>format</I>] [<B>-i</B>|<B>--icc-profile</B>
<I>profile</I>] [<B>-L</B>|<B>--list-devices</B>] [<B>-f</B>|<B>--formatted-device-list</B> <I>format</I>]
[<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</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>]

15998
sane-backends-1.0.23.html 100644
Wyświetl plik

Plik diff jest za duży Load Diff

936
sane-backends.html
Wyświetl plik

Plik diff jest za duży Load Diff

1
sane-md5sums.txt
Wyświetl plik

@ -12,6 +12,7 @@ a0cfdfdebca2feb4f2ba5d3418b15a42 sane-backends-1.0.20.tar.gz
be586a23633949cf2ecf0c9c6d769130 sane-backends-1.0.21.tar.gz
fadf56a60f4776bfb24491f66b617cf5 sane-backends-1.0.22.tar.gz
e226a89c54173efea80e91e9a5eb6573 sane-backends-1.0.23.tar.gz
1ca68e536cd7c1852322822f5f6ac3a4 sane-backends-1.0.24.tar.gz
a7de89c3e67495e8a38ca63b2ff693c4 sane-frontends-1.0.10.tar.gz
59b143e12c926726db16983d288aa1a1 sane-frontends-1.0.11.tar.gz
6a6166428491b268f5ebe03f16d1bc1f sane-frontends-1.0.12.tar.gz

1881
sane-mfgs.html
Wyświetl plik

Plik diff jest za duży Load Diff

1
sane-supported-devices.html
Wyświetl plik

@ -104,6 +104,7 @@
</p>
<p>
SANE version:
<a href="sane-backends-1.0.23.html">1.0.23</a>,
<a href="sane-backends-1.0.22.html">1.0.22</a>,
<a href="sane-backends-1.0.21.html">1.0.21</a>,
<a href="sane-backends-1.0.20.html">1.0.20</a>,