1sane(7) SANE Scanner Access Now Easy sane(7)
2
6 sane - Scanner Access Now Easy: API for accessing scanners
7
10 SANE is an application programming interface (API) that provides stan‐
11 dardized access to any raster image scanner hardware. The standardized
12 interface makes it possible to write just one driver for each scanner
13 device instead of one driver for each scanner and application.
14 While SANE is primarily targeted at a UNIX environment, the standard
16 has been carefully designed to make it possible to implement the API on
17 virtually any hardware or operating system.
18 This manual page provides a summary of the information available about
20 SANE.
21 If you have trouble getting your scanner detected, read the PROBLEMS
23 section.
24
27 An application that uses the SANE interface is called a SANE frontend.
28 A driver that implements the SANE interface is called a SANE backend.
29 A meta backend provides some means to manage one or more other back‐
30 ends.
31
35 The package `sane-backends' contains a lot of backends, documentation
36 (including the SANE standard), networking support, and the command line
37 frontend `scanimage'. The frontends `xscanimage', `xcam', and
38 `scanadf' are included in the package `sane-frontends'. Both packages
39 can be downloaded from the SANE homepage
40 (http://www.sane-project.org/). Information about other frontends and
41 backends can also be found on the SANE homepage.
42
45 The following sections provide short descriptions and links to more
46 information about several aspects of SANE. A name with a number in
47 parenthesis (e.g. `sane-dll(5)') points to a manual page. In this case
48 `man 5 sane-dll' will display the page. Entries like
49 `/usr/share/doc/sane-backends-1.0.22/sane.tex' are references to text
50 files that were copied to the SANE documentation directory
51 (/usr/share/doc/sane-backends-1.0.22/) during installation. Everything
52 else is a URL to a resource on the web.
53 SANE homepage
56 Information on all aspects of SANE including a tutorial and a link to
57 the SANE FAQ can be found on the SANE homepage:
58 http://www.sane-project.org/.
59 SANE device lists
61 The SANE device lists contain information about the status of SANE
62 support for a specific device. If your scanner is not listed there
63 (either supported or unsupported), please contact us. See section HOW
64 CAN YOU HELP SANE for details. There are lists for specific releases
65 of SANE, for the current development version and a search engine:
66 http://www.sane-project.org/sane-supported-devices.html. The lists
67 are also installed on your system at /usr/share/doc/sane-back‐
68 ends-1.0.22/.
69 SANE mailing list
71 There is a mailing list for the purpose of discussing the SANE stan‐
72 dard and its implementations: sane-devel. Despite its name, the list
73 is not only intended for developers, but also for users. There are
74 also some more lists for special topics, however, for users,
75 sane-devel is the right list. How to subscribe and unsubscribe:
76 http://www.sane-project.org/mailing-lists.html.
77 SANE IRC channel
79 The IRC (Internet Relay Chat) channel #sane can be found on the
80 Freenode network (irc.freenode.net). It's for discussing SANE prob‐
81 lems, talking about development and general SANE related chatting.
82 Before asking for help, please read the other documentation mentioned
83 in this manual page. The channel's topic is also used for announce‐
84 ments of problems with SANE infrastructure (mailing lists, web
85 server, etc.).
86 Compiling and installing SANE
88 Look at /usr/share/doc/sane-backends-1.0.22/README and the os-depen‐
89 dent README files for information about compiling and installing
90 SANE.
91 SCSI configuration
93 For information about various systems and SCSI controllers see
94 sane-scsi(5).
95 USB configuration
97 For information about USB configuration see sane-usb(5).
98
101 scanimage
102 Command-line frontend. See scanimage(1).
103 saned
105 SANE network daemon that allows remote clients to access image acqui‐
106 sition devices available on the local host. See saned(8).
107 sane-find-scanner
109 Command-line tool to find SCSI and USB scanners and determine their
110 Unix device files. See sane-find-scanner(1).
111 Also, have a look at the sane-frontends package (including xscanimage,
113 xcam, and scanadf) and the frontend information page at
114 http://www.sane-project.org/sane-frontends.html.
115
118 abaton
119 The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
120 (8bit, 256 levels of gray) and the Scan 300/S (black and white,
121 untested). See sane-abaton(5) for details.
122 agfafocus
124 This backend supports AGFA Focus scanners and the Siemens S9036
125 (untested). See sane-agfafocus(5) for details.
126 apple
128 The SANE backend for Apple flatbed scanners supports the following
129 scanners: AppleScanner, OneScanner and ColorOneScanner. See
130 sane-apple(5) for details.
131 artec
133 The SANE Artec backend supports several Artec/Ultima SCSI flatbed
134 scanners as well as the BlackWidow BW4800SP and the Plustek 19200S.
135 See sane-artec(5) for details.
136 artec_eplus48u
138 The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
139 re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
140 and Trust Easy Webscan 19200. See sane-artec_eplus48u(5) for details.
141 as6e
143 This is a SANE backend for using the Artec AS6E parallel port inter‐
144 face scanner. See sane-as6e(5) for details.
145 avision
147 This backend supports several Avision based scanners. This includes
148 the original Avision scanners (like AV 630, AV 620, ...) as well as
149 the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit‐
150 subishi and Minolta film-scanners. See sane-avision(5) for details.
151 bh
153 The bh backend provides access to Bell+Howell Copiscan II series doc‐
154 ument scanners. See sane-bh(5) for details.
155 canon
157 The canon backend supports the CanoScan 300, CanoScan 600, and
158 CanoScan 2700F SCSI flatbed scanners. See sane-canon(5) for details.
159 canon630u
161 The canon630u backend supports the CanoScan 630u and 636u USB scan‐
162 ners. See sane-canon630u(5) for details.
163 canon_dr
165 The canon_dr backend supports the Canon DR-Series ADF SCSI and USB
166 scanners. See sane-canon_dr(5) for details.
167 canon_pp
169 The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
170 N640P parallel port scanners. See sane-canon_pp(5) for details.
171 cardscan
173 This backend provides support for Corex Cardscan USB scanners. See
174 sane-cardscan(5) for details.
175 coolscan
177 This is a SANE backend for Nikon Coolscan film-scanners. See
178 sane-coolscan(5) for details.
179 coolscan2
181 This is a SANE backend for Nikon Coolscan film-scanners. See
182 sane-coolscan2(5) or http://coolscan2.sourceforge.net for details.
183 epjitsu
185 The epjitsu backend provides support for Epson-based Fujitsu USB
186 scanners. See sane-epjitsu(5) for details.
187 epson
189 The SANE epson backend provides support for Epson SCSI, parallel port
190 and USB flatbed scanners. See sane-epson(5) for details.
191 fujitsu
193 The fujitsu backend provides support for most Fujitsu SCSI and USB,
194 flatbed and adf scanners. See sane-fujitsu(5) for details.
195 genesys
197 The genesys backend provides support for scanners based on the
198 Genesys Logic GL646 and GL841 chips like the Medion 6471 and Hewlett-
199 Packard 2300c. Support for GL841 based scanners is far from being
200 complete. See sane-genesys(5) for details.
201 gt68xx
203 The gt68xx backend provides support for scanners based on the
204 Grandtech GT-6801 and GT-6816 chips like the Artec Ultima 2000 and
205 several Mustek BearPaw CU and TA models. Some Genius, Lexmark,
206 Medion, Packard Bell, Plustek, and Trust scanners are also supported.
207 See sane-gt68xx(5) for details.
208 hp
210 The SANE hp backend provides access to Hewlett-Packard ScanJet scan‐
211 ners which support SCL (Scanner Control Language by HP). See
212 sane-hp(5) for details.
213 hpsj5s
215 The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
216 sane-hpsj5s(5) for details.
217 hp3500
219 The SANE backend for the Hewlett-Packard ScanJet 3500 series. See
220 sane-hp3500(5) for details.
221 hp3900
223 The SANE backend for the Hewlett-Packard ScanJet 3900 series. See
224 sane-hp3900(5) for details.
225 hp4200
227 The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
228 sane-hp4200(5) for details.
229 hp5400
231 The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
232 sane-hp5400(5) for details.
233 hpljm1005
235 The SANE backend for the Hewlett-Packard LaserJet M1005 scanner. See
236 sane-hpljm1005(5) for details.
237 hs2p
239 The SANE backend for the Ricoh IS450 family of SCSI scanners. See
240 sane-hs2p(5) for details.
241 ibm
243 The SANE backend for some IBM and Ricoh SCSI scanners. See
244 sane-ibm(5) for details.
245 kodak
247 The SANE backend for some large Kodak scanners. See sane-kodak(5) for
248 details.
249 kvs1025
251 The SANE backend for Panasonic KV-S102xC scanners. See
252 sane-kvs1025(5) for details.
253 leo
255 This backend supports the Leo S3 and the Across FS-1130, which is a
256 re-badged LEO FS-1130 scanner. See sane-leo(5) for details.
257 lexmark
259 This backend supports the Lexmark X1100 series of USB scanners. See
260 sane-lexmark(5) for details.
261 ma1509
263 The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed
264 scanner. See sane-ma1509(5) for details.
265 magicolor
267 The magicolor backend supports the KONICA MINOLTA magicolor 1690MF
268 multi-function printer/scanner/fax. See sane-magicolor(5) for
269 details.
270 matsushita
272 This backend supports some Panasonic KVSS high speed scanners. See
273 sane-matsushita(5) for details.
274 microtek
276 The microtek backend provides access to the "second generation"
277 Microtek scanners with SCSI-1 command set. See sane-microtek(5) for
278 details.
279 microtek2
281 The microtek2 backend provides access to some Microtek scanners with
282 a SCSI-2 command set. See sane-microtek2(5) for details.
283 mustek
285 The SANE mustek backend supports most Mustek SCSI flatbed scanners
286 including the Paragon and ScanExpress series and the 600 II N and 600
287 II EP (non-SCSI). Some Trust scanners are also supported. See
288 sane-mustek(5) for details.
289 mustek_pp
291 The mustek_pp backend provides access to Mustek parallel port flatbed
292 scanners. See sane-mustek_pp(5) for details.
293 mustek_usb
295 The mustek_usb backend provides access to some Mustek ScanExpress USB
296 flatbed scanners. See sane-mustek_usb(5) for details.
297 mustek_usb2
299 The mustek_usb2 backend provides access to scanners using the SQ113
300 chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
301 sane-mustek_usb2(5) for details.
302 nec
304 The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
305 sane-nec(5) for details.
306 niash
308 The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
309 3300c, 3400c, and 4300c USB flatbed scanners. See sane-niash(5) for
310 details.
311 p5
313 The SANE backend for Primax PagePartner. See sane-p5(5) for details.
314 pie
316 The pie backend provides access to Pacific Image Electronics (PIE)
317 and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
318 pixma
320 The pixma backend supports Canon PIXMA MP series (multi-function
321 devices). See sane-pixma(5) or http://home.arcor.de/wittawat/pixma/
322 for details.
323 plustek
325 The SANE plustek backend supports USB flatbed scanners that use the
326 National Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners
327 using this LM983x chips include some models from Plustek, KYE/Genius,
328 Hewlett-Packard, Mustek, Umax, Epson, and Canon. See sane-plustek(5)
329 for details.
330 plustek_pp
332 The SANE plustek_pp backend supports Plustek parallel port flatbed
333 scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
334 P98003 include some models from Plustek, KYE/Genius, Primax. See
335 sane-plustek_pp(5) for details.
336 ricoh
338 The ricoh backend provides access to the following Ricoh flatbed
339 scanners: IS50 and IS60. See sane-ricoh(5) for details.
340 s9036
342 The s9036 backend provides access to Siemens 9036 flatbed scanners.
343 See sane-s9036(5) for details.
344 sceptre
346 The sceptre backend provides access to the Sceptre S1200 flatbed
347 scanner. See sane-sceptre(5) for details.
348 sharp
350 The SANE sharp backend supports Sharp SCSI scanners. See
351 sane-sharp(5) for details.
352 sm3600
354 The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
355 scanner. See sane-sm3600(5) for details.
356 sm3840
358 The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
359 scanner. See sane-sm3840(5) for details.
360 snapscan
362 The snapscan backend supports AGFA SnapScan flatbed scanners. See
363 sane-snapscan(5) for details.
364 sp15c
366 This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan‐
367 ner. See sane-sp15c(5) for details.
368 st400
370 The sane-st400 backend provides access to Siemens ST400 and ST800.
371 See sane-st400(5) for details.
372 tamarack
374 The SANE tamarack backend supports Tamarack Artiscan flatbed scan‐
375 ners. See sane-tamarack(5) for details.
376 teco1 teco2 teco3
378 The SANE teco1, teco2 and teco3 backends support some TECO scanners,
379 usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
380 See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
381 u12
383 The sane-u12 backend provides USB flatbed scanners based on Plustek's
384 ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
385 bridge chip like the Plustek OpticPro U(T)12. See sane-u12(5) for
386 details.
387 umax
389 The sane-umax backend provides access to several UMAX-SCSI-scanners
390 and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
391 umax_pp
393 The sane-umax_pp backend provides access to Umax parallel port
394 flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
395 umax1200u
397 The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
398 flatbed scanner (and also the UMAX Astra 2000U, sort of). See
399 sane-umax1220u(5) for details.
400 Also, have a look at the backend information page at
402 http://www.sane-project.org/sane-supported-devices.html and the list of
403 projects in /usr/share/doc/sane-backends-1.0.22/PROJECTS.
404
407 dc210
408 Backend for Kodak DC210 Digital Camera. See sane-dc210(5).
409 dc240
411 Backend for Kodak DC240 Digital Camera. See sane-dc240(5).
412 dc25
414 Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
415 dmc
417 Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5).
418 gphoto2
420 Backend for digital cameras supported by the gphoto2 library package.
421 (See http://www.gphoto.org for more information and a list of sup‐
422 ported cameras.) Gphoto2 supports over 140 different camera models.
423 However, please note that more development and testing is needed
424 before all of these cameras will be supported by SANE backend. See
425 sane-gphoto2(5).
426 qcam
428 Backend for Connectix QuickCam cameras. See sane-qcam(5).
429 stv680
431 The sane-st680 backend provides access to webcams with a stv680 chip.
432 See sane-st680(5) for details.
433 Also, have a look at the backend information page at
435 http://www.sane-project.org/sane-supported-devices.html and the list of
436 projects in /usr/share/doc/sane-backends-1.0.22/PROJECTS.
437
440 dll
441 The sane-dll library implements a SANE backend that provides access
442 to an arbitrary number of other SANE backends by dynamic loading. See
443 sane-dll(5).
444 net
446 The SANE network daemon saned provides access to scanners located on
447 different computers in connection with the net backend. See
448 sane-net(5) and saned(8).
449 pnm
451 PNM image reader pseudo-backend. The purpose of this backend is pri‐
452 marily to aid in debugging of SANE frontends. See sane-pnm(5).
453 pint
455 Backend for scanners that use the PINT (Pint Is Not Twain) device
456 driver. The PINT driver is being actively developed on the OpenBSD
457 platform, and has been ported to a few other *nix-like operating sys‐
458 tems. See sane-pint(5).
459 test
461 The SANE test backend is for testing frontends and the SANE installa‐
462 tion. It provides test pictures and various test options. See
463 sane-test(5).
464 v4l
466 The sane-v4l library implements a SANE backend that provides generic
467 access to video cameras and similar equipment using the V4L (Video
468 for Linux) API. See sane-v4l(5).
469 Also, have a look at the backend information page at
471 http://www.sane-project.org/sane-supported-devices.html and the list of
472 projects in /usr/share/doc/sane-backends-1.0.22/PROJECTS.
473
476 By default, all SANE backends (drivers) are loaded dynamically by the
477 sane-dll meta backend. If you have any questions about the dynamic
478 loading, read sane-dll(5). SANE frontend can also be linked to other
479 backends directly by copying or linking a backend to libsane.so in
480 /usr/lib64/sane.
481
483 It's not hard to write a SANE backend. It can take some time, however.
484 You should have basic knowledge of C and enough patience to work
485 through the documentation and find out how your scanner works. Appended
486 is a list of some documents that help to write backends and frontends.
487 The SANE standard defines the application programming interface (API)
489 that is used to communicate between frontends and backends. It can be
490 found at /usr/share/doc/sane-backends-1.0.22/sane.ps (if latex is
491 installed on your system) and on the SANE website:
492 http://www.sane-project.org/html/ (HTML), or
493 http://www.sane-project.org/sane.ps (Postscript).
494 There is some more information for programmers in /usr/share/doc/sane-
496 backends-1.0.22/backend-writing.txt. Most of the internal SANE rou‐
497 tines (sanei) are documented using doxygen:
498 http://www.sane-project.org/sanei/. Before a new backend or frontend
499 project is started, have a look at /usr/share/doc/sane-back‐
500 ends-1.0.22/PROJECTS for projects that are planned or not yet included
501 into the SANE distribution and at our bug-tracking system:
502 http://www.http://www.sane-project.org/bugs.html.
503 There are some links on how to find out about the protocol of a scan‐
505 ner: http://www.meier-geinitz.de/sane/misc/develop.html.
506 If you start writing a backend or frontend or any other part of SANE,
509 please contact the sane-devel mailing list for coordination so the same
510 work isn't done twice.
511
514 /etc/sane.d/*.conf
515 The backend configuration files.
516 /usr/lib64/sane/libsane-*.a
518 The static libraries implementing the backends.
519 /usr/lib64/sane/libsane-*.so
521 The shared libraries implementing the backends (present on sys‐
522 tems that support dynamic loading).
523 /usr/share/doc/sane-backends-1.0.22/*
525 SANE documentation: The standard, READMEs, text files for back‐
526 ends etc.
527
530 If your device isn't found but you know that it is supported, make sure
531 that it is detected by your operating system. For SCSI and USB scan‐
532 ners, use the sane-find-scanner tool (see sane-find-scanner(1) for
533 details). It prints one line for each scanner it has detected and some
534 comments (#). If sane-find-scanner finds your scanner only as root but
535 not as normal user, the permissions for the device files are not
536 adjusted correctly. If the scanner isn't found at all, the operating
537 system hasn't detected it and may need some help. Depending on the type
538 of your scanner, read sane-usb(5) or sane-scsi(5). If your scanner (or
539 other device) is not connected over the SCSI bus or USB, read the back‐
540 end's manual page for details on how to set it up.
541 Now your scanner is detected by the operating system but not by SANE?
543 Try scanimage -L. If the scanner is not found, check that the back‐
544 end's name is mentioned in /etc/sane.d/dll.conf. Some backends are
545 commented out by default. Remove the comment sign for your backend in
546 this case. Also some backends aren't compiled at all if one of their
547 prerequisites are missing. Examples include dc210, dc240, canon_pp,
548 hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you
549 need one of these backends and they aren't available, read the build
550 instructions in the README file and the individual manual pages of the
551 backends.
552 Another reason for not being detected by scanimage -L may be a missing
554 or wrong configuration in the backend's configuration file. While SANE
555 tries to automatically find most scanners, some can't be setup cor‐
556 rectly without the intervention of the administrator. Also on some
557 operating systems auto-detection may not work. Check the backend's man‐
558 ual page for details.
559 If your scanner is still not found, try setting the various environment
561 variables that are available to assist in debugging. The environment
562 variables are documented in the relevant manual pages. For example, to
563 get the maximum amount of debug information when testing a Mustek SCSI
564 scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
565 and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L . The
566 debug messages for the dll backend tell if the mustek backend was found
567 and loaded at all. The mustek messages explain what the mustek backend
568 is doing while the SCSI debugging shows the low level handling. If you
569 can't find out what's going on by checking the messages carefully, con‐
570 tact the sane-devel mailing list for help (see REPORTING BUGS below).
571 Now that your scanner is found by scanimage -L, try to do a scan: scan‐
573 image >image.pnm. This command starts a scan for the default scanner
574 with default settings. All the available options are listed by running
575 scanimage --help. If scanning aborts with an error message, turn on
576 debugging as mentioned above. Maybe the configuration file needs some
577 tuning, e.g. to setup the path to a firmware that is needed by some
578 scanners. See the backend's manual page for details. If you can't find
579 out what's wrong, contact sane-devel.
580 To check that the SANE libraries are installed correctly you can use
582 the test backend, even if you don't have a scanner or other SANE
583 device:
584 scanimage -d test -T
586 You should get a list of PASSed tests. You can do the same with your
588 backend by changing "test" to your backend's name.
589 So now scanning with scanimage works and you want to use one of the
591 graphical frontends like xsane, xscanimage, or quiteinsane but those
592 frontends don't detect your scanner? One reason may be that you
593 installed two versions of SANE. E.g. the version that was installed by
594 your distribution in /usr and one you installed from source in
595 /usr/local/. Make sure that only one version is installed. Another
596 possible reason is, that your system's dynamic loader can't find the
597 SANE libraries. For Linux, make sure that /etc/ld.so.conf contains
598 /usr/local/lib and does not contain /usr/local/lib/sane. See also the
599 documentation of the frontends.
600
602 We appreciate any help we can get. Please have a look at our web page
603 about contributing to SANE: http://www.sane-project.org/contrib.html
604
606 For reporting bugs or requesting new features, please use our bug-
607 tracking system: http://www.sane-project.org/bugs.html. You can also
608 contact the author of your backend directly. Usually the email address
609 can be found in the /usr/share/doc/sane-backends-1.0.22/AUTHORS file or
610 the backend's manpage. For general discussion about SANE, please use
611 the SANE mailing list sane-devel (see http://www.sane-project.org/mail‐
612 ing-lists.html for details).
613
615 saned(8), sane-find-scanner(1), scanimage(1), sane-abaton(5),
616 sane-agfafocus(5), sane-apple(5), sane-artec(5),
617 sane-artec_eplus48u(5), sane-as6e(5), sane-avision(5), sane-bh(5),
618 sane-canon(5), sane-canon630u(5), sane-canon_dr(5), sane-canon_pp(5),
619 sane-cardscan(5), sane-coolscan2(5), sane-coolscan(5), sane-dc210(5),
620 sane-dc240(5), sane-dc25(5), sane-dll(5), sane-dmc(5), sane-epson(5),
621 sane-fujitsu(5), sane-genesys(5), sane-gphoto2(5), sane-gt68xx(5),
622 sane-hp(5), sane-hpsj5s(5), sane-hp3500(5), sane-hp3900(5),
623 sane-hp4200(5), sane-hp5400(5), sane-hpljm1005(5), sane-ibm(5),
624 sane-kodak(5), sane-leo(5), sane-lexmark(5), sane-ma1509(5), sane-mat‐
625 sushita(5), sane-microtek2(5), sane-microtek(5), sane-mustek(5),
626 sane-mustek_pp(5), sane-mustek_usb(5), sane-mustek_usb2(5),
627 sane-nec(5), sane-net(5), sane-niash(5), sane-pie(5), sane-pint(5),
628 sane-plustek(5), sane-plustek_pp(5), sane-pnm(5), sane-qcam(5),
629 sane-ricoh(5), sane-s9036(5), sane-sceptre(5), sane-scsi(5),
630 sane-sharp(5), sane-sm3600(5), sane-sm3840(5), sane-snapscan(5),
631 sane-sp15c(5), sane-st400(5), sane-stv680(5), sane-tamarack(5),
632 sane-teco1(5), sane-teco2(5), sane-teco3(5), sane-test(5), sane-u12(5),
633 sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane-usb(5),
634 sane-v4l(5)
635
638 David Mosberger-Tang and many many more (see /usr/share/doc/sane-back‐
639 ends-1.0.22/AUTHORS for details). This man page was written by Henning
640 Meier-Geinitz. Quite a lot of text was taken from the SANE standard,
641 several man pages, and README files.
642 14 Jul 2008 sane(7)