diff options
| author | Jörg Frings-Fürst <debian@jff-webhosting.net> | 2019-07-31 17:00:58 +0200 | 
|---|---|---|
| committer | Jörg Frings-Fürst <debian@jff-webhosting.net> | 2019-07-31 17:00:58 +0200 | 
| commit | d087d778ffb62e2713cb848540bcc819470365bd (patch) | |
| tree | d69692a274dd1c7d0672e6bb7155a0fc106f9d49 /doc/sane-kodak.man | |
| parent | c8bd2513ecba169cff44c09c8058c36987357b18 (diff) | |
| parent | 3759ce55ba79b8d3b9d8ed247a252273ee7dade3 (diff) | |
Merge branch 'feature/upstream' into develop
Diffstat (limited to 'doc/sane-kodak.man')
| -rw-r--r-- | doc/sane-kodak.man | 42 | 
1 files changed, 21 insertions, 21 deletions
| diff --git a/doc/sane-kodak.man b/doc/sane-kodak.man index 2566f3d..61ea88e 100644 --- a/doc/sane-kodak.man +++ b/doc/sane-kodak.man @@ -5,7 +5,7 @@  sane\-kodak \- SANE backend for big Kodak flatbed and ADF scanners  .SH DESCRIPTION -The  +The  .B sane\-kodak  library implements a SANE (Scanner Access Now Easy) backend which  provides access to large Kodak flatbed and ADF scanners. @@ -13,44 +13,44 @@ provides access to large Kodak flatbed and ADF scanners.  This document describes backend version 7, which shipped with SANE 1.0.21.  .SH SUPPORTED HARDWARE -This version should support models which speak the Kodak SCSI and Firewire  -protocols. The i1860 was used to develop the backend, but other models may  -work with only minimal modifications. Please see the list at  +This version should support models which speak the Kodak SCSI and Firewire +protocols. The i1860 was used to develop the backend, but other models may +work with only minimal modifications. Please see the list at  http://www.sane\-project.org/sane\-supported\-devices.html for an updated list. -If you have a machine not on that list, or reported as 'untested': the best way  -to determine level of support is to test the scanner directly, or to collect a  -trace of the windows driver in action.  Please contact the author for help or  +If you have a machine not on that list, or reported as 'untested': the best way +to determine level of support is to test the scanner directly, or to collect a +trace of the windows driver in action.  Please contact the author for help or  with test results.  .SH UNSUPPORTED HARDWARE -Most of the recent Kodak consumer or workgroup level machines are based on  -other chipsets and are not supported by this backend. Some of these scanners  +Most of the recent Kodak consumer or workgroup level machines are based on +other chipsets and are not supported by this backend. Some of these scanners  may be supported by another backend.  .SH OPTIONS  Effort has been made to expose the basic hardware options, including:  .PP -source s  +source s  .RS  Selects the source for the scan. Options  may include "Flatbed", "ADF Front", "ADF Back", "ADF Duplex".  .RE  .PP -mode m  +mode m  .RS  Selects the mode for the scan. Options  may include "Lineart", "Halftone", "Gray", and "Color".  .RE  .PP -resolution  +resolution  .RS  Controls scan resolution. Available choices may be limited by mode.  .RE  .PP  tl\-x, tl\-y, br\-x, br\-y  .RS -Sets scan area upper left and lower right coordinates. These are renamed  +Sets scan area upper left and lower right coordinates. These are renamed  t, l, x, y by some frontends.  .RE  .PP @@ -61,14 +61,14 @@ coordinates when using ADF and to detect double feed errors.  .RE  .PP  Other options will be available based on the capabilities of the scanner. -Use 'scanimage \-\-help' to get a list, but be aware that some options may  -be settable only when another option has been set, and that advanced options  +Use 'scanimage \-\-help' to get a list, but be aware that some options may +be settable only when another option has been set, and that advanced options  may be hidden by some frontend programs.  .PP  .SH CONFIGURATION FILE  The configuration file "kodak.conf" is used to tell the backend how to look  for scanners, and provide options controlling the operation of the backend. -This file is read each time the frontend asks the backend for a list  +This file is read each time the frontend asks the backend for a list  of scanners, generally only when the frontend starts. If the configuration  file is missing, the backend will use a set of compiled defaults, which  are identical to the default configuration file shipped with SANE. @@ -77,8 +77,8 @@ Scanners can be specified in the configuration file in 2 ways:  .PP  "scsi KODAK"  .RS -Requests backend to search all scsi busses in the system for a device  -which reports itself to be a scanner made by 'KODAK'.  +Requests backend to search all scsi busses in the system for a device +which reports itself to be a scanner made by 'KODAK'.  .RE  .PP  "scsi /dev/sg0" (or other scsi device file) @@ -89,7 +89,7 @@ specify one. Probably should not be used with the other "scsi" line above.  .RE  .PP  The only configuration option supported is "buffer\-size=xxx", allowing you -to set the number of bytes in the data buffer to something other than the  +to set the number of bytes in the data buffer to something other than the  compiled\-in default, 32768 (32K). Some users report that their scanner will  "hang" mid\-page, or fail to transmit the image if the buffer is not large  enough. @@ -124,7 +124,7 @@ enables debugging output to stderr. Valid values are:  .RE  .SH KNOWN ISSUES -Most hardware options are either not supported or not exposed for control by  +Most hardware options are either not supported or not exposed for control by  the user, including: multifeed detection, image compression, autocropping,  endorser, iThresholding, multi\-stream, etc.  .PP @@ -133,7 +133,7 @@ endorser, iThresholding, multi\-stream, etc.  The various authors of the sane\-fujitsu backend provided useful code.  .br  Kodak provided access to hardware, documentation and personnel. -   +  .SH "SEE ALSO"  sane(7),  sane\-scsi(5) | 
