Updated mustek_usb and plustek backend entries. Added FILES section. Minor

fixes and updates.
Henning Meier-Geinitz <henning@meier-geinitz.d>

doc/sane.man

@@ -1,4 +1,4 @@
-.TH sane 7 "24 Jan 2002"
+.TH sane 7 "11 Mar 2002"
 .IX sane
 
 .SH NAME
@@ -193,7 +193,8 @@ scanners. See sane-mustek_pp(5) for details.
 .TP
 .B mustek_usb
 The mustek_usb backend provides access to some Mustek USB flatbed
-scanners. See sane-mustek_usb(5) for details.
+scanners. Some Mustek BearPaw scanners are supported by the plustek backend,
+however. See sane-mustek_usb(5) for details.
 .TP
 .B nec
 The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See
@@ -204,8 +205,8 @@ The pie backend provides access to PIE and Devcom SCSI flatbed
 scanners. See sane-pie(5) for details.
 .TP
 .B plustek
-The SANE plustek backend supports Plustek parallel port scanners. See
-sane-plustek(5) for details.
+The SANE plustek backend supports Plustek parallel port and LM983[1/2/3] based
+USB flatbed scanners. See sane-plustek(5) for details.
 .TP
 .B ricoh
 The ricoh backend provides access to the following Ricoh flatbed
@@ -355,7 +356,8 @@ sane-find-scanner:\ found\ "MUSTEK\ MFC-06000CZ\ 1.01" at device /dev/scanner
 sane-find-scanner:\ found\ "MUSTEK\ MFC-06000CZ\ 1.01" at device /dev/sge
 .PP
 Note that sane-find-scanner will find any scanner that is connected to a SCSI
-bus.  It will even find scanners that are not supported at all by SANE.
+bus and also some USB scanners.  It will even find scanners that are not
+supported at all by SANE.
 
 There may be several causes for the following messages from the frontends:
 "scanimage: no SANE devices found" or "xscanimage: no devices available.".
@@ -366,7 +368,7 @@ ask the maintainer of your backend (see @DOCDIR@/AUTHORS) or the SANE mailing
 list (see above) if support is planned.
 .TP
 *
-SANE can't access the device files (e.g /dev/sga). Check the permissions.
+SANE can't access the device files (e.g /dev/sg0). Check the permissions.
 .TP
 *
 Your backend is not listed in @CONFIGDIR@/dll.conf (or commented out).
@@ -383,13 +385,28 @@ check that /etc/ld.so.conf contains /usr/local/lib and does
 .B not
 contain /usr/local/lib/sane. See also the documentation of the frontends.
 
+.SH FILES
+.TP
+.I @CONFIGDIR@/*.conf
+The backend configuration files.
+.TP
+.I @LIBDIR@/libsane-*.a
+The static libraries implementing the backends.
+.TP
+.I @LIBDIR@/libsane-*.so
+The shared libraries implementing the backends (present on systems that
+support dynamic loading).
+.TP
+.I @DOCDIR@/*
+SANE documentation: The standard, READMEs, text files for backends etc.
+
 .SH REPORTING BUGS
 If you think you found a bug in a backend, contact the author of your
 backend. Usually the email address can be found in the @DOCDIR@/AUTHORS
-file. If he isn't marked as `active maintainer' you can also contact the SANE
-mailing list sane-devel (see http://www.mostang.com/sane/mail.html for
-details). You must be subscribed to the list, otherwise your mail won't be
-sent to the subscribers.
+file. If he isn't marked as `active maintainer' or doesn't answer you can also
+contact the SANE mailing list sane-devel (see
+http://www.mostang.com/sane/mail.html for details). You must be subscribed to
+the list, otherwise your mail won't be sent to the subscribers.
 .P
 If you want to report bugs concerning compilation, installation, porting, and
 documentation of SANE, you can also contact the author of this manual page: