From 84c44d29d116324941bf35085810bc5e1b8afddc Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Sun, 7 Nov 2004 19:26:31 +0000 Subject: [PATCH] Updated man pages. --- man/gamma4scanimage.1.html | 2 +- man/sane-abaton.5.html | 2 +- man/sane-agfafocus.5.html | 2 +- man/sane-apple.5.html | 2 +- man/sane-artec.5.html | 2 +- man/sane-artec_eplus48u.5.html | 2 +- man/sane-as6e.5.html | 4 +- man/sane-avision.5.html | 67 ++-- man/sane-bh.5.html | 2 +- man/sane-canon.5.html | 2 +- man/sane-canon630u.5.html | 2 +- man/sane-canon_pp.5.html | 2 +- man/sane-config.1.html | 2 +- man/sane-coolscan.5.html | 2 +- man/sane-coolscan2.5.html | 119 +++---- man/sane-dc210.5.html | 2 +- man/sane-dc240.5.html | 2 +- man/sane-dc25.5.html | 2 +- man/sane-dll.5.html | 2 +- man/sane-dmc.5.html | 2 +- man/sane-epson.5.html | 2 +- man/sane-find-scanner.1.html | 27 +- man/sane-fujitsu.5.html | 2 +- man/sane-gphoto2.5.html | 2 +- man/sane-gt68xx.5.html | 135 ++++---- man/sane-hp.5.html | 2 +- man/sane-hp5400.5.html | 2 +- man/sane-hpsj5s.5.html | 2 +- man/sane-ibm.5.html | 2 +- man/sane-leo.5.html | 2 +- man/sane-ma1509.5.html | 2 +- man/sane-matsushita.5.html | 2 +- man/sane-microtek.5.html | 2 +- man/sane-microtek2.5.html | 2 +- man/sane-mustek.5.html | 8 +- man/sane-mustek_pp.5.html | 4 +- man/sane-mustek_usb.5.html | 6 +- man/sane-nec.5.html | 2 +- man/sane-net.5.html | 10 +- man/sane-niash.5.html | 15 +- man/sane-pie.5.html | 2 +- man/sane-pint.5.html | 2 +- man/sane-plustek.5.html | 83 ++--- man/sane-plustek_pp.5.html | 77 +++-- man/sane-pnm.5.html | 2 +- man/sane-qcam.5.html | 2 +- man/sane-ricoh.5.html | 2 +- man/sane-s9036.5.html | 2 +- man/sane-sceptre.5.html | 2 +- man/sane-scsi.5.html | 2 +- man/sane-sharp.5.html | 2 +- man/sane-sm3600.5.html | 2 +- man/sane-snapscan.5.html | 2 +- man/sane-sp15c.5.html | 2 +- man/sane-st400.5.html | 2 +- man/sane-tamarack.5.html | 2 +- man/sane-teco1.5.html | 2 +- man/sane-teco2.5.html | 62 ++-- man/sane-teco3.5.html | 2 +- man/sane-test.5.html | 2 +- man/sane-u12.5.html | 8 +- man/sane-umax.5.html | 2 +- man/sane-umax1220u.5.html | 2 +- man/sane-umax_pp.5.html | 114 ++++--- man/sane-usb.5.html | 128 +++---- man/sane-v4l.5.html | 2 +- man/sane.7.html | 586 --------------------------------- man/scanimage.1.html | 4 +- 68 files changed, 515 insertions(+), 1042 deletions(-) delete mode 100644 man/sane.7.html diff --git a/man/gamma4scanimage.1.html b/man/gamma4scanimage.1.html index 7d0a5bb3..6e42ce49 100644 --- a/man/gamma4scanimage.1.html +++ b/man/gamma4scanimage.1.html @@ -71,7 +71,7 @@

EMAIL-CONTACT

        Oliver.Rauch@Rauch-Domain.DE
 
-sane-backends 1.0.14-cvs          11 Sep 2002               gamma4scanimage(1)
+sane-backends 1.0.15              11 Sep 2002               gamma4scanimage(1)
diff --git a/man/sane-abaton.5.html b/man/sane-abaton.5.html index cb15dce8..bd36b6d6 100644 --- a/man/sane-abaton.5.html +++ b/man/sane-abaton.5.html @@ -142,7 +142,7 @@ The sane-abaton backend was partially written by David Huggins-Daines, based on the sane-apple backend by Milon Firikis. -sane-backends 1.0.14-cvs 19 Nov 1998 sane-abaton(5) +sane-backends 1.0.15 19 Nov 1998 sane-abaton(5)
diff --git a/man/sane-agfafocus.5.html b/man/sane-agfafocus.5.html index 4879b2e6..b1dff584 100644 --- a/man/sane-agfafocus.5.html +++ b/man/sane-agfafocus.5.html @@ -178,7 +178,7 @@

AUTHOR

        Ingo Schneider and Karl Anders Øygard.
 
-sane-backends 1.0.14-cvs          17 Oct 1998                sane-agfafocus(5)
+sane-backends 1.0.15              17 Oct 1998                sane-agfafocus(5)
diff --git a/man/sane-apple.5.html b/man/sane-apple.5.html index 388a440a..d7635bbe 100644 --- a/man/sane-apple.5.html +++ b/man/sane-apple.5.html @@ -283,7 +283,7 @@ Firikis. It is mostly based on the mustek backend from David Mosberger and Andreas Czechanowski -sane-backends 1.0.14-cvs 13 May 1998 sane-apple(5) +sane-backends 1.0.15 13 May 1998 sane-apple(5)
diff --git a/man/sane-artec.5.html b/man/sane-artec.5.html index 0573ba25..fbcde8e6 100644 --- a/man/sane-artec.5.html +++ b/man/sane-artec.5.html @@ -172,7 +172,7 @@

AUTHOR

        Chris Pinkham (cpinkham@corp.infi.net)
 
-sane-backends 1.0.14-cvs          24 Jan 2000                    sane-artec(5)
+sane-backends 1.0.15              24 Jan 2000                    sane-artec(5)
diff --git a/man/sane-artec_eplus48u.5.html b/man/sane-artec_eplus48u.5.html index c6b1ae62..1491f256 100644 --- a/man/sane-artec_eplus48u.5.html +++ b/man/sane-artec_eplus48u.5.html @@ -187,7 +187,7 @@ http://www.angelfire.com/linux/crapsite. Please contact me if you find a bug or missing feature: <crapsite@gmx.net> -sane-backends 1.0.14-cvs 19 Nov 2002 sane-artec_eplus48u(5) +sane-backends 1.0.15 19 Nov 2002 sane-artec_eplus48u(5)
diff --git a/man/sane-as6e.5.html b/man/sane-as6e.5.html index b8a82dc7..1f78a594 100644 --- a/man/sane-as6e.5.html +++ b/man/sane-as6e.5.html @@ -38,7 +38,7 @@

SEE ALSO

-       sane(7), as6edriver(5), saned(1), http://as6edriver.sourceforge.net
+       sane(7), as6edriver(5), saned(8), http://as6edriver.sourceforge.net
@@ -50,7 +50,7 @@

EMAIL-CONTACT

        yossarian@users.sourceforge.net
 
-sane-backends 1.0.14-cvs        Dec 14th, 2003                    sane-as6e(5)
+sane-backends 1.0.15            Dec 14th, 2003                    sane-as6e(5)
diff --git a/man/sane-avision.5.html b/man/sane-avision.5.html index c8d0f576..8609d481 100644 --- a/man/sane-avision.5.html +++ b/man/sane-avision.5.html @@ -13,8 +13,8 @@

NAME

        sane-avision  - SANE backend for original Avision and Avision OEM scan-
-       ners (HP, Minolta, Mitsubishi, UMAX and possibly  more)  flatbed  scan-
-       ners.
+       ners (HP, Minolta, Mitsubishi, UMAX and possibly more) flatbed and film
+       scanners.
@@ -29,8 +29,11 @@ backend that provides access to various Avision scanners and the Avi- sion OEM scanners labelled by HP, Minolta, Mitsubishi or Fujitsu. - I suggest you hold one hand on the power-button of the scanner while - you try the first scans! + It is fully big-endian aware and in every-day use on PowerPC and SPARC + systems. + + I suggest you hold one hand on the power-button of the scanner while + you try the first scans - especially with film-scanners! @@ -38,14 +41,15 @@ The configuration file for this backend resides in /usr/local/etc/sane.d/avision.conf. - Its contents is a list of device names that correspond to Avision and - Avision compatible scanners and backend-options. Empty lines and lines - starting with a hash mark (#) are ignored. A sample configuration file + Its contents is a list of device names that correspond to Avision and + Avision compatible scanners and backend-options. Empty lines and lines + starting with a hash mark (#) are ignored. A sample configuration file is shown below: # this is a comment option force-a4 + option force-a3 option disable-gamma-table option disable-calibration option one-calib-only @@ -59,10 +63,17 @@ - force-a4: Forces the backend to overwrite the scanable area - returned by the scanner. This might be needed for - the AV 630 which returns no area - or newer scanners - which retun the area in a unkown format our backend - doesn't recongize yet. + returned by the scanner to ISO A4. Scanner that are + known to return bogus data are marked in the backend + so if you need this option please report this to the + backend maintainer. USE WITH CARE! + + - force-a3: + Forces the backend to overwrite the scanable area + returned by the scanner to ISO A3. Scanner that are + known to return bogus data are marked in the backend + so if you need this option please report this to the + backend maintainer. USE WITH CARE! - disable-gamma-table: Disables the usage of the scanner's gamma-table. You @@ -103,10 +114,10 @@ usb usb-sec Where 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 exam- + 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 exam- ple 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 + by the scanner, for example "HP" or "AVISION". See sane-scsi(5) for details. Note: Since the backend now includes native USB access, @@ -116,7 +127,7 @@ the HP 53xx, HP 74xx or Minolta film-scanners. 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 + used by libusb corresponding to the USB scanner. For example "0x03f0 0x0701" or "libusb:002:003". See sane-usb(5) for details. The program sane-find-scanner helps to find out the correct scsi or usb @@ -129,7 +140,7 @@

FILES

        /usr/local/etc/sane.d/avision.conf
-              The  backend  configuration  file  (see  also   description   of
+              The   backend   configuration  file  (see  also  description  of
               SANE_CONFIG_DIR below).
 
        /usr/local/lib/sane/libsane-avision.a
@@ -145,22 +156,22 @@
        SANE_CONFIG_DIR
               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
+              are  separated  by a colon (`:'), under OS/2, they are separated
               by a semi-colon (`;').  If this variable is not set, the config-
-              uration file is searched in two default directories: first,  the
-              current     working     directory     (".")    and    then    in
+              uration  file is searched in two default directories: first, the
+              current    working    directory    (".")     and     then     in
               /usr/local/etc/sane.d.  If the value of the environment variable
-              ends  with  the  directory separator character, then the default
+              ends with the directory separator character,  then  the  default
               directories are searched after the explicitly specified directo-
-              ries.   For  example,  setting SANE_CONFIG_DIR to "/tmp/config:"
-              would   result   in   directories   "tmp/config",    ".",    and
+              ries.  For example, setting  SANE_CONFIG_DIR  to  "/tmp/config:"
+              would    result    in   directories   "tmp/config",   ".",   and
               "/usr/local/etc/sane.d" being searched (in this order).
 
        SANE_DEBUG_AVISION
-              If  the  library  was  compiled with debug support enabled, this
-              environment variable controls the debug level for this  backend.
-              Higher  debug  levels  increase the verbosity of the output. The
-              debug level 7 is the author's prefered value  to  debug  backend
+              If the library was compiled with  debug  support  enabled,  this
+              environment  variable controls the debug level for this backend.
+              Higher debug levels increase the verbosity of  the  output.  The
+              debug  level  7  is the author's prefered value to debug backend
               problems.
 
               Example: export SANE_DEBUG_AVISION=7
@@ -169,14 +180,14 @@

SEE ALSO

        sane(7), sane-scsi(5), sane-usb(5)
-       http://www.rocklinux-consulting.de/oss/avision/
+       http://www.exactcode.de/oss/avision/

AUTHOR

        René Rebe and Meino Christian Cramer
 
-sane-backends 1.0.14-cvs          04 Mar 2003                  sane-avision(5)
+sane-backends 1.0.15              04 Mar 2003                  sane-avision(5)
diff --git a/man/sane-bh.5.html b/man/sane-bh.5.html index 84f583b9..90bce1bc 100644 --- a/man/sane-bh.5.html +++ b/man/sane-bh.5.html @@ -502,7 +502,7 @@ Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark Temple. -sane-backends 1.0.14-cvs 15 Sep 1999 sane-bh(5) +sane-backends 1.0.15 15 Sep 1999 sane-bh(5)
diff --git a/man/sane-canon.5.html b/man/sane-canon.5.html index 49a62e0a..301eb359 100644 --- a/man/sane-canon.5.html +++ b/man/sane-canon.5.html @@ -108,7 +108,7 @@ support by Mitsuru Okaniwa; FS2710S support by Ulrich Deiters Man page by Henning Meier-Geinitz (mostly based on canon.README) -sane-backends 1.0.14-cvs 03 May 2001 sane-canon(5) +sane-backends 1.0.15 03 May 2001 sane-canon(5)
diff --git a/man/sane-canon630u.5.html b/man/sane-canon630u.5.html index 01f9ab20..2fb5577e 100644 --- a/man/sane-canon630u.5.html +++ b/man/sane-canon630u.5.html @@ -117,7 +117,7 @@

AUTHOR

        Nathan Rutman
 
-sane-backends 1.0.14-cvs          06 Apr 2002                sane-canon630u(5)
+sane-backends 1.0.15              06 Apr 2002                sane-canon630u(5)
diff --git a/man/sane-canon_pp.5.html b/man/sane-canon_pp.5.html index e7114d75..f95e7b6f 100644 --- a/man/sane-canon_pp.5.html +++ b/man/sane-canon_pp.5.html @@ -222,7 +222,7 @@ Many thanks to Kevin Easton for his comments and help, and Kent A. Sig- norini for his help with the N340P. -sane-backends 1.0.14-cvs 1 October 2002 sane-canon_pp(5) +sane-backends 1.0.15 1 October 2002 sane-canon_pp(5)
diff --git a/man/sane-config.1.html b/man/sane-config.1.html index 7e4a6812..0e622b32 100644 --- a/man/sane-config.1.html +++ b/man/sane-config.1.html @@ -69,7 +69,7 @@ This manual page was written by Julien BLACHE <jblache@debian.org>, for the Debian GNU/Linux system (but may be used by others). -sane-backends 1.0.14-cvs 8 Jan 2004 sane-config(1) +sane-backends 1.0.15 8 Jan 2004 sane-config(1)
diff --git a/man/sane-coolscan.5.html b/man/sane-coolscan.5.html index d5eca9ff..9bcfff7d 100644 --- a/man/sane-coolscan.5.html +++ b/man/sane-coolscan.5.html @@ -122,7 +122,7 @@

EMAIL-CONTACT

        andreas.rick@free.fr
 
-sane-backends 1.0.14-cvs          4 July 2000                 sane-coolscan(5)
+sane-backends 1.0.15              4 July 2000                 sane-coolscan(5)
diff --git a/man/sane-coolscan2.5.html b/man/sane-coolscan2.5.html index 3b3200aa..0766817d 100644 --- a/man/sane-coolscan2.5.html +++ b/man/sane-coolscan2.5.html @@ -17,12 +17,13 @@

DESCRIPTION

-       The  library  implements  a SANE (Scanner Access Now Easy) backend that
-       provides access to Nikon Coolscan film  scanners.   Some  functions  of
-       this backend should be considered beta-quality software. Most functions
-       have been stable for a long time, but of course new development can not
-       and  will  not function properly from the very first day. Please report
-       any strange behaviour to the maintainer of the backend.
+       The  sane-coolscan2 library implements a SANE (Scanner Access Now Easy)
+       backend that provides access to Nikon  Coolscan  film  scanners.   Some
+       functions  of  this backend should be considered beta-quality software.
+       Most functions have been stable for a long  time,  but  of  course  new
+       development  can not and will not function properly from the very first
+       day. Please report any strange behaviour to the maintainer of the back-
+       end.
 
        At present, the following scanners are known to work with this backend:
 
@@ -34,109 +35,109 @@
               LS-4000 ED                   IEEE 1394
               LS-8000 ED                   IEEE 1394
 
-       Please  send  mail to the backend author (andras@users.sourceforge.net)
+       Please send mail to the backend  author  (andras@users.sourceforge.net)
        to report successes or failures.

OPTIONS

        The options the backend supports can either be selected through command
-       line  options  to  programs  like  scanimage or through GUI elements in
+       line options to programs like scanimage  or  through  GUI  elements  in
        xscanimage or xsane.
 
        Valid command line options and their syntax can be listed by using
               scanimage --help -d coolscan2:<interface>:<device>
-       where <interface> and <device> specify the device in  question,  as  in
-       the  configuration  file (see next section). The "-d" parameter and its
-       argument can be omitted to obtain  information  on  the  first  scanner
+       where  <interface>  and  <device> specify the device in question, as in
+       the configuration file (see next section). The "-d" parameter  and  its
+       argument  can  be  omitted  to  obtain information on the first scanner
        identified. Use the command
               scanimage -L
        to list all devices recognized by your SANE installation.
 
-       The  options  should  be fully described by the description or tooltips
-       given by frontend. Here is a description of some of the most  important
+       The options should be fully described by the  description  or  tooltips
+       given  by frontend. Here is a description of some of the most important
        options, in the syntax with which they must be supplied to scanimage:
 
        --frame <n>
-              This  option specifies which frame to operate on, if a motorized
-              film strip feeder or APS adapter are used. The frame number  <n>
+              This option specifies which frame to operate on, if a  motorized
+              film  strip feeder or APS adapter are used. The frame number <n>
               ranges from 1 to the number of frames available, which is sensed
-              each time the backend is  initialized  (usually  each  time  you
+              each  time  the  backend  is  initialized (usually each time you
               start the frontend).
 
        --subframe <x>
-              This  option  shifts  the  scan  window  by the specified amount
+              This option shifts the  scan  window  by  the  specified  amount
               (default unit is mm).
 
        --infrared=yes/no
-              If set to "yes", the scanner will  read  the  infrared  channel,
-              thus  allowing defect removal in software. The infrared image is
-              read during a second scan, with no options altered. The  backend
-              must  not be restarted between the scans.  If you use scanimage,
-              perform a batch scan with batch-count=2 to obtain the IR  infor-
-              mation.
+              If  set  to  "yes",  the scanner will read the infrared channel,
+              thus allowing defect removal in software. The infrared image  is
+              read  during a second scan, with no options altered. The backend
+              must not be restarted between the scans.  If you use  scanimage,
+              perform  a  batch  scan  with  batch-count=2  to  obtain  the IR
+              information.
 
        --depth <n>
               Here <n> can either be 8 or the maximum number of bits supported
-              by the scanner (10, 12, or 14). It specifies whether or not  the
-              scanner  reduces the scanned data to 8 bits before sending it to
+              by  the scanner (10, 12, or 14). It specifies whether or not the
+              scanner reduces the scanned data to 8 bits before sending it  to
               the backend. If 8 bits are used, some information and thus image
-              quality  is  lost, but the amount of data is smaller compared to
-              higher depths. Also, many imaging  programs  and  image  formats
+              quality is lost, but the amount of data is smaller  compared  to
+              higher  depths.  Also,  many  imaging programs and image formats
               cannot handle depths greater than 8 bits.
 
        --autofocus
-              Perform  autofocus  operation. Unless otherwise specified by the
+              Perform autofocus operation. Unless otherwise specified  by  the
               other options ( --focus-on-centre and friends), focusing is per-
               formed on the centre of the selected scan area.
 
        --ae-wb
 
-       --ae   Perform  a  pre-scan to calculate exposure values automatically.
-              --ae-wb will maintain the white balance, while --ae will  adjust
+       --ae   Perform a pre-scan to calculate exposure  values  automatically.
+              --ae-wb  will maintain the white balance, while --ae will adjust
               each channel separately.
 
        --exposure
-              Multiply  all  exposure times with this value. This allows expo-
+              Multiply all exposure times with this value. This  allows  expo-
               sure correction without modifying white balance.
 
        --load Load the next slide when using the slide loader.
 
        --eject
-              Eject the film strip or  mounted  slide  when  using  the  slide
+              Eject  the  film  strip  or  mounted  slide when using the slide
               loader.
 
        --reset
-              Reset  scanner. The scanner will perform the same action as when
-              power is turned on: it will eject the film strip  and  calibrate
-              itself.  Use  this  whenever  the scanner refuses to load a film
+              Reset scanner. The scanner will perform the same action as  when
+              power  is  turned on: it will eject the film strip and calibrate
+              itself. Use this whenever the scanner refuses  to  load  a  film
               strip properly, as a result of which --eject does not work.

CONFIGURATION FILE

-       The configuration file  /usr/local/etc/sane.d/coolscan2.conf  specifies
-       the  device(s)  that  the  backend will use. Owing to the nature of the
-       supported connection types SCSI, USB, and IEEE 1394, the  default  con-
+       The  configuration  file /usr/local/etc/sane.d/coolscan2.conf specifies
+       the device(s) that the backend will use. Owing to  the  nature  of  the
+       supported  connection  types SCSI, USB, and IEEE 1394, the default con-
        figuration file supplied with the SANE distribution should work without
        being edited.
 
-       Each line in the configuration file is either of the  following,  where
+       Each  line  in the configuration file is either of the following, where
        all entries are case-sensitive:
 
        blank or starting with a '#' character
-              These  lines  are  ignored, thus '#' can be used to include com-
+              These lines are ignored, thus '#' can be used  to  include  com-
               ments.
 
        containing only the word "auto"
-              This instructs the backend to probe for a  scanner  by  scanning
-              the  buses for devices with know identifiers. This is the action
+              This  instructs  the  backend to probe for a scanner by scanning
+              the buses for devices with know identifiers. This is the  action
               taken when no configuration file is present.
 
        a line of the form <interface>:<device>
-              Here <interface> can be one of "scsi" or "usb", and <device>  is
-              the  device file of the scanner. Note that IEEE 1394 devices are
-              handled by the SBP-2 module in the kernel and appear to SANE  as
+              Here  <interface> can be one of "scsi" or "usb", and <device> is
+              the device file of the scanner. Note that IEEE 1394 devices  are
+              handled  by the SBP-2 module in the kernel and appear to SANE as
               SCSI devices.
 
 
@@ -150,16 +151,16 @@
               that support dynamic loading).
 
        /usr/local/etc/sane.d/coolscan2.conf
-              Configuration file for this backend, read each time the  backend
+              Configuration  file for this backend, read each time the backend
               is initialized.

ENVIRONMENT

        SANE_DEBUG_COOLSCAN2
-              If  the  library  was  compiled with debug support enabled, this
-              environment variable controls the debug level for this  backend.
-              E.g.,  a  value  of 128 requests all debug output to be printed.
+              If the library was compiled with  debug  support  enabled,  this
+              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.
 
 
@@ -170,29 +171,29 @@

BUGS

-       Currently, the SANE protocol  does  not  allow  automatically  updating
-       options  whenever  the hardware changes. Thus the number of choices for
-       the --frame option will be fixed when the backend is initialized  (usu-
-       ally  when  the  user runs the frontend). In particular, if there is no
-       film strip in the automatic film strip feeder when the backend is  ini-
+       Currently,  the  SANE  protocol  does  not allow automatically updating
+       options whenever the hardware changes. Thus the number of  choices  for
+       the  --frame option will be fixed when the backend is initialized (usu-
+       ally when the user runs the frontend). In particular, if  there  is  no
+       film  strip in the automatic film strip feeder when the backend is ini-
        tialized, the frame option will not appear at all. Also, restarting the
        frontend after swapping film adapters is strongly recommended.
 
-       Linux kernels prior to 2.4.19 had a patch that truncated  INQUIRY  data
+       Linux  kernels  prior to 2.4.19 had a patch that truncated INQUIRY data
        from IEEE 1394 scanners to 36 bytes, discarding vital information about
-       the scanner. The IEEE 1394 models therefore only work  with  2.4.19  or
+       the  scanner.  The  IEEE 1394 models therefore only work with 2.4.19 or
        later.
 
-       No  real  bugs  currently known, please report any to the backend main-
+       No real bugs currently known, please report any to  the  backend  main-
        tainer or the SANE developers' email list.

AUTHORS

-       The   backend   is   written   and   maintained   by    András    Major
+       The    backend    is   written   and   maintained   by   András   Major
        (andras@users.sourceforge.net).
 
-sane-backends 1.0.14-cvs          22/08/2002                 sane-coolscan2(5)
+sane-backends 1.0.15              22/08/2002                 sane-coolscan2(5)
diff --git a/man/sane-dc210.5.html b/man/sane-dc210.5.html index 7b265046..1141f475 100644 --- a/man/sane-dc210.5.html +++ b/man/sane-dc210.5.html @@ -123,7 +123,7 @@ be subscribed to the list, otherwise your mail won't be sent to the subscribers. -sane-backends 1.0.14-cvs 15 July 2000 sane-dc210(5) +sane-backends 1.0.15 15 July 2000 sane-dc210(5)
diff --git a/man/sane-dc240.5.html b/man/sane-dc240.5.html index fe6ba23f..ffaf2e42 100644 --- a/man/sane-dc240.5.html +++ b/man/sane-dc240.5.html @@ -126,7 +126,7 @@ be subscribed to the list, otherwise your mail won't be sent to the subscribers. -sane-backends 1.0.14-cvs 23 March 2001 sane-dc240(5) +sane-backends 1.0.15 23 March 2001 sane-dc240(5)
diff --git a/man/sane-dc25.5.html b/man/sane-dc25.5.html index bdcc2447..3efdd4a0 100644 --- a/man/sane-dc25.5.html +++ b/man/sane-dc25.5.html @@ -116,7 +116,7 @@ be subscribed to the list, otherwise your mail won't be sent to the subscribers. -sane-backends 1.0.14-cvs 12 April 1999 sane-dc25(5) +sane-backends 1.0.15 12 April 1999 sane-dc25(5)
diff --git a/man/sane-dll.5.html b/man/sane-dll.5.html index 28106f31..97eacc71 100644 --- a/man/sane-dll.5.html +++ b/man/sane-dll.5.html @@ -148,7 +148,7 @@

AUTHOR

        David Mosberger
 
-sane-backends 1.0.14-cvs          4 Dec 2002                       sane-dll(5)
+sane-backends 1.0.15              4 Dec 2002                       sane-dll(5)
diff --git a/man/sane-dmc.5.html b/man/sane-dmc.5.html index 138fcb26..34880be8 100644 --- a/man/sane-dmc.5.html +++ b/man/sane-dmc.5.html @@ -159,7 +159,7 @@ The backend is derived from sane-hp by David Mosberger -sane-backends 1.0.14-cvs 13 May 1998 sane-dmc(5) +sane-backends 1.0.15 13 May 1998 sane-dmc(5)
diff --git a/man/sane-epson.5.html b/man/sane-epson.5.html index 08522b61..87c76f3e 100644 --- a/man/sane-epson.5.html +++ b/man/sane-epson.5.html @@ -284,7 +284,7 @@ The package is actively maintained by Karl Heinz Kremer (khk@khk.net). The software is based on work by Christian Bucher and Kazuhiro Sasayama -sane-backends 1.0.14-cvs 27-Dec-2000 sane-epson(5) +sane-backends 1.0.15 27-Dec-2000 sane-epson(5)
diff --git a/man/sane-find-scanner.1.html b/man/sane-find-scanner.1.html index d0261aa8..202d32a8 100644 --- a/man/sane-find-scanner.1.html +++ b/man/sane-find-scanner.1.html @@ -17,7 +17,7 @@

SYNOPSIS

-       sane-find-scanner [-h|-?]  [-v] [-q] [-p] [-f] [devname]
+       sane-find-scanner [-h|-?]  [-v] [-q] [-p] [-f] [-F filename] [devname]
@@ -69,14 +69,22 @@ devices. That's useful if sane-find-scanner is wrong in determing the device type. - devname Test device file "devname". No other devices are checked if + -F filename + filename is a file that contains USB descriptors in the format + of /proc/bus/usb/devices as used by Linux. sane-find-scanner + tries to identify the chipset(s) of all USB scanners found in + such a file. This option is useful for developers when the out- + put of "cat /proc/bus/usb/devices" is avaliable but the scanner + itsself isn't. + + devname Test device file "devname". No other devices are checked if devname is given.

EXAMPLE

        sane-find-scanner -v
-       Check all SCSI and USB devices for available scanners and print a  line
+       Check  all SCSI and USB devices for available scanners and print a line
        for every device file.
 
        sane-find-scanner /dev/scanner
@@ -88,7 +96,7 @@

SEE ALSO

-       sane(7),   sane-scsi(5),   sane-usb(5),   scanimage(1),  xscanimage(1),
+       sane(7),  sane-scsi(5),   sane-usb(5),   scanimage(1),   xscanimage(1),
        xsane(1), sane-"backendname"(5)
 
 
@@ -99,21 +107,20 @@

SUPPORTED PLATFORMS

-       USB support is limited to  Linux  (kernel,  libusb),  FreeBSD  (kernel,
-       libusb),  NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the ven-
+       USB  support  is  limited  to  Linux (kernel, libusb), FreeBSD (kernel,
+       libusb), NetBSD (libusb), OpenBSD (kernel, libusb). Detecting the  ven-
        dor and device ids only works with Linux or libusb.
 
-       SCSI support is available on Irix,  EMX,  Linux,  Next,  AIX,  Solaris,
+       SCSI  support  is  available  on  Irix, EMX, Linux, Next, AIX, Solaris,
        FreeBSD, NetBSD, OpenBSD, and HP-UX.

BUGS

        No support for most parallel port scanners yet.
-       Detection of USB chipsets is limited to GrandTech 6801 and 6816, Mustek
-       chips and National Semiconductor lm983x chips.
+       Detection of USB chipsets is limited to a few chipsets.
 
-sane-backends 1.0.14-cvs          18 Jul 2003             sane-find-scanner(1)
+sane-backends 1.0.15              4 Oct 2004              sane-find-scanner(1)
diff --git a/man/sane-fujitsu.5.html b/man/sane-fujitsu.5.html index e3dbc39f..9b39bbd5 100644 --- a/man/sane-fujitsu.5.html +++ b/man/sane-fujitsu.5.html @@ -157,7 +157,7 @@ them yet. I don't know if the ScanPartner 15C still works, because I'm not able to test it. 3091/3092 don't support halftone -sane-backends 1.0.14-cvs 17 Apr 2002 sane-fujitsu(5) +sane-backends 1.0.15 17 Apr 2002 sane-fujitsu(5)
diff --git a/man/sane-gphoto2.5.html b/man/sane-gphoto2.5.html index 4c25b670..c1f7406e 100644 --- a/man/sane-gphoto2.5.html +++ b/man/sane-gphoto2.5.html @@ -131,7 +131,7 @@ be subscribed to the list, otherwise your mail won't be sent to the subscribers. -sane-backends 1.0.14-cvs 04 September 2001 sane-gphoto2(5) +sane-backends 1.0.15 04 September 2001 sane-gphoto2(5)
diff --git a/man/sane-gt68xx.5.html b/man/sane-gt68xx.5.html index 4adda697..3eb31c20 100644 --- a/man/sane-gt68xx.5.html +++ b/man/sane-gt68xx.5.html @@ -32,6 +32,7 @@ Genius Colorpage Vivid4 Genius Colorpage Vivid4x Genius Colorpage Vivid4xe + Genius Colorpage Vivid 1200 xe Googlegear 2000 Lexmark X70 Lexmark X73 @@ -47,8 +48,11 @@ Mustek BearPaw 2400 TA (Plus) Mustek BearPaw 2448 CS Plus Mustek BearPaw 2448 TA Plus + Mustek Plug-n-Scan 2400 M + Plug-n-Scan 2400 MT Mustek ScanExpress A3 USB Mustek ScanExpress 1200 UB Plus + Mustek ScanExpress 1248 UB Mustek ScanExpress 2400 USB Mustek ScanMagic 1200 UB Plus Packard Bell Diamond 1200 (Plus) @@ -61,6 +65,7 @@ RevScan 19200i Trust Compact Scan USB 19200 Trust Flat Scan USB 19200 + Trust 240TH Easy Webscan Gold More details can be found on the gt68xx backend homepage http://www.meier-geinitz.de/sane/gt68xx/. @@ -79,82 +84,87 @@ scanner's name is only slightly different from the models mentioned above, please let me know. + If you own a scanner that isn't detected by the gt68xx backend but has + a GT-6801 or GT-6816 chipset, you can try to add it to the backend. + Have a look at the following web page: http://www.meier- + geinitz.de/sane/gt68xx-backend/adding.html +

KERNEL ISSUES

        If libusb-0.1.6 or later is installed, this section can be skipped. The
-       scanner should be found by sane-find-scanner without  further  actions.
-       For   setting   permissions   and  general  USB  information  looks  at
+       scanner  should  be found by sane-find-scanner without further actions.
+       For  setting  permissions  and  general  USB   information   looks   at
        sane-usb(5).
 
-       The scanners based on the GT-6816 (Mustek BearPaw TA and  BearPaw  Plus
-       models,  the  Packard Bell and the Lexmark scanner) need a Linux kernel
-       2.4.12 or newer.  Recent 2.2 kernels  may  also  work,  but  I  haven't
-       tested  them.  Older kernels or other operating systems won't work. Use
+       The  scanners  based on the GT-6816 (Mustek BearPaw TA and BearPaw Plus
+       models, the Packard Bell and the Lexmark scanner) need a  Linux  kernel
+       2.4.12  or  newer.   Recent  2.2  kernels  may also work, but I haven't
+       tested them. Older kernels or other operating systems won't  work.  Use
        libusb instead.
 
-       The scanners based on the GT-6801 (all other scanners) need Linux  ker-
+       The  scanners based on the GT-6801 (all other scanners) need Linux ker-
        nel 2.4.21 or newer. Older kernels will not work.

FIRMWARE FILE

        You need a firmware file for your scanner. That's a small file contain-
-       ing software that will be uploaded to the scanner's memory.  It's  usu-
-       ally  named  *.usb,  e.g.   PS1fw.usb.  It comes on the installation CD
-       that was provided by the manufacturer, but it may be packaged  together
+       ing  software  that will be uploaded to the scanner's memory. It's usu-
+       ally named *.usb, e.g.  PS1fw.usb.  It comes  on  the  installation  CD
+       that  was provided by the manufacturer, but it may be packaged together
        with the installation program in an .exe file. For Mustek scanners, the
        file can be dowloaded from the gt68xx backend homepage. For other scan-
-       ners,  check  the CD for .usb files. If everything else fails, you must
-       install the Windows driver and get the firmware from there (usually  in
-       the  windows/system  or  system32  directories). Put that firmware file
-       into /usr/local/share/sane/gt68xx/.  Make sure that  it's  readable  by
+       ners, check the CD for .usb files. If everything else fails,  you  must
+       install  the Windows driver and get the firmware from there (usually in
+       the windows/system or system32 directories).  Put  that  firmware  file
+       into  /usr/local/share/sane/gt68xx/.   Make  sure that it's readable by
        everyone.

CONFIGURATION

-       The  contents of the gt68xx.conf file is a list of usb lines containing
-       vendor and product ids that correspond to USB scanners.  The  file  can
-       also  contain option lines.  Empty lines and lines starting with a hash
-       mark (#) are ignored.  The scanners are autodetected by  usb  vendor_id
-       product_id  statements  which  are  already  included into gt68xx.conf.
-       "vendor_id" and "product_id" are hexadecimal numbers that  identfy  the
+       The contents of the gt68xx.conf file is a list of usb lines  containing
+       vendor  and  product  ids that correspond to USB scanners. The file can
+       also contain option lines.  Empty lines and lines starting with a  hash
+       mark  (#)  are ignored.  The scanners are autodetected by usb vendor_id
+       product_id statements which  are  already  included  into  gt68xx.conf.
+       "vendor_id"  and  "product_id" are hexadecimal numbers that identfy the
        scanner.
 
-       The  override,  firmware, vendor, model, and afe options must be placed
+       The override, firmware, vendor, model, and afe options must  be  placed
        after the usb line they refer to.
 
-       Option override is used  to  override  the  default  model  parameters.
+       Option  override  is  used  to  override  the default model parameters.
        That's necessary for some scanners that use the same vendor/product ids
-       but are different. For these scanners there are already  commented  out
-       override  lines  in  the  configuration  file.  override mustek-scanex-
-       press-1200-ub-plus is necessary for  the  Mustek  Scanexpress  1200  UB
+       but  are  different. For these scanners there are already commented out
+       override lines in  the  configuration  file.   override  mustek-scanex-
+       press-1200-ub-plus  is  necessary  for  the  Mustek Scanexpress 1200 UB
        Plus, the Medion/Lifetec/Tevion LT 9452, and the Trust Compact Scan USB
-       19200.  override artec-ultima-2000 is used for the Artec  Ultima  2000,
-       the  Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/ Cytron
-       MD/LT 9385, the Medion/ Lifetec/ Tevion MD 9458,  and  the  Trust  Flat
-       Scan  USB  19200.  override mustek-bearpaw-2400-cu is necessary for the
-       Mustek BearPaw 2400 CU and the Fujitsu  1200CUS.  The  override  option
+       19200.   override  artec-ultima-2000 is used for the Artec Ultima 2000,
+       the Boeder SmartScan Slim Edition, the Medion/ Lifetec/ Tevion/  Cytron
+       MD/LT  9385,  the  Medion/  Lifetec/ Tevion MD 9458, and the Trust Flat
+       Scan USB 19200.  override mustek-bearpaw-2400-cu is necessary  for  the
+       Mustek  BearPaw  2400  CU  and the Fujitsu 1200CUS. The override option
        must be the first one after the usb line.
 
-       Option  firmware  selects  the name and path of the firmware file. It's
-       only necessary if the default (or override) doesn't work.  The  default
-       firmware  directory  is /usr/local/share/sane/gt68xx/.  You may need to
-       create this directory. If you want to place the  firmware  files  at  a
+       Option firmware selects the name and path of the  firmware  file.  It's
+       only  necessary  if the default (or override) doesn't work. The default
+       firmware directory is /usr/local/share/sane/gt68xx/.  You may  need  to
+       create  this  directory.  If  you want to place the firmware files at a
        different path, use a firmware line.
 
-       The  vendor and model options are not absolutely necessary but for con-
-       venience. Quite a lot of scanners from  different  manufacturers  share
+       The vendor and model options are not absolutely necessary but for  con-
+       venience.  Quite  a  lot of scanners from different manufacturers share
        the same vendor/product ids so you can set the "correct" name here.
 
        The afe option allows to set custom offset and gain values for the Ana-
-       log FrontEnd of the scanner. This option can be either used  to  select
-       the  AFE values if automatic coarse calibration is disabled, or to make
+       log  FrontEnd  of the scanner. This option can be either used to select
+       the AFE values if automatic coarse calibration is disabled, or to  make
        automatic coarse calibration faster. For the latter usage, enable debug
-       level  3 (see below), scan an image and look for debug line string with
-       "afe". Copy this line to gt68xx.conf.  The option has  six  parameters:
-       red  offset,  red gain, green offset, green gain, blue offset, and blue
+       level 3 (see below), scan an image and look for debug line string  with
+       "afe".  Copy  this line to gt68xx.conf.  The option has six parameters:
+       red offset, red gain, green offset, green gain, blue offset,  and  blue
        gain.
 
        A sample configuration file is shown below:
@@ -170,7 +180,7 @@

FILES

        /usr/local/etc/sane.d/gt68xx.conf
-              The  backend  configuration  file  (see  also   description   of
+              The   backend   configuration  file  (see  also  description  of
               SANE_CONFIG_DIR below).
 
        /usr/local/lib/sane/libsane-gt68xx.a
@@ -186,22 +196,22 @@
        SANE_CONFIG_DIR
               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
+              are  separated  by a colon (`:'), under OS/2, they are separated
               by a semi-colon (`;').  If this variable is not set, the config-
-              uration file is searched in two default directories: first,  the
-              current     working     directory     (".")    and    then    in
+              uration  file is searched in two default directories: first, the
+              current    working    directory    (".")     and     then     in
               /usr/local/etc/sane.d.  If the value of the environment variable
-              ends  with  the  directory separator character, then the default
+              ends with the directory separator character,  then  the  default
               directories are searched after the explicitly specified directo-
-              ries.   For  example,  setting SANE_CONFIG_DIR to "/tmp/config:"
-              would   result   in   directories   "tmp/config",    ".",    and
+              ries.  For example, setting  SANE_CONFIG_DIR  to  "/tmp/config:"
+              would    result    in   directories   "tmp/config",   ".",   and
               "/usr/local/etc/sane.d" being searched (in this order).
 
        SANE_DEBUG_GT68XX
-              If  the  library  was  compiled with debug support enabled, this
-              environment variable controls the debug level for this  backend.
+              If the library was compiled with  debug  support  enabled,  this
+              environment  variable controls the debug level for this backend.
               Higher debug levels increase the verbosity of the output. If the
-              debug level is set to 1 or higher,  some  debug  options  become
+              debug  level  is  set  to 1 or higher, some debug options become
               available that are normally hidden. Handle them with care.
 
               Example: export SANE_DEBUG_GT68XX=4
@@ -209,41 +219,40 @@

SEE ALSO

-       sane(7),     sane-usb(5),    sane-artec_eplus48u(5)    sane-plustek(5),
+       sane(7),    sane-usb(5),    sane-artec_eplus48u(5)     sane-plustek(5),
        sane-ma1509(5), sane-mustek_usb(5), sane-mustek(5), sane-mustek_pp(5)
-       /usr/local/doc/sane-1.0.14-cvs/gt68xx/gt68xx.CHANGES
+       /usr/local/doc/sane-1.0.15/gt68xx/gt68xx.CHANGES
        http://www.meier-geinitz.de/sane/gt68xx
 
 
-

AUTHOR

        Henning Meier-Geinitz <henning@meier-geinitz.de>
-       The original gt68xx  driver  was  written  by  Sergey  Vlasov,  Andreas
-       Nowack,  and  David Stevenson. Thanks for sending patches and answering
+       The  original  gt68xx  driver  was  written  by  Sergey Vlasov, Andreas
+       Nowack, and David Stevenson. Thanks for sending patches  and  answering
        questions to them and all the other contributors.

BUGS

-       Currently scanning seems  to  only  work  reliably  under  Linux.  With
-       FreeBSD,  NetBSD and OpenBSD scanning works only once. Then the scanner
+       Currently  scanning  seems  to  only  work  reliably  under Linux. With
+       FreeBSD, NetBSD and OpenBSD scanning works only once. Then the  scanner
        isn't detected anymore and has to be replugged.
 
        The first few lines of the image are garbage for the 2400 TA Plus.
 
-       Interpolation should be used instead of just copying data, when the  X-
+       Interpolation  should be used instead of just copying data, when the X-
        and Y-resolution differ.
 
        Support for buttons is missing.
 
-       More  detailed bug information is available at the gt68xx backend home-
+       More detailed bug information is available at the gt68xx backend  home-
        page http://www.meier-geinitz.de/sane/gt68xx.  Please contact me if you
-       find  a bug or missing feature: <henning@meier-geinitz.de>. Please send
-       a  debug  log  if  your   scanner   isn't   detected   correctly   (see
+       find a bug or missing feature: <henning@meier-geinitz.de>. Please  send
+       a   debug   log   if   your   scanner  isn't  detected  correctly  (see
        SANE_DEBUG_GT68XX above).
 
-sane-backends 1.0.14-cvs          4 Apr 2004                    sane-gt68xx(5)
+sane-backends 1.0.15              2 Oct 2004                    sane-gt68xx(5)
diff --git a/man/sane-hp.5.html b/man/sane-hp.5.html index 83aae9d4..e9870045 100644 --- a/man/sane-hp.5.html +++ b/man/sane-hp.5.html @@ -255,7 +255,7 @@ The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart PhotoScanner support by Peter Kirchgessner. -sane-backends 1.0.14-cvs 27 Mar 2004 sane-hp(5) +sane-backends 1.0.15 27 Mar 2004 sane-hp(5)
diff --git a/man/sane-hp5400.5.html b/man/sane-hp5400.5.html index c72dfde1..0fc050b2 100644 --- a/man/sane-hp5400.5.html +++ b/man/sane-hp5400.5.html @@ -110,7 +110,7 @@ other operating systems and especially on big-endian platforms. The scanner may get wrong data. -sane-backends 1.0.14-cvs 17 Apr 2003 sane-hp5400(5) +sane-backends 1.0.15 17 Apr 2003 sane-hp5400(5)
diff --git a/man/sane-hpsj5s.5.html b/man/sane-hpsj5s.5.html index 7f22f0ec..4b433943 100644 --- a/man/sane-hpsj5s.5.html +++ b/man/sane-hpsj5s.5.html @@ -111,7 +111,7 @@ Max Vorobiev Man page mostly based on canon.man -sane-backends 1.0.14-cvs 24 Feb 2002 sane-hpsj5s(5) +sane-backends 1.0.15 24 Feb 2002 sane-hpsj5s(5)
diff --git a/man/sane-ibm.5.html b/man/sane-ibm.5.html index f08401a9..2926f92a 100644 --- a/man/sane-ibm.5.html +++ b/man/sane-ibm.5.html @@ -94,7 +94,7 @@ mf <massifr@tiscalinet.it> Maintained by Henning Meier-Geinitz <henning@meier-geinitz.de> -sane-backends 1.0.14-cvs 15 Apr 2003 sane-ibm(5) +sane-backends 1.0.15 15 Apr 2003 sane-ibm(5)
diff --git a/man/sane-leo.5.html b/man/sane-leo.5.html index 13cca1f5..5a9f0060 100644 --- a/man/sane-leo.5.html +++ b/man/sane-leo.5.html @@ -134,7 +134,7 @@ The package is actively maintained by Frank Zago. http://www.zago.net/sane/#leo -sane-backends 1.0.14-cvs 16 April 2002 sane-leo(5) +sane-backends 1.0.15 16 April 2002 sane-leo(5)
diff --git a/man/sane-ma1509.5.html b/man/sane-ma1509.5.html index f5e6f31d..7b452140 100644 --- a/man/sane-ma1509.5.html +++ b/man/sane-ma1509.5.html @@ -127,7 +127,7 @@ More detailed bug information is available at the MA-1509 backend home- page http://www.meier-geinitz.de/sane/ma1509-backend/. -sane-backends 1.0.14-cvs 24 Feb 2003 sane-ma1509(5) +sane-backends 1.0.15 24 Feb 2003 sane-ma1509(5)
diff --git a/man/sane-matsushita.5.html b/man/sane-matsushita.5.html index 1dcc571d..c04cec04 100644 --- a/man/sane-matsushita.5.html +++ b/man/sane-matsushita.5.html @@ -184,7 +184,7 @@ The package is actively maintained by Frank Zago. http://www.zago.net/sane/#matsushita -sane-backends 1.0.14-cvs February 11th, 2004 sane-matsushita(5) +sane-backends 1.0.15 February 11th, 2004 sane-matsushita(5)
diff --git a/man/sane-microtek.5.html b/man/sane-microtek.5.html index d673a3b3..91df3287 100644 --- a/man/sane-microtek.5.html +++ b/man/sane-microtek.5.html @@ -166,7 +166,7 @@ ers mailing list. Have a look at http://www.sane-project.org/mail- ing-lists.html concerning subscription to sane-devel. -sane-backends 1.0.14-cvs February 8, 2000 sane-microtek(5) +sane-backends 1.0.15 February 8, 2000 sane-microtek(5)
diff --git a/man/sane-microtek2.5.html b/man/sane-microtek2.5.html index d9ddf038..428495e7 100644 --- a/man/sane-microtek2.5.html +++ b/man/sane-microtek2.5.html @@ -283,7 +283,7 @@ Karsten Festag karsten.festag@gmx.de -sane-backends 1.0.14-cvs 28 Jan 2002 sane-microtek2(5) +sane-backends 1.0.15 28 Jan 2002 sane-microtek2(5)
diff --git a/man/sane-mustek.5.html b/man/sane-mustek.5.html index 627bca49..9b4b165f 100644 --- a/man/sane-mustek.5.html +++ b/man/sane-mustek.5.html @@ -70,7 +70,7 @@ noises and the scan mechanism may be damaged. Thus, if you hear such a noise, IMMEDIATELY turn off the scanner. This shouldn't happen if your scanner is in the list of known scanners. There is more information in - the /usr/local/doc/sane-1.0.14-cvs/PROBLEMS file. + the /usr/local/doc/sane-1.0.15/PROBLEMS file. 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 scan- @@ -245,7 +245,7 @@ access the I/O ports. Thus, either make frontends such as scanimage(1) and xscanimage(1) setuid root (generally not recommended for safety reasons) or, alternatively, access this backend through the network - daemon saned(1). + daemon saned(8). If the Mustek backend blocks while sending the inqiury command to the scanner, add the option force-wait to mustek.conf. @@ -311,7 +311,7 @@

SEE ALSO

        sane(7),  sane-find-scanner(1), sane-scsi(5), sane-mustek_usb(5), sane-
        gt68xx(5), sane-plustek(5), sane-mustek_pp(5)
-       /usr/local/doc/sane-1.0.14-cvs/mustek/mustek.CHANGES
+       /usr/local/doc/sane-1.0.15/mustek/mustek.CHANGES
        http://www.meier-geinitz.de/sane/mustek-backend/
 
 
@@ -334,7 +334,7 @@
        More  detailed bug information is available at the Mustek backend home-
        page: http://www.meier-geinitz.de/sane/mustek-backend/.
 
-sane-backends 1.0.14-cvs          25 Dec 2002                   sane-mustek(5)
+sane-backends 1.0.15              25 Dec 2002                   sane-mustek(5)
diff --git a/man/sane-mustek_pp.5.html b/man/sane-mustek_pp.5.html index 3f7685ce..17e6746e 100644 --- a/man/sane-mustek_pp.5.html +++ b/man/sane-mustek_pp.5.html @@ -83,7 +83,7 @@ Some scanners work faster when EPP/ECP is enabled in the BIOS. Note that the backend needs to run as root. To allow user access to the - scanner run the backend through the network interface (See saned(1) and + scanner run the backend through the network interface (See saned(8) and sane-net(5)). Note also that the backend does not support parport shar- ing , i.e. if you try printing while scanning, your computer may crash. This backend also conflicts with the sane-musteka4s2 backend. You can @@ -338,7 +338,7 @@

SEE ALSO

-       sane(7), sane-mustek(5), sane-net(5), saned(1), sane-find-scanner(1)
+       sane(7), sane-mustek(5), sane-net(5), saned(8), sane-find-scanner(1)
 
        For latest bug fixes and information see
               http://www.penguin-breeder.org/sane/mustek_pp/
diff --git a/man/sane-mustek_usb.5.html b/man/sane-mustek_usb.5.html
index 44920074..96fb2458 100644
--- a/man/sane-mustek_usb.5.html
+++ b/man/sane-mustek_usb.5.html
@@ -149,8 +149,8 @@
 
SEE ALSO
        sane(7),  sane-usb(5),  sane-mustek(5),  sane-mustek_pp(5),  sane-plus-
        tek(5), sane-gt68xx(5), sane-ma1509(5)
-       /usr/local/doc/sane-1.0.14-cvs/mustek_usb/mustek_usb.CHANGES,
-       /usr/local/doc/sane-1.0.14-cvs/mustek_usb/mustek_usb.TODO
+       /usr/local/doc/sane-1.0.15/mustek_usb/mustek_usb.CHANGES,
+       /usr/local/doc/sane-1.0.15/mustek_usb/mustek_usb.TODO
        http://www.meier-geinitz.de/sane/mustek_usb-backend/
 
 
@@ -176,7 +176,7 @@
        More  detailed bug information is available at the Mustek backend home-
        page http://www.meier-geinitz.de/sane/mustek_usb-backend/.
 
-sane-backends 1.0.14-cvs          3 Mar 2004                sane-mustek_usb(5)
+sane-backends 1.0.15              3 Mar 2004                sane-mustek_usb(5)
 

 

 

diff --git a/man/sane-nec.5.html b/man/sane-nec.5.html
index 2606ab8d..94b7abc2 100644
--- a/man/sane-nec.5.html
+++ b/man/sane-nec.5.html
@@ -67,7 +67,7 @@
 
AUTHORS
        Kazuya Fukuda
 
-sane-backends 1.0.14-cvs          17 Feb 2000                      sane-nec(5)
+sane-backends 1.0.15              17 Feb 2000                      sane-nec(5)
 

 

 

diff --git a/man/sane-net.5.html b/man/sane-net.5.html
index 834bbbd7..8783fd22 100644
--- a/man/sane-net.5.html
+++ b/man/sane-net.5.html
@@ -67,10 +67,10 @@
        ner.univ.edu are contacted in addition to the hosts listed above.
 
        For this backend to function properly, it is also necessary  to  define
-       the  sane service in /etc/services.  The sane service should be defined
-       using a line of the following form:
+       the  sane-port  service  in  /etc/services.  The sane service should be
+       defined using a line of the following form:
 
-              sane 6566/tcp # SANE network scanner daemon
+              sane-port 6566/tcp # SANE network scanner daemon
@@ -122,7 +122,7 @@

SEE ALSO

-       sane(7), saned(1), sane-dll(5), scanimage(1)
+       sane(7), saned(8), sane-dll(5), scanimage(1)
 
        http://www.penguin-breeder.org/?page=sane-net
 
@@ -131,7 +131,7 @@
 
AUTHOR
        David Mosberger and Andreas Beck
 
-sane-backends 1.0.14-cvs          8 Oct 2002                       sane-net(5)
+sane-backends 1.0.15              8 Oct 2002                       sane-net(5)
 

 

 

diff --git a/man/sane-niash.5.html b/man/sane-niash.5.html
index 459a56fc..4ac12c3e 100644
--- a/man/sane-niash.5.html
+++ b/man/sane-niash.5.html
@@ -49,11 +49,20 @@
               that support dynamic loading).
 
 
+
+

CAVEATS

+       If you use a
+       Hewlett-Packard Scanjet 3400c or
+       Hewlett-Packard Scanjet 4300c
+       together with Linux kernel 2.6 , kernel version 2.6.8 or newer is  nec-
+       essary.
+
+

ENVIRONMENT

        SANE_DEBUG_NIASH
-              If the library was compiled with  debug  support  enabled,  this
-              environment  variable controls the debug level for this backend.
+              If  the  library  was  compiled with debug support enabled, this
+              environment variable controls the debug level for this  backend.
               Higher debug levels increase the verbosity of the output.
 
               Example: export SANE_DEBUG_NIASH=255
@@ -69,7 +78,7 @@
 
AUTHOR
        Bertrik Sikken <bertrik@zonnet.nl>
 
-sane-backends 1.0.14-cvs         29 July 2004                    sane-niash(5)
+sane-backends 1.0.15             29 July 2004                    sane-niash(5)
 

 

 

diff --git a/man/sane-pie.5.html b/man/sane-pie.5.html
index 45a525bf..f7fea069 100644
--- a/man/sane-pie.5.html
+++ b/man/sane-pie.5.html
@@ -66,7 +66,7 @@
        Please send any information and bug-reports to:
        Simon Munton <simon@munton.demon.co.uk>
 
-sane-backends 1.0.14-cvs          7 Sept 2000                      sane-pie(5)
+sane-backends 1.0.15              7 Sept 2000                      sane-pie(5)
diff --git a/man/sane-pint.5.html b/man/sane-pint.5.html index 16a09e33..e2ad9608 100644 --- a/man/sane-pint.5.html +++ b/man/sane-pint.5.html @@ -135,7 +135,7 @@ No testing has been done on three-pass or handheld scanners, or with Automatic Document Feeder support. -sane-backends 1.0.14-cvs 13 May 1998 sane-pint(5) +sane-backends 1.0.15 13 May 1998 sane-pint(5)
diff --git a/man/sane-plustek.5.html b/man/sane-plustek.5.html index 77aa299e..38bbfbcc 100644 --- a/man/sane-plustek.5.html +++ b/man/sane-plustek.5.html @@ -75,6 +75,7 @@ ---------------------------------------------------------- USB Model: ASIC: Properties: Prod-ID ---------------------------------------------------------- + UMAX 3400 LM9832 600x1200dpi 42bit 512Kb 0x0050 UMAX 3400/3450 LM9832 600x1200dpi 42bit 512Kb 0x0060 UMAX 5400 LM9832 1200x2400dpi 42bit 512Kb 0x0160 @@ -113,13 +114,15 @@ are supported by this backend. Older versions of the U12, the UT12, the U1212 and U1248 (GrandTech chipset) are not supported. - Model Chipset backend - --------------------------- - U1248 GrandTech gt68xx - UT16B GrandTech gt68xx - U12 P98003 u12 - UT12 P98003 u12 - 1212U P98003 u21 + Model Chipset backend + ------------------------------------ + U1248 GrandTech gt68xx + UT16B GrandTech gt68xx + OpticSlim 1200 GrandTech gt68xx + OpticSlim 2400 GrandTech gt68xx + U12 P98003 u12 + UT12 P98003 u12 + 1212U P98003 u12 For a more complete and up to date list see: http://www.sane- project.org/sane-supported-devices.html @@ -134,19 +137,22 @@ device /dev/usbscanner - [usb] tells the backend, that the following devicename (here /dev/usb- - scanner ) 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 auto - then the next matching device is used. + [usb] tells the backend, that the following devicename (here + /dev/usbscanner ) has to be interpreted as USB scanner device. If ven- + dor- and product-id has not been specified, the backend tries to detect + this by its own. If device is set to auto then the next matching device + is used. + The following options can be used for a default setup of your device. + Most of them are also availaby through the frontend. The Options: option warmup t - t specifies the warmup period in seconds + t specifies the warmup period in seconds, if set to -1, the + automatic warmup function will be used option lampOff t - t is the time in seconds for switching off the lamps in standby + t is the time in seconds for switching off the lamps in standby mode option lOffonEnd b @@ -154,7 +160,7 @@ lamps off, 0 --> do not change lamp status option mov m - m is the model override switch. It works only with Mustek + m is the model override switch. It works only with Mustek BearPaw devices. m/PID | 0x1000 | 0x1001 ------+--------------+-------------- @@ -162,33 +168,34 @@ 1 | no function | BearPaw 1200 option invertNegatives b - b 0 --> do not invert the picture during negativ scans, 1 --> + b 0 --> do not invert the picture during negativ scans, 1 --> invert picture option cacheCalData b - b 0 --> do not save coarse calibration results, 1 --> save + b 0 --> do not save coarse calibration results, 1 --> save results of coarse calibration in ~/.sane/ directory option altCalibration b - b 0 --> use standard calibration routines, 1 --> use alternate + b 0 --> use standard calibration routines, 1 --> use alternate calibration (only non Plustek devices, standard for CIS devices) option skipFine b - b 0 --> perform fine calibration, 1 --> skip fine calibration + b 0 --> perform fine calibration, 1 --> skip fine calibration (only non Plustek devices) option skipFineWhite b - b 0 --> perform white fine calibration, 1 --> skip white fine + b 0 --> perform white fine calibration, 1 --> skip white fine calibration (only non Plustek devices) option skipCalibration b - b 0 --> perform calibration, 1 --> skip calibration (only non + b 0 --> perform calibration, 1 --> skip calibration (only non Plustek devices) option enableTPA b - b 0 --> default behaviour, specified by the internal tables, 1 - --> override internal tables and allow TPA mode (EPSON only) + b 0 --> default behaviour, specified by the internal tables, 1 + --> override internal tables and allow TPA mode (EPSON/UMAX + only) option posOffX x option posOffY y @@ -216,11 +223,14 @@ can be adjusted. option red_gain r + option red_offset ro option green_gain g + option green_offset go option blue_gain b - r g b These values can be used to adjust the internally detected - gain values of the AFE for each channel. The range is between 0 - and 63. + option blue_offset bo + r g b ro go bo These values can be used to set the gain and off- + set values of the AFE for each channel. The range is between 0 + and 63. -1 means autocalibration. See the plustek.conf file for examples. @@ -273,24 +283,22 @@

SEE ALSO

-       sane(7), sane-usb(5), sane-plustek(5),
-       /usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-USB.changes
-       http://www.gjaeger.de/scanner/plustek.html
+       sane(7), sane-usb(5), sane-u12(5), sane-gt68xx(5),
+       /usr/local/doc/sane-1.0.15/plustek/Plustek-USB.changes
+       http://www.gjaeger.de/scanner/plustek/

CONTACT AND BUG-REPORTS

        Please send any information and bug-reports to:
-       Plustek Driver Mailing List <plustek@linuxhacker.org>
-       or directly to:
-       Gerhard Jaeger <gerhard@gjaeger.de>
+       SANE Mailing List
 
        Additional info and hints can be obtained from our
        Mailing-List archive at:
-       http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3
+       http://www.sane-project.org/mailing-lists.html
 
        or directly from the projects' homepage at:
-       http://www.gjaeger.de/scanner/plustek.html
+       http://www.gjaeger.de/scanner/plustek/
 
        To obtain debug messages from the backend, please set the  environment-
        variable  SANE_DEBUG_PLUSTEK before calling your favorite scan-frontend
@@ -298,7 +306,7 @@
        i.e.: export SANE_DEBUG_PLUSTEK=20 ; xscanimage
 
        The value controls the verbosity of the backend. Please note, that val-
-       ues  greater  than 19 force the backend to output raw data files, which
+       ues  greater  than 24 force the backend to output raw data files, which
        could be rather large. The ending of these files is ".raw".  For  prob-
        lem reports it should be enough the set the verbosity to 13.
 
@@ -311,7 +319,8 @@
          of the CDD-sensor and the stepper motor i.e. you have a
          600x1200 dpi scanner and you are scanning using 800dpi,
          so scaling is necesary, because the sensor only delivers
-         600dpi but the motor is capable to perform 1200dpi steps.
+         600dpi but the motor is capable to perform 1200dpi
+         steps.
        * Plusteks' model policy is somewhat inconsistent. This
          means, they sell technical different devices under the
          same product name. Therefore it is possible that some
@@ -320,7 +329,7 @@
          the one your device has.
        * Negative/Slide scanning quality is poor.
 
-sane-backends 1.0.14-cvs          22 Mar 2004                  sane-plustek(5)
+sane-backends 1.0.15             02 July 2004                  sane-plustek(5)
diff --git a/man/sane-plustek_pp.5.html b/man/sane-plustek_pp.5.html index 5be16f4b..5aaf5e4a 100644 --- a/man/sane-plustek_pp.5.html +++ b/man/sane-plustek_pp.5.html @@ -185,28 +185,25 @@ source-files of this sane-backend installation. Unpack this tar-ball and go to the directory: sane-backends/doc/plustek - Within this directory, you should find a file called: - Makefile.module + Within this directory, you should find a script called: + MakeModule.sh Now if your Linux kernelsources are installed correctly, it should be - possible to build, install and load the module pt_drv. Try - make -f Makefile.module - to obtain a help text, about the targets, the makefile supports. - Use - make -f Makefile.module all - to build the module. Use - make -f Makefile.module install - to install the module. Use - make -f Makefile.module load - to load the module. - Note: Installing and loading the can only be done as superuser. + possible to build, install and load the module pt_drv. Please note, + that the kernelsources need to be configured correctly. Refer to your + distributions manual on how this is done. As root user, try + ./MakeModule.sh + the script will try and get all necessary information about your run- + ning kernel and will lead you through the whole installation process. + Note: Installing and loading the can only be done as superuser.

KERNEL MODULE SETUP

-       The  configuration  of  the  kernel module is done by providing some or
+       The configuration of the kernel module is done  by  providing  some  or
        more options found below to the kernel module at load time. This can be
-       done  by  invoking  insmod with the appropriate parameters or appending
-       the options to the file /etc/conf.modules
+       done by invoking insmod with the appropriate  parameters  or  appending
+       the options to the file /etc/modules.conf (kernel < 2.6.x) or /etc/mod-
+       probe.conf (kernel >= 2.6.x)
 
        The Options:
        lampoff=lll
@@ -274,13 +271,14 @@
               has  been set to EPP-mode. When detecting any other mode such as
               ECP or PS/2 the driver tries to set to a faster, supported mode.
               If  this  fails,  it  will use the SPP mode, as this mode should
-              work with all Linux supported parallel ports.
+              work with all Linux supported parallel ports. If in doubt, enter
+              your BIOS and set it to any mode except ECP.
 
        Former Plustek scanner models (4830, 9630) supplied a ISA parallel port
        adapter card. This card is not supported by the driver.
 
-       The  ASIC 96001/3 based models have sometimes trouble with high resolu-
-       tion modes. If you encounter sporadic corrupted  images  (parts  dupli-
+       The ASIC 96001/3 based models have sometimes trouble with high  resolu-
+       tion  modes.  If  you encounter sporadic corrupted images (parts dupli-
        cated or shifted horizontally) kill all other applications before scan-
        ning and (if sufficient memory available) disable swapping.
 
@@ -299,8 +297,11 @@
               The shared library implementing this backend (present on systems
               that support dynamic loading).
 
-       /lib/modules/<Kernel-Version>/misc/pt_drv.o
-              The Linux Kernelmodule.
+       /lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.o
+              The Linux kernelmodule for kernels < 2.6.x.
+
+       /lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.ko
+              The Linux kernelmodule for kernels >= 2.6.x.
@@ -308,20 +309,20 @@ SANE_CONFIG_DIR 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 + are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the config- - uration file is searched in two default directories: first, the - current working directory (".") and then in + uration file is searched in two default directories: first, the + current working directory (".") and then in /usr/local/etc/sane.d. If the value of the environment variable - ends with the directory separator character, then the default + ends with the directory separator character, then the default directories are searched after the explicitly specified directo- - ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:" - would result in directories "tmp/config", ".", and + ries. For example, setting SANE_CONFIG_DIR to "/tmp/config:" + would result in directories "tmp/config", ".", and "/usr/local/etc/sane.d" being searched (in this order). SANE_DEBUG_PLUSTEK_PP - If the library was compiled with debug support enabled, this - environment variable controls the debug level for this backend. + If the library was compiled with debug support enabled, this + environment variable controls the debug level for this backend. Higher debug levels increase the verbosity of the output. Example: export SANE_DEBUG_PLUSTEK_PP=10 @@ -330,26 +331,24 @@

SEE ALSO

        sane(7),
-       /usr/local/doc/sane-1.0.14-cvs/plustek/Plustek-PARPORT.changes
-       http://www.gjaeger.de/scanner/plustek.html
+       /usr/local/doc/sane-1.0.15/plustek/Plustek-PARPORT.changes
+       http://www.gjaeger.de/scanner/plustek_pp/

CONTACT AND BUG-REPORTS

        Please send any information and bug-reports to:
-       Plustek Driver Mailing List <plustek@linuxhacker.org>
-       or directly to:
-       Gerhard Jaeger <gerhard@gjaeger.de>
+       SANE Mailing List
 
        Additional info and hints can be obtained from our
        Mailing-List archive at:
-       http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3
+       http://www.sane-project.org/mailing-lists.html
 
        or directly from the projects' homepage at:
-       http://www.gjaeger.de/scanner/plustek.html
+       http://www.gjaeger.de/scanner/plustek_pp/
 
-       To obtain debug messages from the backend, please set the  environment-
-       variable  SANE_DEBUG_PLUSTEK_PP before calling your favorite scan-fron-
+       To  obtain debug messages from the backend, please set the environment-
+       variable SANE_DEBUG_PLUSTEK_PP before calling your favorite  scan-fron-
        tend (i.e. xscanimage).
        i.e.: export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
 
@@ -387,7 +386,7 @@
        * The scanspeed on 600x1200 dpi models is slow.
        * The scanquality of the A3I is poor
 
-sane-backends 1.0.14-cvs          13 Jan 2004               sane-plustek_pp(5)
+sane-backends 1.0.15             18 June 2004               sane-plustek_pp(5)
diff --git a/man/sane-pnm.5.html b/man/sane-pnm.5.html index 653f595a..e721e38a 100644 --- a/man/sane-pnm.5.html +++ b/man/sane-pnm.5.html @@ -74,7 +74,7 @@

SEE ALSO

        sane(7)
 
-sane-backends 1.0.14-cvs         22 April 2001                     sane-pnm(5)
+sane-backends 1.0.15             22 April 2001                     sane-pnm(5)
diff --git a/man/sane-qcam.5.html b/man/sane-qcam.5.html index 0bcb2eeb..31bb6e20 100644 --- a/man/sane-qcam.5.html +++ b/man/sane-qcam.5.html @@ -109,7 +109,7 @@

SEE ALSO

        sane(7)
 
-sane-backends 1.0.14-cvs        25 October 1997                   sane-qcam(5)
+sane-backends 1.0.15            25 October 1997                   sane-qcam(5)
diff --git a/man/sane-ricoh.5.html b/man/sane-ricoh.5.html index 36b03c01..107943c2 100644 --- a/man/sane-ricoh.5.html +++ b/man/sane-ricoh.5.html @@ -85,7 +85,7 @@

AUTHOR

        Feico W. Dillema
 
-sane-backends 1.0.14-cvs          24 Jun 2000                    sane-ricoh(5)
+sane-backends 1.0.15              24 Jun 2000                    sane-ricoh(5)
diff --git a/man/sane-s9036.5.html b/man/sane-s9036.5.html index bc50dca0..50098434 100644 --- a/man/sane-s9036.5.html +++ b/man/sane-s9036.5.html @@ -83,7 +83,7 @@ Ingo Schneider -sane-backends 1.0.14-cvs 24 Jun 2000 sane-s9036(5) +sane-backends 1.0.15 24 Jun 2000 sane-s9036(5)
diff --git a/man/sane-sceptre.5.html b/man/sane-sceptre.5.html index c5913ab6..8019d1ce 100644 --- a/man/sane-sceptre.5.html +++ b/man/sane-sceptre.5.html @@ -147,7 +147,7 @@ The package is actively maintained by Frank Zago. http://www.zago.net/sane/#sceptre -sane-backends 1.0.14-cvs April 21st, 2002 sane-sceptre(5) +sane-backends 1.0.15 April 21st, 2002 sane-sceptre(5)
diff --git a/man/sane-scsi.5.html b/man/sane-scsi.5.html index 9dd05eb5..98a53648 100644 --- a/man/sane-scsi.5.html +++ b/man/sane-scsi.5.html @@ -303,7 +303,7 @@

AUTHOR

        David Mosberger
 
-sane-backends 1.0.14-cvs          28 Oct 2003                     sane-scsi(5)
+sane-backends 1.0.15              28 Oct 2003                     sane-scsi(5)
diff --git a/man/sane-sharp.5.html b/man/sane-sharp.5.html index 25679dc3..d75931ed 100644 --- a/man/sane-sharp.5.html +++ b/man/sane-sharp.5.html @@ -366,7 +366,7 @@ Parts of this man page are a plain copy of sane-mustek(5) by David Mos- berger-Tang, Andreas Czechanowski and Andreas Bolsch -sane-backends 1.0.14-cvs 21 Nov 2000 sane-sharp(5) +sane-backends 1.0.15 21 Nov 2000 sane-sharp(5)
diff --git a/man/sane-sm3600.5.html b/man/sane-sm3600.5.html index 04a1eab7..ce090bd6 100644 --- a/man/sane-sm3600.5.html +++ b/man/sane-sm3600.5.html @@ -110,7 +110,7 @@ Marian Eichholz (eichholz@computer.org) Glenn Ramsey (glenn@componic.com) -sane-backends 1.0.14-cvs 10.02.2002 sane-sm3600(5) +sane-backends 1.0.15 10.02.2002 sane-sm3600(5)
diff --git a/man/sane-snapscan.5.html b/man/sane-snapscan.5.html index e300bdde..f3f0b8c8 100644 --- a/man/sane-snapscan.5.html +++ b/man/sane-snapscan.5.html @@ -114,7 +114,7 @@ Man page by Henning Meier-Geinitz (mostly based on the web pages and source code). -sane-backends 1.0.14-cvs 26 May 2001 sane-snapscan(5) +sane-backends 1.0.15 26 May 2001 sane-snapscan(5)
diff --git a/man/sane-sp15c.5.html b/man/sane-sp15c.5.html index 3c0f6b16..d3b4b1cb 100644 --- a/man/sane-sp15c.5.html +++ b/man/sane-sp15c.5.html @@ -78,7 +78,7 @@ working first driver. Watch this space for changes. -sane-backends 1.0.14-cvs 17 Apr 2002 sane-sp15c(5) +sane-backends 1.0.15 17 Apr 2002 sane-sp15c(5)
diff --git a/man/sane-st400.5.html b/man/sane-st400.5.html index 7df35510..aedf74dd 100644 --- a/man/sane-st400.5.html +++ b/man/sane-st400.5.html @@ -153,7 +153,7 @@

AUTHOR

        Ingo Wilken <Ingo.Wilken@informatik.uni-oldenburg.de>
 
-sane-backends 1.0.14-cvs          08 Mar 1999                    sane-st400(5)
+sane-backends 1.0.15              08 Mar 1999                    sane-st400(5)
diff --git a/man/sane-tamarack.5.html b/man/sane-tamarack.5.html index 1da54146..f10a21a6 100644 --- a/man/sane-tamarack.5.html +++ b/man/sane-tamarack.5.html @@ -87,7 +87,7 @@

AUTHOR

        Roger Wolff
 
-sane-backends 1.0.14-cvs          24 Jun 2000                 sane-tamarack(5)
+sane-backends 1.0.15              24 Jun 2000                 sane-tamarack(5)
diff --git a/man/sane-teco1.5.html b/man/sane-teco1.5.html index 1405c565..15da0560 100644 --- a/man/sane-teco1.5.html +++ b/man/sane-teco1.5.html @@ -166,7 +166,7 @@ Thanks to Gerard Delafond for the VM4542 support. Thanks to Jean-Yves Simon for the VM3510 support. -sane-backends 1.0.14-cvs August 30th, 2002 sane-teco1(5) +sane-backends 1.0.15 August 30th, 2002 sane-teco1(5)
diff --git a/man/sane-teco2.5.html b/man/sane-teco2.5.html index 2e108632..434ad816 100644 --- a/man/sane-teco2.5.html +++ b/man/sane-teco2.5.html @@ -29,7 +29,7 @@ ---------------------- -------------- ----------- Mustek ScanMagic 4830S VM3575 untested - Primax Jewel 4800 VM356A basic + Primax Jewel 4800 VM356A good Primax Profi 9600 VM6575 basic Primax Profi 19200 VM6586 good Relisys APOLLO Express 3 VM356A basic @@ -39,7 +39,7 @@ Relisys AVEC Super 3 VM3575 basic Relisys SCORPIO Pro VM6575 good Relisys SCORPIO Pro-S VM6586 untested - Relisys SCORPIO Super 3 VM3575 basic + Relisys SCORPIO Super 3 VM3575 good For all these scanners, black&white and grayscale mode work well. How- ever, most of them do not support more than a handful of resolutions in @@ -78,54 +78,62 @@ Color selects the resolution for a scan. The scanner can do only the resolutions listed. + All values with ydpi > 300 (300 x 600) or 600 (600 x 1200) + result in a wrong proportion for the scan. The proportion can be + adjusted with the following command: convert -geometry + (dpi/max_xdpi * 100%)x100% max_xdpi is for the vm3575 constant + with 300 dpi e.g. 600dpi adjust with: convert -geometry + 200%x100% + Geometry options -l -t -x -y control the scan area: -l sets the top left x coordinate, -t the top left y coordinate, -x selects the width and -y the height of - the scan area. All parameters are specified in millimeters by + the scan area. All parameters are specified in millimeters by default. Enhancement options --custom-gamma (no custom gamma option for the VM3564 and VM356A) - (color mode only) allows the user to specify a gamma table (see + (color mode only) allows the user to specify a gamma table (see the next 3 parameters). --red-gamma-table - (color mode only) can be used to download a user defined gamma + (color mode only) can be used to download a user defined gamma table for the red channel. The table must be 256 bytes long. --green-gamma-table - (color mode only) can be used to download a user defined gamma + (color mode only) can be used to download a user defined gamma table for the green channel. The table must be 256 bytes long. --blue-gamma-table - (color mode only) can be used to download a user defined gamma + (color mode only) can be used to download a user defined gamma table for the blue channel. The table must be 256 bytes long. --white-level-r - (VM3564, VM356A, VM3575 only) Selects what red radiance level - should be considered "white", when scanning some sheets by - changing the calibration value loaded into the scanner. Scale - 0..64 in steps of 1. + (VM3564, VM356A, VM3575 and VM6575 only) Selects what red radi- + ance level should be considered "white", when scanning some + sheets by changing the calibration value loaded into the scan- + ner. Scale 0..64 in steps of 1. --white-level-g - (VM3564, VM356A, VM3575 only) Selects what green radiance level - should be considered "white", when scanning some sheets by - changing the calibration i value loaded into the scanner. Scale - 0..64 in steps of 1. + (VM3564, VM356A, VM3575 and VM6575 only) Selects what green + radiance level should be considered "white", when scanning some + sheets by changing the calibration i value loaded into the scan- + ner. Scale 0..64 in steps of 1. - --white-level-g - (VM3564, VM356A, VM3575 only) Selects what blue radiance level - should be considered "white", when scanning some sheets by - changing the calibration value loaded into the scanner. Scale - 0..64 in steps of 1. + --white-level-b + (VM3564, VM356A, VM3575 and VM6575 only) Selects what blue radi- + ance level should be considered "white", when scanning some + sheets by changing the calibration value loaded into the scan- + ner. Scale 0..64 in steps of 1. --preview - requests a preview scan. The resolution used for that scan is 22 - dpi and the scan area is the maximum allowed. The scan mode is - user selected. The default is "no". + requests a preview scan. The resolution used for that scan is 50 + dpi (for VM356A and VM6575 75 dpi) and the scan area is the max- + imum allowed. The scan mode is user selected. The default is + "no". @@ -154,9 +162,9 @@ SANE_TECO2_CAL_ALGO Either 0 or 1. Selects the algorithm for the calibration. A - value of 1 seems to give better scans on the VM3575. Feedback on - it is welcome. For VM356A and VM3575 default 1. For other sup- - ported types default 0. + value of 1 seems to give better scans on the VM356A, VM3575. + Feedback on it is welcome. For VM356A, VM3575, VM6575 default + 1. For other supported types default 0. @@ -203,7 +211,7 @@ Michael Hoeller for his testing the VM356A. -sane-backends 1.0.14-cvs 15 January 2004 sane-teco2(5) +sane-backends 1.0.15 03 August 2004 sane-teco2(5)
diff --git a/man/sane-teco3.5.html b/man/sane-teco3.5.html index 8de004ae..2e25ee24 100644 --- a/man/sane-teco3.5.html +++ b/man/sane-teco3.5.html @@ -139,7 +139,7 @@ The package is actively maintained by Frank Zago. http://www.zago.net/sane/#teco3 -sane-backends 1.0.14-cvs 25 July 2002 sane-teco3(5) +sane-backends 1.0.15 25 July 2002 sane-teco3(5)
diff --git a/man/sane-test.5.html b/man/sane-test.5.html index 38edd599..a6350dfe 100644 --- a/man/sane-test.5.html +++ b/man/sane-test.5.html @@ -279,7 +279,7 @@

BUGS

        - config file values aren't tested for correctness
 
-sane-backends 1.0.14-cvs          24 Jul 2002                     sane-test(5)
+sane-backends 1.0.15              24 Jul 2002                     sane-test(5)
diff --git a/man/sane-u12.5.html b/man/sane-u12.5.html index b5099955..942c3608 100644 --- a/man/sane-u12.5.html +++ b/man/sane-u12.5.html @@ -130,8 +130,8 @@

SEE ALSO

        sane(7), sane-usb(5), sane-plustek(5),
-       /usr/local/doc/sane-1.0.14-cvs/u12/U12.changes
-       http://www.gjaeger.de/scanner/u12.html
+       /usr/local/doc/sane-1.0.15/u12/U12.changes
+       http://www.gjaeger.de/scanner/u12/
@@ -144,7 +144,7 @@ http://www.sane-project.org/mailing-lists.html or directly from the projects' homepage at: - http://www.gjaeger.de/scanner/u12.html + http://www.gjaeger.de/scanner/u12/ To obtain debug messages from the backend, please set the environment- variable SANE_DEBUG_U12 before calling your favorite scan-frontend @@ -161,7 +161,7 @@ * When using libusb, it might be, that the backend hangs. In that case, reconnect the scanner. -sane-backends 1.0.14-cvs 23 Apr 2004 sane-u12(5) +sane-backends 1.0.15 18 June 2004 sane-u12(5)
diff --git a/man/sane-umax.5.html b/man/sane-umax.5.html index 14e236dd..b854f13e 100644 --- a/man/sane-umax.5.html +++ b/man/sane-umax.5.html @@ -268,7 +268,7 @@

EMAIL-CONTACT

        Oliver.Rauch@Rauch-Domain.DE
 
-sane-backends 1.0.14-cvs       29 november 2002                   sane-umax(5)
+sane-backends 1.0.15           29 november 2002                   sane-umax(5)
diff --git a/man/sane-umax1220u.5.html b/man/sane-umax1220u.5.html index 4923ab4b..ccafed48 100644 --- a/man/sane-umax1220u.5.html +++ b/man/sane-umax1220u.5.html @@ -134,7 +134,7 @@ When reporting bugs, please run the backend with SANE_DEBUG_UMAX1220U set to 10 and attach a copy of the log messages. -sane-backends 1.0.14-cvs 6 Jan 2002 sane-umax1220u(5) +sane-backends 1.0.15 6 Jan 2002 sane-umax1220u(5)
diff --git a/man/sane-umax_pp.5.html b/man/sane-umax_pp.5.html index 2e4652b4..461b54c2 100644 --- a/man/sane-umax_pp.5.html +++ b/man/sane-umax_pp.5.html @@ -30,36 +30,37 @@ Astra 1600P Astra 2000P - This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200 dpi - scan resolutions, in color and gray levels. There is a software lineart + This backend handles 75x75, 150x150, 300x300, 600x600 and 600x1200 for + 1220P/1600P/2000P dpi scan reslutions,and 75x75, 150x150, 300x300 and + 300x600 for 610P. In color and gray levels, there is a software lineart mode. - These scanners share the same ASIC. Only parts such as CCD and ADC - change from one to another. They even all reports being UMAX Astra - 1220P via IEEE1284. There isn't software way to recognize them prop- - erly. Under windows, model is set by the driver installed, regardless - of the hardware. + The new generation models share a newer version of the 610P ASIC embed- + ded in an EPAT chip. Only parts such as CCD and ADC change from one to + another. They even all reports being UMAX Astra 1220P via IEEE1284. + There isn't software way to recognize them properly. Under windows, + model is set by the driver installed, regardless of the hardware. EPP/ECP MODES ONLY - The current version of the backend uses only EPP or ECP mode to - communicate with the scanner. PS/2 and SPP mode aren't imple- - mented. It is recommended that you set your parallel port to EPP - in BIOS with the current version of this backend. You can leave - it to ECP or ECP+EPP, but in this case you may not use ppdev but - only direct hardware access if you have to use ECP. ECPEPP will - only + The current version of the backend uses only EPP or ECP mode to + communicate with the scanner. PS/2 mode isn't implemented. The + 610P only use SPP. It is recommended that you set your parallel + port to EPP in BIOS with the current version of this backend. + You can leave it to ECP or ECP+EPP, but in this case you may not + use ppdev but only direct hardware access if you have to use + ECP. ECPEPP will only work if you use a 2.4 or 2.6 kernel with ppdev character device support. - This backend does support parport sharing only if you have a kernel + This backend does support parport sharing only if you have a kernel with ppdev support. - Note that if you don't use the ppdev character device, the backend + 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 back- - end through the network interface (See saned(1) and sane-net(5)). A - more relaxed solution (security wise) is to add suid bit to the fron- - tend (See chmod(1)). The backend drop root priviledges as soon as it - can, right after gaining direct access to IO ports, which lessen risks + end through the network interface (See saned(8) and sane-net(5)). A + more relaxed solution (security wise) is to add suid bit to the fron- + tend (See chmod(1)). The backend drop root priviledges as soon as it + can, right after gaining direct access to IO ports, which lessen risks when being root. @@ -93,7 +94,7 @@ NOTE: in all cases, you must have sufficient priviledges to get access to the chosen device or address. Depending on the security settings, devices may not be available for all users. - You have to change permissions on the dev/ppi* or /dev/parport* + You have to change permissions on the dev/ppi* or /dev/parport* devices. You can rename any device using the @@ -109,43 +110,42 @@

CONFIGURATION

        Please make sure to edit umax_pp.conf before you use the backend.
 
-       The  contents  of the umax_pp.conf file is a list of options and device
+       The contents of the umax_pp.conf file is a list of options  and  device
        names that correspond to Umax scanners.  Empty lines and lines starting
        with a hash mark (#) are ignored.
 
-       The  height  options  supported  are  red-brightness, green-brightness,
-       blue-brightness, red-contrast,  green-contrast,  blue-contrast,  astra,
-       and buffer.
+       The height  options  supported  are  red-gain,  green-gain,  blue-gain,
+       red-offset, green-offset, blue-offset, astra, and buffer.
 
-       Options red-brightness , green-brightness and blue-brightness allow you
-       to adjust the sensitivy of your scanner for  the  given  color.  Values
-       range  from  0  (lowest  brightness)  to  15 (highest). If the advanced
-       option "Brightness" isn't checked in the  frontend,  the  backend  does
-       automatic  brightness calibration, and do not use user provided values.
+       Options  red-gain  ,  green-gain  and 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 user provided values.
 
-       Options red-contrast , green-contrast and blue-contrast  allow  you  to
-       adjust  the  contrast of your scanner for the given color. Values range
-       from 0 (lowest contrast) to 15 (highest).
+       Options  red-offset  , green-offset and blue-offset allow you to adjust
+       the offset of your scanner for the given color.  Values  range  from  0
+       (lowest offset) to 15 (highest).
 
-       Option astra allows you to change the model of  your  scanner.  Current
-       auto  detection  is  based on side effects on scanning when using 1220P
+       Option  astra  allows  you to change the model of your scanner. Current
+       auto detection is based on side effects on scanning  when  using  1220P
        command set on other models, so it may fail on unkown hardware combina-
-       tion.  Valid  values  are  610, 1220, 1600 and 2000. It is usefull only
+       tion. Valid values are 610, 1220, 1600 and 2000.  It  is  usefull  only
        when autodetection fails to detect properly your scanner model. If your
        scanner work properly but is reported wrongly, let it be that way.  The
-       only valid case to change the  model  is  when  your  scanner  produces
+       only  valid  case  to  change  the  model is when your scanner produces
        'black' or prevent scanner model autodetection.
 
-       Option  buffer  allows  you  to change the size of the scan buffer. The
-       size must be specified in bytes. The  default  value  is  2  megabytes.
-       Decreasing  this  value  will improve the smoothness of progress bar in
+       Option buffer allows you to change the size of  the  scan  buffer.  The
+       size  must  be  specified  in  bytes. The default value is 2 megabytes.
+       Decreasing this value will improve the smoothness of  progress  bar  in
        the frontend, but will stall the scan more often.

FILES

        /usr/local/etc/sane.d/umax_pp.conf
-              The  backend  configuration  file  (see  also   description   of
+              The   backend   configuration  file  (see  also  description  of
               SANE_CONFIG_DIR below).
 
        /usr/local/lib/sane/libsane-umax_pp.a
@@ -161,21 +161,21 @@
        SANE_CONFIG_DIR
               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
+              are  separated  by a colon (`:'), under OS/2, they are separated
               by a semi-colon (`;').  If this variable is not set, the config-
-              uration file is searched in two default directories: first,  the
-              current     working     directory     (".")    and    then    in
+              uration  file is searched in two default directories: first, the
+              current    working    directory    (".")     and     then     in
               /usr/local/etc/sane.d.  If the value of the environment variable
-              ends  with  the  directory separator character, then the default
+              ends with the directory separator character,  then  the  default
               directories are searched after the explicitly specified directo-
-              ries.   For  example,  setting SANE_CONFIG_DIR to "/tmp/config:"
-              would   result   in   directories   "tmp/config",    ".",    and
+              ries.  For example, setting  SANE_CONFIG_DIR  to  "/tmp/config:"
+              would    result    in   directories   "tmp/config",   ".",   and
               "/usr/local/etc/sane.d" being searched (in this order).
 
        SANE_DEBUG_UMAX_PP
-              If  the  library  was  compiled with debug support enabled, this
-              environment variable controls the debug level for this  backend.
-              E.g.,  a  value  of 128 requests all debug output to be printed.
+              If the library was compiled with  debug  support  enabled,  this
+              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.
 
               level   debug output
@@ -189,8 +189,8 @@
                6       special debug information
 
        SANE_DEBUG_UMAX_PP_LOW
-              This variable sets the debug level for the  SANE  interface  for
-              the  Umax  ASIC. Note that enabling this will spam your terminal
+              This  variable  sets  the debug level for the SANE interface for
+              the Umax ASIC. Note that enabling this will spam  your  terminal
               with some million lines of debug output.
 
               level   debug output
@@ -205,7 +205,7 @@

SEE ALSO

-       sane(7), sane-net(5), saned(1)
+       sane(7), sane-net(5), saned(8)
 
        For latest bug fixes and information see
               http://umax1220p.sourceforge.net/
@@ -216,6 +216,12 @@
        Stéphane VOLTZ <svoltz@wanadoo.fr>
 
 
+
+

CREDITS

+       Support  for the 610P has been made possible thank to an hardware dona-
+       tion by William Stuart.
+
+

BUG REPORTS

        If something doesn't work, please contact me. But I need some  informa-
@@ -241,7 +247,7 @@
               better),  or  you  think I should know something, please include
               it.
 
-sane-backends 1.0.14-cvs       16 September 2003               sane-umax_pp(5)
+sane-backends 1.0.15            23 August 2004                 sane-umax_pp(5)
diff --git a/man/sane-usb.5.html b/man/sane-usb.5.html index b718711f..5027d737 100644 --- a/man/sane-usb.5.html +++ b/man/sane-usb.5.html @@ -64,152 +64,152 @@ nel, libsub), NetBSD (libusb), OpenBSD (kernel, libusb) and MacOS X (libusb). Testing on MacOS X is very limited and not all scanners seem to work reliably with the BSDs. For installation issues, also check the - /usr/local/doc/sane-1.0.14-cvs/README.platform files. The scanner mod- - ule is on longer available on Linux 2.6 and later. Use libusb instead. + /usr/local/doc/sane-1.0.15/README.platform files. The scanner module is + on longer available on Linux 2.6 and later. Use libusb instead. - Generally speaking, if your scanner works with one method, there is no + Generally speaking, if your scanner works with one method, there is no need to switch to the other one. - Libusb is the more general approach and is able to access any scanner. + Libusb is the more general approach and is able to access any scanner. Also, it supports more platforms. - Autodetecting scanners and using USB control messages with the kernel + Autodetecting scanners and using USB control messages with the kernel access method only works with recent (>=v2.4.12) Linux kernels. If you - need one of these two features on a different platform, use libusb - instead. Also, the kernel scanner driver may be removed from Linux + need one of these two features on a different platform, use libusb + instead. Also, the kernel scanner driver may be removed from Linux 2.5/2.6 in future so libusb will be the only access method.

LIBUSB

-       SANE can only use libusb 0.1.6 or newer. It needs to  be  installed  at
+       SANE  can  only  use libusb 0.1.6 or newer. It needs to be installed at
        build-time.
 
-       Libusb  can  only access your scanner if it's not claimed by the kernel
-       scanner driver. If you want to use libusb,  unload  the  kernel  driver
+       Libusb can only access your scanner if it's not claimed by  the  kernel
+       scanner  driver.  If  you  want to use libusb, unload the kernel driver
        (e.g. rmmod scanner under Linux) or disable the driver when compiling a
        new kernel. For Linux, your kernel needs support for the USB filesystem
        (usbfs). For kernels older than 2.4.19, replace "usbfs" with "usbdevfs"
-       because the name has changed. This filesystem must be  mounted.  That's
-       done  automatically  at  boot  time, if /etc/fstab contains a line like
+       because  the  name has changed. This filesystem must be mounted. That's
+       done automatically at boot time, if /etc/fstab  contains  a  line  like
        this:
 
               none /proc/bus/usb usbfs defaults  0  0
 
-       The permissions for the device files used by libusb  must  be  adjusted
-       for  user  access. Otherwise only root can use SANE devices. For Linux,
-       the devices are located in /proc/bus/usb/. There are directories  named
-       e.g.  "001"  (the  bus  name)  containing  files "001", "002" etc. (the
+       The  permissions  for  the device files used by libusb must be adjusted
+       for user access. Otherwise only root can use SANE devices.  For  Linux,
+       the  devices are located in /proc/bus/usb/. There are directories named
+       e.g. "001" (the bus name)  containing  files  "001",  "002"  etc.  (the
        device files). The right device files can be found out by running scan-
-       image  -L  as  root. Setting permissions with "chmod" is not permanent,
-       however. They will be resetted after reboot or replugging the  scanner.
-       In  Linux  versions  before 2.6 it was also possible to mount the usbfs
-       with the option "devmode=0666", e.g. by using  the  following  line  in
+       image -L as root. Setting permissions with "chmod"  is  not  permanent,
+       however.  They will be resetted after reboot or replugging the scanner.
+       In Linux versions before 2.6 it was also possible to  mount  the  usbfs
+       with  the  option  "devmode=0666",  e.g. by using the following line in
        /etc/fstab:
 
               none /proc/bus/usb usbfs defaults,devmode=0666  0  0
 
-       DUE  TO A KERNEL BUG THIS WON'T WORK WITH CURRENT 2.6 KERNELS. USE HOT-
+       DUE TO A KERNEL BUG THIS WON'T WORK WITH CURRENT 2.6 KERNELS. USE  HOT-
        PLUG INSTEAD
 
-       However, this way everyone has access to all USB devices.  Another  way
-       to  set  permissions is to use the hotplug utilities (http://linux-hot-
+       However,  this  way everyone has access to all USB devices. Another way
+       to set permissions is to use the hotplug  utilities  (http://linux-hot-
        plug.sourceforge.net/), which support dynamic setting of access permis-
-       sions.  SANE comes with hotplug scripts in the directory tools/hotplug.
-       They can be used for setting permissions.  Last, the frontends  can  be
+       sions. SANE comes with hotplug scripts in the directory  tools/hotplug.
+       They  can  be used for setting permissions.  Last, the frontends can be
        run as root. However, that's not recommended for security reasons.
 
-       For  the  BSDs,  the  device  files are named /dev/ugen*.  Use chmod to
+       For the BSDs, the device files are  named  /dev/ugen*.   Use  chmod  to
        apply appropriate permissions.

GENERIC KERNEL SCANNER DRIVER

        Ensure that the access permissions for the USB device are set appropri-
-       ately.   We recommend to add a group "scanner" to /etc/group which con-
+       ately.  We recommend to add a group "scanner" to /etc/group which  con-
        tains all users that should have access to the scanner.  The permission
-       of  the device should then be set to allow group read and write access.
-       For example, if the scanner is at USB  device  /dev/usb/scanner0,  then
+       of the device should then be set to allow group read and write  access.
+       For  example,  if  the scanner is at USB device /dev/usb/scanner0, then
        the following two commands would set the permission correctly:
 
               $ chgrp scanner /dev/usb/scanner0
               $ chmod 660 /dev/usb/scanner0
 
        If your scanner isn't detected automatically by your operating system's
-       scanner driver, you need to tell the kernel the vendor and product  ids
-       of  your scanner. For Linux, this can be done with modprobe parameters:
-       First, remove the scanner module (rmmod scanner), then load  it  again:
-       modprobe  scanner  vendor=0x0001  product=0x0002.   Use the appropriate
-       vendor and product ids (e.g.  from  /var/log/messages,  dmesg,  or  cat
-       /proc/bus/usb/devices).   Some scanners supported by the gt68xx backend
+       scanner  driver, you need to tell the kernel the vendor and product ids
+       of your scanner. For Linux, this can be done with modprobe  parameters:
+       First,  remove  the scanner module (rmmod scanner), then load it again:
+       modprobe scanner vendor=0x0001  product=0x0002.   Use  the  appropriate
+       vendor  and  product  ids  (e.g.  from /var/log/messages, dmesg, or cat
+       /proc/bus/usb/devices).  Some scanners supported by the gt68xx  backend
        are not supported by the current version of the generic scanner driver.
-       See  sane-gt68xx(5)  for  details.  For these scanners, there will be a
+       See sane-gt68xx(5) for details. For these scanners,  there  will  be  a
        message concerning "only 2 or three endpoints" in syslog.
 
-       For OpenBSD the kernel may need to be recompiled. For details  look  at
-       /usr/local/doc/sane-1.0.14-cvs/README.openbsd.    Similar    approaches
-       should be used for the other BSDs.
+       For  OpenBSD  the kernel may need to be recompiled. For details look at
+       /usr/local/doc/sane-1.0.15/README.openbsd. Similar approaches should be
+       used for the other BSDs.
 
-       Linux kernel messages in syslog  like  "kernel:  scanner.c:  open_scan-
+       Linux  kernel  messages  in  syslog like "kernel: scanner.c: open_scan-
        ner(1): Unable to access minor data" can be ignored. They are generated
        when SANE scans all available USB devices for scanners.

SANE ISSUES

-       This section assumes that your scanner is detected  by  sane-find-scan-
-       ner.  It  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. Informa-
-       tion on the  level  of  support  can  be  found  on  the  SANE  webpage
+       This  section  assumes that your scanner is detected by sane-find-scan-
+       ner. It 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.  Informa-
+       tion  on  the  level  of  support  can  be  found  on  the SANE webpage
        (http://www.sane-project.org/), and the individual backend manpages.
 
        Most backends can detect USB scanners automatically using "usb" config-
-       uration file lines. This method allows to identify scanners by the  USB
-       vendor  and  product numbers.  The syntax for specifying a scanner this
+       uration  file lines. This method allows to identify scanners by the USB
+       vendor and product numbers.  The syntax for specifying a  scanner  this
        way is:
 
               usb VENDOR PRODUCT
 
        where VENDOR is the USB vendor id, and PRODUCT is the USB product id of
-       the  scanner.  Both  ids are non-negative integer numbers in decimal or
+       the scanner. Both ids are non-negative integer numbers  in  decimal  or
        hexadecimal format. The correct values for these fields can be found by
-       looking  into  the  syslog  (e.g., /var/log/messages) or under Linux by
-       issuing the command "cat /proc/bus/usb/devices/".  This is  an  example
+       looking into the syslog (e.g., /var/log/messages)  or  under  Linux  by
+       issuing  the  command "cat /proc/bus/usb/devices/".  This is an example
        of a config file line:
 
               usb 0x055f 0x0006
 
-       would  have the effect that all USB devices in the system with a vendor
-       id of 0x55f and a product id of 0x0006 would be probed  and  recognized
+       would have the effect that all USB devices in the system with a  vendor
+       id  of  0x55f and a product id of 0x0006 would be probed and recognized
        by the backend.
 
-       If  your  scanner is not detected automatically, it may be necessary to
-       edit the appropriate backend configuration file before using  SANE  for
-       the  first  time.  For most systems, the configuration file should list
+       If your scanner is not detected automatically, it may be  necessary  to
+       edit  the  appropriate backend configuration file before using SANE for
+       the first time.  For most systems, the configuration file  should  list
        the name of the USB device file that the scanner is connected to (e.g.,
-       under  Linux,  /dev/usb/scanner0  or  /dev/usbscanner0  is  such  a USB
-       device, the device file  for  FreeBSD  is  e.g.   /dev/uscanner0).   If
-       libusb  is  used,  the  device  name  looks like the following example:
+       under Linux,  /dev/usb/scanner0  or  /dev/usbscanner0  is  such  a  USB
+       device,  the  device  file  for  FreeBSD  is e.g.  /dev/uscanner0).  If
+       libusb is used, the device  name  looks  like  the  following  example:
        libusb:001:002.
 
        For a detailed description of each backend's configuration file, please
        refer to the relevant backend manual page (e.g.  sane-mustek_usb(5) for
        Mustek USB scanners).
 
-       Do not create a symlink from /dev/scanner to  the  USB  device  because
-       this  link is used by the SCSI backends. The scanner may be confused if
+       Do  not  create  a  symlink from /dev/scanner to the USB device because
+       this link is used by the SCSI backends. The scanner may be confused  if
        it receives SCSI commands.

ENVIRONMENT

        SANE_DEBUG_SANEI_USB
-              If the library was compiled with  debug  support  enabled,  this
-              environment  variable  controls  the debug level for the USB I/O
+              If  the  library  was  compiled with debug support enabled, this
+              environment variable controls the debug level for  the  USB  I/O
               subsystem.  E.g., a value of 128 requests all debug output to be
               printed.  Smaller levels reduce verbosity. Values greater than 4
-              enable  libusb  debugging  (if   available).   Example:   export
+              enable   libusb   debugging   (if  available).  Example:  export
               SANE_DEBUG_SANEI_USB=4.
 
 
@@ -222,7 +222,7 @@
 
AUTHOR
        Henning Meier-Geinitz
 
-sane-backends 1.0.14-cvs          8 Mar 2004                       sane-usb(5)
+sane-backends 1.0.15              8 Mar 2004                       sane-usb(5)
 

 

 

diff --git a/man/sane-v4l.5.html b/man/sane-v4l.5.html
index 43561408..fff112f9 100644
--- a/man/sane-v4l.5.html
+++ b/man/sane-v4l.5.html
@@ -105,7 +105,7 @@
 
SEE ALSO
        sane(7), xcam(1).
 
-sane-backends 1.0.14-cvs          28 Aug 2002                      sane-v4l(5)
+sane-backends 1.0.15              28 Aug 2002                      sane-v4l(5)
 

 

 

diff --git a/man/sane.7.html b/man/sane.7.html
deleted file mode 100644
index 44cb70f3..00000000
--- a/man/sane.7.html
+++ /dev/null
@@ -1,586 +0,0 @@
-
-
-sane.7
-
-

-
sane.7

-

-
-
-sane(7)                  SANE Scanner Access Now Easy                  sane(7)
-
-
-

-
NAME
-       sane - Scanner Access Now Easy: API for accessing scanners
-
-
-

-
DESCRIPTION
-       SANE  is an application programming interface (API) that provides stan-
-       dardized access to any raster image scanner hardware. The  standardized
-       interface  makes  it possible to write just one driver for each scanner
-       device instead of one driver for each scanner and application.
-
-       While SANE is primarily targeted at a UNIX  environment,  the  standard
-       has been carefully designed to make it possible to implement the API on
-       virtually any hardware or operating system.
-
-       This manual page provides a summary of the information available  about
-       SANE.
-
-       If  you  have  trouble getting your scanner detected, read the PROBLEMS
-       section.
-
-
-

-
TERMINOLOGY
-       An application that uses the SANE interface is called a SANE  frontend.
-       A  driver  that implements the SANE interface is called a SANE backend.
-       A meta backend provides some means to manage one or  more  other  back-
-       ends.
-
-
-

-
SOFTWARE PACKAGES
-       The  package  `sane-backends' contains a lot of backends, documentation
-       (including the SANE standard), networking support, and the command line
-       frontend   `scanimage'.    The   frontends  `xscanimage',  `xcam',  and
-       `scanadf' are included in the package `sane-frontends'.  Both  packages
-       can       be      downloaded      from      the      SANE      homepage
-       (http://www.sane-project.org/).  Information about other frontends  and
-       backends      can     be     found     on     the     frontend     page
-       (http://www.sane-project.org/sane-frontends.html).
-
-
-

-
GENERAL INFORMATION
-       The following sections provide short descriptions  and  links  to  more
-       information  about  several  aspects  of SANE.  A name with a number in
-       parenthesis (e.g.  `sane-dll(5)') points to a manual page. In this case
-       `man    5    sane-dll'    will   display   the   page.   Entries   like
-       `/usr/local/doc/sane-1.0.14-cvs/sane.tex' are references to text  files
-       that    were    copied    to    the    SANE   documentation   directory
-       (/usr/local/doc/sane-1.0.14-cvs/) during installation. Everything  else
-       is a URL to a resource on the web.
-
-       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:
-         http://www.sane-project.org/.
-
-       SANE device lists
-         The  SANE  device  lists contain information about the status of SANE
-         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:
-         http://www.sane-project.org/sane-supported-devices.html.   The  lists
-         are also installed on your system at /usr/local/doc/sane-1.0.14-cvs/.
-
-       SANE mailing list
-         There is a mailing list for the purpose of discussing the SANE  stan-
-         dard and its implementations: sane-devel.  Despite its name, the list
-         is not only intended for developers, but also for users.  Since  this
-         is currently the only mailing list devoted to SANE, it's perfectly OK
-         to ask questions that are not strictly related to  SANE  development.
-         How  to  subscribe and unsubscribe: http://www.sane-project.org/mail-
-         ing-lists.html.
-
-       SANE IRC channel
-         The IRC (Internet Relay Chat) channel  #sane  can  be  found  on  the
-         Freenode  network  (irc.freenode.net). It's for discussing SANE prob-
-         lems, talking about development and general  SANE  related  chatting.
-         Before asking for help, please read the other documentation mentioned
-         in this manual page.
-
-       Compiling and installing SANE
-         Look at /usr/local/doc/sane-1.0.14-cvs/README  and  the  os-dependent
-         README files for information about compiling and installing SANE.
-
-       SCSI configuration
-         For  information  about  various  systems  and  SCSI  controllers see
-         sane-scsi(5).
-
-       USB configuration
-         For information about USB configuration see sane-usb(5).
-
-
-

-
FRONTENDS AND MISCELLANEOUS PROGRAMS
-       scanimage
-         Command-line frontend. See scanimage(1).
-
-       saned
-         SANE network daemon that allows remote clients to access image acqui-
-         sition devices available on the local host. See saned(1).
-
-       sane-find-scanner
-         Command-line  tool  to find SCSI and USB scanners and determine their
-         Unix device files. See sane-find-scanner(1).
-
-       Also, have a look at the sane-frontends package (including  xscanimage,
-       xcam,   and   scanadf)   and   the   frontend   information   page   at
-       http://www.sane-project.org/sane-frontends.html.
-
-
-

-
BACKENDS FOR SCANNERS
-       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 sane-abaton(5) for details.
-
-       agfafocus
-         This backend supports AGFA  Focus  scanners  and  the  Siemens  S9036
-         (untested).  See sane-agfafocus(5) for details.
-
-       apple
-         The  SANE  backend  for Apple flatbed scanners supports the following
-         scanners:   AppleScanner,   OneScanner   and   ColorOneScanner.   See
-         sane-apple(5) for details.
-
-       artec
-         The  SANE  Artec  backend  supports several Artec/Ultima SCSI flatbed
-         scanners as well as the BlackWidow BW4800SP and the  Plustek  19200S.
-         See sane-artec(5) for details.
-
-       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 sane-artec_eplus48u(5) for details.
-
-       as6e
-         This is a SANE backend for using the Artec AS6E parallel port  inter-
-         face scanner. See sane-as6e(5) for details.
-
-       avision
-         This  backend  supports several Avision based scanners. This includes
-         the original Avision scanners (like AV 630, AV 620, ...) as  well  as
-         the  HP  ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit-
-         subishi and Minolta film-scanners.  See sane-avision(5) for  details.
-
-       bh
-         The bh backend provides access to Bell+Howell Copiscan II series doc-
-         ument scanners. See sane-bh(5) for details.
-
-       canon
-         The canon backend  supports  the  CanoScan  300,  CanoScan  600,  and
-         CanoScan  2700F SCSI flatbed scanners. See sane-canon(5) for details.
-
-       canon630u
-         The canon630u backend supports the CanoScan 630u and 636u  USB  scan-
-         ners.  See sane-canon630u(5) for details.
-
-       canon_pp
-         The  canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
-         N640P parallel port scanners.  See sane-canon_pp(5) for details.
-
-       coolscan
-         This  is  a  SANE  backend  for  Nikon  Coolscan  film-scanners.  See
-         sane-coolscan(5) for details.
-
-       coolscan2
-         This  is  a  SANE  backend  for  Nikon  Coolscan  film-scanners.  See
-         sane-coolscan2(5) or http://coolscan2.sourceforge.net for details.
-
-       epson
-         The SANE epson backend provides support for Epson SCSI, parallel port
-         and USB flatbed scanners. See sane-epson(5) for details.
-
-       fujitsu
-         The fujitsu backend provides support for Fujitsu 3091, 3093, 3096 and
-         fi-4340 SCSI scanners. See sane-fujitsu(5) for details.
-
-       gt68xx
-         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 sane-gt68xx(5) for details.
-
-       hp
-         The SANE hp backend provides access to Hewlett-Packard ScanJet  scan-
-         ners  which  support  SCL  (Scanner  Control  Language  by  HP).  See
-         sane-hp(5) for details.
-
-       hpsj5s
-         The SANE backend for the  Hewlett-Packard  ScanJet  5S  scanner.  See
-         sane-hpsj5s(5) for details.
-
-       hp5400
-         The  SANE  backend  for the Hewlett-Packard ScanJet 54XXC series. See
-         sane-hp5400(5) for details.
-
-       ibm
-         The  SANE  backend  for  some  IBM  and  Ricoh  SCSI  scanners.   See
-         sane-ibm(5) for details.
-
-       leo
-         This  backend  supports the Leo S3 and the Across FS-1130, which is a
-         re-badged LEO FS-1130 scanner. See sane-leo(5) for details.
-
-       ma1509
-         The ma1509 backend supports the  Mustek  BearPaw  1200F  USB  flatbed
-         scanner. See sane-ma1509(5) for details.
-
-       matsushita
-         This  backend  supports  some Panasonic KVSS high speed scanners. See
-         sane-matsushita(5) for details.
-
-       microtek
-         The microtek backend  provides  access  to  the  "second  generation"
-         Microtek  scanners  with SCSI-1 command set. See sane-microtek(5) for
-         details.
-
-       microtek2
-         The microtek2 backend provides access to some Microtek scanners  with
-         a SCSI-2 command set. See sane-microtek2(5) for details.
-
-       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
-         sane-mustek(5) for details.
-
-       mustek_pp
-         The mustek_pp backend provides access to Mustek parallel port flatbed
-         scannersr. See sane-mustek_pp(5) for details.
-
-       mustek_usb
-         The mustek_usb backend provides access to some Mustek ScanExpress USB
-         flatbed scanners. See sane-mustek_usb(5) for details.
-
-       nec
-         The SANE nec backend supports the NEC PC-IN500/4C SCSI  scanner.  See
-         sane-nec(5) for details.
-
-       pie
-         The  pie  backend  provides access to Pacific Image Electronics (PIE)
-         and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
-
-       plustek
-         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 sane-plustek(5)
-         for details.
-
-       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
-         sane-plustek_pp(5) for details.
-
-       ricoh
-         The  ricoh  backend  provides  access  to the following Ricoh flatbed
-         scanners: IS50 and IS60. See sane-ricoh(5) for details.
-
-       s9036
-         The s9036 backend provides access to Siemens 9036  flatbed  scanners.
-         See sane-s9036(5) for details.
-
-       sceptre
-         The  sceptre  backend  provides  access  to the Sceptre S1200 flatbed
-         scanner. See sane-sceptre(5)
-          for details.
-
-       sharp
-         The  SANE  sharp  backend   supports   Sharp   SCSI   scanners.   See
-         sane-sharp(5) for details.
-
-       sm3600
-         The  SANE  sm3600  backend  supports  the Microtek ScanMaker 3600 USB
-         scanner. See sane-sm3600(5) for details.
-
-       snapscan
-         The snapscan backend supports AGFA  SnapScan  flatbed  scanners.  See
-         sane-snapscan(5) for details.
-
-       sp15c
-         This  backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
-         ner. See sane-sp15c(5) for details.
-
-       st400
-         The sane-st400 backend provides access to Siemens  ST400  and  ST800.
-         See sane-st400(5) for details.
-
-       tamarack
-         The  SANE  tamarack  backend supports Tamarack Artiscan flatbed scan-
-         ners. See sane-tamarack(5) for details.
-
-       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 sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
-
-       umax
-         The sane-umax backend provides access to  several  UMAX-SCSI-scanners
-         and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
-
-       umax_pp
-         The  sane-umax_pp  backend  provides  access  to  Umax  parallel port
-         flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
-
-       umax1200u
-         The sane-umax1220u  backend  supports  the  UMAX  Astra  1220U  (USB)
-         flatbed  scanner  (and  also  the  UMAX  Astra  2000U,  sort of). See
-         sane-umax1220u(5) for details.
-
-       Also,   have   a   look   at   the   backend   information   page    at
-       http://www.sane-project.org/sane-supported-devices.html and the list of
-       projects in /usr/local/doc/sane-1.0.14-cvs/PROJECTS.
-
-
-

-
BACKENDS FOR DIGITAL CAMERAS
-       dc210
-         Backend for Kodak DC210 Digital Camera. See sane-dc210(5).
-
-       dc240
-         Backend for Kodak DC240 Digital Camera. See sane-dc240(5).
-
-       dc25
-         Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5).
-
-       dmc
-         Backend for the Polaroid Digital Microscope Camera. See  sane-dmc(5).
-
-       gphoto2
-         Backend for digital cameras supported by the gphoto2 library package.
-         (See  http://www.gphoto.org  for  more  information  and  a  list  of
-         supported  cameras.)  Gphoto2 supports over 140 different camera mod-
-         els.  However, please note  that  more  development  and  testing  is
-         needed before all of these cameras will be supported by SANE backend.
-         See sane-gphoto2(5).
-
-       qcam
-         Backend for Connectix QuickCam cameras. See sane-qcam(5).
-
-       Also,   have   a   look   at   the   backend   information   page    at
-       http://www.sane-project.org/sane-supported-devices.html and the list of
-       projects in /usr/local/doc/sane-1.0.14-cvs/PROJECTS.
-
-
-

-
MISCELLANEOUS BACKENDS
-       dll
-         The sane-dll library implements a SANE backend that  provides  access
-         to an arbitrary number of other SANE backends by dynamic loading. See
-         sane-dll(5).
-
-       net
-         The SANE network daemon saned provides access to scanners located  on
-         different   computers   in  connection  with  the  net  backend.  See
-         sane-net(5) and saned(1).
-
-       pnm
-         PNM image reader pseudo-backend. The purpose of this backend is  pri-
-         marily to aid in debugging of SANE frontends. See sane-pnm(5).
-
-       pint
-         Backend  for  scanners  that  use the PINT (Pint Is Not Twain) device
-         driver.  The PINT driver is being actively developed on  the  OpenBSD
-         platform, and has been ported to a few other *nix-like operating sys-
-         tems. See sane-pint(5).
-
-       test
-         The SANE test backend is for testing frontends and the SANE installa-
-         tion.   It  provides  test  pictures  and  various  test options. See
-         sane-test(5).
-
-       v4l
-         The sane-v4l library implements a SANE backend that provides  generic
-         access  to  video  cameras and similar equipment using the V4L (Video
-         for Linux) API. See sane-v4l(5).
-
-       Also,   have   a   look   at   the   backend   information   page    at
-       http://www.sane-project.org/sane-supported-devices.html and the list of
-       projects in /usr/local/doc/sane-1.0.14-cvs/PROJECTS.
-
-
-

-
CHANGING THE TOP-LEVEL BACKEND
-       By default, all SANE backends (drivers) are loaded dynamically  by  the
-       sane-dll  meta  backend.  If  you  have any questions about the dynamic
-       loading, read sane-dll(5).  SANE frontend can also be linked  to  other
-       backends  directly  by  copying  or  linking a backend to libsane.so in
-       /usr/local/lib/sane.
-
-
-

-
DEVELOPER'S DOCUMENTATION
-       It's not hard to write a SANE backend. It can take some time,  however.
-       You  should  have  basic  knowledge  of  C  and enough patience to work
-       through the documentation and find out how your scanner works. Appended
-       is  a list of some documents that help to write backends and frontends.
-
-       The SANE standard defines the application programming  interface  (API)
-       that  is  used to communicate between frontends and backends. It can be
-       found at /usr/local/doc/sane-1.0.14-cvs/sane.ps (if latex is  installed
-       on      your      system)      and     on     the     SANE     website:
-       http://www.sane-project.org/html/              (HTML),               or
-       http://www.sane-project.org/sane.ps (Postscript).
-
-       There     is    some    more    information    for    programmers    in
-       /usr/local/doc/sane-1.0.14-cvs/backend-writing.txt.  Most of the inter-
-       nal    SANE    routines   (sanei)   are   documented   using   doxygen:
-       http://www.sane-project.org/sanei/.  Before a new backend  or  frontend
-       project        is       started,       have       a       look       at
-       /usr/local/doc/sane-1.0.14-cvs/PROJECTS for projects that  are  planned
-       or  not yet included into the SANE distribution and at our bug-tracking
-       system: http://www.http://www.sane-project.org/bugs.html.
-
-       There are some links on how to find out about the protocol of  a  scan-
-       ner: http://www.meier-geinitz.de/sane/misc/develop.html.
-
-       If  you  start writing a backend or frontend or any other part of SANE,
-       please contact the sane-devel mailing list for coordination so the same
-       work isn't done twice.
-
-
-

-
FILES
-       /usr/local/etc/sane.d/*.conf
-              The backend configuration files.
-
-       /usr/local/lib/sane/libsane-*.a
-              The static libraries implementing the backends.
-
-       /usr/local/lib/sane/libsane-*.so
-              The  shared libraries implementing the backends (present on sys-
-              tems that support dynamic loading).
-
-       /usr/local/doc/sane-1.0.14-cvs/*
-              SANE documentation: The standard, READMEs, text files for  back-
-              ends etc.
-
-
-

-
PROBLEMS
-       If your device isn't found but you know that it is supported, make sure
-       that it is detected by your operating system. For SCSI  and  USB  scan-
-       ners,  use  the  sane-find-scanner  tool  (see sane-find-scanner(1) for
-       details). It prints one line for each scanner it has detected and  some
-       comments  (#). If sane-find-scanner 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 sane-usb(5) or sane-scsi(5).  If your scanner (or
-       other device) is not connected over the SCSI bus or USB, read the back-
-       end's manual page for details on how to set it up.
-
-       Now  your  scanner is detected by the operating system but not by SANE?
-       Try scanimage -L.  If the scanner is not found, check  that  the  back-
-       end's  name is mentioned in /usr/local/etc/sane.d/dll.conf.  Some back-
-       ends are commented out by default. Remove the  comment  sign  for  your
-       backend  in this case. Also some backends aren't compiled at all if one
-       of their prerequisites are  missing.  Examples  include  dc210,  dc240,
-       canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan, pnm.
-       If you need one of these backends and they aren't available,  read  the
-       build  instructions  in the README file and the individual manual pages
-       of the backends.
-
-       Another reason for not being detected by scanimage -L may be a  missing
-       or  wrong configuration in the backend's configuration file. While SANE
-       tries to automatically find most scanners, some  can't  be  setup  cor-
-       rectly  without  the  intervention  of  the administrator. Also on some
-       operating systems auto-detection may not work. Check the backend's man-
-       ual page for details.
-
-       If your scanner is still not found, try setting the various environment
-       variables that are available to assist in debugging.   The  environment
-       variables are documented in the relevant manual pages.  For example, to
-       get the maximum amount of debug information when testing a Mustek  SCSI
-       scanner,  set  environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
-       and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage  -L  .   The
-       debug messages for the dll backend tell if the mustek backend was found
-       and loaded at all. The mustek messages explain what the mustek  backend
-       is  doing while the SCSI debugging shows the low level handling. If you
-       can't find out what's going on by checking the messages carefully, con-
-       tact the sane-devel mailing list for help (see REPORTING BUGS below).
-
-       Now that your scanner is found by scanimage -L, try to do a scan: scan-
-       image >image.pnm.  This command starts a scan for the  default  scanner
-       with  default settings. All the available options are listed by running
-       scanimage --help.  If scanning aborts with an error  message,  turn  on
-       debugging  as  mentioned above. Maybe the configuration file needs some
-       tuning, e.g. to setup the path to a firmware that  is  needed  by  some
-       scanners.  See the backend's manual page for details. If you can't find
-       out what's wrong, contact sane-devel.
-
-       To check that the SANE libraries are installed correctly  you  can  use
-       the  test  backend,  even  if  you  don't  have a scanner or other SANE
-       device:
-
-              scanimage -d test -T
-
-       You should get a list of PASSed tests. You can do the  same  with  your
-       backend by changing "test" to your backend's name.
-
-       So  now  scanning  with  scanimage works and you want to use one of the
-       graphical frontends like xsane, xscanimage, or  quiteinsane  but  those
-       frontends  don't  detect  your  scanner?  One  reason  may  be that you
-       installed two versions of SANE.  E.g. the version that was installed by
-       your  distribution  in  /usr  and  one  you  installed  from  source in
-       /usr/local/.  Make sure that only one  version  is  installed.  Another
-       possible  reason  is,  that your system's dynamic loader can't find the
-       SANE libraries. For Linux,  make  sure  that  /etc/ld.so.conf  contains
-       /usr/local/lib  and does not contain /usr/local/lib/sane.  See also the
-       documentation of the frontends.
-
-
-

-
HOW CAN YOU HELP SANE
-       We appreciate any help we can get. Please have alook at  our  web  page
-       about contributing to SANE: http://www.sane-project.org/contrib.html
-
-
-

-
CONTACT
-       For  reporting  bugs  or  requesting  new features, please use our bug-
-       tracking system: 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 /usr/local/doc/sane-1.0.14-cvs/AUTHORS file or  the
-       backend's  manpage.  For  general discussion about SANE, please use the
-       SANE mailing  list  sane-devel  (see  http://www.sane-project.org/mail-
-       ing-lists.html for details).
-
-
-

-
SEE ALSO
-       saned(1),     sane-find-scanner(1),    scanimage(1),    sane-abaton(5),
-       sane-agfafocus(5),            sane-apple(5),             sane-artec(5),
-       sane-artec_eplus48u(5),   sane-as6e(5),   sane-avision(5),  sane-bh(5),
-       sane-canon(5), sane-canon630u(5), sane-canon_pp(5),  sane-coolscan2(5),
-       sane-coolscan(5),     sane-dc210(5),    sane-dc240(5),    sane-dc25(5),
-       sane-dll(5),     sane-dmc(5),      sane-epson(5),      sane-fujitsu(5),
-       sane-gphoto2(5),     sane-gt68xx(5),     sane-hp(5),    sane-hpsj5s(5),
-       sane-hp5400(5)      sane-ibm(5),      sane-leo(5),      sane-ma1509(5),
-       sane-matsushita(5),         sane-microtek2(5),        sane-microtek(5),
-       sane-mustek(5),  sane-mustek_pp(5),  sane-mustek_usb(5),   sane-nec(5),
-       sane-net(5),  sane-pie(5),  sane-pint(5),  sane-plustek(5),  sane-plus-
-       tek_pp(5),  sane-pnm(5),  sane-qcam(5),  sane-ricoh(5),  sane-s9036(5),
-       sane-sceptre(5),     sane-scsi(5),    sane-sharp(5),    sane-sm3600(5),
-       sane-snapscan(5),   sane-sp15c(5),   sane-st400(5),   sane-tamarack(5),
-       sane-teco1(5), sane-teco2(5), sane-teco3(5), sane-test(5), sane-u12(5),
-       sane-umax1220u(5),    sane-umax(5),    sane-umax_pp(5),    sane-usb(5),
-       sane-v4l(5)
-
-
-

-
AUTHOR
-       David      Mosberger-Tang      and      many     many     more     (see
-       /usr/local/doc/sane-1.0.14-cvs/AUTHORS for details).  This man page was
-       written  by  Henning  Meier-Geinitz. Quite a lot of text was taken from
-       the SANE standard, several man pages, and README files.
-
-sane-backends 1.0.14-cvs          06 Jan 2004                          sane(7)
-

-

-

-Man(1) output converted with
-man2html
-

-
-
diff --git a/man/scanimage.1.html b/man/scanimage.1.html
index 757d90ee..08fd7831 100644
--- a/man/scanimage.1.html
+++ b/man/scanimage.1.html
@@ -115,7 +115,7 @@
 
        The  --accept-md5-only  option only accepts user authorization requests
        that support MD5 security. The SANE network daemon (saned)  is  capable
-       of doing such requests. See saned(1).
+       of doing such requests. See saned(8).
 
        The  -n  or  --dont-scan  option  requests that scanimage only sets the
        options provided by the user but doesn't actually perform a scan.  This
@@ -274,7 +274,7 @@
        For vector options, the help output currently has no indication  as  to
        how many elements a vector-value should have.
 
-sane-backends 1.0.14-cvs          22 Feb 2004                     scanimage(1)
+sane-backends 1.0.15              22 Feb 2004                     scanimage(1)