Man page fixes

2005-11-24 20:17:43 +00:00 · 2005-11-24 20:17:43 +00:00 · a65178b7bb
commit a65178b7bb
--- a/23
+++ b/23
@ -1,3 +1,26 @@
+2005-11-24  Mattias Ellert <mattias.ellert@tsl.uu.se>
+
+	* doc/gamma4scanimage.man, doc/sane-abaton.man, doc/sane-agfafocus.man,
+	  doc/sane-apple.man, doc/sane-artec.man, doc/sane-avision.man,
+	  doc/sane-bh.man, doc/sane-canon.man, doc/sane-canon630u.man,
+	  doc/sane-config.man, doc/sane-coolscan.man, doc/sane-coolscan2.man,
+	  doc/sane-dc210.man, doc/sane-dc240.man, doc/sane-dc25.man,
+	  doc/sane-dmc.man, doc/sane-epson.man, doc/sane-find-scanner.man,
+	  doc/sane-fujitsu.man, doc/sane-genesys.man, doc/sane-gphoto2.man,
+	  doc/sane-gt68xx.man, doc/sane-hp.man, doc/sane-hp4200.man,
+	  doc/sane-hp5400.man, doc/sane-ibm.man, doc/sane-leo.man,
+	  doc/sane-lexmark.man, doc/sane-ma1509.man, doc/sane-matsushita.man,
+	  doc/sane-microtek.man, doc/sane-microtek2.man, doc/sane-mustek.man,
+	  doc/sane-mustek_pp.man, doc/sane-mustek_usb2.man, doc/sane-nec.man,
+	  doc/sane-net.man, doc/sane-niash.man, doc/sane-pint.man,
+	  doc/sane-plustek.man, doc/sane-plustek_pp.man, doc/sane-ricoh.man,
+	  doc/sane-s9036.man, doc/sane-sceptre.man, doc/sane-sharp.man,
+	  doc/sane-snapscan.man, doc/sane-sp15c.man, doc/sane-st400.man,
+	  doc/sane-tamarack.man, doc/sane-teco1.man, doc/sane-teco2.man,
+	  doc/sane-teco3.man, doc/sane-u12.man, doc/sane-umax1220u.man,
+	  doc/sane-umax_pp.man, doc/sane-usb.man, doc/sane-v4l.man,
+	  doc/sane.man, doc/saned.man, doc/scanimage.man: man page fixes
+
 2005-11-23  Oliver Schwartz <Oliver.Schwartz@gmx.de>

 	* backend/snapscan-options.c: Disable bilevel colour / halftoning
--- a/doc/gamma4scanimage.man
+++ b/doc/gamma4scanimage.man
@ -52,7 +52,7 @@ defines the maximum output value. Take a look at the output of scanimage -h to
 find out what maxout has to be. The default value is 255.
 .PP
 .SH EXAMPLE
-.B scanimage \-\-custom-gamma=yes \-\-gamma-table 
+.B scanimage --custom-gamma=yes --gamma-table 
 .I `gamma4scanimage 1.8 0 11500 16383 255`
 >image.pnm

--- a/doc/sane-abaton.man
+++ b/doc/sane-abaton.man
@ -14,9 +14,9 @@ is recognized, but support for it is untested.
 If you own a Abaton scanner other than the ones listed above that
 works with this backend, or if you own an Abaton scanner that does not
 work with this backend, please contact
-.IR sane\-devel@lists.alioth.debian.org
+.IR sane-devel@lists.alioth.debian.org
 with the model number, so that arrangements can be made to include
-support for it. Have a look at http://www.sane\-project.org/mailing\-lists.html
+support for it. Have a look at http://www.sane-project.org/mailing-lists.html
 concerning subscription to sane-devel.
 .PP
 Abaton is out of business, and these scanners are not supported by
@ -107,7 +107,7 @@ former is more likely than the latter.
 If you have found something that you think is a bug, please attempt to
 recreate it with the SANE_DEBUG_ABATON environment variable set to
 255, and send a report detailing the conditions surrounding the bug to
-.IR sane\-devel@lists.alioth.debian.org .
+.IR sane-devel@lists.alioth.debian.org .

 .SH TODO
 .TP
@ -119,7 +119,7 @@ confidence that it will work, as well as to fully exploit the
 information returned by the INQUIRY command.

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5), scanimage(1)
+sane(7), sane-scsi(5), scanimage(1)

 .SH AUTHOR
 The sane-abaton backend was partially written by David Huggins-Daines,
--- a/doc/sane-agfafocus.man
+++ b/doc/sane-agfafocus.man
@ -31,8 +31,8 @@ color scans.
 If you own a scanner other than the ones listed above that works with
 this backend, please let us know by sending the scanner's model name,
 SCSI id, and firmware revision to
-.IR sane\-devel@lists.alioth.debian.org .
-Have a look at http://www.sane\-project.org/mailing\-lists.html
+.IR sane-devel@lists.alioth.debian.org .
+Have a look at http://www.sane-project.org/mailing-lists.html
 concerning subscription to sane-devel.
 .PP
 All of these scanners are pre-SCSI-2, and do not even report properly
@ -167,7 +167,7 @@ a scanner, I could be helpful in adding support for these scanners.
 The AGFA HORIZON scanners are SCSI-2 scanners, and it would probably
 be easier to support these scanners in a SCSI-2 compliant backend.
 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)

 .SH AUTHOR

--- a/doc/sane-apple.man
+++ b/doc/sane-apple.man
@ -23,9 +23,9 @@ ColorOneScanner 24bit RGB color          3-pass
 If you own a Apple scanner other than the ones listed above that
 works with this backend, please let us know by sending the scanner's
 model name, SCSI id, and firmware revision to
-.IR sane\-devel@lists.alioth.debian.org .
-See http://www.sane\-project.org/mailing\-lists.html for details on how to subscribe to
-sane\-devel.
+.IR sane-devel@lists.alioth.debian.org .
+See http://www.sane-project.org/mailing-lists.html for details on how to subscribe to
+sane-devel.

 .SH "DEVICE NAMES"
 This backend expects device names of the form:
@ -129,7 +129,7 @@ have the hardware to experiment on it. Another reason is the lack
 of understanding of how SANE API could provide enaugh means to me
 to actually describe other array types than the gamma one.

-.SH UNSUPPORTED FEATURES.
+.SH UNSUPPORTED FEATURES
 The following "features" will never be supported. At least as I am maintaining
 the sane-apple backend.
 .TP
@ -195,26 +195,20 @@ options panel to exceed from your screen. It happens with mine
 and I am running at 1024x768 my X Server. What can I say? Try smaller
 fonts in the X server, or virtual screens.
 .TP
-.B Weird SCSI behaviour.
+.B Weird SCSI behaviour
 I am quoting David Myers Here...

 >> OS: FreeBSD 2.2.6
 .br
 >> CC: egcs-1.02
 .br
->Just wanted to follow up on this...  I recently changed my SCSI card from
-.br
->the Adaptec 2940UW to a dual-channel Symbios 786 chipset.  When I started up
-.br
->SANE with your driver, I managed to scan line art drawings okay, but Gray16
-.br
->scans led to a stream of SCSI error messages on the console, ultimately
-.br
->hanging with a message saying the scanner wasn't releasing the SCSI bus.
-.br
->This may be that the Symbios is simply less tolerant of ancient
-.br
->hardware, or may be bugs in your driver or in SANE itself...
+Just wanted to follow up on this...  I recently changed my SCSI card from
+the Adaptec 2940UW to a dual-channel Symbios 786 chipset.  When I started up
+SANE with your driver, I managed to scan line art drawings okay, but Gray16
+scans led to a stream of SCSI error messages on the console, ultimately
+hanging with a message saying the scanner wasn't releasing the SCSI bus.
+This may be that the Symbios is simply less tolerant of ancient
+hardware, or may be bugs in your driver or in SANE itself...

 .SH DEBUG
 If you encounter a GUI bug please set the environment variable
@ -240,7 +234,7 @@ the report.
 .SH TODO
 .TP
 .B Non Blocking Support
-Make sane\-apple a non blocking backend. Properly support for
+Make sane-apple a non blocking backend. Properly support for
 .B sane_set_io_mode
 and
 .B sane_get_select_fd
@ -251,7 +245,7 @@ Make scan possible for all models in all supported modes.
 .B Missing Functionality

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)

 .SH AUTHOR
 The sane-apple backend was written not entirely from scratch by
--- a/doc/sane-artec.man
+++ b/doc/sane-artec.man
@ -12,22 +12,21 @@ that provides access to Artec/Ultima SCSI flatbed scanners.  At present,
 the following scanners are known to work at least partially with this backend:
 .PP
 .RS
-.IP *
-Artec A6000C
-.IP *
-Artec A6000C PLUS
-.IP *
-Artec ViewStation AT3
-.IP *
-BlackWidow BW4800SP (rebadged Artec AT3)
-.IP *
-Artec ViewStation AT6
-.IP *
-Artec ViewStation AT12
-.IP *
-Artec AM12S
-.IP *
-Plustek 19200S (rebadged Artec AM12S)
+* Artec A6000C
+.br
+* Artec A6000C PLUS
+.br
+* Artec ViewStation AT3
+.br
+* BlackWidow BW4800SP (rebadged Artec AT3)
+.br
+* Artec ViewStation AT6
+.br
+* Artec ViewStation AT12
+.br
+* Artec AM12S
+.br
+* Plustek 19200S (rebadged Artec AM12S)
 .RE
 .PP
 Although this manual page is generally updated with each release,
@ -172,7 +171,7 @@ correction is not totally working on models other than the AT3.

 .SH "SEE ALSO"

-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)

 .SH AUTHOR

--- a/doc/sane-avision.man
+++ b/doc/sane-avision.man
@ -169,7 +169,7 @@ Example:
 export SANE_DEBUG_AVISION=7

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5), sane\-usb(5)
+sane(7), sane-scsi(5), sane-usb(5)
 .br
 http://www.exactcode.de/oss/avision/

--- a/doc/sane-bh.man
+++ b/doc/sane-bh.man
@ -30,9 +30,9 @@ COPISCAN II 3338(A) Simplex Scanner (with ACE)
 .PP
 If you have a Bell+Howell scanner and are able to test it with this
 backend, please contact
-.IR sane\-devel@lists.alioth.debian.org
+.IR sane-devel@lists.alioth.debian.org
 with the model number and testing results. Have a look at
-http://www.sane\-project.org/mailing\-lists.html concerning subscription to
+http://www.sane-project.org/mailing-lists.html concerning subscription to
 sane-devel. Additionally, the author is curious as to the likelihood of using
 this backend with the newer 4000 and 8000 series scanners.  If you have such a
 beast, please let me know.
@ -269,6 +269,7 @@ a list of standard resolutions; only these resolutions can be used.
 Sets the compression mode of the scanner.  Determines the type of data
 returned from the scanner.  Values are:
 .RS
+.br
 .B none
 \- uncompressed data \- delivered in a SANE_FRAME_GRAY frame
 .br
@ -535,10 +536,10 @@ This is a new backend; detailed bug reports are welcome -- and expected ;)
 If you have found something that you think is a bug, please attempt to
 recreate it with the SANE_DEBUG_BH environment variable set to
 255, and send a report detailing the conditions surrounding the bug to
-.IR sane\-devel@lists.alioth.debian.org .
+.IR sane-devel@lists.alioth.debian.org .

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5), scanimage(1), scanadf(1)
+sane(7), sane-scsi(5), scanimage(1), scanadf(1)

 .SH AUTHOR
 The sane-bh backend was written by Tom Martone, based on the sane-ricoh
--- a/doc/sane-canon.man
+++ b/doc/sane-canon.man
@ -88,7 +88,7 @@ Example:
 export SANE_DEBUG_CANON=4

 .SH "SEE ALSO"
-sane\-scsi(5)
+sane-scsi(5)
 .br
 http://www.rzg.mpg.de/~mpd/sane/
 .br
--- a/doc/sane-canon630u.man
+++ b/doc/sane-canon630u.man
@ -97,7 +97,7 @@ Example:
 .br 
 SANE_DEBUG_CANON630U=12 scanimage > /dev/null
 .SH "SEE ALSO"
-sane(7), sane\-usb(5), sane\-find\-scanner(1)
+sane(7), sane-usb(5), sane-find-scanner(1)
 .br
 http://canon-fb630u.sourceforge.net/
 .br
--- a/doc/sane-config.man
+++ b/doc/sane-config.man
@ -2,7 +2,7 @@
 .SH NAME
 sane-config \- get information about the installed version of libsane
 .SH SYNOPSIS
-.B  sane-config [\-\-prefix] [\-\-exec-prefix] [\-\-libs] [\-\-cflags] [\-\-ldflags] [\-\-version] [\-\-help \fI[OPTION]\fP]
+.B  sane-config [--prefix] [--exec-prefix] [--libs] [--cflags] [--ldflags] [--version] [--help \fI[OPTION]\fP]
 .SH DESCRIPTION
 .PP
 .B sane-config
@ -18,32 +18,32 @@ backend library (libsane).
 .B sane-config
 accepts the following options (you can't use more than one option at the same time):
 .TP 8
-.B  \-\-version
+.B  --version
 Print the currently installed version of libsane on the standard output.
 .TP 8
-.B  \-\-help OPTION
+.B  --help OPTION
 Print a short usage message. If OPTION is specified, help for that option
 (e.g. --libs) is printed (if available).
 .TP 8
-.B  \-\-libs
+.B  --libs
 Print the additional libraries that are necessary to link a
 .B SANE
 frontend to libsane.
 .TP 8
-.B  \-\-ldflags
+.B  --ldflags
 Print the linker flags that are necessary to link a
 .B  SANE
 frontend to libsane.
 .TP 8
-.B  \-\-cflags
+.B  --cflags
 Print the compiler flags that are necessary to compile a
 .B SANE
 frontend. 
 .TP 8
-.B  \-\-prefix
+.B  --prefix
 Print the prefix used during compilation of libsane.
 .TP 8
-.B  \-\-exec-prefix
+.B  --exec-prefix
 Print the exec-prefix used during compilation of libsane.
 .SH "SEE ALSO"
 .BR sane (7)
--- a/doc/sane-coolscan.man
+++ b/doc/sane-coolscan.man
@ -93,7 +93,7 @@ The homepage of this backend
 .I http://www.sema.be/coolscan/
 The original version of the coolscan backend by Didier
 .PP
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)

 .SH THANKS TO

--- a/doc/sane-coolscan2.man
+++ b/doc/sane-coolscan2.man
@ -157,7 +157,7 @@ a value of 128 requests all debug output to be printed.  Smaller
 levels reduce verbosity.

 .SH "SEE ALSO"
-sane\-scsi(5), sane\-usb(5), scanimage(1), xscanimage(1), xsane(1)
+sane-scsi(5), sane-usb(5), scanimage(1), xscanimage(1), xsane(1)

 .SH BUGS
 Currently, the SANE protocol does not allow automatically updating options
--- a/doc/sane-dc210.man
+++ b/doc/sane-dc210.man
@ -102,6 +102,6 @@ Known bugs/limitations are: ?
 .PP
 More general comments, suggestions, and inquiries about frontends
 or SANE should go to the SANE Developers mailing list 
-(see http://www.sane\-project.org/mailing\-lists.html for details). 
+(see http://www.sane-project.org/mailing-lists.html for details). 
 You must be subscribed to the list, otherwise your mail won't be
 sent to the subscribers.
--- a/doc/sane-dc240.man
+++ b/doc/sane-dc240.man
@ -107,7 +107,7 @@ actually be found in multiple directories.
 .PP
 More general comments, suggestions, and inquiries about frontends
 or SANE should go to the SANE Developers mailing list 
-(see http://www.sane\-project.org/mailing\-lists.html for details). 
+(see http://www.sane-project.org/mailing-lists.html for details). 
 You must be subscribed to the list, otherwise your mail won't be
 sent to the subscribers.

--- a/doc/sane-dc25.man
+++ b/doc/sane-dc25.man
@ -94,6 +94,6 @@ updated immediately.
 .PP
 More general comments, suggestions, and inquiries about frontends
 or SANE should go to the SANE Developers mailing list 
-(see http://www.sane\-project.org/mailing\-lists.html for details). 
+(see http://www.sane-project.org/mailing-lists.html for details). 
 You must be subscribed to the list, otherwise your mail won't be
 sent to the subscribers.
--- a/doc/sane-dmc.man
+++ b/doc/sane-dmc.man
@ -131,7 +131,7 @@ be read in one SCSI transfer.  In this case, the driver performs
 buffering and you can read the image in as small an increment as you
 like.
 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .SH AUTHOR
 David F. Skoll
 .PP
--- a/doc/sane-epson.man
+++ b/doc/sane-epson.man
@ -275,7 +275,7 @@ only if you know what you are doing!

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1)

 .SH BUGS

--- a/doc/sane-find-scanner.man
+++ b/doc/sane-find-scanner.man
@ -4,12 +4,12 @@
 sane-find-scanner \- find SCSI and USB scanners and their device files
 .SH SYNOPSIS
 .B sane-find-scanner
-.RB [ \-h | \-? ]
-.RB [ \-v ]
-.RB [ \-q ]
-.RB [ \-p ]
-.RB [ \-f ]
-.RB [ \-F 
+.RB [ -h | -? ]
+.RB [ -v ]
+.RB [ -q ]
+.RB [ -p ]
+.RB [ -f ]
+.RB [ -F 
 .IR filename ]
 .RI [ devname ]

@ -64,28 +64,28 @@ At the time of writing this will only detect Mustek parallel port scanners.

 .SH OPTIONS
 .TP 8
-.B \-h, \-?
+.B -h, -?
 Prints a short usage message.
 .TP 8
-.B \-v
+.B -v
 Verbose output. If used once, 
 .B sane-find-scanner
 shows every device name and the test result.  If used twice, SCSI inquiry
 information and the USB device descriptors are also printed.
 .TP 8
-.B \-q
+.B -q
 Be quiet. Print only the devices, no comments.
 .TP 8
-.B \-p
+.B -p
 Probe parallel port scanners.
 .TP 8
-.B \-f
+.B -f
 Force opening all explicitly given devices as SCSI and USB devices. That's
 useful if 
 .B sane-find-scanner
 is wrong in determining the device type.
 .TP 8
-.B \-F filename
+.B -F filename
 filename is a file that contains USB descriptors in the format of
 /proc/bus/usb/devices as used by Linux.
 .B sane-find-scanner
--- a/doc/sane-fujitsu.man
+++ b/doc/sane-fujitsu.man
@ -102,7 +102,7 @@ brightness b
 Only supported for M3096
 .RE
 .PP
-treshold t
+threshold t
 .RS
 Only supported for M3096
 .RE
@ -152,9 +152,9 @@ often be alleviated by using "scsi-buf-size=32768".

 .SH "SEE ALSO"
 sane(7),
-sane\-scsi(5),
-sane\-sp15c(5)
-sane\-usb(5),
+sane-scsi(5),
+sane-sp15c(5)
+sane-usb(5),
 .br
 Fujitsu ScanPartner 15C OEM Manual, Doc. No. 250-0081-0
 .br
--- a/doc/sane-genesys.man
+++ b/doc/sane-genesys.man
@ -1,10 +1,10 @@
 .\" .IX sane-genesys
 .TH "sane-genesys" "5" "20 Nov 2005" "@PACKAGEVERSION@" "SANE Scanner Access Now Easy"
 .SH "NAME"
-sane\-genesys \- SANE backend for GL646 and GL841 based USB flatbed scanners
+sane-genesys \- SANE backend for GL646 and GL841 based USB flatbed scanners
 .SH "DESCRIPTION"
 The
-.B sane\-genesys
+.B sane-genesys
 library implements a SANE (Scanner Access Now Easy) backend that provides
 access to USB flatbed scanners based on the Genesys GL646 and GL841 chips.
 At present, the following scanners are known to work with this backend:
@ -14,7 +14,7 @@ Medion MD6228
 .br 
 Medion MD6274
 .br 
-Hewlett\-Packard HP2300C
+Hewlett-Packard HP2300C
 .br
 Canon LiDE 35/40/50/60
 .RE
@ -28,19 +28,19 @@ If you own a scanner other than the ones listed above that works with this
 backend, please let me know this by sending the scanner's exact model name and
 the USB vendor and device ids (e.g. from
 .I /proc/bus/usb/devices ,
-.I sane\-find\-scanner
-or syslog) to the sane\-devel mailing list. Even if the scanner's name is only
+.I sane-find-scanner
+or syslog) to the sane-devel mailing list. Even if the scanner's name is only
 slightly different from the models mentioned above, please let me know.
 .PP 
 If you own a scanner that isn't detected by the genesys backend but has a GL646
 or GL841 chipset, you can try to add it to the backend. 
 .PP 
 .SH "SYSTEM ISSUES"
-This backend needs libusb\-0.1.6 or later installed, and hasn't tested in other
+This backend needs libusb-0.1.6 or later installed, and hasn't tested in other
 configuration than a linux kernel 2.6.9 or higher. However, it should work any
 system with libusb where the SANE package can be compiled. For
 setting permissions and general USB information look at
-.BR sane\-usb (5).
+.BR sane-usb (5).


 .SH "CONFIGURATION"
@ -52,7 +52,7 @@ lines starting with a hash mark (#) are ignored.  The scanners are
 autodetected by
 .B usb vendor_id product_id
 statements which are already included into
-.I genesys.conf .
+.IR genesys.conf .
 "vendor_id" and "product_id" are hexadecimal numbers that identfy the
 scanner. 
 .PP 
@ -64,10 +64,10 @@ The backend configuration file (see also description of
 .B SANE_CONFIG_DIR
 below).
 .TP 
-.I @LIBDIR@/libsane\-genesys.a
+.I @LIBDIR@/libsane-genesys.a
 The static library implementing this backend.
 .TP 
-.I @LIBDIR@/libsane\-genesys.so
+.I @LIBDIR@/libsane-genesys.so
 The shared library implementing this backend (present on systems that
 support dynamic loading).
 .SH "ENVIRONMENT"
@ -76,7 +76,7 @@ support dynamic loading).
 This environment variable specifies the list of directories that may
 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
+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
 environment variable ends with the directory separator character, then
@ -110,14 +110,14 @@ export SANE_DEBUG_GENESYS_GL646=255

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5)
+.BR sane-usb (5)
 .br 


 .SH "AUTHOR"
 Oliver Rauch
 .br 
-Henning Meier\-Geinitz <henning@meier\-geinitz.de>
+Henning Meier-Geinitz <henning@meier-geinitz.de>
 .br 
 Gerhard Jaeger <gerhard@gjaeger.de>
 .br 
--- a/doc/sane-gphoto2.man
+++ b/doc/sane-gphoto2.man
@ -112,7 +112,7 @@ Many, no doubt.
 .PP
 More general comments, suggestions, and inquiries about frontends
 or SANE should go to the SANE Developers mailing list 
-(see http://www.sane\-project.org/mailing\-lists.html for details). 
+(see http://www.sane-project.org/mailing-lists.html for details). 
 You must be subscribed to the list, otherwise your mail won't be
 sent to the subscribers.

--- a/doc/sane-gt68xx.man
+++ b/doc/sane-gt68xx.man
@ -32,7 +32,7 @@ Please use libusb-0.1.8 or later. Without libusb or with older libusb versions
 all kinds of trouble can be expected. The scanner should be found by
 sane-find-scanner without further actions. For setting permissions and general
 USB information looks at
-.BR sane\-usb (5).
+.BR sane-usb (5).
 .PP

 .SH FIRMWARE FILE
@ -183,13 +183,13 @@ export SANE_DEBUG_GT68XX=4

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5),
-.BR sane\-artec_eplus48u (5)
-.BR sane\-plustek (5),
-.BR sane\-ma1509 (5),
-.BR sane\-mustek_usb (5),
-.BR sane\-mustek (5),
-.BR sane\-mustek_pp (5)
+.BR sane-usb (5),
+.BR sane-artec_eplus48u (5)
+.BR sane-plustek (5),
+.BR sane-ma1509 (5),
+.BR sane-mustek_usb (5),
+.BR sane-mustek (5),
+.BR sane-mustek_pp (5)
 .br
 .I @DOCDIR@/gt68xx/gt68xx.CHANGES
 .br
--- a/doc/sane-hp.man
+++ b/doc/sane-hp.man
@ -62,9 +62,9 @@ SCL (beside the OfficeJets), the above list of supported scanners is
 complete.
 Other HP scanners are not supported by the "hp" backend, but might be supported
 by another one. See
-.IR http://www.sane\-project.org/ .
+.IR http://www.sane-project.org/ .
 You can also watch the sane-devel mailinglist at
-.IR http://www.sane\-project.org/mailing\-lists.html .
+.IR http://www.sane-project.org/mailing-lists.html .
 .PP
 More details about the hp backend can be found on its homepage 
 .IR http://www.kirchgessner.net/sane.html .
@ -148,14 +148,14 @@ Otherwise startup of frontends and changing parameters might be slower.
 A sample configuration file is shown below:
 .PP
 .RS
+.ft CR
+.nf
 /dev/scanner
-.br
 # this is a comment
-.br
 /dev/hpscan
-.RS 2
-option connect-device
-.RE
+  option connect-device
+.fi
+.ft R
 .RE
 .PP
 /dev/scanner is typically a symlink to the actual SCSI scanner device.
@ -267,7 +267,7 @@ These scanners are using an internal parallel-to-SCSI converter which
 is supported by the ppSCSI-driver (see above).

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5), sane\-usb(5)
+sane(7), sane-scsi(5), sane-usb(5)
 .SH AUTHOR
 The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
 PhotoScanner support by Peter Kirchgessner.
--- a/doc/sane-hp4200.man
+++ b/doc/sane-hp4200.man
@ -86,7 +86,7 @@ export SANE_DEBUG_HP4200=4

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5),
+.BR sane-usb (5),
 .br
 .I http://hp4200-backend.sourceforge.net/

--- a/doc/sane-hp5400.man
+++ b/doc/sane-hp5400.man
@ -86,7 +86,7 @@ export SANE_DEBUG_HP5400=4

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5),
+.BR sane-usb (5),
 .br
 .I http://hp5400backend.sourceforge.net/

--- a/doc/sane-ibm.man
+++ b/doc/sane-ibm.man
@ -79,8 +79,8 @@ debug levels increase the verbosity of the output.

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-find\-scanner (1),
-.BR sane\-scsi (5),
+.BR sane-find-scanner (1),
+.BR sane-scsi (5),

 .SH AUTHOR
 mf <massifr@tiscalinet.it>
--- a/doc/sane-leo.man
+++ b/doc/sane-leo.man
@ -147,7 +147,7 @@ None known.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHOR
--- a/doc/sane-lexmark.man
+++ b/doc/sane-lexmark.man
@ -141,7 +141,7 @@ Dark compensation not implemented.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHOR
--- a/doc/sane-ma1509.man
+++ b/doc/sane-ma1509.man
@ -55,7 +55,7 @@ for example.
 .SH CONFIGURATION
 The contents of the
 .I ma1509.conf
-file is a list of options and device names that correspond to Mustek BearPAw
+file is a list of options and device names that correspond to Mustek BearPaw
 1200F scanners.  Empty lines and lines starting with a hash mark (#) are
 ignored.
 .PP
--- a/doc/sane-matsushita.man
+++ b/doc/sane-matsushita.man
@ -159,7 +159,7 @@ None known.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHOR
--- a/doc/sane-microtek.man
+++ b/doc/sane-microtek.man
@ -149,7 +149,7 @@ A value of 128 requests maximally copious debug output; smaller
 levels reduce verbosity.

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)

 .SH AUTHOR
 Matt Marjanovic
@ -189,6 +189,6 @@ setenv SANE_DEBUG_MICROTEK 128
 .PP
 More general comments, suggestions, and inquiries about frontends
 or SANE should go to 
-.BR sane\-devel@lists.alioth.debian.org ,
+.BR sane-devel@lists.alioth.debian.org ,
 the SANE Developers mailing list. Have a look at
-http://www.sane\-project.org/mailing\-lists.html concerning subscription to sane-devel.
+http://www.sane-project.org/mailing-lists.html concerning subscription to sane-devel.
--- a/doc/sane-microtek2.man
+++ b/doc/sane-microtek2.man
@ -53,7 +53,7 @@ Scanpaq:SQ2030:Parport
 .TE
 .PP
 Additional information can be found at
-.BR http://www.sane\-project.org/ .
+.BR http://www.sane-project.org/ .
 .PP
 If you own a Microtek scanner other than the ones listed above,
 it may or may not work with SANE! Because equal scanners are sold under
--- a/doc/sane-mustek.man
+++ b/doc/sane-mustek.man
@ -92,13 +92,13 @@ If you own a Mustek (or Trust) scanner other than the ones listed
 above that works with this backend, please let us know by sending the
 scanner's exact model name (look at the front and back of the scanner)
 and a debug output to
-.IR sane\-devel@lists.alioth.debian.org .
+.IR sane-devel@lists.alioth.debian.org .
 You can get the debug output by setting the environment variable
 .B SANE_DEBUG_MUSTEK
-to 5 and showing the list of available scanners with scanimage\ \-L . Please
+to 5 and showing the list of available scanners with scanimage\ -L. Please
 send all of it to the mailing list. You must be subscribed to sane-devel
 before you can send mail to the list. See
-.I http://www.sane\-project.org/mailing\-lists.html
+.I http://www.sane-project.org/mailing-lists.html
 for details.

 .SH "DEVICE NAMES"
--- a/doc/sane-mustek_pp.man
+++ b/doc/sane-mustek_pp.man
@ -102,14 +102,14 @@ BIOS or disable it in the backend itself (see GLOBAL OPTIONS).
 Note that the backend needs to run as root or has to have appropriate access
 rights to /dev/parport* if libieee1284 support is compiled in. To allow user 
 access to the scanner run the backend through the network interface (See 
-saned(8) and sane\-net(5)). Note also that the backend
+saned(8) and sane-net(5)). Note also that the backend
 .I does not
 support
 .IR "parport sharing" ,
 i.e. if you try printing while scanning, your computer may crash. To enable
 parport sharing, you have to enable libieee1284 at compile time. This backend
 also conflicts with the
-.I sane\-musteka4s2
+.I sane-musteka4s2
 backend. You can only enable one of them in your dll.conf. However, you have
 to enable the backend explicitly in your dll.conf, just remove the hash mark
 in the line "mustek_pp".
@ -439,10 +439,10 @@ The backend configuration file (see also description of
 .B SANE_CONFIG_DIR
 below).
 .TP
-.I @LIBDIR@/libsane\-mustek_pp.a
+.I @LIBDIR@/libsane-mustek_pp.a
 The static library implementing this backend.
 .TP
-.I @LIBDIR@/libsane\-mustek_pp.so
+.I @LIBDIR@/libsane-mustek_pp.so
 The shared library implementing this backend (present on systems that
 support dynamic loading).

@ -511,7 +511,7 @@ level   debug output
 
 .PP
 .SH "SEE ALSO"
-sane(7), sane\-mustek(5), sane\-net(5), saned(8), sane-find-scanner(1)
+sane(7), sane-mustek(5), sane-net(5), saned(8), sane-find-scanner(1)

 .TP
 For latest bug fixes and information see
@ -528,9 +528,9 @@ Eddy De Greef <eddy_de_greef at tiscali dot be>

 .SH BUGS
 Too many... please send bug reports to 
-.I sane\-devel@lists.alioth.debian.org
+.I sane-devel@lists.alioth.debian.org
 (note that you have to subscribe first to the list before you can send
-emails... see http://www.sane\-project.org/mailing\-lists.html)
+emails... see http://www.sane-project.org/mailing-lists.html)
 .PP

 .SH BUG REPORTS
--- a/doc/sane-mustek_usb2.man
+++ b/doc/sane-mustek_usb2.man
@ -28,7 +28,7 @@ Please use libusb-0.1.8 or later. Without libusb or with older libusb versions
 all kinds of trouble can be expected. The scanner should be found by
 sane-find-scanner without further actions. For setting permissions and general
 USB information looks at
-.BR sane\-usb (5).
+.BR sane-usb (5).
 .PP

 .SH FILES
@ -70,12 +70,12 @@ export SANE_DEBUG_MUSTEK_USB2=4

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5),
-.BR sane\-plustek (5),
-.BR sane\-ma1509 (5),
-.BR sane\-mustek_usb (5),
-.BR sane\-mustek (5),
-.BR sane\-mustek_pp (5)
+.BR sane-usb (5),
+.BR sane-plustek (5),
+.BR sane-ma1509 (5),
+.BR sane-mustek_usb (5),
+.BR sane-mustek (5),
+.BR sane-mustek_pp (5)
 .br
 .I @DOCDIR@/mustek_usb2/mustek_usb2.CHANGES
 .br
--- a/doc/sane-nec.man
+++ b/doc/sane-nec.man
@ -54,6 +54,6 @@ environment variable controls the debug level for this backend.  E.g.,
 a value of 128 requests all debug output to be printed.  Smaller
 levels reduce verbosity.
 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .SH AUTHORS
 Kazuya Fukuda
--- a/doc/sane-net.man
+++ b/doc/sane-net.man
@ -129,7 +129,7 @@ levels reduce verbosity.
 .SH BUGS
 If saned has timed out, the net backend may loop with authorization requests.
 .SH "SEE ALSO"
-sane(7), saned(8), sane\-dll(5), scanimage(1)
+sane(7), saned(8), sane-dll(5), scanimage(1)

 .I http://www.penguin-breeder.org/?page=sane-net
 .SH AUTHOR
--- a/doc/sane-niash.man
+++ b/doc/sane-niash.man
@ -55,8 +55,8 @@ or
 Hewlett-Packard Scanjet 4300c 
 .br
 together with Linux kernel
-.B 2.6
-, kernel version 
+.BR 2.6 ,
+kernel version 
 .B 2.6.8 
 or newer is necessary.

@ -72,7 +72,7 @@ export SANE_DEBUG_NIASH=255

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5)
+.BR sane-usb (5)
 .br
 http://www.sourceforge.net/projects/hp3300backend
 .SH AUTHOR
--- a/doc/sane-pint.man
+++ b/doc/sane-pint.man
@ -21,8 +21,8 @@ successfully.
 If have successfully used the PINT driver with your scanner, but it
 does not work using this SANE backend, please let us know.  To do
 this, send a mail with the relevant information for your scanner to
-.IR sane\-devel@lists.alioth.debian.org .
-Have a look at http://www.sane\-project.org/mailing\-lists.html concerning subscription
+.IR sane-devel@lists.alioth.debian.org .
+Have a look at http://www.sane-project.org/mailing-lists.html concerning subscription
 to sane-devel.

 .SH "DEVICE NAMES"
--- a/doc/sane-plustek.man
+++ b/doc/sane-plustek.man
@ -176,12 +176,12 @@ For a more complete and up to date list see:
 .SH "CONFIGURATION"
 To use your scanner with this backend, you need at least two
 entries in the configuration file
-.br
 .I @CONFIGDIR@/plustek.conf
-.TP
+.RS
 .I [usb] vendor-id product-id
-.TP
+.br
 .I device /dev/usbscanner
+.RE
 .PP
 .I [usb]
 tells the backend, that the following devicename (here
@ -405,9 +405,9 @@ export SANE_DEBUG_PLUSTEK=10

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5),
-.BR sane\-u12 (5),
-.BR sane\-gt68xx (5),
+.BR sane-usb (5),
+.BR sane-u12 (5),
+.BR sane-gt68xx (5),
 .br
 .I @DOCDIR@/plustek/Plustek-USB.changes
 .br
--- a/doc/sane-plustek_pp.man
+++ b/doc/sane-plustek_pp.man
@ -138,28 +138,26 @@ See this file for examples.
 .PP
 This section decribes the backends' configuration file entries.
 The file is located at:
-.PP
-.RS
 .I @CONFIGDIR@/plustek_pp.conf
-.RE
 .PP
 For a proper setup, you will need at least two entries:
-
-.TP
+.RS
 .I [direct]
-.TP
+.br
 .I device 0x378
+.RE
 .PP
 or
-.TP
+.RS
 .I [kernel]
-.TP
+.br
 .I device /dev/pt_drv
+.RE
 .PP
 .I direct
 tells the backend, that the following devicename (here
-.I 0x378
-) has to be interpreted as parallel port scanner device. In
+.IR 0x378 )
+has to be interpreted as parallel port scanner device. In
 fact it is the address to use, alternatively you can use
 .I /dev/parport0
 if the backend has been compiled with libieee1284 support.
--- a/doc/sane-ricoh.man
+++ b/doc/sane-ricoh.man
@ -73,7 +73,7 @@ Example:
 export SANE_DEBUG_RICOH=4

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .SH AUTHOR
 Feico W. Dillema

--- a/doc/sane-s9036.man
+++ b/doc/sane-s9036.man
@ -66,6 +66,6 @@ Example:
 export SANE_DEBUG_S9036=4

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .SH AUTHOR
 Ingo Schneider
--- a/doc/sane-sceptre.man
+++ b/doc/sane-sceptre.man
@ -142,7 +142,7 @@ None known.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHOR
--- a/doc/sane-sharp.man
+++ b/doc/sane-sharp.man
@ -495,7 +495,7 @@ firmware of the scanner.
 tested.

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .SH AUTHORS
 Kazuya Fukuda, Abel Deuring
 .SH CREDITS
--- a/doc/sane-snapscan.man
+++ b/doc/sane-snapscan.man
@ -95,7 +95,7 @@ levels reduce verbosity.
 Man page doesn't provide much information yet.

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .br
 http://www.cs.ualberta.ca/~charter/SnapScan/snapscan.html
 .br
--- a/doc/sane-sp15c.man
+++ b/doc/sane-sp15c.man
@ -39,7 +39,7 @@ This allows frontends such as xscanimage to set scanning region,
 resolution, bit-depth (and color), and enable the automatic document feeder.

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5), sane-fujitsu(5)
+sane(7), sane-scsi(5), sane-fujitsu(5)
 .br
 Fujitsu ScanPartner 15C OEM Manual, Doc. No. 250-0081-0
 .br
--- a/doc/sane-st400.man
+++ b/doc/sane-st400.man
@ -22,8 +22,8 @@ The Siemens ST/Highscan series includes several more models, e.g. the ST300
 and ST600.  If you own one of these scanners, or a scanner other than the
 ones listed above that works with this backend, please let us know by sending
 the scanner's model name, SCSI ID, and firmware revision to
-.IR sane\-devel@lists.alioth.debian.org .
-Have a look at http://www.sane\-project.org/mailing\-lists.html concerning subscription
+.IR sane-devel@lists.alioth.debian.org .
+Have a look at http://www.sane-project.org/mailing-lists.html concerning subscription
 to sane-devel.

 .SH "DEVICE NAMES"
@ -137,10 +137,10 @@ also set the environment variable SANE_DEBUG_SANEI_SCSI to 128 before sending
 me the report.

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .br
 http://www.informatik.uni-oldenburg.de/~ingo/sane/ 

 .SH AUTHOR

-Ingo Wilken <Ingo.Wilken@informatik.uni\-oldenburg.de>
+Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
--- a/doc/sane-tamarack.man
+++ b/doc/sane-tamarack.man
@ -75,6 +75,6 @@ Example:
 export SANE_DEBUG_TAMARACK=4

 .SH "SEE ALSO"
-sane(7), sane\-scsi(5)
+sane(7), sane-scsi(5)
 .SH AUTHOR
 Roger Wolff
--- a/doc/sane-teco1.man
+++ b/doc/sane-teco1.man
@ -183,7 +183,7 @@ None known.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHOR
--- a/doc/sane-teco2.man
+++ b/doc/sane-teco2.man
@ -196,7 +196,7 @@ Plenty. Parts of this backend are still under development.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHORS
--- a/doc/sane-teco3.man
+++ b/doc/sane-teco3.man
@ -145,7 +145,7 @@ Not much.

 .SH "SEE ALSO"

-sane\-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)
+sane-scsi(5), scanimage(1), xscanimage(1), xsane(1), sane(7)


 .SH AUTHOR
--- a/doc/sane-u12.man
+++ b/doc/sane-u12.man
@ -51,19 +51,19 @@ ColorPage HR6 V1         0x0458           0x2004
 .SH "CONFIGURATION"
 To use your scanner with this backend, you need at least two
 entries in the configuration file
-.br
 .I @CONFIGDIR@/u12.conf
-.TP
+.RS
 .I [usb] vendor-id product-id
-.TP
+.br
 .I device /dev/usbscanner
+.RE
 .PP
 .I [usb]
 tells the backend, that the following devicename (here
-.I /dev/usbscanner
-) has to be interpreted as USB scanner device. If vendor- and
+.IR /dev/usbscanner )
+has to be interpreted as USB scanner device. If vendor- and
 product-id has not been specified, the backend tries to
-detect this by its own. If device ist set to
+detect this by its own. If device is set to
 .I auto
 then the next matching device is used.
 .PP
@ -146,8 +146,8 @@ export SANE_DEBUG_U12=10

 .SH "SEE ALSO"
 .BR sane (7),
-.BR sane\-usb (5),
-.BR sane\-plustek (5),
+.BR sane-usb (5),
+.BR sane-plustek (5),
 .br
 .I @DOCDIR@/u12/U12.changes
 .br
--- a/doc/sane-umax1220u.man
+++ b/doc/sane-umax1220u.man
@ -103,7 +103,7 @@ sure to adjust the scan area before doing a scan, since by default, the scan
 area is zero.

 .SH SEE ALSO
-sane(7), sane\-usb(5)
+sane(7), sane-usb(5)

 .TP
 For latest bug fixes and information see
--- a/doc/sane-umax_pp.man
+++ b/doc/sane-umax_pp.man
@ -1,10 +1,10 @@
 .\" .IX sane-umax_pp
 .TH "sane-umax_pp" "5" "23 August 2004" "@PACKAGEVERSION@" "SANE Scanner Access Now Easy"
 .SH "NAME"
-sane\-umax_pp \- SANE backend for Umax Astra parallel port flatbed scanners
+sane-umax_pp \- SANE backend for Umax Astra parallel port flatbed scanners
 .SH "DESCRIPTION"
 The
-.B sane\-umax_pp
+.B sane-umax_pp
 library implements a SANE (Scanner Access Now Easy) backend that
 provides access to Umax parallel port flatbed scanners.  The
 following scanners work with this backend:
@ -53,7 +53,7 @@ if you have a kernel with ppdev support.
 .PP 
 Note that if you don't use the ppdev character device, the backend 
 needs to run as root. To allow user access to the scanner
-run the backend through the network interface (See saned(8) and sane\-net(5)).
+run the backend through the network interface (See saned(8) and sane-net(5)).
 A more relaxed solution (security wise) is to add suid bit to the frontend
 (See chmod(1)).
 The backend drop root priviledges as soon as it can, right after gaining direct
@ -75,7 +75,7 @@ auto
 autodetect all parallel ports and probe
 them for scanner
 .TP
-safe\-auto
+safe-auto
 autodetect all parallel ports and probe
 them for scanner, but does not try direct
 hardware access
@ -128,22 +128,22 @@ scanners.  Empty lines and lines starting with a hash mark (#) are
 ignored.
 .PP 
 The height options supported are
-.BR red\-gain ,
-.BR green\-gain ,
-.BR blue\-gain ,
-.BR red\-offset ,
-.BR green\-offset ,
-.BR blue\-offset ,
+.BR red-gain ,
+.BR green-gain ,
+.BR blue-gain ,
+.BR red-offset ,
+.BR green-offset ,
+.BR blue-offset ,
 .BR astra ,
 and
 .BR buffer .

 Options
-.B red\-gain
+.B red-gain
 ,
-.B green\-gain
+.B green-gain
 and
-.B blue\-gain
+.B blue-gain
 allow you to adjust the sensitivy of your scanner for the given color. Values
 range from 0 (lowest gain) to 15 (highest). If the advanced option "Gain" isn't
 checked in the frontend, the backend does automatic gain calibration, and do not use
@ -152,11 +152,11 @@ user provided values.
 .PP 

 Options
-.B red\-offset
+.B red-offset
 ,
-.B green\-offset
+.B green-offset
 and
-.B blue\-offset
+.B blue-offset
 allow you to adjust the offset of your scanner for the given color. Values
 range from 0 (lowest offset) to 15 (highest). 
 .PP 
@ -192,10 +192,10 @@ The backend configuration file (see also description of
 .B SANE_CONFIG_DIR
 below).
 .TP 
-.I @LIBDIR@/libsane\-umax_pp.a
+.I @LIBDIR@/libsane-umax_pp.a
 The static library implementing this backend.
 .TP 
-.I @LIBDIR@/libsane\-umax_pp.so
+.I @LIBDIR@/libsane-umax_pp.so
 The shared library implementing this backend (present on systems that
 support dynamic loading).

@ -205,7 +205,7 @@ support dynamic loading).
 This environment variable specifies the list of directories that may
 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
+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
 environment variable ends with the directory separator character, then
@ -263,7 +263,7 @@ level   debug output
 
 .PP 
 .SH "SEE ALSO"
-sane(7), sane\-net(5), saned(8)
+sane(7), sane-net(5), saned(8)

 .TP 
 For latest bug fixes and information see
@ -282,10 +282,10 @@ your scanner to be able to help you...

 .TP 
 .I SANE version
-run "scanimage \-V" to determine this
+run "scanimage -V" to determine this
 .TP 
 .I the backend version and your scanner hardware
-run "SANE_DEBUG_UMAX_PP=255 scanimage \-L 2>log" as root. If you don't get any output
+run "SANE_DEBUG_UMAX_PP=255 scanimage -L 2>log" as root. If you don't get any output
 from the umax_pp backend, make sure a line "umax_pp" is included into
 your @CONFIGDIR@/dll.conf.
 If your scanner isn't detected, make sure you've defined the right port address, or the
--- a/doc/sane-usb.man
+++ b/doc/sane-usb.man
@ -87,7 +87,7 @@ doesn't make sense to go on, if this is not the case. While sane-find-scanner
 is able to detect any USB scanner, actual scanning will only work if the
 scanner is supported by a SANE backend. Information on the level of support
 can be found on the SANE webpage
-.RI ( http://www.sane\-project.org/ ),
+.RI ( http://www.sane-project.org/ ),
 and the individual backend manpages.
 .PP
 Most backends can detect USB scanners automatically using "usb" configuration
--- a/doc/sane-v4l.man
+++ b/doc/sane-v4l.man
@ -83,9 +83,9 @@ Juergen G. Schimmer, Henning Meier-Geinitz
 If more than one video card is present, a crash may occur. Frequency and geometry
 selection is missing.
 .br
-Send bug reports to the SANE mailing list: sane\-devel@lists.alioth.debian.org.  You must
+Send bug reports to the SANE mailing list: sane-devel@lists.alioth.debian.org.  You must
 be subscribed to the list to send mail. See
-http://www.sane\-project.org/mailing\-lists.html for details.
+http://www.sane-project.org/mailing-lists.html for details.

 .SH SEE ALSO
 sane(7), xcam(1).
--- a/doc/sane.man
+++ b/doc/sane.man
@ -51,7 +51,7 @@ are included in the package
 Both packages can be downloaded from the
 .B SANE
 homepage 
-.RI ( http://www.sane\-project.org/ ).
+.RI ( http://www.sane-project.org/ ).
 Information about other frontends and backends can also be found on the
 .B SANE
 homepage.
@ -61,9 +61,9 @@ The following sections provide short descriptions and links to more
 information about several aspects of
 .B SANE.
 A name with a number in parenthesis (e.g. 
-.RB ` sane\-dll (5)')
+.RB ` sane-dll (5)')
 points to a manual page. In this case 
-.RB ` "man 5 sane\-dll" '
+.RB ` "man 5 sane-dll" '
 will display the page. Entries like
 .RI ` @DOCDIR@/sane.tex '
 are references to text files that were copied to the
@ -76,7 +76,7 @@ during installation. Everything else is a URL to a resource on the web.
 .B SANE homepage
 Information on all aspects of SANE including a tutorial and a link to the SANE FAQ
 can be found on the SANE homepage:
-.IR http://www.sane\-project.org/ .
+.IR http://www.sane-project.org/ .
 .TP
 .B SANE device lists
 The 
@ -87,7 +87,7 @@ support for a specific device. If your scanner is not listed there (either
 supported or unsupported), please contact us. See section HOW CAN YOU HELP
 SANE for details. There are lists for specific releases of SANE, for the
 current development version and a search engine:
-.IR http://www.sane\-project.org/sane\-supported\-devices.html .
+.IR http://www.sane-project.org/sane-supported-devices.html .
 The lists are also installed on your system at @DOCDIR@/.
 .TP
 .B SANE mailing list
@ -96,7 +96,7 @@ implementations: sane-devel.  Despite its name, the list is not only intended
 for developers, but also for users. There are also some more lists for special
 topics, however, for users, sane-devel is the right list. How to subscribe and
 unsubscribe:
-.IR http://www.sane\-project.org/mailing\-lists.html .
+.IR http://www.sane-project.org/mailing-lists.html .
 .TP
 .B SANE IRC channel
 The IRC (Internet Relay Chat) channel #sane can be found on the Freenode
@ -118,11 +118,11 @@ installing
 .TP
 .B SCSI configuration
 For information about various systems and SCSI controllers see
-.BR sane\-scsi (5).
+.BR sane-scsi (5).
 .TP
 .B USB configuration
 For information about USB configuration see
-.BR sane\-usb (5).
+.BR sane-usb (5).

 .SH "FRONTENDS AND MISCELLANEOUS PROGRAMS"
 .TP 2
@ -146,45 +146,45 @@ Also, have a look at the
 package (including
 .BR xscanimage ", " xcam ", and " scanadf )
 and the frontend information page at
-.IR http://www.sane\-project.org/sane\-frontends.html .
+.IR http://www.sane-project.org/sane-frontends.html .

 .SH "BACKENDS FOR SCANNERS"
 .TP 2
 .B abaton
 The SANE backend for Abaton flatbed scanners supports the Scan 300/GS (8bit,
 256 levels of gray) and the Scan 300/S (black and white, untested). See
-.BR sane\-abaton (5)
+.BR sane-abaton (5)
 for details.
 .TP
 .B agfafocus
 This backend supports AGFA Focus scanners and the Siemens S9036 (untested).
 See
-.BR sane\-agfafocus (5)
+.BR sane-agfafocus (5)
 for details.
 .TP
 .B apple
 The SANE backend for Apple flatbed scanners supports the following scanners:
 AppleScanner, OneScanner and ColorOneScanner. See
-.BR sane\-apple (5)
+.BR sane-apple (5)
 for details.
 .TP
 .B artec
 The SANE Artec backend supports several Artec/Ultima SCSI flatbed scanners as
 well as the BlackWidow BW4800SP and the Plustek 19200S. See
-.BR sane\-artec (5)
+.BR sane-artec (5)
 for details.
 .TP
 .B artec_eplus48u
 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
-.BR sane\-artec_eplus48u (5)
+.BR sane-artec_eplus48u (5)
 for details.
 .TP
 .B as6e
 This is a SANE backend for using the Artec AS6E parallel port interface
 scanner. See
-.BR sane\-as6e (5)
+.BR sane-as6e (5)
 for details.
 .TP
 .B avision
@ -193,41 +193,41 @@ 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 
-.BR sane\-avision (5)
+.BR sane-avision (5)
 for details.
 .TP
 .B bh
 The bh backend provides access to Bell+Howell Copiscan II series document
 scanners. See
-.BR sane\-bh (5)
+.BR sane-bh (5)
 for details.
 .TP
 .B canon
 The canon backend supports the CanoScan 300, CanoScan 600, and CanoScan
 2700F SCSI flatbed scanners. See
-.BR sane\-canon (5)
+.BR sane-canon (5)
 for details.
 .TP
 .B canon630u
 The canon630u backend supports the CanoScan 630u and 636u USB scanners.  See
-.BR sane\-canon630u (5)
+.BR sane-canon630u (5)
 for details.
 .TP
 .B canon_pp
 The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and N640P
 parallel port scanners.  See
-.BR sane\-canon_pp (5)
+.BR sane-canon_pp (5)
 for details.
 .TP
 .B coolscan
 This is a SANE backend for Nikon Coolscan film-scanners. See
-.BR sane\-coolscan (5)
+.BR sane-coolscan (5)
 for details.
 .TP
 .B coolscan2
 This is a SANE backend for Nikon Coolscan film-scanners.
 See
-.BR sane\-coolscan2 (5)
+.BR sane-coolscan2 (5)
 or
 .I http://coolscan2.sourceforge.net
 for details.
@ -235,20 +235,20 @@ for details.
 .B epson
 The SANE epson backend provides support for Epson SCSI, parallel port and USB
 flatbed scanners. See
-.BR sane\-epson (5)
+.BR sane-epson (5)
 for details.
 .TP
 .B fujitsu
 The fujitsu backend provides support for Fujitsu 3091, 3093, 3096 and
 fi-4340 SCSI scanners. See
-.BR sane\-fujitsu (5)
+.BR sane-fujitsu (5)
 for details.
 .TP
 .B genesys
 The genesys backend provides support for scanners based on the Genesys Logic
 GL646 and GL841 chips like the Medion 6471 and Hewlett-Packard 2300c.
 Support for GL841 based scanners is far from being complete. See
-.BR sane\-genesys (5)
+.BR sane-genesys (5)
 for details.
 .TP
 .B gt68xx
@ -256,108 +256,108 @@ The gt68xx backend provides support for scanners based on the Grandtech
 GT-6801 and GT-6816 chips like the 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
-.BR sane\-gt68xx (5)
+.BR sane-gt68xx (5)
 for details.
 .TP
 .B hp
 The SANE hp backend provides access to Hewlett-Packard ScanJet scanners which
 support SCL (Scanner Control Language by HP). See
-.BR sane\-hp (5)
+.BR sane-hp (5)
 for details.
 .TP
 .B hpsj5s
 The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
-.BR sane\-hpsj5s (5)
+.BR sane-hpsj5s (5)
 for details.
 .TP
 .B hp4200
 The SANE backend for the Hewlett-Packard ScanJet 4200 series. See
-.BR sane\-hp4200 (5)
+.BR sane-hp4200 (5)
 for details.
 .TP
 .B hp5400
 The SANE backend for the Hewlett-Packard ScanJet 54XXC series. See
-.BR sane\-hp5400 (5)
+.BR sane-hp5400 (5)
 for details.
 .TP
 .B ibm
 The SANE backend for some IBM and Ricoh SCSI scanners. See
-.BR sane\-ibm (5)
+.BR sane-ibm (5)
 for details.
 .TP
 .B leo
 This backend supports the Leo S3 and the Across FS-1130, which is a re-badged
 LEO FS-1130 scanner. See
-.BR sane\-leo (5)
+.BR sane-leo (5)
 for details.
 .TP
 .B lexmark
 This backend supports the Lexmark X1100 series of USB scanners. See
-.BR sane\-lexmark (5)
+.BR sane-lexmark (5)
 for details.
 .TP
 .B ma1509
 The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed scanner. See
-.BR sane\-ma1509 (5)
+.BR sane-ma1509 (5)
 for details.
 .TP
 .B matsushita
 This backend supports some Panasonic KVSS high speed scanners. See
-.BR sane\-matsushita (5)
+.BR sane-matsushita (5)
 for details.
 .TP
 .B microtek
 The microtek backend provides access to the "second generation" Microtek
 scanners with SCSI-1 command set. See 
-.BR sane\-microtek (5)
+.BR sane-microtek (5)
 for details.
 .TP
 .B microtek2
 The microtek2 backend provides access to some Microtek scanners with a
 SCSI-2 command set. See
-.BR sane\-microtek2 (5)
+.BR sane-microtek2 (5)
 for details.
 .TP
 .B mustek
 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
-.BR sane\-mustek (5)
+.BR sane-mustek (5)
 for details.
 .TP
 .B mustek_pp
 The mustek_pp backend provides access to Mustek parallel port flatbed
 scanners. See
-.BR sane\-mustek_pp (5)
+.BR sane-mustek_pp (5)
 for details.
 .TP
 .B mustek_usb
 The mustek_usb backend provides access to some Mustek ScanExpress USB flatbed
 scanners. See
-.BR sane\-mustek_usb (5)
+.BR sane-mustek_usb (5)
 for details.
 .TP
 .B mustek_usb2
 The mustek_usb backend provides access to scanners using the SQ113 chipset like
 the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
-.BR sane\-mustek_usb2 (5)
+.BR sane-mustek_usb2 (5)
 for details.
 .TP
 .B nec
 The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
-.BR sane\-nec (5)
+.BR sane-nec (5)
 for details.
 .TP
 .B niash
 The niash backend supports the Agfa Snapscan Touch and the HP ScanJet 3300c,
 3400c, and 4300c USB flatbed scanners. See
-.BR sane\-niash (5)
+.BR sane-niash (5)
 for details.
 .TP
 .B pie
 The pie backend provides access to Pacific Image Electronics (PIE) and Devcom
 SCSI flatbed scanners. See
-.BR sane\-pie (5)
+.BR sane-pie (5)
 for details.
 .TP
 .B plustek
@ -365,101 +365,101 @@ 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
-.BR sane\-plustek (5)
+.BR sane-plustek (5)
 for details.
 .TP
 .B plustek_pp
 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
-.BR sane\-plustek_pp (5)
+.BR sane-plustek_pp (5)
 for details.
 .TP
 .B ricoh
 The ricoh backend provides access to the following Ricoh flatbed
 scanners: IS50 and IS60. See
-.BR sane\-ricoh (5)
+.BR sane-ricoh (5)
 for details.
 .TP
 .B s9036
 The s9036 backend provides access to Siemens 9036 flatbed scanners. See
-.BR sane\-s9036 (5)
+.BR sane-s9036 (5)
 for details.
 .TP
 .B sceptre
 The sceptre backend provides access to the Sceptre S1200 flatbed scanner. See
-.BR sane\-sceptre (5)
+.BR sane-sceptre (5)
 for details.
 .TP
 .B sharp
 The SANE sharp backend supports Sharp SCSI scanners. See
-.BR sane\-sharp (5)
+.BR sane-sharp (5)
 for details.
 .TP
 .B sm3600
 The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB scanner. See
-.BR sane\-sm3600 (5)
+.BR sane-sm3600 (5)
 for details.
 .TP
 .B sm3840
 The SANE sm3840 backend suppoert the Microtek ScanMaker 3840 USB scanner.  See
-.BR sane\-sm3840 (5)
+.BR sane-sm3840 (5)
 for details.
 .TP
 .B snapscan
 The snapscan backend supports AGFA SnapScan flatbed scanners. See
-.BR sane\-snapscan (5)
+.BR sane-snapscan (5)
 for details.
 .TP
 .B sp15c
 This backend supports the Fujitsu FCPA ScanPartner 15C flatbed scanner. See
-.BR sane\-sp15c (5)
+.BR sane-sp15c (5)
 for details.
 .TP
 .B st400
 The sane-st400 backend provides access to Siemens ST400 and ST800. See
-.BR sane\-st400 (5)
+.BR sane-st400 (5)
 for details.
 .TP
 .B tamarack
 The SANE tamarack backend supports Tamarack Artiscan flatbed scanners. See
-.BR sane\-tamarack (5)
+.BR sane-tamarack (5)
 for details.
 .TP
 .B teco1 teco2 teco3
 The SANE teco1, teco2 and teco3 backends support some TECO scanners,
 usually sold under the Relisys, Trust, Primax, Piotech, Dextra
 names. See
-.BR sane\-teco1 "(5), " sane\-teco2 "(5) and " sane\-teco3 (5)
+.BR sane-teco1 "(5), " sane-teco2 "(5) and " sane-teco3 (5)
 for details.
 .TP
 .B u12
 The sane-u12 backend provides USB flatbed scanners based on Plustek's ASIC 98003
 (parallel-port ASIC) and a GeneSys Logics' USB-parport bridge chip like the
 Plustek OpticPro U(T)12. See
-.BR sane\-u12 (5)
+.BR sane-u12 (5)
 for details.
 .TP
 .B umax
 The sane-umax backend provides access to several UMAX-SCSI-scanners and some
 Linotype Hell SCSI-scanners. See
-.BR sane\-umax (5)
+.BR sane-umax (5)
 for details.
 .TP
 .B umax_pp
 The sane-umax_pp backend provides access to Umax parallel port flatbed scanners
 and the HP 3200C. See 
-.BR sane\-umax_pp (5)
+.BR sane-umax_pp (5)
 for details.
 .TP
 .B umax1200u
 The sane-umax1220u backend supports the UMAX Astra 1220U (USB) flatbed scanner
 (and also the UMAX Astra 2000U, sort of). See
-.BR sane\-umax1220u (5)
+.BR sane-umax1220u (5)
 for details.
 .PP
 Also, have a look at the backend information page at
-.I http://www.sane\-project.org/sane\-supported\-devices.html
+.I http://www.sane-project.org/sane-supported-devices.html
 and the list of projects in
 .IR @DOCDIR@/PROJECTS .

@ -467,19 +467,19 @@ and the list of projects in
 .TP 2
 .B dc210
 Backend for Kodak DC210 Digital Camera. See
-.BR sane\-dc210 (5).
+.BR sane-dc210 (5).
 .TP
 .B dc240
 Backend for Kodak DC240 Digital Camera. See
-.BR sane\-dc240 (5).
+.BR sane-dc240 (5).
 .TP
 .B dc25
 Backend for Kodak DC20/DC25 Digital Cameras. See
-.BR sane\-dc25 (5).
+.BR sane-dc25 (5).
 .TP
 .B dmc
 Backend for the Polaroid Digital Microscope Camera. See
-.BR sane\-dmc (5).
+.BR sane-dmc (5).
 .TP
 .B gphoto2
 Backend for digital cameras supported by the gphoto2 library package.  (See
@ -489,14 +489,14 @@ for more information and a list of supported cameras.)  Gphoto2 supports over
 testing is needed before all of these cameras will be supported by
 .B SANE
 backend.  See
-.BR sane\-gphoto2 (5).
+.BR sane-gphoto2 (5).
 .TP
 .B qcam
 Backend for Connectix QuickCam cameras. See 
-.BR sane\-qcam (5).
+.BR sane-qcam (5).
 .PP
 Also, have a look at the backend information page at
-.I http://www.sane\-project.org/sane\-supported\-devices.html
+.I http://www.sane-project.org/sane-supported-devices.html
 and the list of projects in
 .IR @DOCDIR@/PROJECTS .

@ -508,21 +508,21 @@ The sane-dll library implements a
 backend that provides access to an arbitrary number of other
 .B SANE
 backends by dynamic loading. See
-.BR sane\-dll (5).
+.BR sane-dll (5).
 .TP
 .B net
 The 
 .B SANE
 network daemon saned provides access to scanners located on different
 computers in connection with the net backend. See
-.BR sane\-net "(5) and " saned (8).
+.BR sane-net "(5) and " saned (8).
 .TP
 .B pnm
 PNM image reader pseudo-backend. The purpose of this backend is primarily to
 aid in debugging of
 .B SANE
 frontends. See
-.BR sane\-pnm (5).
+.BR sane-pnm (5).
 .TP
 .B pint
 Backend for scanners that use the
@ -531,7 +531,7 @@ Backend for scanners that use the
 .B PINT
 driver is being actively developed on the OpenBSD platform, and has been
 ported to a few other *nix-like operating systems. See
-.BR sane\-pint (5).
+.BR sane-pint (5).
 .TP
 .B test
 The
@ -539,7 +539,7 @@ The
 test backend is for testing frontends and the
 .B SANE
 installation.  It provides test pictures and various test options. See
-.BR sane\-test (5).
+.BR sane-test (5).
 .TP
 .B v4l
 The sane-v4l library implements a
@ -548,10 +548,10 @@ backend that provides generic access to video cameras and similar equipment
 using the
 .B V4L
 (Video for Linux) API. See
-.BR sane\-v4l (5) .
+.BR sane-v4l (5) .
 .PP
 Also, have a look at the backend information page at
-.I http://www.sane\-project.org/sane\-supported\-devices.html
+.I http://www.sane-project.org/sane-supported-devices.html
 and the list of projects in
 .IR @DOCDIR@/PROJECTS .

@ -562,7 +562,7 @@ backends (drivers) are loaded dynamically by the
 .B sane-dll
 meta backend. If you have any questions about the dynamic loading,
 read
-.BR sane\-dll (5).
+.BR sane-dll (5).
 .B SANE
 frontend can also be linked to other backends directly by copying or linking a
 backend to
@ -587,9 +587,9 @@ communicate between frontends and backends. It can be found at
 (if latex is installed on your system) and on the
 .B SANE
 website:
-.I http://www.sane\-project.org/html/
+.I http://www.sane-project.org/html/
 (HTML), or
-.I http://www.sane\-project.org/sane.ps
+.I http://www.sane-project.org/sane.ps
 (Postscript).
 .PP
 There is some more information for programmers in
@ -605,7 +605,7 @@ Before a new backend or frontend project is started, have a look at
 for projects that are planned or not yet included into the
 .B SANE
 distribution and at our bug-tracking system:
-.IR http://www.http://www.sane\-project.org/bugs.html .
+.IR http://www.http://www.sane-project.org/bugs.html .
 .PP
 There are some links on how to find out about the protocol of a scanner: 
 .IR http://www.meier-geinitz.de/sane/misc/develop.html .
@ -646,9 +646,9 @@ 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
-.BR sane\-usb (5)
+.BR sane-usb (5)
 or
-.BR sane\-scsi (5).
+.BR sane-scsi (5).
 If your scanner (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.
 .PP
@ -711,9 +711,9 @@ don't have a scanner or other
 .B SANE
 device:
 .IP
-.B scanimage \-d
+.B scanimage -d
 .I test
-.B \-T
+.B -T
 .PP
 You should get a list of PASSed tests. You can do the same with your backend
 by changing "test" to your backend's name.
@ -749,13 +749,13 @@ See also the documentation of the frontends.
 We appreciate any help we can get. Please have a look at our web page about
 contributing to 
 .BR SANE :
-.I http://www.sane\-project.org/contrib.html
+.I http://www.sane-project.org/contrib.html
 .PP

 .SH "CONTACT"
 For reporting bugs or requesting new features, please use our bug-tracking
 system:
-.IR http://www.sane\-project.org/bugs.html .
+.IR http://www.sane-project.org/bugs.html .
 You can also contact the author of your backend directly. Usually the email
 address can be found in the
 .I @DOCDIR@/AUTHORS
@ -763,7 +763,7 @@ file or the backend's manpage. For general discussion about SANE, please use
 the
 .B SANE
 mailing list sane-devel (see
-.I http://www.sane\-project.org/mailing\-lists.html
+.I http://www.sane-project.org/mailing-lists.html
 for details).
 .PP

@ -771,74 +771,74 @@ for details).
 .BR saned (8),
 .BR sane-find-scanner (1),
 .BR scanimage (1),
-.BR sane\-abaton (5),
-.BR sane\-agfafocus (5),
-.BR sane\-apple (5),
-.BR sane\-artec (5),
-.BR sane\-artec_eplus48u (5),
-.BR sane\-as6e (5),
-.BR sane\-avision (5),
-.BR sane\-bh (5),
-.BR sane\-canon (5),
-.BR sane\-canon630u (5),
-.BR sane\-canon_pp (5),
-.BR sane\-coolscan2 (5),
-.BR sane\-coolscan (5),
-.BR sane\-dc210 (5),
-.BR sane\-dc240 (5),
-.BR sane\-dc25 (5),
-.BR sane\-dll (5),
-.BR sane\-dmc (5),
-.BR sane\-epson (5),
-.BR sane\-fujitsu (5),
-.BR sane\-genesys (5),
-.BR sane\-gphoto2 (5),
-.BR sane\-gt68xx (5),
-.BR sane\-hp (5),
-.BR sane\-hpsj5s (5),
-.BR sane\-hp4200 (5),
-.BR sane\-hp5400 (5),
-.BR sane\-ibm (5),
-.BR sane\-leo (5),
-.BR sane\-lexmark (5),
-.BR sane\-ma1509 (5),
-.BR sane\-matsushita (5),
-.BR sane\-microtek2 (5),
-.BR sane\-microtek (5),
-.BR sane\-mustek (5),
-.BR sane\-mustek_pp (5),
-.BR sane\-mustek_usb (5),
-.BR sane\-mustek_usb2 (5),
-.BR sane\-nec (5),
-.BR sane\-net (5),
-.BR sane\-niash (5),
-.BR sane\-pie (5),
-.BR sane\-pint (5),
-.BR sane\-plustek (5),
-.BR sane\-plustek_pp (5),
-.BR sane\-pnm (5),
-.BR sane\-qcam (5),
-.BR sane\-ricoh (5),
-.BR sane\-s9036 (5),
-.BR sane\-sceptre (5),
-.BR sane\-scsi (5),
-.BR sane\-sharp (5),
-.BR sane\-sm3600 (5),
-.BR sane\-sm3840 (5),
-.BR sane\-snapscan (5),
-.BR sane\-sp15c (5),
-.BR sane\-st400 (5),
-.BR sane\-tamarack (5),
-.BR sane\-teco1 (5),
-.BR sane\-teco2 (5),
-.BR sane\-teco3 (5),
-.BR sane\-test (5),
-.BR sane\-u12 (5),
-.BR sane\-umax1220u (5),
-.BR sane\-umax (5),
-.BR sane\-umax_pp (5),
-.BR sane\-usb (5),
-.BR sane\-v4l (5)
+.BR sane-abaton (5),
+.BR sane-agfafocus (5),
+.BR sane-apple (5),
+.BR sane-artec (5),
+.BR sane-artec_eplus48u (5),
+.BR sane-as6e (5),
+.BR sane-avision (5),
+.BR sane-bh (5),
+.BR sane-canon (5),
+.BR sane-canon630u (5),
+.BR sane-canon_pp (5),
+.BR sane-coolscan2 (5),
+.BR sane-coolscan (5),
+.BR sane-dc210 (5),
+.BR sane-dc240 (5),
+.BR sane-dc25 (5),
+.BR sane-dll (5),
+.BR sane-dmc (5),
+.BR sane-epson (5),
+.BR sane-fujitsu (5),
+.BR sane-genesys (5),
+.BR sane-gphoto2 (5),
+.BR sane-gt68xx (5),
+.BR sane-hp (5),
+.BR sane-hpsj5s (5),
+.BR sane-hp4200 (5),
+.BR sane-hp5400 (5),
+.BR sane-ibm (5),
+.BR sane-leo (5),
+.BR sane-lexmark (5),
+.BR sane-ma1509 (5),
+.BR sane-matsushita (5),
+.BR sane-microtek2 (5),
+.BR sane-microtek (5),
+.BR sane-mustek (5),
+.BR sane-mustek_pp (5),
+.BR sane-mustek_usb (5),
+.BR sane-mustek_usb2 (5),
+.BR sane-nec (5),
+.BR sane-net (5),
+.BR sane-niash (5),
+.BR sane-pie (5),
+.BR sane-pint (5),
+.BR sane-plustek (5),
+.BR sane-plustek_pp (5),
+.BR sane-pnm (5),
+.BR sane-qcam (5),
+.BR sane-ricoh (5),
+.BR sane-s9036 (5),
+.BR sane-sceptre (5),
+.BR sane-scsi (5),
+.BR sane-sharp (5),
+.BR sane-sm3600 (5),
+.BR sane-sm3840 (5),
+.BR sane-snapscan (5),
+.BR sane-sp15c (5),
+.BR sane-st400 (5),
+.BR sane-tamarack (5),
+.BR sane-teco1 (5),
+.BR sane-teco2 (5),
+.BR sane-teco3 (5),
+.BR sane-test (5),
+.BR sane-u12 (5),
+.BR sane-umax1220u (5),
+.BR sane-umax (5),
+.BR sane-umax_pp (5),
+.BR sane-usb (5),
+.BR sane-v4l (5)

 .SH AUTHOR
 David Mosberger-Tang and many many more (see
--- a/doc/saned.man
+++ b/doc/saned.man
@ -4,7 +4,7 @@
 saned \- SANE network daemon
 .SH SYNOPSIS
 .B saned
-.RB [ \-d | \-s
+.RB [ -d | -s
 .RI [ n ]]
 .SH DESCRIPTION
 .B saned
@ -13,9 +13,9 @@ to access image acquisition devices available on the local host.
 .SH OPTIONS
 .PP
 The
-.B \-d
+.B -d
 and
-.B \-s
+.B -s
 flags request that
 .B saned
 run in debug mode (as opposed to
@ -26,12 +26,12 @@ explicitly waits for a connection request.  When compiled with
 debugging enabled, these flags may be followed by a number to request
 debug info. The larger the number, the more verbose the debug output.
 E.g.,
-.B \-d128
+.B -d128
 will request printing of all debug info. Debug level 0 means no debug output
 at all. The default value is 2. If flag
-.B \-d
+.B -d
 is used, the debug messages will be printed to stderr while
-.B \-s
+.B -s
 requests using syslog.
 .PP
 If 
--- a/doc/scanimage.man
+++ b/doc/scanimage.man
@ -4,32 +4,32 @@
 scanimage \- scan an image
 .SH SYNOPSIS
 .B scanimage
-.RB [ \-d | \-\-device-name
+.RB [ -d | --device-name
 .IR dev ]
-.RB [ \-\-format
+.RB [ --format
 .IR format ]
-.RB [ \-i | \-\-icc-profile
+.RB [ -i | --icc-profile
 .IR profile ]
-.RB [ \-L | \-\-list-devices ]
-.RB [ \-f | \-\-formatted-device-list 
+.RB [ -L | --list-devices ]
+.RB [ -f | --formatted-device-list 
 .IR format ]
-.RB [ \-\-batch 
+.RB [ --batch 
 .RI [= format ]]
-.RB [ \-\-batch-start
+.RB [ --batch-start
 .IR start ]
-.RB [ \-\-batch-count
+.RB [ --batch-count
 .IR count ]
-.RB [ \-\-batch-increment
+.RB [ --batch-increment
 .IR increment ]
-.RB [ \-\-batch-double ]
-.RB [ \-\-accept-md5-only ]
-.RB [ \-p | \-\-progress ]
-.RB [ \-n | \-\-dont-scan ]
-.RB [ \-T | \-\-test ]
-.RB [ \-h | \-\-help ]
-.RB [ \-v | \-\-verbose ]
-.RB [ \-B | \-\-buffersize ]
-.RB [ \-V | \-\-version ]
+.RB [ --batch-double ]
+.RB [ --accept-md5-only ]
+.RB [ -p | --progress ]
+.RB [ -n | --dont-scan ]
+.RB [ -T | --test ]
+.RB [ -h | --help ]
+.RB [ -v | --verbose ]
+.RB [ -B | --buffersize ]
+.RB [ -V | --version ]
 .RI [ device-specific-options ]
 .SH DESCRIPTION
 .B scanimage
@ -55,7 +55,7 @@ to get a list of available backends).
 .SH EXAMPLES
 To get a list of devices:

-  scanimage \-L
+  scanimage -L

 To scan with default settings to the file image.pnm:

@ -63,14 +63,14 @@ To scan with default settings to the file image.pnm:

 To print all available options:

-  scanimage \-h
+  scanimage -h

 .SH OPTIONS
 .PP
 The
-.B \-d
+.B -d
 or
-.B \-\-device-name
+.B --device-name
 options must be followed by a
 .B SANE
 device-name like 
@ -78,7 +78,7 @@ device-name like
 or 
 .RI ` hp:/dev/usbscanner0 '.
 A (partial) list of available devices can be obtained with the
-.B \-\-list-devices
+.B --list-devices
 option (see below).  If no device-name is specified explicitly,
 .B scanimage
 reads a device-name from the environment variable
@ -88,7 +88,7 @@ If this variable is not set,
 will attempt to open the first available device.
 .PP
 The
-.B \-\-format 
+.B --format 
 .I format
 option selects how image data is written to standard output.
 .I format
@ -97,19 +97,19 @@ can be
 or
 .BR tiff.
 If
-.B \-\-format
+.B --format
 is not used, PNM is written.
 .PP
 The
-.B \-i
+.B -i
 or
-.B \-\-icc-profile
+.B --icc-profile
 option is used to include an ICC profile into a TIFF file.
 .PP
 The
-.B \-L
+.B -L
 or
-.B \-\-list-devices
+.B --list-devices
 option requests a (partial) list of devices that are available.  The
 list is not complete since some devices may be available, but are not
 listed in any of the configuration files (which are typically stored
@ -121,11 +121,11 @@ by its full device name.  You may need to consult your system administrator to
 find out the names of such devices.
 .PP
 The
-.B \-f
+.B -f
 or
-.B \-\-formatted-device-list
+.B --formatted-device-list
 option works similar to
-.BR \-\-list-devices ,
+.BR --list-devices ,
 but requires a format string.
 .B scanimage
 replaces the placeholders
@ -134,7 +134,7 @@ with the device name, vendor name, model name, scanner type and an index
 number respectively. The command
 .PP
 .RS
-.B scanimage \-f
+.B scanimage -f
 .I \*(lq scanner number %i device %d is a %t, model %m, produced by %v \*(rq
 .PP
 .RE
@ -146,43 +146,43 @@ SCSI, produced by SHARP
 .RE
 .PP
 The
-.B \-\-batch*
+.B --batch*
 options provide the features for scanning documents using document
 feeders.  
-.BR \-\-batch
+.BR --batch
 .RI [ format ]
 is used to specify the format of the filename that each page will be written
 to.  Each page is written out to a single file.  If
 .I format
-is not specified, the default of out%d.pnm (or out%d.tif for \-\-format tiff)
+is not specified, the default of out%d.pnm (or out%d.tif for --format tiff)
 will be used.  
 .I format
 is given as a printf style string with one integer parameter.
-.B \-\-batch-start
+.B --batch-start
 .I start
 selects the page number to start naming files with. If this option is not
 given, the counter will start at 0.
-.B \-\-batch-count
+.B --batch-count
 .I count
 specifies the number of pages to attempt to scan.  If not given, 
 scanimage will continue scanning until the scanner returns a state
 other than OK.  Not all scanners with document feeders signal when the
 ADF is empty, use this command to work around them.
 With 
-.B \-\-batch-increment
+.B --batch-increment
 .I increment
 you can change the amount that the number in the filename is incremented
 by.  Generally this is used when you are scanning double-sided documents
 on a single-sided document feeder.  A specific command is provided to
 aid this:
-.B \-\-batch-double
+.B --batch-double
 will automatically set the increment to 2.
-.B \-\-batch-prompt
+.B --batch-prompt
 will ask for pressing RETURN before scanning a page. This can be used for
 scanning multiple pages without an automatic document feeder.
 .PP
 The
-.B \-\-accept-md5-only
+.B --accept-md5-only
 option only accepts user authorization requests that support MD5 security. The
 .B SANE
 network daemon
@ -191,9 +191,9 @@ is capable of doing such requests. See
 .BR saned (8).
 .PP
 The
-.B \-p
+.B -p
 or
-.B \-\-progress
+.B --progress
 option requests that
 .B scanimage
 prints a progress counter. It shows how much image data of the current image has
@ -202,9 +202,9 @@ already been received by
 (in percent).
 .PP
 The
-.B \-n
+.B -n
 or
-.B \-\-dont-scan
+.B --dont-scan
 option requests that
 .B scanimage
 only sets the options provided by the user but doesn't actually perform a
@ -212,9 +212,9 @@ scan. This option can be used to e.g. turn off the scanner's lamp (if
 supported by the backend).
 .PP
 The
-.B \-T
+.B -T
 or
-.B \-\-test
+.B --test
 option requests that
 .B scanimage
 performs a few simple sanity tests to make sure the backend works as
@ -225,34 +225,34 @@ API (in particular the
 function is exercised by this test).
 .PP
 The
-.B \-h
+.B -h
 or
-.B \-\-help
+.B --help
 options request help information.  The information is printed on
 standard output and in this case, no attempt will be made to acquire
 an image.
 .PP
 The
-.B \-v
+.B -v
 or
-.B \-\-verbose
+.B --verbose
 options increase the verbosity of the operation of
 .B scanimage.
 The option may be specified repeatedly, each time increasing the verbosity
 level.
 .PP
 The
-.B \-B
+.B -B
 or
-.B \-\-buffersize
+.B --buffersize
 option changes the input buffersize that
 .B scanimage
 uses from default 32*1024 to 1024*1024 kbytes.
 .PP
 The
-.B \-V
+.B -V
 or
-.B \-\-version
+.B --version
 option requests that
 .B scanimage
 prints the program and package name, the version number of
@ -263,7 +263,7 @@ loads. Usually that's the dll backend. If more information about the version
 numbers of the backends are necessary, the
 .B DEBUG
 variable for the dll backend can be used. Example: SANE_DEBUG_DLL=3 scanimage
-\-L.
+-L.
 .PP
 As you might imagine, much of the power of
 .B scanimage
@ -277,49 +277,49 @@ invoke
 via a command-line of the form:
 .PP
 .RS
-.B scanimage \-\-help \-\-device-name
+.B scanimage --help --device-name
 .I dev
 .RE
 .PP
 The documentation for the device-specific options printed by
-.B \-\-help
+.B --help
 is best explained with a few examples:

- \-\-brightness -100..100% [0]
+ --brightness -100..100% [0]
 .br
    Controls the brightness of the acquired image.
 .PP
 .RS
 The description above shows that option
-.B \-\-brightness
+.B --brightness
 expects an option value in the range from -100 to 100 percent.  The
 value in square brackets indicates that the current option value is 0
 percent.
 .RE

- \-\-default-enhancements
+ --default-enhancements
 .br
    Set default values for enhancement controls.
 .PP
 .RS
 The description above shows that option
-.B \-\-default-enhancements
+.B --default-enhancements
 has no option value.  It should be thought of as having an immediate
 effect at the point of the command-line at which it appears.  For
 example, since this option resets the
-.B \-\-brightness
+.B --brightness
 option, the option-pair
-.B \-\-brightness 50 \-\-default-enhancements
+.B --brightness 50 --default-enhancements
 would effectively be a no-op.
 .RE

- \-\-mode Lineart|Gray|Color [Gray]
+ --mode Lineart|Gray|Color [Gray]
 .br
    Selects the scan mode (e.g., lineart or color).
 .PP
 .RS
 The description above shows that option
-.B \-\-mode
+.B --mode
 accepts an argument that must be one of the strings
 .BR Lineart ,
 .BR Gray ,
@ -331,12 +331,12 @@ set to
 For convenience, it is legal to abbreviate the string values as long as
 they remain unique.  Also, the case of the spelling doesn't matter.  For
 example, option setting
-.B \-\-mode col
+.B --mode col
 is identical to
-.BR "\-\-mode Color" .
+.BR "--mode Color" .
 .RE

- \-\-custom-gamma[=(yes|no)] [inactive]
+ --custom-gamma[=(yes|no)] [inactive]
 .br
    Determines whether a builtin or a custom gamma-table
 .br
@ -344,34 +344,34 @@ is identical to
 .PP
 .RS
 The description above shows that option
-.B \-\-custom-gamma
+.B --custom-gamma
 expects either no option value, a "yes" string, or a "no" string.
 Specifying the option with no value is equivalent to specifying "yes".
 The value in square-brackets indicates that the option is not
 currently active.  That is, attempting to set the option would result
 in an error message.  The set of available options typically depends
 on the settings of other options.  For example, the
-.B \-\-custom-gamma
+.B --custom-gamma
 table might be active only when a grayscale or color scan-mode has
 been requested.

 Note that the
-.B \-\-help
+.B --help
 option is processed only after all other options have been processed.
 This makes it possible to see the option settings for a particular
 mode by specifying the appropriate mode-options along
 with the
-.B \-\-help
+.B --help
 option.  For example, the command-line:
 .PP
-.B  scanimage \-\-help \-\-mode
+.B  scanimage --help --mode
 .I color
 .PP
 would print the option settings that are in effect when the color-mode
 is selected.
 .RE

- \-\-gamma-table 0..255,...
+ --gamma-table 0..255,...
 .br
    Gamma-correction table.  In color mode this option
 .br
@ -381,7 +381,7 @@ is selected.
 .PP
 .RS
 The description above shows that option
-.B \-\-gamma-table
+.B --gamma-table
 expects zero or more values in the range 0 to 255.  For example, a
 legal value for this option would be "3,4,5,6,7,8,9,10,11,12".  Since
 it's cumbersome to specify long vectors in this form, the same can be
@ -398,7 +398,7 @@ for details).
 .RE

 .br
- \-\-filename <string> [/tmp/input.ppm]
+ --filename <string> [/tmp/input.ppm]
 .br
    The filename of the image to be loaded.
 .PP
@ -428,7 +428,7 @@ user:password:resource
 .PP
 scanimage uses this information to answer user authorization requests
 automatically. The file must have 0600 permissions or stricter. You should
-use this file in conjunction with the \-\-accept-md5-only option to avoid
+use this file in conjunction with the --accept-md5-only option to avoid
 server-side attacks. The resource may contain any character but is limited
 to 127 characters.
 .SH "SEE ALSO"