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.21/sane.tex' are references to text
50 files that were copied to the SANE documentation directory
51 (/usr/share/doc/sane-backends-1.0.21/) 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.21/.
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.21/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 matsushita
267 This backend supports some Panasonic KVSS high speed scanners. See
268 sane-matsushita(5) for details.
269 microtek
271 The microtek backend provides access to the "second generation"
272 Microtek scanners with SCSI-1 command set. See sane-microtek(5) for
273 details.
274 microtek2
276 The microtek2 backend provides access to some Microtek scanners with
277 a SCSI-2 command set. See sane-microtek2(5) for details.
278 mustek
280 The SANE mustek backend supports most Mustek SCSI flatbed scanners
281 including the Paragon and ScanExpress series and the 600 II N and 600
282 II EP (non-SCSI). Some Trust scanners are also supported. See
283 sane-mustek(5) for details.
284 mustek_pp
286 The mustek_pp backend provides access to Mustek parallel port flatbed
287 scanners. See sane-mustek_pp(5) for details.
288 mustek_usb
290 The mustek_usb backend provides access to some Mustek ScanExpress USB
291 flatbed scanners. See sane-mustek_usb(5) for details.
292 mustek_usb2
294 The mustek_usb2 backend provides access to scanners using the SQ113
295 chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
296 sane-mustek_usb2(5) for details.
297 nec
299 The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
300 sane-nec(5) for details.
301 niash
303 The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
304 3300c, 3400c, and 4300c USB flatbed scanners. See sane-niash(5) for
305 details.
306 p5
308 The SANE backend for Primax PagePartner. See sane-p5(5) for details.
309 pie
311 The pie backend provides access to Pacific Image Electronics (PIE)
312 and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
313 pixma
315 The pixma backend supports Canon PIXMA MP series (multi-function
316 devices). See sane-pixma(5) or http://home.arcor.de/wittawat/pixma/
317 for details.
318 plustek
320 The SANE plustek backend supports USB flatbed scanners that use the
321 National Semiconductor LM983[1/2/3]-chipset aka Merlin. Scanners
322 using this LM983x chips include some models from Plustek, KYE/Genius,
323 Hewlett-Packard, Mustek, Umax, Epson, and Canon. See sane-plustek(5)
324 for details.
325 plustek_pp
327 The SANE plustek_pp backend supports Plustek parallel port flatbed
328 scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and
329 P98003 include some models from Plustek, KYE/Genius, Primax. See
330 sane-plustek_pp(5) for details.
331 ricoh
333 The ricoh backend provides access to the following Ricoh flatbed
334 scanners: IS50 and IS60. See sane-ricoh(5) for details.
335 s9036
337 The s9036 backend provides access to Siemens 9036 flatbed scanners.
338 See sane-s9036(5) for details.
339 sceptre
341 The sceptre backend provides access to the Sceptre S1200 flatbed
342 scanner. See sane-sceptre(5) for details.
343 sharp
345 The SANE sharp backend supports Sharp SCSI scanners. See
346 sane-sharp(5) for details.
347 sm3600
349 The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
350 scanner. See sane-sm3600(5) for details.
351 sm3840
353 The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB
354 scanner. See sane-sm3840(5) for details.
355 snapscan
357 The snapscan backend supports AGFA SnapScan flatbed scanners. See
358 sane-snapscan(5) for details.
359 sp15c
361 This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan‐
362 ner. See sane-sp15c(5) for details.
363 st400
365 The sane-st400 backend provides access to Siemens ST400 and ST800.
366 See sane-st400(5) for details.
367 tamarack
369 The SANE tamarack backend supports Tamarack Artiscan flatbed scan‐
370 ners. See sane-tamarack(5) for details.
371 teco1 teco2 teco3
373 The SANE teco1, teco2 and teco3 backends support some TECO scanners,
374 usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
375 See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
376 u12
378 The sane-u12 backend provides USB flatbed scanners based on Plustek's
379 ASIC 98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport
380 bridge chip like the Plustek OpticPro U(T)12. See sane-u12(5) for
381 details.
382 umax
384 The sane-umax backend provides access to several UMAX-SCSI-scanners
385 and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
386 umax_pp
388 The sane-umax_pp backend provides access to Umax parallel port
389 flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
390 umax1200u
392 The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
393 flatbed scanner (and also the UMAX Astra 2000U, sort of). See
394 sane-umax1220u(5) for details.
395 Also, have a look at the backend information page at
397 http://www.sane-project.org/sane-supported-devices.html and the list of
398 projects in /usr/share/doc/sane-backends-1.0.21/PROJECTS.
399
402 dc210
403 Backend for Kodak DC210 Digital Camera. See sane-dc210(5).
404 dc240
406 Backend for Kodak DC240 Digital Camera. See sane-dc240(5).
407 dc25
409 Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
410 dmc
412 Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5).
413 gphoto2
415 Backend for digital cameras supported by the gphoto2 library package.
416 (See http://www.gphoto.org for more information and a list of sup‐
417 ported cameras.) Gphoto2 supports over 140 different camera models.
418 However, please note that more development and testing is needed
419 before all of these cameras will be supported by SANE backend. See
420 sane-gphoto2(5).
421 qcam
423 Backend for Connectix QuickCam cameras. See sane-qcam(5).
424 stv680
426 The sane-st680 backend provides access to webcams with a stv680 chip.
427 See sane-st680(5) for details.
428 Also, have a look at the backend information page at
430 http://www.sane-project.org/sane-supported-devices.html and the list of
431 projects in /usr/share/doc/sane-backends-1.0.21/PROJECTS.
432
435 dll
436 The sane-dll library implements a SANE backend that provides access
437 to an arbitrary number of other SANE backends by dynamic loading. See
438 sane-dll(5).
439 net
441 The SANE network daemon saned provides access to scanners located on
442 different computers in connection with the net backend. See
443 sane-net(5) and saned(8).
444 pnm
446 PNM image reader pseudo-backend. The purpose of this backend is pri‐
447 marily to aid in debugging of SANE frontends. See sane-pnm(5).
448 pint
450 Backend for scanners that use the PINT (Pint Is Not Twain) device
451 driver. The PINT driver is being actively developed on the OpenBSD
452 platform, and has been ported to a few other *nix-like operating sys‐
453 tems. See sane-pint(5).
454 test
456 The SANE test backend is for testing frontends and the SANE installa‐
457 tion. It provides test pictures and various test options. See
458 sane-test(5).
459 v4l
461 The sane-v4l library implements a SANE backend that provides generic
462 access to video cameras and similar equipment using the V4L (Video
463 for Linux) API. See sane-v4l(5).
464 Also, have a look at the backend information page at
466 http://www.sane-project.org/sane-supported-devices.html and the list of
467 projects in /usr/share/doc/sane-backends-1.0.21/PROJECTS.
468
471 By default, all SANE backends (drivers) are loaded dynamically by the
472 sane-dll meta backend. If you have any questions about the dynamic
473 loading, read sane-dll(5). SANE frontend can also be linked to other
474 backends directly by copying or linking a backend to libsane.so in
475 /usr/lib64/sane.
476
478 It's not hard to write a SANE backend. It can take some time, however.
479 You should have basic knowledge of C and enough patience to work
480 through the documentation and find out how your scanner works. Appended
481 is a list of some documents that help to write backends and frontends.
482 The SANE standard defines the application programming interface (API)
484 that is used to communicate between frontends and backends. It can be
485 found at /usr/share/doc/sane-backends-1.0.21/sane.ps (if latex is
486 installed on your system) and on the SANE website:
487 http://www.sane-project.org/html/ (HTML), or
488 http://www.sane-project.org/sane.ps (Postscript).
489 There is some more information for programmers in /usr/share/doc/sane-
491 backends-1.0.21/backend-writing.txt. Most of the internal SANE rou‐
492 tines (sanei) are documented using doxygen:
493 http://www.sane-project.org/sanei/. Before a new backend or frontend
494 project is started, have a look at /usr/share/doc/sane-back‐
495 ends-1.0.21/PROJECTS for projects that are planned or not yet included
496 into the SANE distribution and at our bug-tracking system:
497 http://www.http://www.sane-project.org/bugs.html.
498 There are some links on how to find out about the protocol of a scan‐
500 ner: http://www.meier-geinitz.de/sane/misc/develop.html.
501 If you start writing a backend or frontend or any other part of SANE,
504 please contact the sane-devel mailing list for coordination so the same
505 work isn't done twice.
506
509 /etc/sane.d/*.conf
510 The backend configuration files.
511 /usr/lib64/sane/libsane-*.a
513 The static libraries implementing the backends.
514 /usr/lib64/sane/libsane-*.so
516 The shared libraries implementing the backends (present on sys‐
517 tems that support dynamic loading).
518 /usr/share/doc/sane-backends-1.0.21/*
520 SANE documentation: The standard, READMEs, text files for back‐
521 ends etc.
522
525 If your device isn't found but you know that it is supported, make sure
526 that it is detected by your operating system. For SCSI and USB scan‐
527 ners, use the sane-find-scanner tool (see sane-find-scanner(1) for
528 details). It prints one line for each scanner it has detected and some
529 comments (#). If sane-find-scanner finds your scanner only as root but
530 not as normal user, the permissions for the device files are not
531 adjusted correctly. If the scanner isn't found at all, the operating
532 system hasn't detected it and may need some help. Depending on the type
533 of your scanner, read sane-usb(5) or sane-scsi(5). If your scanner (or
534 other device) is not connected over the SCSI bus or USB, read the back‐
535 end's manual page for details on how to set it up.
536 Now your scanner is detected by the operating system but not by SANE?
538 Try scanimage -L. If the scanner is not found, check that the back‐
539 end's name is mentioned in /etc/sane.d/dll.conf. Some backends are
540 commented out by default. Remove the comment sign for your backend in
541 this case. Also some backends aren't compiled at all if one of their
542 prerequisites are missing. Examples include dc210, dc240, canon_pp,
543 hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm. If you
544 need one of these backends and they aren't available, read the build
545 instructions in the README file and the individual manual pages of the
546 backends.
547 Another reason for not being detected by scanimage -L may be a missing
549 or wrong configuration in the backend's configuration file. While SANE
550 tries to automatically find most scanners, some can't be setup cor‐
551 rectly without the intervention of the administrator. Also on some
552 operating systems auto-detection may not work. Check the backend's man‐
553 ual page for details.
554 If your scanner is still not found, try setting the various environment
556 variables that are available to assist in debugging. The environment
557 variables are documented in the relevant manual pages. For example, to
558 get the maximum amount of debug information when testing a Mustek SCSI
559 scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
560 and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L . The
561 debug messages for the dll backend tell if the mustek backend was found
562 and loaded at all. The mustek messages explain what the mustek backend
563 is doing while the SCSI debugging shows the low level handling. If you
564 can't find out what's going on by checking the messages carefully, con‐
565 tact the sane-devel mailing list for help (see REPORTING BUGS below).
566 Now that your scanner is found by scanimage -L, try to do a scan: scan‐
568 image >image.pnm. This command starts a scan for the default scanner
569 with default settings. All the available options are listed by running
570 scanimage --help. If scanning aborts with an error message, turn on
571 debugging as mentioned above. Maybe the configuration file needs some
572 tuning, e.g. to setup the path to a firmware that is needed by some
573 scanners. See the backend's manual page for details. If you can't find
574 out what's wrong, contact sane-devel.
575 To check that the SANE libraries are installed correctly you can use
577 the test backend, even if you don't have a scanner or other SANE
578 device:
579 scanimage -d test -T
581 You should get a list of PASSed tests. You can do the same with your
583 backend by changing "test" to your backend's name.
584 So now scanning with scanimage works and you want to use one of the
586 graphical frontends like xsane, xscanimage, or quiteinsane but those
587 frontends don't detect your scanner? One reason may be that you
588 installed two versions of SANE. E.g. the version that was installed by
589 your distribution in /usr and one you installed from source in
590 /usr/local/. Make sure that only one version is installed. Another
591 possible reason is, that your system's dynamic loader can't find the
592 SANE libraries. For Linux, make sure that /etc/ld.so.conf contains
593 /usr/local/lib and does not contain /usr/local/lib/sane. See also the
594 documentation of the frontends.
595
597 We appreciate any help we can get. Please have a look at our web page
598 about contributing to SANE: http://www.sane-project.org/contrib.html
599
601 For reporting bugs or requesting new features, please use our bug-
602 tracking system: http://www.sane-project.org/bugs.html. You can also
603 contact the author of your backend directly. Usually the email address
604 can be found in the /usr/share/doc/sane-backends-1.0.21/AUTHORS file or
605 the backend's manpage. For general discussion about SANE, please use
606 the SANE mailing list sane-devel (see http://www.sane-project.org/mail‐
607 ing-lists.html for details).
608
610 saned(8), sane-find-scanner(1), scanimage(1), sane-abaton(5),
611 sane-agfafocus(5), sane-apple(5), sane-artec(5),
612 sane-artec_eplus48u(5), sane-as6e(5), sane-avision(5), sane-bh(5),
613 sane-canon(5), sane-canon630u(5), sane-canon_dr(5), sane-canon_pp(5),
614 sane-cardscan(5), sane-coolscan2(5), sane-coolscan(5), sane-dc210(5),
615 sane-dc240(5), sane-dc25(5), sane-dll(5), sane-dmc(5), sane-epson(5),
616 sane-fujitsu(5), sane-genesys(5), sane-gphoto2(5), sane-gt68xx(5),
617 sane-hp(5), sane-hpsj5s(5), sane-hp3500(5), sane-hp3900(5),
618 sane-hp4200(5), sane-hp5400(5), sane-hpljm1005(5), sane-ibm(5),
619 sane-kodak(5), sane-leo(5), sane-lexmark(5), sane-ma1509(5), sane-mat‐
620 sushita(5), sane-microtek2(5), sane-microtek(5), sane-mustek(5),
621 sane-mustek_pp(5), sane-mustek_usb(5), sane-mustek_usb2(5),
622 sane-nec(5), sane-net(5), sane-niash(5), sane-pie(5), sane-pint(5),
623 sane-plustek(5), sane-plustek_pp(5), sane-pnm(5), sane-qcam(5),
624 sane-ricoh(5), sane-s9036(5), sane-sceptre(5), sane-scsi(5),
625 sane-sharp(5), sane-sm3600(5), sane-sm3840(5), sane-snapscan(5),
626 sane-sp15c(5), sane-st400(5), sane-stv680(5), sane-tamarack(5),
627 sane-teco1(5), sane-teco2(5), sane-teco3(5), sane-test(5), sane-u12(5),
628 sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane-usb(5),
629 sane-v4l(5)
630
633 David Mosberger-Tang and many many more (see /usr/share/doc/sane-back‐
634 ends-1.0.21/AUTHORS for details). This man page was written by Henning
635 Meier-Geinitz. Quite a lot of text was taken from the SANE standard,
636 several man pages, and README files.
637 14 Jul 2008 sane(7)