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 backends, documentation, networking
36 support, and the command line frontend scanimage(1). The frontends xs‐
37 canimage(1), xcam(1), and scanadf(1) are included in the package
38 sane-frontends. Both packages can be downloaded from the SANE homepage
39 (http://www.sane-project.org/). Information about other frontends and
40 backends can also be found on the SANE homepage.
41
44 The following sections provide short descriptions and links to more in‐
45 formation about several aspects of SANE. A name with a number in
46 parenthesis (e.g. sane-dll(5)) points to a manual page. In this case
47 man 5 sane-dll will display the page. Entries like /usr/share/doc/sane-
48 backends/README are references to text files that were copied to the
49 SANE documentation directory (/usr/share/doc/sane-backends/) during in‐
50 stallation. Everything else is a URL to a resource on the web.
51 SANE homepage
54 Information on all aspects of SANE including a tutorial and a link to
55 the SANE FAQ can be found on the SANE homepage:
56 http://www.sane-project.org/.
57 SANE device lists
59 The SANE device lists contain information about the status of SANE
60 support for a specific device. If your scanner is not listed there
61 (either supported or unsupported), please contact us. See section HOW
62 CAN YOU HELP SANE for details. There are lists for specific releases
63 of SANE, for the current development version and a search engine:
64 http://www.sane-project.org/sane-supported-devices.html. The lists
65 are also installed on your system at /usr/share/doc/sane-backends/.
66 SANE mailing list
68 There is a mailing list for the purpose of discussing the SANE stan‐
69 dard and its implementations: sane-devel. Despite its name, the list
70 is not only intended for developers, but also for users. There are
71 also some more lists for special topics. However, for users, sane-de‐
72 vel is the right list. How to subscribe and unsubscribe:
73 http://www.sane-project.org/mailing-lists.html.
74 SANE IRC channel
76 The IRC (Internet Relay Chat) channel #sane can be found on the
77 Freenode network (irc.libera.chat). It's for discussing SANE prob‐
78 lems, talking about development and general SANE related chatting.
79 Before asking for help, please read the other documentation mentioned
80 in this manual page. The channel's topic is also used for announce‐
81 ments of problems with SANE infrastructure (mailing lists, web
82 server, etc.).
83 Compiling and installing SANE
85 Look at /usr/share/doc/sane-backends/README and the os-dependent
86 README files for information about compiling and installing SANE.
87 SCSI configuration
89 For information about various systems and SCSI controllers see
90 sane-scsi(5).
91 USB configuration
93 For information about USB configuration see sane-usb(5).
94
97 scanimage
98 Command-line frontend. See scanimage(1).
99 saned
101 SANE network daemon that allows remote clients to access image acqui‐
102 sition devices available on the local host. See saned(8).
103 sane-find-scanner
105 Command-line tool to find SCSI and USB scanners and determine their
106 UNIX device files. See sane-find-scanner(1).
107 Also, have a look at the sane-frontends package (which includes xscan‐
109 image(1), xcam(1), and scanadf(1)) and the frontend information page at
110 http://www.sane-project.org/sane-frontends.html.
111
114 abaton
115 Supports Abaton flatbed scanners such as the Scan 300/GS (8bit, 256
116 levels of gray) and the Scan 300/S (black and white, untested). See
117 sane-abaton(5) for details.
118 agfafocus
120 Supports AGFA Focus scanners and the Siemens S9036 (untested). See
121 sane-agfafocus(5) for details.
122 apple
124 Supports Apple flatbed scanners including the following scanners: Ap‐
125 pleScanner, OneScanner and ColorOneScanner. See sane-apple(5) for de‐
126 tails.
127 artec
129 Supports several Artec/Ultima SCSI flatbed scanners as well as the
130 BlackWidow BW4800SP and the Plustek 19200S. See sane-artec(5) for de‐
131 tails.
132 artec_eplus48u
134 Supports the Artec E+ 48U scanner and re-badged models like Tevion MD
135 9693, Medion MD 9693, Medion MD 9705 and Trust Easy Webscan 19200.
136 See sane-artec_eplus48u(5) for details.
137 as6e
139 Supports the Artec AS6E parallel port interface scanner. See
140 sane-as6e(5) for details.
141 avision
143 Supports several Avision based scanners including the original Avi‐
144 sion scanners (like AV 630, AV 620, ...) as well as the HP ScanJet
145 53xx and 74xx series, Fujitsu ScanPartner, some Mitsubishi and Mi‐
146 nolta film-scanners. See sane-avision(5) for details.
147 bh
149 Supports Bell+Howell Copiscan II series document scanners. See
150 sane-bh(5) for details.
151 canon
153 Supports the CanoScan 300, CanoScan 600, and CanoScan 2700F SCSI
154 flatbed scanners. See sane-canon(5) for details.
155 canon630u
157 Supports the CanoScan 630u and 636u USB scanners. See
158 sane-canon630u(5) for details.
159 canon_dr
161 Supports the Canon DR-Series ADF SCSI and USB scanners. See
162 sane-canon_dr(5) for details.
163 canon_lide70
165 Supports the CanoScan LiDE 70 and 600 USB scanners. See
166 sane-canon_lide70(5) for details.
167 canon_pp
169 Supports the CanoScan FB330P, FB630P, N340P and N640P parallel port
170 scanners. See sane-canon_pp(5) for details.
171 cardscan
173 Support for Corex Cardscan USB scanners. See sane-cardscan(5) for de‐
174 tails.
175 coolscan coolscan2 coolscan3
177 Supports Nikon Coolscan film-scanners. See sane-coolscan(5),
178 sane-coolscan2(5) and sane-coolscan3(5) for details.
179 epjitsu
181 Supports Epson-based Fujitsu USB scanners. See sane-epjitsu(5) for
182 details.
183 epson
185 Old driver for Epson SCSI, parallel port and USB flatbed scanners.
186 See sane-epson(5) for details but try epson2 first.
187 epson2
189 Newer driver for Epson SCSI, parallel port, network and USB flatbed
190 scanners (try this before epson which is outdated). See sane-ep‐
191 son2(5) for details.
192 escl
194 Supports scanners through the eSCL protocol. See sane-escl(5) for de‐
195 tails.
196 fujitsu
198 Supports most Fujitsu SCSI and USB, flatbed and adf scanners. See
199 sane-fujitsu(5) for details.
200 genesys
202 Supports several scanners based on the Genesys Logic GL646, GL841,
203 GL843, GL847 and GL124 chips like the Medion 6471 and Hewlett-Packard
204 2300c. See sane-genesys(5) for details.
205 gt68xx
207 Supports scanners based on the Grandtech GT-6801 and GT-6816 chips
208 like the Artec Ultima 2000 and several Mustek BearPaw CU and TA mod‐
209 els.
210 Some Genius, Lexmark, Medion, Packard Bell, Plustek, and Trust scan‐
211 ners are also supported. See sane-gt68xx(5) for details.
212 hp
214 Supports Hewlett-Packard ScanJet scanners which utilize SCL (Scanner
215 Control Language by HP). See sane-hp(5) for details.
216 hpsj5s
218 Supports the Hewlett-Packard ScanJet 5S scanner. See sane-hpsj5s(5)
219 for details.
220 hp3500
222 Supports the Hewlett-Packard ScanJet 3500 series. See sane-hp3500(5)
223 for details.
224 hp3900
226 Supports the Hewlett-Packard ScanJet 3900 series. See sane-hp3900(5)
227 for details.
228 hp4200
230 Supports the Hewlett-Packard ScanJet 4200 series. See sane-hp4200(5)
231 for details.
232 hp5400
234 Supports the Hewlett-Packard ScanJet 54XXC series. See sane-hp5400(5)
235 for details.
236 hpljm1005
238 Supports the Hewlett-Packard LaserJet M1005 scanner. See
239 sane-hpljm1005(5) for details.
240 hs2p
242 Supports the Ricoh IS450 family of SCSI scanners. See sane-hs2p(5)
243 for details.
244 ibm
246 Supports some IBM and Ricoh SCSI scanners. See sane-ibm(5) for de‐
247 tails.
248 kodak
250 Supports some large Kodak scanners. See sane-kodak(5) for details.
251 kodakaio
253 Supports Kodak AiO printer/scanners. See sane-kodakaio(5) for de‐
254 tails.
255 kvs1025
257 Supports Panasonic KV-S102xC scanners. See sane-kvs1025(5) for de‐
258 tails.
259 leo
261 Supports the LEO S3 and the Across FS-1130, which is a re-badged LEO
262 FS-1130 scanner. See sane-leo(5) for details.
263 lexmark
265 Supports the Lexmark X1100 series of USB scanners. See sane-lex‐
266 mark(5) for details.
267 ma1509
269 Supports the Mustek BearPaw 1200F USB flatbed scanner. See
270 sane-ma1509(5) for details.
271 magicolor
273 Supports the KONICA MINOLTA magicolor 1690MF multi-function
274 printer/scanner/fax. See sane-magicolor(5) for details.
275 matsushita
277 Supports some Panasonic KVSS high speed scanners. See sane-mat‐
278 sushita(5) for details.
279 microtek
281 Supports "second generation" Microtek scanners with SCSI-1 command
282 set. See sane-microtek(5) for details.
283 microtek2
285 Supports some Microtek scanners with a SCSI-2 command set. See
286 sane-microtek2(5) for details.
287 mustek
289 Supports most Mustek SCSI flatbed scanners including the Paragon and
290 ScanExpress series and the 600 II N and 600 II EP (non-SCSI). Some
291 Trust scanners are also supported. See sane-mustek(5) for details.
292 mustek_pp
294 Supports Mustek parallel port flatbed scanners. See sane-mustek_pp(5)
295 for details.
296 mustek_usb
298 Supports some Mustek ScanExpress USB flatbed scanners. See
299 sane-mustek_usb(5) for details.
300 mustek_usb2
302 Supports scanners using the SQ113 chipset like the Mustek BearPaw
303 2448 TA Pro USB flatbed scanner. See sane-mustek_usb2(5) for details.
304 nec
306 Supports the NEC PC-IN500/4C SCSI scanner. See sane-nec(5) for de‐
307 tails.
308 niash
310 Supports the Agfa Snapscan Touch and the HP ScanJet 3300c, 3400c, and
311 4300c USB flatbed scanners. See sane-niash(5) for details.
312 p5
314 Supports the Primax PagePartner. See sane-p5(5) for details.
315 pie
317 Supports Pacific Image Electronics (PIE) and Devcom SCSI flatbed
318 scanners. See sane-pie(5) for details.
319 pixma
321 Supports Canon PIXMA MP series (multi-function devices), Canon image‐
322 CLASS series (laser devices), Canon MAXIFY series and some Canon
323 CanoScan series. See sane-pixma(5) for details.
324 plustek
326 Supports USB flatbed scanners that use the National Semiconductor
327 LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x chips in‐
328 clude some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek,
329 Umax, Epson, and Canon. See sane-plustek(5) for details.
330 plustek_pp
332 Supports Plustek parallel port flatbed scanners using the Plustek
333 ASIC P96001, P96003, P98001 and P98003, which includes some models
334 from Plustek, KYE/Genius, Primax. See sane-plustek_pp(5) for details.
335 ricoh
337 Supports the Ricoh flatbed scanners IS50 and IS60. See sane-ricoh(5)
338 for details.
339 ricoh2
341 Supports the Ricoh flatbed scanners: SG-3100SNw, SP-100SU, and
342 SP-111SU. See sane-ricoh2(5) for details.
343 s9036
345 Supports Siemens 9036 flatbed scanners. See sane-s9036(5) for de‐
346 tails.
347 sceptre
349 Supports the Sceptre S1200 flatbed scanner. See sane-sceptre(5) for
350 details.
351 sharp
353 Supports Sharp SCSI scanners. See sane-sharp(5) for details.
354 sm3600
356 Supports the Microtek ScanMaker 3600 USB scanner. See sane-sm3600(5)
357 for details.
358 sm3840
360 Supports the Microtek ScanMaker 3840 USB scanner. See sane-sm3840(5)
361 for details.
362 snapscan
364 Supports AGFA SnapScan flatbed scanners including some which are re‐
365 badged to other brands. See sane-snapscan(5) for details.
366 sp15c
368 Supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See
369 sane-sp15c(5) for details.
370 st400
372 Supports the Siemens ST400 and ST800. See sane-st400(5) for details.
373 tamarack
375 Supports Tamarack Artiscan flatbed scanners. See sane-tamarack(5) for
376 details.
377 teco1 teco2 teco3
379 Supports some TECO scanners, usually sold under the Relisys, Trust,
380 Primax, Piotech, Dextra names. See sane-teco1(5), sane-teco2(5) and
381 sane-teco3(5) for details.
382 u12
384 Supports USB flatbed scanners based on Plustek's ASIC 98003 (paral‐
385 lel-port ASIC) and a GeneSys Logics' USB-parport bridge chip like the
386 Plustek OpticPro U(T)12. See sane-u12(5) for details.
387 umax
389 Supports UMAX-SCSI-scanners and some Linotype Hell SCSI-scanners. See
390 sane-umax(5) for details.
391 umax_pp
393 Supports Umax parallel port flatbed scanners and the HP 3200C. See
394 sane-umax_pp(5) for details.
395 umax1200u
397 Supports the UMAX Astra 1220U (USB) flatbed scanner (and also the
398 UMAX Astra 2000U, sort of). See sane-umax1220u(5) for details.
399 xerox_mfp
401 Supports multiple Samsung-based Samsung, Xerox, and Dell scanners.
402 See sane-xerox_mfp(5) for details.
403 Also, have a look at the backend information page at
405 http://www.sane-project.org/sane-supported-devices.html and the list of
406 projects in /usr/share/doc/sane-backends/PROJECTS.
407
410 dc210
411 Supports the Kodak DC210 Digital Camera. See sane-dc210(5).
412 dc240
414 Supports the Kodak DC240 Digital Camera. See dc240(5).
415 dc25
417 Supports Kodak DC20/DC25 Digital Cameras. See dc25(5).
418 dmc
420 Supports the Polaroid Digital Microscope Camera. See dmc(5).
421 gphoto2
423 Supports digital cameras supported by the gphoto2 library package.
424 (See http://www.gphoto.org for more information and a list of sup‐
425 ported cameras.) Gphoto2 supports over 140 different camera models.
426 However, please note that more development and testing is needed be‐
427 fore all of these cameras will be supported by SANE backend. See
428 gphoto2(5).
429 qcam
431 Supports Connectix QuickCam cameras. See qcam(5).
432 stv680
434 Supports webcams with a stv680 chip. See stv680(5) for details.
435 Also, have a look at the backend information page at
437 http://www.sane-project.org/sane-supported-devices.html and the list of
438 projects in /usr/share/doc/sane-backends/PROJECTS.
439
442 dll
443 Implements a SANE backend that provides access to an arbitrary number
444 of other SANE backends by dynamic loading. See sane-dll(5).
445 net
447 The SANE network daemon saned(8) provides access to scanners located
448 on different computers in connection with the sane-net(5) backend.
449 See saned(8).
450 pnm
452 PNM image reader pseudo-backend. The purpose of this backend is pri‐
453 marily to aid in debugging of SANE frontends. See sane-pnm(5).
454 pint
456 Supports scanners that use the PINT (Pint Is Not Twain) device
457 driver. The PINT driver is being actively developed on the OpenBSD
458 platform, and has been ported to a few other *NIX-like operating sys‐
459 tems. See sane-pint(5).
460 test
462 Tests frontends and the SANE installation. It provides test pictures
463 and various test options. See sane-test(5).
464 v4l
466 Provides generic access to video cameras and similar equipment using
467 the V4L (Video for Linux) API. See sane-v4l(5).
468 Also, have a look at the backend information page at
470 http://www.sane-project.org/sane-supported-devices.html and the list of
471 projects in /usr/share/doc/sane-backends/PROJECTS.
472
475 By default, all SANE backends (drivers) are loaded dynamically by the
476 sane-dll meta backend. If you have any questions about the dynamic
477 loading, read sane-dll(5). SANE frontends can also be linked to other
478 backends directly by copying or linking a backend to libsane.so in
479 /usr/lib64/sane.
480
482 It's not hard to write a SANE backend. It can take some time, however.
483 You should have basic knowledge of C and enough patience to work
484 through the documentation and find out how your scanner works. Appended
485 is a list of some documents that help to write backends and frontends.
486 The SANE standard defines the application programming interface (API)
488 that is used to communicate between frontends and backends. It can be
489 found at http://sane-project.gitlab.io/standard/ .
490 There is some more information for programmers in /usr/share/doc/sane-
492 backends/backend-writing.txt. Most of the internal SANE routines
493 (sanei) are documented using doxygen:
494 http://www.sane-project.org/sanei/. Before a new backend or frontend
495 project is started, have a look at /usr/share/doc/sane-back‐
496 ends/PROJECTS for projects that are planned or not yet included into
497 the SANE distribution and at our bug-tracking system:
498 http://www.http://www.sane-project.org/bugs.html.
499 There are some links on how to find out about the protocol of a scan‐
501 ner: http://www.meier-geinitz.de/sane/misc/develop.html.
502 If you start writing a backend or frontend or any other part of SANE,
505 please contact the sane-devel mailing list for coordination so that
506 work is not duplicated.
507
510 /etc/sane.d/*.conf
511 The backend configuration files.
512 /usr/lib64/sane/libsane-*.a
514 The static libraries implementing the backends.
515 /usr/lib64/sane/libsane-*.so
517 The shared libraries implementing the backends (present on sys‐
518 tems that support dynamic loading).
519 /usr/share/doc/sane-backends/*
521 SANE documentation: The READMEs, text files for backends 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(1) utility. It prints one line for
528 each scanner it has detected and some comments (#). If sane-find-scan‐
529 ner(1) finds your scanner only as root but not as normal user, the per‐
530 missions for the device files are not adjusted correctly. If the scan‐
531 ner isn't found at all, the operating system hasn't detected it and may
532 need some help. Depending on the type of your scanner, read sane-usb(5)
533 or sane-scsi(5). If your scanner (or other device) is not connected
534 over the SCSI bus or USB, read the backend's manual page for details on
535 how to set it up.
536 Is your scanner detected by the operating system but not by SANE? Try
538 scanimage -L. If the scanner is not found, check that the backend's
539 name is mentioned in /etc/sane.d/dll.conf. Some backends are commented
540 out by default. Remove the comment sign for your backend in this case.
541 Also some backends aren't compiled at all if one of their prerequisites
542 are missing. Examples include dc210, dc240, canon_pp, hpsj5s, gphoto2,
543 pint, qcam, v4l, net, sm3600, snapscan, pnm. If you need one of these
544 backends and it isn't available, read the build instructions in the
545 README file and the individual manual pages of the backends.
546 Another reason for not being detected by scanimage -L may be a missing
548 or incorrect configuration in the backend's configuration file. While
549 SANE tries to automatically find most scanners, some can't be setup
550 correctly without the intervention of the administrator. Also on some
551 operating systems auto-detection may not work. Check the backend's man‐
552 ual page for details.
553 If your scanner is still not found, try setting the various environment
555 variables that are available to assist in debugging. The environment
556 variables are documented in the relevant manual pages. For example, to
557 get the maximum amount of debug information when testing a Mustek SCSI
558 scanner, set environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
559 and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage -L. The
560 SANE_DEBUG_DLL messages tell if the sane-mustek(5) backend was found
561 and loaded at all. The SANE_DEBUG_MUSTEK messages explain what the
562 backend is doing while the SANE_DEBUG_SCSI debugging shows the low
563 level handling. If you can't find out what's going on by checking the
564 messages carefully, contact the sane-devel mailing list for help (see
565 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 de‐
578 vice:
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 (1) works and you want to use one of the
586 graphical frontends like xsane(1), xscanimage(1), or quiteinsane (1)
587 but those frontends don't detect your scanner? One reason may be that
588 you installed two versions of SANE. E.g. the version that was in‐
589 stalled by your distribution in /usr and one you installed from source
590 in /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/AUTHORS file or the
605 backend's manpage. For general discussion about SANE, please use the
606 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), sane-ag‐
611 fafocus(5), sane-apple(5), sane-artec(5), sane-artec_eplus48u(5),
612 sane-as6e(5), sane-avision(5), sane-bh(5), sane-canon(5),
613 sane-canon630u(5), sane-canon_dr(5), sane-canon_pp(5), sane-card‐
614 scan(5), sane-coolscan(5), sane-coolscan2(5), sane-coolscan3(5),
615 sane-dc210(5), sane-dc240(5), sane-dc25(5), sane-dll(5), sane-dmc(5),
616 sane-epson(5), sane-epson2(5), sane-escl(5), sane-fujitsu(5),
617 sane-genesys(5), sane-gphoto2(5), sane-gt68xx(5), sane-hp(5),
618 sane-hpsj5s(5), sane-hp3500(5), sane-hp3900(5), sane-hp4200(5),
619 sane-hp5400(5), sane-hpljm1005(5), sane-ibm(5), sane-kodak(5),
620 sane-leo(5), sane-lexmark(5), sane-ma1509(5), sane-matsushita(5),
621 sane-microtek2(5), sane-microtek(5), sane-mustek(5), sane-mustek_pp(5),
622 sane-mustek_usb(5), sane-mustek_usb2(5), sane-nec(5), sane-net(5),
623 sane-niash(5), sane-pie(5), sane-pint(5), sane-plustek(5), sane-plus‐
624 tek_pp(5), sane-pnm(5), sane-qcam(5), sane-ricoh(5), sane-ricoh2(5),
625 sane-s9036(5), sane-sceptre(5), sane-scsi(5), sane-sharp(5),
626 sane-sm3600(5), sane-sm3840(5), sane-snapscan(5), sane-sp15c(5),
627 sane-st400(5), sane-stv680(5), sane-tamarack(5), sane-teco1(5),
628 sane-teco2(5), sane-teco3(5), sane-test(5), sane-u12(5),
629 sane-umax1220u(5), sane-umax(5), sane-umax_pp(5), sane-usb(5),
630 sane-v4l(5), sane-xerox_mfp(5)
631
634 David Mosberger-Tang and many many more (see /usr/share/doc/sane-back‐
635 ends/AUTHORS for details). This man page was written by Henning Meier-
636 Geinitz. Quite a lot of text was taken from the SANE standard, several
637 man pages, and README files.
638 03 Jan 2020 sane(7)