From 351b7328520c16730ceb46e5acae16038c42185e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Frings-F=C3=BCrst?= Date: Tue, 16 Feb 2021 18:24:19 +0100 Subject: New upstream version 1.0.32 --- doc/sane-avision.man | 42 +++++++++++++++++++++++++++--------------- 1 file changed, 27 insertions(+), 15 deletions(-) (limited to 'doc/sane-avision.man') diff --git a/doc/sane-avision.man b/doc/sane-avision.man index f0a5091..517ac1b 100644 --- a/doc/sane-avision.man +++ b/doc/sane-avision.man @@ -5,10 +5,6 @@ sane\-avision \- SANE backend for original Avision and Avision OEM scanners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film scanners. -.SH ABOUT THIS FILE - -This file is a short description for the avision-backend shipped with SANE. - .SH DESCRIPTION The .B sane\-avision @@ -16,7 +12,7 @@ library implements a SANE (Scanner Access Now Easy) backend that provides access to various Avision scanners and the Avision OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu. -It is fully big-endian aware and in every-day use on PowerPC and SPARC +It is fully big-endian aware and in everyday use on PowerPC and SPARC systems. .B I suggest you hold one hand on the power-button of the scanner while @@ -102,9 +98,14 @@ Where .I scsi-spec is the path-name to a special device or a device ID for the device that corresponds to a SCSI scanner. The special device name must be a generic -SCSI device or a symlink to such a device, for example on Linux "/dev/sga" -or "/dev/sg0". The device ID is the ID returned by the scanner, for example -"HP" or "AVISION". See sane\-scsi(5) for details. +SCSI device or a symlink to such a device, for example on Linux +.I /dev/sga +or +.IR /dev/sg0 . +The device ID is the ID returned by the scanner, for example +"HP" or "AVISION". See +.BR sane\-scsi (5) +for details. .TP Note: Since the backend now includes native USB access, @@ -116,10 +117,12 @@ the HP 53xx, HP 74xx or Minolta film-scanners. .I usb-spec is the USB device name, the vendor/product ID pair or the name used by libusb corresponding to the USB scanner. For example "0x03f0 0x0701" or -"libusb:002:003". See sane\-usb(5) for details. +"libusb:002:003". See +.BR sane\-usb (5) +for details. The program -.IR sane\-find\-scanner +.BR sane\-find\-scanner (1) helps to find out the correct scsi or usb device name. A list with supported devices is built into the avision backend so @@ -147,13 +150,19 @@ contain the configuration file. Under UNIX, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configuration file is searched in two default directories: first, the current working -directory (".") and then in @CONFIGDIR@. If the value of the +directory (".") and then in +.IR @CONFIGDIR@ . +If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting .B SANE_CONFIG_DIR -to "/tmp/config:" would result in directories "tmp/config", ".", and -"@CONFIGDIR@" being searched (in this order). +to "/tmp/config:" would result in directories +.IR tmp/config , +.IR . , +and +.I @CONFIGDIR@ +being searched (in this order). .TP .B SANE_DEBUG_AVISION If the library was compiled with debug support enabled, this @@ -165,11 +174,14 @@ Example: export SANE_DEBUG_AVISION=7 .SH "SEE ALSO" -sane(7), sane\-scsi(5), sane\-usb(5) +.BR sane (7), +.BR sane\-scsi (5), +.BR sane\-usb (5) .br -http://exactcode.com/site/open_source/saneavision/ +.I http://exactcode.com/site/open_source/saneavision .SH MAINTAINER Ren\['e] Rebe + .SH AUTHOR Ren\['e] Rebe and Meino Christian Cramer -- cgit v1.2.3