kopia lustrzana https://gitlab.com/sane-project/website
552 wiersze
23 KiB
HTML
552 wiersze
23 KiB
HTML
<HTML>
|
||
<HEAD>
|
||
<TITLE>sane.7</TITLE>
|
||
</HEAD>
|
||
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
||
<H1>sane.7</H1>
|
||
<HR>
|
||
<PRE>
|
||
<!-- Manpage converted by man2html 3.0.1 -->
|
||
<B><A HREF="sane.7.html">sane(7)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane.7.html">sane(7)</A></B>
|
||
|
||
|
||
</PRE>
|
||
<H2>DESCRIPTION</H2><PRE>
|
||
<B>SANE</B> is an application programming interface (API) that
|
||
provides standardized 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.
|
||
|
||
While <B>SANE</B> is primarily targeted at a UNIX environment,
|
||
the standard has been carefully designed to make it possi
|
||
ble to implement the API on virtually any hardware or
|
||
operating system.
|
||
|
||
This manual page provides a summary of the information
|
||
available about <B>SANE</B>.
|
||
|
||
If you have trouble getting your scanner detected, read
|
||
the PROBLEMS section.
|
||
|
||
|
||
|
||
</PRE>
|
||
<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> inter
|
||
face 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 backends.
|
||
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>SOFTWARE PACKAGES</H2><PRE>
|
||
The package `<B>sane-backends</B>' contains a lot of backends,
|
||
documentation (including the <B>SANE</B> standard), networking
|
||
support, and the command line frontend `<B>scanimage</B>'. The
|
||
frontends `<B>xscanimage</B>', `<B>xcam</B>', and `<B>scanadf</B>' are included
|
||
in the package `<B>sane-frontends</B>'. Both packages can be
|
||
downloaded from the <B>SANE</B> homepage (<I>http://www.sane-pro</I>
|
||
<I>ject.org/</I>). Information about other frontends and back
|
||
ends can be found on the frontend page
|
||
(<I>http://www.sane-project.org/sane-frontends.html</I>).
|
||
|
||
|
||
|
||
</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 parenthesis (e.g. `<B>sane-dll(5)</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/doc/sane-1.0.15/sane.tex</I>' are references to text
|
||
files that were copied to the <B>SANE</B> documentation directory
|
||
(<I>/usr/doc/sane-1.0.15/</I>) during installation. Every
|
||
thing else is a URL to a resource on the web.
|
||
|
||
|
||
your system at /usr/doc/sane-1.0.15/.
|
||
|
||
<B>SANE</B> <B>mailing</B> <B>list</B>
|
||
There is a mailing list for the purpose of discussing
|
||
the SANE standard and its implementations: sane-devel.
|
||
Despite its name, the list is not only intended for
|
||
developers, but also for users. Since this is currently
|
||
the only mailing list devoted to SANE, it's perfectly OK
|
||
to ask questions that are not strictly related to SANE
|
||
development. 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> problems, talking about development and
|
||
general <B>SANE</B> related chatting. Before asking for help,
|
||
please read the other documentation mentioned in this
|
||
manual page.
|
||
|
||
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
|
||
Look at <I>/usr/doc/sane-1.0.15/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 con
|
||
trollers see <B>sane-scsi(5)</B>.
|
||
|
||
<B>USB</B> <B>configuration</B>
|
||
For information about USB configuration see <B>sane-usb(5)</B>.
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>FRONTENDS AND MISCELLANEOUS PROGRAMS</H2><PRE>
|
||
<B>scanimage</B>
|
||
Command-line frontend. See <B>scanimage(1)</B>.
|
||
|
||
<B>saned</B>
|
||
<B>SANE</B> network daemon that allows remote clients to access
|
||
image acquisition devices available on the local host.
|
||
See <B>saned(8)</B>.
|
||
|
||
<B>sane-find-scanner</B>
|
||
Command-line tool to find SCSI and USB scanners and
|
||
determine their Unix device files. See <B>sane-find-scan</B>
|
||
<B>ner(1)</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 informa
|
||
tion page at <I>http://www.sane-project.org/sane-fron</I>
|
||
<I>tends.html</I>.
|
||
|
||
The SANE backend for Apple flatbed scanners supports the
|
||
following scanners: AppleScanner, OneScanner and Col
|
||
orOneScanner. See <B>sane-apple(5)</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. See <B>sane-artec(5)</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 and Trust Easy Webscan
|
||
19200. See <B>sane-artec_eplus48u(5)</B> for details.
|
||
|
||
<B>as6e</B>
|
||
This is a SANE backend for using the Artec AS6E parallel
|
||
port interface scanner. See <B>sane-as6e(5)</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 Mitsubishi and
|
||
Minolta film-scanners. See <B>sane-avision(5)</B> for details.
|
||
|
||
<B>bh</B>
|
||
The bh backend provides access to Bell+Howell Copiscan
|
||
II series document scanners. See <B>sane-bh(5)</B> for details.
|
||
|
||
<B>canon</B>
|
||
The canon backend supports the CanoScan 300, CanoScan
|
||
600, and CanoScan 2700F SCSI flatbed scanners. See
|
||
<B>sane-canon(5)</B> for details.
|
||
|
||
<B>canon630u</B>
|
||
The canon630u backend supports the CanoScan 630u and
|
||
636u USB scanners. See <B>sane-canon630u(5)</B> for details.
|
||
|
||
<B>canon_pp</B>
|
||
The canon_pp backend supports the CanoScan FB330P,
|
||
FB630P, N340P and N640P parallel port scanners. See
|
||
<B>sane-canon_pp(5)</B> for details.
|
||
|
||
<B>coolscan</B>
|
||
This is a SANE backend for Nikon Coolscan film-scanners.
|
||
See <B>sane-coolscan(5)</B> for details.
|
||
|
||
<B>coolscan2</B>
|
||
This is a SANE backend for Nikon Coolscan film-scanners.
|
||
See <B>sane-coolscan2(5)</B> or <I>http://coolscan2.source</I>
|
||
<I>forge.net</I> for details.
|
||
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>sane-gt68xx(5)</B> for details.
|
||
|
||
<B>hp</B>
|
||
The SANE hp backend provides access to Hewlett-Packard
|
||
ScanJet scanners which support SCL (Scanner Control Lan
|
||
guage by HP). See <B>sane-hp(5)</B> for details.
|
||
|
||
<B>hpsj5s</B>
|
||
The SANE backend for the Hewlett-Packard ScanJet 5S
|
||
scanner. See <B>sane-hpsj5s(5)</B> for details.
|
||
|
||
<B>hp5400</B>
|
||
The SANE backend for the Hewlett-Packard ScanJet 54XXC
|
||
series. See <B>sane-hp5400(5)</B> for details.
|
||
|
||
<B>ibm</B>
|
||
The SANE backend for some IBM and Ricoh SCSI scanners.
|
||
See <B>sane-ibm(5)</B> for details.
|
||
|
||
<B>leo</B>
|
||
This backend supports the Leo S3 and the Across FS-1130,
|
||
which is a re-badged LEO FS-1130 scanner. See
|
||
<B>sane-leo(5)</B> for details.
|
||
|
||
<B>ma1509</B>
|
||
The ma1509 backend supports the Mustek BearPaw 1200F USB
|
||
flatbed scanner. See <B>sane-ma1509(5)</B> for details.
|
||
|
||
<B>matsushita</B>
|
||
This backend supports some Panasonic KVSS high speed
|
||
scanners. See <B>sane-matsushita(5)</B> for details.
|
||
|
||
<B>microtek</B>
|
||
The microtek backend provides access to the "second gen
|
||
eration" Microtek scanners with SCSI-1 command set. See
|
||
<B>sane-microtek(5)</B> for details.
|
||
|
||
<B>microtek2</B>
|
||
The microtek2 backend provides access to some Microtek
|
||
scanners with a SCSI-2 command set. See
|
||
<B>sane-microtek2(5)</B> for details.
|
||
|
||
<B>mustek</B>
|
||
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 <B>sane-mustek(5)</B>
|
||
for details.
|
||
|
||
<B>niash</B>
|
||
The niash backend supports the Agfa Snapscan Touch and
|
||
the HP ScanJet 3300c, 3400c, and 4300c USB flatbed scan
|
||
ners. See <B>sane-niash(5)</B> for details.
|
||
|
||
<B>pie</B>
|
||
The pie backend provides access to Pacific Image Elec
|
||
tronics (PIE) and Devcom SCSI flatbed scanners. See
|
||
<B>sane-pie(5)</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, Hewlett-Packard,
|
||
Mustek, Umax, Epson, and Canon. See <B>sane-plustek(5)</B> for
|
||
details.
|
||
|
||
<B>plustek_pp</B>
|
||
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 <B>sane-plustek_pp(5)</B>
|
||
for details.
|
||
|
||
<B>ricoh</B>
|
||
The ricoh backend provides access to the following Ricoh
|
||
flatbed scanners: IS50 and IS60. See <B>sane-ricoh(5)</B> for
|
||
details.
|
||
|
||
<B>s9036</B>
|
||
The s9036 backend provides access to Siemens 9036
|
||
flatbed scanners. See <B>sane-s9036(5)</B> for details.
|
||
|
||
<B>sceptre</B>
|
||
The sceptre backend provides access to the Sceptre S1200
|
||
flatbed scanner. See <B>sane-sceptre(5)</B>
|
||
for details.
|
||
|
||
<B>sharp</B>
|
||
The SANE sharp backend supports Sharp SCSI scanners. See
|
||
<B>sane-sharp(5)</B> for details.
|
||
|
||
<B>sm3600</B>
|
||
The SANE sm3600 backend supports the Microtek ScanMaker
|
||
3600 USB scanner. See <B>sane-sm3600(5)</B> for details.
|
||
|
||
<B>snapscan</B>
|
||
The snapscan backend supports AGFA SnapScan flatbed
|
||
scanners. See <B>sane-snapscan(5)</B> for details.
|
||
|
||
<B>sp15c</B>
|
||
Primax, Piotech, Dextra names. See <B>sane-teco1(5)</B>,
|
||
<B>sane-teco2(5)</B> and <B>sane-teco3(5)</B> for details.
|
||
|
||
<B>umax</B>
|
||
The sane-umax backend provides access to several UMAX-
|
||
SCSI-scanners and some Linotype Hell SCSI-scanners. See
|
||
<B>sane-umax(5)</B> for details.
|
||
|
||
<B>umax_pp</B>
|
||
The sane-umax_pp backend provides access to Umax paral
|
||
lel port flatbed scanners and the HP 3200C. See
|
||
<B>sane-umax_pp(5)</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 <B>sane-umax1220u(5)</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 projects in <I>/usr/doc/sane-1.0.15/PRO</I>
|
||
<I>JECTS</I>.
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>BACKENDS FOR DIGITAL CAMERAS</H2><PRE>
|
||
<B>dc210</B>
|
||
Backend for Kodak DC210 Digital Camera. See
|
||
<B>sane-dc210(5)</B>.
|
||
|
||
<B>dc240</B>
|
||
Backend for Kodak DC240 Digital Camera. See
|
||
<B>sane-dc240(5)</B>.
|
||
|
||
<B>dc25</B>
|
||
Backend for Kodak DC20/DC25 Digital Cameras. See
|
||
<B>sane-dc25(5)</B>.
|
||
|
||
<B>dmc</B>
|
||
Backend for the Polaroid Digital Microscope Camera. See
|
||
<B>sane-dmc(5)</B>.
|
||
|
||
<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 supported 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>sane-gphoto2(5)</B>.
|
||
|
||
<B>qcam</B>
|
||
Backend for Connectix QuickCam cameras. See
|
||
|
||
<B>net</B>
|
||
The <B>SANE</B> network daemon saned provides access to scan
|
||
ners located on different computers in connection with
|
||
the net backend. See <B>sane-net(5)</B> and <B>saned(8)</B>.
|
||
|
||
<B>pnm</B>
|
||
PNM image reader pseudo-backend. The purpose of this
|
||
backend is primarily to aid in debugging of <B>SANE</B> fron
|
||
tends. See <B>sane-pnm(5)</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 systems. See
|
||
<B>sane-pint(5)</B>.
|
||
|
||
<B>test</B>
|
||
The <B>SANE</B> test backend is for testing frontends and the
|
||
<B>SANE</B> installation. It provides test pictures and vari
|
||
ous test options. See <B>sane-test(5)</B>.
|
||
|
||
<B>v4l</B>
|
||
The sane-v4l library implements a <B>SANE</B> backend that pro
|
||
vides generic access to video cameras and similar equip
|
||
ment using the <B>V4L</B> (Video for Linux) API. See
|
||
<B>sane-v4l(5)</B><B>.</B>
|
||
|
||
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/doc/sane-1.0.15/PRO</I>
|
||
<I>JECTS</I>.
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>CHANGING THE TOP-LEVEL BACKEND</H2><PRE>
|
||
By default, all <B>SANE</B> backends (drivers) are loaded dynami
|
||
cally by the <B>sane-dll</B> meta backend. If you have any ques
|
||
tions about the dynamic loading, read <B>sane-dll(5)</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 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
|
||
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 scanner: <I>http://www.meier-</I>
|
||
<I>geinitz.de/sane/misc/develop.html</I>.
|
||
|
||
|
||
If you start writing a backend or frontend or any other
|
||
part of <B>SANE,</B> please contact the sane-devel mailing list
|
||
for coordination so the same work isn't done twice.
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>FILES</H2><PRE>
|
||
<I>/etc/sane.d/*.conf</I>
|
||
The backend configuration files.
|
||
|
||
<I>/usr/lib/sane/libsane-*.a</I>
|
||
The static libraries implementing the backends.
|
||
|
||
<I>/usr/lib/sane/libsane-*.so</I>
|
||
The shared libraries implementing the backends
|
||
(present on systems that support dynamic loading).
|
||
|
||
<I>/usr/doc/sane-1.0.15/*</I>
|
||
<B>SANE</B> documentation: The standard, READMEs, text
|
||
files for backends etc.
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>PROBLEMS</H2><PRE>
|
||
If your device isn't found but you know that it is sup
|
||
ported, make sure that it is detected by your operating
|
||
system. For SCSI and USB scanners, use the <B>sane-find-scan</B>
|
||
<B>ner</B> tool (see <B>sane-find-scanner(1)</B> for details). It prints
|
||
one line for each scanner it has detected and some com
|
||
ments (#). 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>sane-usb(5)</B> or <B>sane-scsi(5)</B>. If your scan
|
||
ner (or other device) is not connected over the SCSI bus
|
||
or USB, read the backend's manual page for details on how
|
||
to set it up.
|
||
|
||
|
||
Now your scanner is detected by the operating system but
|
||
not by <B>SANE</B>? Try <B>scanimage</B> <B>-L</B>. If the scanner is not
|
||
found, check that the backend'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
|
||
manual page for details.
|
||
|
||
If your scanner is still not found, try setting the vari
|
||
ous environment variables that are available to assist in
|
||
debugging. The environment variables are documented in
|
||
the relevant manual pages. For example, to get the maxi
|
||
mum amount of debug information when testing a Mustek SCSI
|
||
scanner, set environment variables <B>SANE_DEBUG_DLL</B>,
|
||
<B>SANE_DEBUG_MUSTEK</B>, and <B>SANE_DEBUG_SANEI_SCSI</B> to 128 and
|
||
then invoke <B>scanimage</B> <B>-L</B> <B>.</B> The debug messages for the dll
|
||
backend tell if the mustek backend was found and loaded at
|
||
all. The mustek messages explain what the mustek backend
|
||
is doing while the SCSI debugging shows the low level han
|
||
dling. If you can't find out what's going on by checking
|
||
the messages carefully, contact 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>scanimage</B> <B>>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 debug
|
||
ging as mentioned above. Maybe the configuration file
|
||
needs some tuning, e.g. to setup the path to a firmware
|
||
that is needed by some scanners. See the backend's manual
|
||
page for details. If you can't find out what's wrong, con
|
||
tact 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:
|
||
|
||
<B>scanimage</B> <B>-d</B> <I>test</I> <B>-T</B>
|
||
|
||
You should get a list of PASSed tests. You can do the same
|
||
with your backend by changing "test" to your backend's
|
||
name.
|
||
|
||
So now scanning with <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 pos
|
||
sible 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> con
|
||
tain <I>/usr/local/lib/sane</I>. See also the documentation of
|
||
the frontends.
|
||
|
||
|
||
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>
|
||
<H2>SEE ALSO</H2><PRE>
|
||
<B>saned(8)</B>, <B>sane-find-scanner(1)</B>, <B>scanimage(1)</B>, <B>sane-aba</B>
|
||
<B>ton(5)</B>, <B>sane-agfafocus(5)</B>, <B>sane-apple(5)</B>, <B>sane-artec(5)</B>,
|
||
<B>sane-artec_eplus48u(5)</B>, <B>sane-as6e(5)</B>, <B>sane-avision(5)</B>,
|
||
<B>sane-bh(5)</B>, <B>sane-canon(5)</B>, <B>sane-canon630u(5)</B>,
|
||
<B>sane-canon_pp(5)</B>, <B>sane-coolscan2(5)</B>, <B>sane-coolscan(5)</B>,
|
||
<B>sane-dc210(5)</B>, <B>sane-dc240(5)</B>, <B>sane-dc25(5)</B>, <B>sane-dll(5)</B>,
|
||
<B>sane-dmc(5)</B>, <B>sane-epson(5)</B>, <B>sane-fujitsu(5)</B>,
|
||
<B>sane-gphoto2(5)</B>, <B>sane-gt68xx(5)</B>, <B>sane-hp(5)</B>,
|
||
<B>sane-hpsj5s(5)</B>, <B>sane-hp5400(5)</B> <B>sane-ibm(5)</B>, <B>sane-leo(5)</B>,
|
||
<B>sane-ma1509(5)</B>, <B>sane-matsushita(5)</B>, <B>sane-microtek2(5)</B>,
|
||
<B>sane-microtek(5)</B>, <B>sane-mustek(5)</B>, <B>sane-mustek_pp(5)</B>,
|
||
<B>sane-mustek_usb(5)</B>, <B>sane-nec(5)</B>, <B>sane-net(5)</B>,
|
||
<B>sane-niash(5)</B>, <B>sane-pie(5)</B>, <B>sane-pint(5)</B>, <B>sane-plustek(5)</B>,
|
||
<B>sane-plustek_pp(5)</B>, <B>sane-pnm(5)</B>, <B>sane-qcam(5)</B>,
|
||
<B>sane-ricoh(5)</B>, <B>sane-s9036(5)</B>, <B>sane-sceptre(5)</B>,
|
||
<B>sane-scsi(5)</B>, <B>sane-sharp(5)</B>, <B>sane-sm3600(5)</B>, <B>sane-snap</B>
|
||
<B>scan(5)</B>, <B>sane-sp15c(5)</B>, <B>sane-st400(5)</B>, <B>sane-tamarack(5)</B>,
|
||
<B>sane-teco1(5)</B>, <B>sane-teco2(5)</B>, <B>sane-teco3(5)</B>, <B>sane-test(5)</B>,
|
||
<B>sane-u12(5)</B>, <B>sane-umax1220u(5)</B>, <B>sane-umax(5)</B>,
|
||
<B>sane-umax_pp(5)</B>, <B>sane-usb(5)</B>, <B>sane-v4l(5)</B>
|
||
|
||
|
||
|
||
</PRE>
|
||
<H2>AUTHOR</H2><PRE>
|
||
David Mosberger-Tang and many many more (see
|
||
<I>/usr/doc/sane-1.0.15/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.
|
||
|
||
|
||
|
||
sane-backends 1.0.15 03 Aug 2004 <B>sane(7)</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>
|