kopia lustrzana https://gitlab.com/sane-project/backends
doc: cosmetic corrections to man pages from translator review
Ralph Little
rodzic
312edd6d5f
commit
d6419c2490
|
|
@ -84,7 +84,7 @@ support dynamic loading).
|
|||
.SH ENVIRONMENT
|
||||
.TP
|
||||
.B SANE_CONFIG_DIR
|
||||
This environment variable is list of directories where SANE looks
|
||||
This environment variable is a list of directories where SANE looks
|
||||
for the configuration file. On *NIX systems, directory names are
|
||||
separated by a colon (`:'), under OS/2 by a semi-colon (`;').
|
||||
If SANE_CONFIG_DIR is not set, SANE defaults to
|
||||
|
|
@ -177,7 +177,6 @@ bugs.
|
|||
We know we have a GUI bug when a parameter is not showing up when it
|
||||
should (active) or vice versa. Finding out which parameters are active
|
||||
across various Apple modes and models from the documentation
|
||||
.I ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripherals_Documentation/
|
||||
is an interesting exercise. I may have missed some dependencies. For example
|
||||
of the threshold parameter the Apple Scanners Programming Guide says
|
||||
nothing. I had to assume it is valid only in LineArt mode.
|
||||
|
|
@ -238,7 +237,8 @@ looks like, goto to
|
|||
.I apple.h
|
||||
and #define the
|
||||
.B NEUTRALIZE_BACKEND
|
||||
macro. You can select the scanner model through the APPLE_MODEL_SELECT
|
||||
macro. You can select the scanner model through the
|
||||
.B APPLE_MODEL_SELECT
|
||||
macro. Available options are
|
||||
.BR APPLESCANNER ,
|
||||
.BR ONESCANNER ,
|
||||
|
|
@ -246,7 +246,9 @@ and
|
|||
.BR COLORONESCANNER .
|
||||
.PP
|
||||
If you encounter a SCSI bus error or trimmed and/or displaced images please
|
||||
set the environment variable SANE_DEBUG_SANEI_SCSI to 255 before sending me
|
||||
set the environment variable
|
||||
.B SANE_DEBUG_SANEI_SCSI
|
||||
to 255 before sending me
|
||||
the report.
|
||||
|
||||
.SH TODO
|
||||
|
|
@ -257,12 +259,12 @@ Make
|
|||
a non blocking backend. Properly support
|
||||
.BR sane_set_io_mode ()
|
||||
and
|
||||
.BR sane_get_select_fd ()
|
||||
.BR sane_get_select_fd ().
|
||||
.TP
|
||||
.B Scan
|
||||
Make scanning possible for all models in all supported modes.
|
||||
.PP
|
||||
Add other missing functionality
|
||||
Add other missing functionality.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
.BR sane (7),
|
||||
|
|
@ -274,4 +276,4 @@ The
|
|||
backend was written not entirely from scratch by
|
||||
Milon Firikis. It is mostly based on the
|
||||
.BR sane\-mustek (5)
|
||||
backend from David Mosberger and Andreas Czechanowski
|
||||
backend from David Mosberger and Andreas Czechanowski.
|
||||
|
|
|
|||
|
|
@ -50,7 +50,9 @@ find the firmware file under
|
|||
.SH CONFIGURATION
|
||||
The contents of the
|
||||
.I artec_eplus48u.conf
|
||||
file is a list of usb lines containing vendor and product ids that correspond
|
||||
file is a list of
|
||||
.I 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
|
||||
|
|
@ -59,7 +61,9 @@ statements which are already included into
|
|||
.I artec_eplus48u.conf .
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identify the scanner.
|
||||
.PP
|
||||
Every usb section can have additional options.
|
||||
Every
|
||||
.I usb
|
||||
section can have additional options.
|
||||
.TP
|
||||
.B artecFirmwareFile @DATADIR@/sane/artec_eplus48u/Artec48.usb
|
||||
The path to the firmware file. This option is required.
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ compression is disabled and the image is delivered in a
|
|||
frame.
|
||||
.TP
|
||||
.B \-\-mode lineart|halftone [lineart]
|
||||
Selects the scan mode (e.g., lineart,monochrome, or color).
|
||||
Selects the scan mode (e.g., lineart, monochrome, or color).
|
||||
.TP
|
||||
.B \-\-resolution 200|240|300dpi [200]
|
||||
Sets the resolution of the scanned image. Each scanner model supports
|
||||
|
|
@ -148,7 +148,8 @@ Bottom-right y position of scan area.
|
|||
.B \-\-source Automatic Document Feeder|Manual Feed Tray [Automatic Document Feeder]
|
||||
Selects the scan source (such as a document feeder). This option is provided
|
||||
to allow multiple image scans with
|
||||
.BR xsane (1); it has no other purpose.
|
||||
.BR xsane (1);
|
||||
it has no other purpose.
|
||||
.TP
|
||||
.B \-\-batch[=(yes|no)] [no]
|
||||
Enable/disable batch mode scanning. Batch mode allows scanning at maximum throughput
|
||||
|
|
@ -171,7 +172,7 @@ Sets the timeout in seconds for semi-automatic feeder. The value 0 specifies
|
|||
the hardware default value which varies based on the scanner model.
|
||||
.TP
|
||||
.B \-\-check\-adf[=(yes|no)] [no]
|
||||
Check ADF Status prior to starting scan using the OBJECT POSITION command.
|
||||
Check ADF status prior to starting scan using the OBJECT POSITION command.
|
||||
Note that this feature requires RSC firmware level 1.5 or higher and dip
|
||||
switch 4 must be in the on position. NOTE: This option has not been tested
|
||||
extensively and may produce undesirable results.
|
||||
|
|
@ -381,7 +382,7 @@ with a hash mark (#) are ignored.
|
|||
.SH OPTIONS
|
||||
The following options can be specified in the
|
||||
.I bh.conf
|
||||
file.
|
||||
file:
|
||||
.TP
|
||||
.B disable\-optional\-frames
|
||||
This option prevents the backend from sending any optional frames. This
|
||||
|
|
@ -544,7 +545,9 @@ prior to initiating the last scan command. Currently, there is no mechanism
|
|||
available for the frontend to pass this knowledge to the backend.
|
||||
If batch mode is enabled and the
|
||||
.B \-\-end\-count
|
||||
terminates a scanadf session,
|
||||
terminates a
|
||||
.BR scanadf (1)
|
||||
session,
|
||||
an extra page will be pulled through the scanner, but is neither read
|
||||
nor delivered to the frontend. The issue can be avoided by specifying
|
||||
.B \-\-batch=no
|
||||
|
|
@ -556,7 +559,7 @@ with revision 1.2 or higher that is faster and more reliable than the
|
|||
standard Bar/Patch code decoder. This is not currently supported.
|
||||
|
||||
.SH BUGS
|
||||
This is a new backend; detailed bug reports are welcome -- and expected ;)
|
||||
Detailed bug reports are welcome -- and expected ;)
|
||||
.PP
|
||||
If you have found something that you think is a bug, please attempt to
|
||||
recreate it with the
|
||||
|
|
|
|||
|
|
@ -68,30 +68,28 @@ The supported options are currently
|
|||
and
|
||||
.BR force_nibble
|
||||
|
||||
Option
|
||||
.B ieee1284
|
||||
.IR port-name
|
||||
defines which port to use. The format of port-name is OS dependent, based on
|
||||
the names presented by libieee1284. Please only have one of these lines, or
|
||||
.TP
|
||||
.B ieee1284 port-name
|
||||
Defines which port to use. The format of port-name is OS dependent, based on
|
||||
the names presented by
|
||||
.BR libieee1284 (3).
|
||||
Please only have one of these lines, or
|
||||
all but one will be ignored.
|
||||
|
||||
Option
|
||||
.B calibrate
|
||||
.IR cal-file
|
||||
.IR [port-name]
|
||||
defines which calibration file to use on a per-port basis. If you only have
|
||||
.TP
|
||||
.B calibrate cal-file [port-name]
|
||||
Defines which calibration file to use on a per-port basis. If you only have
|
||||
one parport, the port-name argument may be omitted \- but be careful as this
|
||||
will cause problems on multi-scanner systems. You may have as many of these
|
||||
lines as you like, as long as each has a unique port name. The tilde (`~')
|
||||
character is acceptable and will be expanded to the value of the HOME
|
||||
environment.
|
||||
character is acceptable and will be expanded to the value of the
|
||||
.B HOME
|
||||
environment variable.
|
||||
|
||||
Option
|
||||
.B init_mode
|
||||
.IR <AUTO|FB620P|FB630P>
|
||||
.IR [portname]
|
||||
defines which initialisation (wake-up) mode to use on a per-port basis.
|
||||
If you only have one parport, the portname argument may be omitted \- but
|
||||
.TP
|
||||
.B init_mode <AUTO|FB620P|FB630P> [port-name]
|
||||
Defines which initialisation (wake-up) mode to use on a per-port basis.
|
||||
If you only have one parport, the port-name argument may be omitted \- but
|
||||
be careful as this may cause problems on multi-scanner systems.
|
||||
You may have as many of these lines as you like, as long as each has a unique
|
||||
port name. The valid initialisation modes are FB620P (which strobes 10101010
|
||||
|
|
@ -100,10 +98,11 @@ on the data pins) and AUTO, which will try FB630P mode first then FB620P mode
|
|||
second. The FB620P mode is also used by the FB320P. The FB630P mode is used
|
||||
by the FB330P, N340P, and N640P.
|
||||
|
||||
Option
|
||||
.TP
|
||||
.B force_nibble
|
||||
forces the driver to use nibble mode even if ECP mode is reported to work by
|
||||
libieee1284. This works-around the rare issue of ECP mode being reported to
|
||||
Forces the driver to use nibble mode even if ECP mode is reported to work by
|
||||
.BR libieee1284 (3).
|
||||
This works-around the rare issue of ECP mode being reported to
|
||||
work by the library, then not working.
|
||||
|
||||
.SH TIPS
|
||||
|
|
@ -174,7 +173,9 @@ one returned during calibration) will be loaded.
|
|||
.PP
|
||||
.B Communication Problems
|
||||
.PP
|
||||
ECP mode in libieee1284 doesn't always work properly, even with new hardware.
|
||||
ECP mode in
|
||||
.BR libieee1284 (3)
|
||||
doesn't always work properly, even with new hardware.
|
||||
We believe that this is a ppdev problem. If you change the configuration file
|
||||
to include
|
||||
.B force_nibble
|
||||
|
|
|
|||
|
|
@ -123,9 +123,9 @@ Eject the film strip or mounted slide when using the slide loader.
|
|||
.TP
|
||||
.B \-\-reset
|
||||
Reset scanner. The scanner will perform the same action as when power is
|
||||
turned on: it will eject the film strip (with the SF\-200 bulk feeder)
|
||||
turned on: it will eject the slide (with the SF\-200 bulk feeder)
|
||||
and calibrate itself. Use this whenever the scanner refuses to load
|
||||
a film strip properly, as a result of
|
||||
a slide properly, as a result of
|
||||
which
|
||||
.B \-\-eject
|
||||
does not work.
|
||||
|
|
|
|||
|
|
@ -82,7 +82,9 @@ unit is mm).
|
|||
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
|
||||
If you use
|
||||
.BR scanimage (1),
|
||||
perform a batch scan with
|
||||
.B \-\-batch\-count=2
|
||||
to obtain the IR information.
|
||||
.TP
|
||||
|
|
@ -120,9 +122,9 @@ Eject the film strip or mounted slide when using the slide loader.
|
|||
.TP
|
||||
.B \-\-reset
|
||||
Reset scanner. The scanner will perform the same action as when power is
|
||||
turned on: it will eject the film strip (with the SF\-200 bulk loader)
|
||||
turned on: it will eject the slide (with the SF\-200 bulk loader)
|
||||
and calibrate itself. Use this
|
||||
whenever the scanner refuses to load a film strip properly, as a result of
|
||||
whenever the scanner refuses to load a slide properly, as a result of
|
||||
which
|
||||
.B \-\-eject
|
||||
does not work.
|
||||
|
|
|
|||
|
|
@ -49,7 +49,9 @@ This image is a 1599-by-1200 pixel full-color image constructed by filtering
|
|||
and interpolating the "raw" image. The filtering and interpolation is
|
||||
done in software, so this mode is very slow. Also, this mode places
|
||||
restrictions on how the image is read which means that the "preview" mode
|
||||
of xscanimage does not work in Super Resolution mode.
|
||||
of
|
||||
.BR xscanimage (1)
|
||||
does not work in Super Resolution mode.
|
||||
.RB ( xcam (1)
|
||||
and the non-preview modes of
|
||||
.BR scanimage (1)
|
||||
|
|
@ -150,4 +152,4 @@ David F. Skoll
|
|||
.PP
|
||||
The backend is derived from
|
||||
.BR sane\-hp (5)
|
||||
by David Mosberger
|
||||
by David Mosberger.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
.IX sane\-epjitsu
|
||||
|
||||
.SH NAME
|
||||
sane\-epjitsu \- SANE backend for Epson-based Fujitsu USB scanners.
|
||||
sane\-epjitsu \- SANE backend for Epson-based Fujitsu USB scanners
|
||||
|
||||
.SH DESCRIPTION
|
||||
The
|
||||
|
|
@ -35,12 +35,13 @@ Selects the source for the scan. Options may include "Flatbed", "ADF Front", "AD
|
|||
Selects the mode for the scan. Options may include "Lineart", "Gray", "Color".
|
||||
.RE
|
||||
.PP
|
||||
.BR resolution , y\-resolution
|
||||
.BR resolution , " y\-resolution"
|
||||
.RS
|
||||
Controls scan resolution. Setting
|
||||
.B \-\-resolution
|
||||
also sets
|
||||
.B \-\-y\-resolution, though this behavior is overridden by some frontends.
|
||||
.BR \-\-y\-resolution ,
|
||||
though this behavior is overridden by some frontends.
|
||||
.RE
|
||||
.PP
|
||||
Other options will be available based on the capabilities of the scanner. Use
|
||||
|
|
|
|||
|
|
@ -5,12 +5,12 @@ sane\-epson \- SANE backend for EPSON scanners
|
|||
.SH DESCRIPTION
|
||||
The
|
||||
.B sane\-epson
|
||||
library implements a SANE Scanner Access Now Easy) backend that
|
||||
library implements a SANE (Scanner Access Now Easy) backend that
|
||||
provides access to Epson flatbed scanners. Some functions of this
|
||||
backend should be considered
|
||||
.B beta-quality
|
||||
software! Most functions have been stable for a long time, but of
|
||||
course new development can not and often times will not function properly from
|
||||
course new development can not and often will not function properly from
|
||||
the very first day. Please report any strange behavior to the
|
||||
maintainer of the backend.
|
||||
.PP
|
||||
|
|
@ -255,8 +255,9 @@ The parallel interface can be configured in two ways: An integer value starting
|
|||
at the beginning of a line will be interpreted as the IO address of the parallel
|
||||
port. To make it clearer that a configured IO address is a parallel port the
|
||||
port address can be preceded by the string "PIO". The PIO connection does not
|
||||
use a special device file in the /dev directory. The IO address can be specified
|
||||
in hex mode (prefixed with "0x").
|
||||
use a special device file in the
|
||||
.I /dev
|
||||
directory. The IO address can be specified in hex mode (prefixed with "0x").
|
||||
.TP
|
||||
.I USB
|
||||
A device file that is preceded by the string "USB" is treated as a scanner
|
||||
|
|
|
|||
|
|
@ -266,7 +266,7 @@ will ignore this option.
|
|||
|
||||
The
|
||||
.B \-\-bay
|
||||
option selects which bay to scan
|
||||
option selects which bay to scan.
|
||||
|
||||
The
|
||||
.B \-\-eject
|
||||
|
|
|
|||
|
|
@ -48,7 +48,8 @@ GL841, GL843, GL847 or GL124 chipset, you can try to add it to the backend.
|
|||
.SH "CALIBRATION"
|
||||
To give correct image quality, sheet fed scanners need to be calibrated using the
|
||||
calibration sheet sold with the scanner. To do calibration, you must insert this target
|
||||
in the feeder then start calibration either by passing the \-\-calibrate option to scanimage
|
||||
in the feeder then start calibration either by passing the \-\-calibrate option to
|
||||
.BR scanimage (1)
|
||||
or by clicking on the available 'calibrate' button in the 'advanced options' in a graphical
|
||||
frontend. The result of the calibration is stored in a file in the home directory of the user doing it.
|
||||
If you plug the scanner in another machine or use it with another account, calibration
|
||||
|
|
@ -100,7 +101,7 @@ Disable use of a software adaptive algorithm to generate lineart and rely on har
|
|||
.TP
|
||||
.B \-\-color-filter None|Red|Green|Blue
|
||||
When using gray or lineart this option selects the used color. Using a color filter
|
||||
will give a monochrome scan. CIS based scanners can to true gray when no filter (None value) is
|
||||
will give a monochrome scan. CIS based scanners can do true gray when no filter (None value) is
|
||||
selected.
|
||||
|
||||
.TP
|
||||
|
|
@ -123,7 +124,7 @@ users.
|
|||
.B \-\-expiration\-time
|
||||
Specify the time (in minutes) a cached calibration is considered valid. If older than the given value, a new
|
||||
calibration is done. A value of -1 means no expiration and cached value are kept forever unless cleared by
|
||||
userwith the calibration clear option. A value of 0 means cache is disabled.
|
||||
user with the calibration clear option. A value of 0 means cache is disabled.
|
||||
|
||||
.PP
|
||||
Additionally, several 'software' options are exposed by the backend. These
|
||||
|
|
@ -248,9 +249,7 @@ Syscan/Ambir DocketPORT 467/485/487/665/685
|
|||
Xerox Travel Scanner 100, Onetouch 2400
|
||||
.RE
|
||||
.TP
|
||||
cncsolutions
|
||||
.RI ( http://www.cncsolutions.com.br )
|
||||
sponsored and supported the work on the Panasonic KV-SS080.
|
||||
cncsolutions sponsored and supported the work on the Panasonic KV-SS080.
|
||||
.br
|
||||
.TP
|
||||
Brian Paavo from Benthic Science Limited for donating a Canoscan LiDE 700F.
|
||||
|
|
@ -298,7 +297,8 @@ due to the way image sensors are built.
|
|||
.PP
|
||||
This backend will be much slower if not using libusb\-1.0. So be sure that sane\-backends is built with
|
||||
the
|
||||
.B \-\-enable-libusb_1_0 option.
|
||||
.B \-\-enable-libusb_1_0
|
||||
option.
|
||||
|
||||
.SH "BUGS"
|
||||
For the LiDE 200, the scanned data at 4800 dpi is obtained "as is" from sensor.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ through the gphoto2 interface. Valid ports and cameras can be obtained
|
|||
by
|
||||
.I "gphoto2 \-\-list\-cameras"
|
||||
and
|
||||
.I "gphoto2 \-\-list\-ports".
|
||||
.IR "gphoto2 \-\-list\-ports" .
|
||||
.PP
|
||||
The
|
||||
.B dumpinquiry
|
||||
|
|
@ -122,9 +122,9 @@ Set to 1, 2, or 3, to enable various levels of debugging within the
|
|||
gphoto2 libraries.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
.BR sane (7) ,
|
||||
.BR scanimage (1) ,
|
||||
.BR xscanimage (1) ,
|
||||
.BR sane (7),
|
||||
.BR scanimage (1),
|
||||
.BR xscanimage (1),
|
||||
.BR libgphoto2 (3)
|
||||
|
||||
.SH AUTHOR
|
||||
|
|
|
|||
|
|
@ -220,8 +220,9 @@ levels reduce verbosity.
|
|||
.TP
|
||||
.B SANE_HOME_HP
|
||||
Only used for OS/2 and along with use of HP PhotoSmart PhotoScanner.
|
||||
Must be set to the directory where the directory .sane is located.
|
||||
Is used to save and read the calibration file.
|
||||
Must be set to the directory where the directory
|
||||
.I .sane
|
||||
is located. Is used to save and read the calibration file.
|
||||
.TP
|
||||
.B SANE_HP_KEEPOPEN_SCSI
|
||||
.TP
|
||||
|
|
|
|||
|
|
@ -27,14 +27,14 @@ backend:
|
|||
.ft R
|
||||
.RE
|
||||
.PP
|
||||
(*) WARNING: None of the advanced options of these scanners are available (ie no color, no high resolution, no automatic cropping). Basically, the driver does no more than what it does for the KV-SS25. I don't have access to such scanners, and thus cannot add these options.
|
||||
(*) WARNING: None of the advanced options of these scanners are available (i.e. no color, no high resolution, no automatic cropping). Basically, the driver does no more than what it does for the KV-SS25. I don't have access to such scanners, and thus cannot add these options.
|
||||
|
||||
Other Panasonic high speed scanners may or may not work with that backend.
|
||||
|
||||
Valid command line options and their syntax can be listed by using
|
||||
Valid command line options and their syntax can be listed by using:
|
||||
.RS
|
||||
.PP
|
||||
scanimage \-\-help \-d matsushita
|
||||
.I scanimage \-\-help \-d matsushita
|
||||
.RE
|
||||
|
||||
.TP
|
||||
|
|
@ -58,13 +58,13 @@ selects the number of pages to scan (one or until the tray is empty).
|
|||
|
||||
.TP
|
||||
.B \-\-paper\-size A4|...|Legal|Letter [A4]
|
||||
options selects the area to scan. It adjust the
|
||||
selects the area to scan. It adjusts the
|
||||
.B \-l \-t \-x \-y
|
||||
options accordingly. It does not need to be the real size of the paper.
|
||||
|
||||
.TP
|
||||
.B \-l \-t \-x \-y
|
||||
control the scan area: \-l sets the top left x coordinate, \-t the top
|
||||
controls 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. It is possible to use
|
||||
the option
|
||||
|
|
@ -85,28 +85,28 @@ controls the contrast of the acquired image. Some models do not support that opt
|
|||
automatically sets brightness, contrast, white level, gamma, noise reduction and image emphasis. These options are not available when automatic\-threshold is in use.
|
||||
.TP
|
||||
.B \-\-halftone\-pattern
|
||||
option sets the tonal gradation for the halftone mode. Pattern downloading is not implemented by the backend.
|
||||
sets the tonal gradation for the halftone mode. Pattern downloading is not implemented by the backend.
|
||||
.TP
|
||||
.B \-\-autoseparation
|
||||
provides automatic separation of text and images.
|
||||
.TP
|
||||
.B \-\-white\-level
|
||||
option indicate the source of the white base.
|
||||
indicates the source of the white base.
|
||||
.TP
|
||||
.B \-\-noise\-reduction
|
||||
reduces the isolated dot noise. This option is not supported by all scanners.
|
||||
.TP
|
||||
.B \-\-image\-emphasis
|
||||
option sets the image emphasis. Some selection are not available on all scanners.
|
||||
sets the image emphasis. Some selection are not available on all scanners.
|
||||
.TP
|
||||
.B \-\-gamma
|
||||
options set the gamma curve. It is only valid for Gray modes, and is not available on all scanners. Gamma downloading is not implemented by the backend.
|
||||
sets the gamma curve. It is only valid for Gray modes, and is not available on all scanners. Gamma downloading is not implemented by the backend.
|
||||
|
||||
|
||||
.SH CONFIGURATION FILE
|
||||
The configuration file
|
||||
.I @CONFIGDIR@/matsushita.conf
|
||||
supports the device name to use (eg
|
||||
supports the device name to use (e.g.
|
||||
.IR /dev/scanner )
|
||||
and the SCSI option to auto-detect the scanners supported.
|
||||
|
||||
|
|
|
|||
|
|
@ -104,7 +104,7 @@ ignored. A sample configuration file is shown below:
|
|||
The configuration file may also contain the special tokens
|
||||
.I norealcal
|
||||
or
|
||||
.I noprecal.
|
||||
.IR noprecal .
|
||||
.I norealcal
|
||||
will disable the use of magic, undocumented scanner calibration commands
|
||||
which are known to work on the E6, but may not work with other models.
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Refer to
|
|||
.BR sane\-microtek (5)
|
||||
for details.
|
||||
.PP
|
||||
And there is work in progress for the ScanMaker 3600.
|
||||
And there is partial progress for the ScanMaker 3600.
|
||||
See
|
||||
.IR http://sourceforge.net/projects/sm3600 .
|
||||
.PP
|
||||
|
|
@ -155,7 +155,9 @@ The configuration file may also contain options. Global options that are valid
|
|||
for all devices are placed above the device names. Device-specific options
|
||||
are
|
||||
placed under the device name. Note that, except for option dump <n> and
|
||||
option strip-height <n>, the entry in the microtek2.conf file only enables
|
||||
option strip-height <n>, the entry in the
|
||||
.I microtek2.conf
|
||||
file only enables
|
||||
the corresponding option for being showed in the frontend. There, in the
|
||||
frontend, you can switch the options on and off.
|
||||
Currently the following options are supported:
|
||||
|
|
|
|||
|
|
@ -181,7 +181,9 @@ is 128. Because of double buffering the buffer actually sent to the scanner
|
|||
is half the size of this value. Try to increase this value to achieve higher
|
||||
scan speeds. Note that some ScanExpress scanners don't like buffer sizes above
|
||||
64 kb (buffersize = 128). If your sg driver can't set SCSI buffer sizes at
|
||||
runtime you may have to change that value, too. See sane\-scsi(5) for details.
|
||||
runtime you may have to change that value, too. See
|
||||
.BR sane\-scsi (5)
|
||||
for details.
|
||||
.PP
|
||||
Option
|
||||
.B blocksize
|
||||
|
|
@ -312,7 +314,7 @@ I/O ports. Thus, either make frontends such as
|
|||
.BR scanimage (1)
|
||||
and
|
||||
.BR xscanimage (1)
|
||||
setuid root (generally not recommended for safety reasons) or, alternatively,
|
||||
setuid root (generally not recommended for security reasons) or, alternatively,
|
||||
access this backend through the network daemon
|
||||
.BR saned (8).
|
||||
.PP
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@ Note that the backend needs to run as root or has to have appropriate access
|
|||
rights to
|
||||
.I /dev/parport*
|
||||
if libieee1284 support is compiled in. To allow user
|
||||
access to the scanner run the backend through the network interface (See
|
||||
access to the scanner run the backend through the network interface (see
|
||||
.BR saned (8)
|
||||
and
|
||||
.BR sane\-net (5)).
|
||||
|
|
@ -109,15 +109,12 @@ Note also that the backend
|
|||
support
|
||||
.IR "parport sharing" ,
|
||||
i.e. if you try printing while scanning, your computer may crash. To enable
|
||||
parport sharing, you have to enable libieee1284 at compile time. This backend
|
||||
also conflicts with the
|
||||
.BR sane\-musteka4s2 (5)
|
||||
backend. You can only enable one of them in your
|
||||
parport sharing, you have to enable
|
||||
.BR libieee1284 (3)
|
||||
at compile time.
|
||||
You may also have to enable the backend explicitly in your
|
||||
.IR dll.conf .
|
||||
However, you have
|
||||
to enable the backend explicitly in your
|
||||
.IR dll.conf ,
|
||||
just remove the hash mark in the line "mustek_pp".
|
||||
Just remove the hash mark in the line "mustek_pp".
|
||||
|
||||
.SH "DEVICE DEFINITION"
|
||||
This backend allows multiple devices being defined and configured via the
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ Instead of using the device name, the scanner can be autodetected by
|
|||
statements which are already included into
|
||||
.IR mustek_usb.conf .
|
||||
This is only supported with Linux 2.4.8 and higher and all systems that
|
||||
support libsub. "vendor_id" and "product_id" are hexadecimal numbers that
|
||||
support libusb. "vendor_id" and "product_id" are hexadecimal numbers that
|
||||
identify the scanner. If this doesn't work, a device name and the option
|
||||
specifying the scanner type must be placed in
|
||||
.I mustek_usb.conf
|
||||
|
|
|
|||
|
|
@ -93,10 +93,8 @@ are contacted in addition to the hosts listed above.
|
|||
For this backend to function properly, it is also necessary to define the
|
||||
.B sane\-port
|
||||
service in
|
||||
.IR /etc/services .
|
||||
The
|
||||
.B sane
|
||||
service should be defined using a line of the following form:
|
||||
.I /etc/services
|
||||
using a line of the following form:
|
||||
.PP
|
||||
.RS
|
||||
sane\-port 6566/tcp # SANE network scanner daemon
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ This backend expects device names of the form:
|
|||
.RE
|
||||
.PP
|
||||
Where
|
||||
\fBvalue\fR is :
|
||||
\fBvalue\fR is:
|
||||
|
||||
.RS
|
||||
.TP
|
||||
|
|
@ -151,7 +151,9 @@ your
|
|||
.IR @CONFIGDIR@/dll.conf .
|
||||
If your scanner isn't detected, make sure you've defined the right port address, or the
|
||||
correct device
|
||||
in your p5.conf.
|
||||
in your
|
||||
.I p5.conf
|
||||
file.
|
||||
.TP
|
||||
.I the name of your scanner/vendor
|
||||
also a worthy information. Please also include the optical resolution and lamp type of your
|
||||
|
|
|
|||
|
|
@ -165,7 +165,7 @@ The backend supports:
|
|||
.br
|
||||
* a custom gamma table,
|
||||
.br
|
||||
* Automatic Document Feeder, Simplex and Duplex.
|
||||
* Automatic Document Feeder, Simplex and Duplex,
|
||||
.br
|
||||
* Transparency Unit, 24 or 48 bits depth. Infrared channel on certain models.
|
||||
.RE
|
||||
|
|
@ -181,7 +181,7 @@ where aaaa is the scanners model and bbbb is the hostname or ip-adress.
|
|||
Example: pixma:MF4800_192.168.1.45 is a MF4800 Series multi-function peripheral.
|
||||
.PP
|
||||
This backend, based on cloning original Canon drivers protocols, is in
|
||||
a production stage. Designed has been carried out without any applicable
|
||||
a production stage. Design has been carried out without any applicable
|
||||
manufacturer documentation, probably never available. However, we have tested
|
||||
it as well as we could, but it may not work in all situations. You will find
|
||||
an up-to-date status at the project homepage. (See below).
|
||||
|
|
@ -233,8 +233,8 @@ backward compatibility reasons.
|
|||
.TP
|
||||
.I button\-1 button\-2
|
||||
(read only) These options will return the value of the respective buttons.
|
||||
value 0 means that the button was not pressed, 1 is returned when the button
|
||||
was pressed. Some scanners with more than two buttons send the button number
|
||||
Value 0 means that the button was not pressed, 1 is returned when the button
|
||||
was pressed. Some scanners, with more than two buttons, send the button number
|
||||
as target.
|
||||
.TP
|
||||
.I original
|
||||
|
|
@ -291,7 +291,7 @@ only scanners that cannot be auto-detected because they are on a different
|
|||
subnet shall be listed here. If you do not use Linux and your OS does not allow enumeration of
|
||||
interfaces (i.e. it does not support the
|
||||
.BR getifaddrs ()
|
||||
qfunction) you also may need
|
||||
function) you also may need
|
||||
to add your scanner here as well.
|
||||
.PP
|
||||
Scanners shall be listed in the configuration file as follows:
|
||||
|
|
@ -300,48 +300,56 @@ Scanners shall be listed in the configuration file as follows:
|
|||
.I <method>://<host>[:port][/timeout=<value>]
|
||||
.RE
|
||||
.PP
|
||||
where method indicates the protocol used (bjnp is used for inkjet multi-functionals
|
||||
and mfnp is used for laser multi-functionals).
|
||||
.PP
|
||||
host is the hostname or IP address of the scanner, e.g. bjnp://10.0.1.4
|
||||
for IPv4, bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a] for a literal
|
||||
IPv6-address or bjnp://myscanner.mydomain.org for a hostname.
|
||||
.PP
|
||||
The port number is optional and in normally implied by the method.
|
||||
.TP
|
||||
.B method
|
||||
indicates the protocol used.
|
||||
.I bjnp
|
||||
is used for inkjet multi-functionals and
|
||||
.I mfnp
|
||||
is used for laser multi-functionals).
|
||||
.TP
|
||||
.B host
|
||||
is the hostname or IP address of the scanner, e.g.
|
||||
.I bjnp://10.0.1.4
|
||||
for IPv4,
|
||||
.I bjnp://[2001:888:118e:18e2:21e:8fff:fe36:b64a]
|
||||
for a literal IPv6-address or
|
||||
.I bjnp://myscanner.mydomain.org
|
||||
for a hostname.
|
||||
.TP
|
||||
.B port
|
||||
is optional and is normally implied by the method.
|
||||
Port 8610 is the standard port for mfnp, 8612 for bjnp.
|
||||
.TP
|
||||
.B timeout
|
||||
scanner-specific timeout value for the network protocol. The value is in ms.
|
||||
.PP
|
||||
A scanner specific timeout value for the network protocol can be set using the
|
||||
bjnp-timeout parameter. The value is in ms.
|
||||
Define each scanner each on a separate line.
|
||||
.PP
|
||||
Define scanners each on a new line.
|
||||
.PP
|
||||
More globally applicable timeouts can be set using the bjnp-timeout parameter as follows:
|
||||
More globally-applicable timeouts can be set using the bjnp-timeout parameter as follows:
|
||||
.PP
|
||||
.RS
|
||||
.I bjnp-timeout=<value>
|
||||
.RE
|
||||
.PP
|
||||
A timeout defined using bjnp-timeout will apply to the following scanner definitions
|
||||
in the file. If required the bjnp-timeout setting
|
||||
in the file. If required, the bjnp-timeout setting
|
||||
can be defined multiple times, where each setting will apply only to the scanners that
|
||||
follow the setting. The last setting is used for the auto discovered scanners.
|
||||
follow the setting. The last setting is used for auto-discovered scanners.
|
||||
If not explicitly set, the default 1000ms setting will apply.
|
||||
.PP
|
||||
Setting timeouts should only be required in exceptional cases.
|
||||
.PP
|
||||
.RE
|
||||
.PP
|
||||
If so desired networking can be disabled as follows:
|
||||
If so desired, networking can be disabled as follows:
|
||||
.RS
|
||||
.IP -
|
||||
If the first non-commented line contains
|
||||
.B networking=no
|
||||
all networking will be disabled.
|
||||
This will cause all further statements in the configuration file to be ignored.
|
||||
.IP -
|
||||
A line that contains
|
||||
.B auto_detection=no
|
||||
will cause auto-detection to be skipped. Explicitly defined network scanners will still be probed.
|
||||
.IP \fInetworking=no\FR
|
||||
If the first non-commented line contains this entry all networking will be disabled.
|
||||
All further statements in the configuration file will be ignored.
|
||||
.IP \fIauto_detection=no\fR
|
||||
This line will cause auto-detection to be skipped.
|
||||
Explicitly defined network scanners will still be probed.
|
||||
.SH USB SUPPORT
|
||||
USB scanners will be auto-detected and require no configuration.
|
||||
.SH NETWORKING SUPPORT
|
||||
|
|
@ -444,7 +452,7 @@ the verbosity and includes the information printed at the lower levels.
|
|||
.RE
|
||||
.TP
|
||||
.B PIXMA_EXPERIMENT
|
||||
Setting to a non-zero value will enable the support for experimental models.
|
||||
Setting to a non-zero value will enable experimental support for further models.
|
||||
You should also set SANE_DEBUG_PIXMA to 11.
|
||||
.TP
|
||||
.B SANE_CONFIG_DIR
|
||||
|
|
|
|||
|
|
@ -411,7 +411,9 @@ means autocalibration.
|
|||
.RE
|
||||
|
||||
.PP
|
||||
See the plustek.conf file for examples.
|
||||
See the
|
||||
.I plustek.conf
|
||||
file for examples.
|
||||
.PP
|
||||
.B Note:
|
||||
.br
|
||||
|
|
@ -475,7 +477,7 @@ export SANE_DEBUG_PLUSTEK=10
|
|||
.BR sane\-usb (5),
|
||||
.BR sane\-u12 (5),
|
||||
.BR sane\-gt68xx (5),
|
||||
.BR sane-\mustek_pp (5),
|
||||
.BR sane\-mustek_pp (5),
|
||||
.BR sane\-find\-scanner (1),
|
||||
.BR scanimage (1)
|
||||
.br
|
||||
|
|
@ -486,24 +488,20 @@ Please send any information and bug-reports to:
|
|||
.br
|
||||
.B SANE Mailing List
|
||||
.PP
|
||||
Additional info and hints can be obtained from our
|
||||
.br
|
||||
Mailing-List archive at:
|
||||
.br
|
||||
.I http://www.sane\-project.org/mailing\-lists.html
|
||||
Additional info and hints can be obtained from our mailing-List archive at:
|
||||
.IR http://www.sane\-project.org/mailing\-lists.html .
|
||||
.PP
|
||||
To obtain debug messages from the backend, please set the
|
||||
environment-variable
|
||||
.B SANE_DEBUG_PLUSTEK
|
||||
before calling your favorite scan-frontend (i.e.
|
||||
.BR scanimage (1)), i.e.:
|
||||
|
||||
.br
|
||||
before calling your favorite SANE frontend (e.g.
|
||||
.BR scanimage (1)):
|
||||
.PP
|
||||
.I export SANE_DEBUG_PLUSTEK=20 ; scanimage
|
||||
.PP
|
||||
The value controls the verbosity of the backend. Please note, that
|
||||
values greater than 24 force the backend to output raw data files,
|
||||
which could be rather large. The ending of these files is ".raw".
|
||||
The value controls the verbosity of the output. Please note that
|
||||
values greater than 24 force the backend to output raw data files
|
||||
which could be rather large. The suffix of these files is ".raw".
|
||||
For problem reports it should be enough the set the verbosity to
|
||||
13.
|
||||
|
||||
|
|
|
|||
|
|
@ -244,12 +244,12 @@ Unpack this tar-ball and go to the directory:
|
|||
.IR sane\-backends/doc/plustek .
|
||||
Within this directory, you should find a script called:
|
||||
.IR MakeModule.sh .
|
||||
Now if your Linux kernelsources are installed correctly,
|
||||
Now if your Linux kernel sources are installed correctly,
|
||||
it should be possible to build, install and load the
|
||||
module
|
||||
.BR pt_drv .
|
||||
.B Please note,
|
||||
that the kernelsources need to be configured correctly.
|
||||
that the kernel sources need to be configured correctly.
|
||||
Refer to your distributions
|
||||
manual on how this is done. As root user, try
|
||||
.PP
|
||||
|
|
@ -259,8 +259,8 @@ the script will try and get all necessary information about your
|
|||
running kernel and will lead you through the whole installation
|
||||
process.
|
||||
.br
|
||||
.B Note: Installing and loading the can only be done as
|
||||
superuser.
|
||||
.B Note:
|
||||
Installing and loading the module can only be done as a superuser.
|
||||
.PP
|
||||
|
||||
.SH "KERNEL MODULE SETUP"
|
||||
|
|
@ -366,18 +366,18 @@ Sample entry for file
|
|||
.IR /etc/modules.conf :
|
||||
.PP
|
||||
.RS
|
||||
alias char\-major\-40 pt_drv
|
||||
.I alias char\-major\-40 pt_drv
|
||||
.br
|
||||
pre-install pt_drv modprobe -k parport
|
||||
.I pre-install pt_drv modprobe -k parport
|
||||
.br
|
||||
options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=0 forceMode=0
|
||||
.I options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=0 forceMode=0
|
||||
.RE
|
||||
.PP
|
||||
For multidevice support, simply add values separated by commas to
|
||||
the different options
|
||||
the different options:
|
||||
.PP
|
||||
.RS
|
||||
options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
|
||||
.I options pt_drv port=0x378,0x278 mov=0,4 slowIO=0,1 forceMode=0,1
|
||||
.RE
|
||||
.PP
|
||||
Remember to call
|
||||
|
|
@ -425,10 +425,10 @@ The shared library implementing this backend (present on systems that
|
|||
support dynamic loading).
|
||||
.TP
|
||||
.I /lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.o
|
||||
The Linux kernelmodule for kernels < 2.6.x.
|
||||
The Linux kernel module for kernels < 2.6.x.
|
||||
.TP
|
||||
.I /lib/modules/<Kernel-Version>/kernel/drivers/parport/pt_drv.ko
|
||||
The Linux kernelmodule for kernels >= 2.6.x.
|
||||
The Linux kernel module for kernels >= 2.6.x.
|
||||
.PP
|
||||
|
||||
.SH ENVIRONMENT
|
||||
|
|
@ -472,21 +472,18 @@ Please send any information and bug-reports to:
|
|||
.br
|
||||
.B SANE Mailing List
|
||||
.PP
|
||||
Additional info and hints can be obtained from our
|
||||
.br
|
||||
Mailing-List archive at:
|
||||
.br
|
||||
.I http://www.sane\-project.org/mailing\-lists.html
|
||||
Additional info and hints can be obtained from our mailing-List archive at:
|
||||
.IR http://www.sane\-project.org/mailing\-lists.html .
|
||||
.PP
|
||||
To obtain debug messages from the backend, please set the
|
||||
environment-variable
|
||||
.B SANE_DEBUG_PLUSTEK_PP
|
||||
before calling your favorite scan-frontend (i.e.
|
||||
.BR xscanimage (1)), i.e.:
|
||||
.br
|
||||
before calling your favorite SANE frontend (e.g.
|
||||
.BR xscanimage (1)):
|
||||
.PP
|
||||
.I export SANE_DEBUG_PLUSTEK_PP=20 ; xscanimage
|
||||
.PP
|
||||
The value controls the verbosity of the backend.
|
||||
The value controls the verbosity of the output.
|
||||
.PP
|
||||
|
||||
.SH "KNOWN BUGS & RESTRICTIONS"
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ is the SCSI vendor string,
|
|||
.I MODEL
|
||||
is the SCSI model string,
|
||||
.I TYPE
|
||||
is type SCSI device type string,
|
||||
is the SCSI device type string,
|
||||
.I BUS
|
||||
is the SCSI bus number (named "host" in
|
||||
.IR /proc/scsi/scsi ),
|
||||
|
|
@ -195,7 +195,7 @@ maximum buffer size can be changed at program run time, and there is no restrict
|
|||
version 2.2.7 on. If the new SG driver is available some backends
|
||||
(e.g.
|
||||
.BR sane\-umax (5),
|
||||
.BR sane\-mustek (5) ,
|
||||
.BR sane\-mustek (5),
|
||||
.BR sane\-sharp (5))
|
||||
automatically request larger SCSI
|
||||
buffers. If a backend does not automatically request a larger SCSI buffer, set
|
||||
|
|
@ -204,9 +204,9 @@ the environment variable
|
|||
to the desired buffer size in bytes. It is not recommended to use more
|
||||
than 1 MB, because for large values the probability increases that the
|
||||
SG driver cannot allocate the necessary buffer(s). For ISA cards, even
|
||||
1 MB might be a too large value. For a detailed discussion of memory
|
||||
issues of the SG driver, see
|
||||
.I http://www.torque.net/sg.
|
||||
1 MB might be a too large value.
|
||||
For a detailed discussion of the Linux SG SCSI driver see:
|
||||
.IR https://tldp.org/HOWTO/SCSI-Generic-HOWTO .
|
||||
.PP
|
||||
For Linux kernels before version 2.2.7 the size of the buffer is only 32KB.
|
||||
This works, but for many cheaper scanners this causes scanning to be slower by
|
||||
|
|
@ -299,7 +299,7 @@ of the form ``restart (ncr dead ?)'' in your
|
|||
.I /var/log/messages
|
||||
file or on the system console, it's an indication that the timeout is too short.
|
||||
In this case, find the line ``if (np->latetime>10)'' in file
|
||||
.I ncr53c8xx.
|
||||
.I ncr53c8xx.c
|
||||
(normally in directory
|
||||
.IR /usr/src/linux/drivers/scsi )
|
||||
and change the constant 10 to, say, 60 (one minute).
|
||||
|
|
@ -329,7 +329,7 @@ and with target-id 0 would be called
|
|||
.IR /dev/sg0a ,
|
||||
and the device with target-id 1 on that same bus would be
|
||||
called
|
||||
.IR /dev/sg0b,
|
||||
.IR /dev/sg0b ,
|
||||
and so on.
|
||||
|
||||
.SH ENVIRONMENT
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@ default selection.
|
|||
|
||||
.TP
|
||||
.B \-\-custom\-gamma
|
||||
Custom Gamma This option determines whether a builtin or a custom
|
||||
Custom Gamma. This option determines whether a builtin or a custom
|
||||
gamma table is used. Possible settings are:
|
||||
.I yes
|
||||
(enables custom gamma tables) or
|
||||
|
|
@ -197,7 +197,7 @@ This option is only available in scan mode
|
|||
|
||||
.TP
|
||||
.B \-\-threshold-red
|
||||
Sets the threshold for the red component of a pixel in
|
||||
Sets the threshold for the red component of a pixel
|
||||
in lineart color scan mode. Possible values are 1..255.
|
||||
The default value is 128.
|
||||
This option is only available in scan mode color
|
||||
|
|
@ -205,7 +205,7 @@ This option is only available in scan mode color
|
|||
|
||||
.TP
|
||||
.B \-\-threshold-green
|
||||
Sets the threshold for the green component of a pixel in
|
||||
Sets the threshold for the green component of a pixel
|
||||
in lineart color scan mode. Possible values are 1..255.
|
||||
The default value is 128.
|
||||
This option is only available in scan mode color
|
||||
|
|
@ -213,7 +213,7 @@ This option is only available in scan mode color
|
|||
|
||||
.TP
|
||||
.B \-\-threshold-blue
|
||||
Sets the threshold for the blue component of a pixel in
|
||||
Sets the threshold for the blue component of a pixel
|
||||
in lineart color scan mode. Possible values are 1..255.
|
||||
The default value is 128.
|
||||
This option is only available in scan mode color
|
||||
|
|
@ -321,11 +321,11 @@ stops.
|
|||
Stops of the carriage can be caused by the following reasons:
|
||||
.PP
|
||||
.RS
|
||||
\- too much "traffic" on the SCSI bus
|
||||
\- too much "traffic" on the SCSI bus,
|
||||
.br
|
||||
\- slow responses by the backend to the scanner,
|
||||
.br
|
||||
\- a program which processes the data acquired by the backend too slow.
|
||||
\- a program which processes the data acquired by the backend is too slow.
|
||||
.PP
|
||||
.RE
|
||||
Too much "traffic" on the SCSI bus: This happens for example, if hard disks
|
||||
|
|
@ -409,12 +409,12 @@ backend. At present, the scanner must power off and on to stop this
|
|||
annoying behaviour.
|
||||
.RE
|
||||
|
||||
2. Threshold level does not work (only JX-610)
|
||||
2. Threshold level does not work (only JX\-610)
|
||||
.PP
|
||||
3. The maximum resolution is limited to 600 dpi(JX-610 supported
|
||||
to 1200 dpi) resp. 400 dpi (JX-250)
|
||||
3. The maximum resolution is limited to 600 dpi (JX\-610 supported
|
||||
to 1200 dpi) resp. 400 dpi (JX\-250)
|
||||
.PP
|
||||
4. If the JX250 is used with an ADF, the following situation can occur: After
|
||||
4. If the JX\-250 is used with an ADF, the following situation can occur: After
|
||||
several scans, the scanner moves, after loading a new sheet of paper, the
|
||||
carriage to the idle position, and then back to the position used for ADF
|
||||
scans. This happens for
|
||||
|
|
@ -436,8 +436,8 @@ tested.
|
|||
Kazuya Fukuda, Abel Deuring
|
||||
|
||||
.SH CREDITS
|
||||
The Sharp backend is based on the Canon backend written by Helmut Koeberle
|
||||
The Sharp backend is based on the Canon backend written by Helmut Koeberle.
|
||||
.PP
|
||||
Parts of this man page are a plain copy of
|
||||
.BR sane\-mustek (5)
|
||||
by David Mosberger-Tang, Andreas Czechanowski and Andreas Bolsch
|
||||
by David Mosberger-Tang, Andreas Czechanowski and Andreas Bolsch.
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ scanimage \-\-help \-d stv680
|
|||
|
||||
.TP
|
||||
.B \-\-mode
|
||||
selects the basic mode of operation of the webcams valid choices.
|
||||
selects the basic mode of operation of the webcam's valid choices.
|
||||
|
||||
The read resolution mode is 8 bits, output resolution is 24 bits.
|
||||
Selects the resolution for a scan.
|
||||
|
|
@ -113,7 +113,7 @@ value loaded into the scanner. Scale \-32 .. 0 .. +32 in steps of 1.
|
|||
.TP
|
||||
.B \-\-white\-level\-g \-32..+32
|
||||
Selects what green radiance level should be
|
||||
considered "white", when scanning some sheets by changing the calibration i
|
||||
considered "white", when scanning some sheets by changing the calibration
|
||||
value loaded into the scanner. Scale \-32 .. 0 .. +32 in steps of 1.
|
||||
|
||||
.TP
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ For
|
|||
a restricted set of resolutions are available.
|
||||
|
||||
.B Note:
|
||||
All values with ydpi > 300 (300 x 600) or 600 (600 x 1200) result in
|
||||
All values with vertical resolution in dpi > 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
|
||||
.BR convert (1)
|
||||
|
|
|
|||
|
|
@ -235,7 +235,7 @@ constraint. Minimum is 4, maximum 192, and quant is 2.
|
|||
.PP
|
||||
Option
|
||||
.B int\-constraint\-array\-constraint\-word\-list
|
||||
(6/7) is an int test option with unit percent and using an array a word list
|
||||
(6/7) is an int test option with unit percent and using an array or word list
|
||||
constraint.
|
||||
.PP
|
||||
Option
|
||||
|
|
@ -258,7 +258,7 @@ set. Minimum is \-42.17, maximum 32767.9999, and quant is 2.0.
|
|||
.PP
|
||||
Option
|
||||
.B fixed\-constraint\-word\-list
|
||||
(3/3) is a Fixed test option with no unit and constraint word list set.
|
||||
(3/3) is a fixed test option with no unit and constraint word list set.
|
||||
.PP
|
||||
|
||||
.SH STRING TEST OPTIONS
|
||||
|
|
|
|||
|
|
@ -167,20 +167,15 @@ Please send any information and bug-reports to:
|
|||
.br
|
||||
.B SANE Mailing List
|
||||
.PP
|
||||
Additional info and hints can be obtained from our
|
||||
.br
|
||||
Mailing-List archive at:
|
||||
.br
|
||||
.I http://www.sane\-project.org/mailing\-lists.html
|
||||
Additional info and hints can be obtained from our mailing-List archive at:
|
||||
.IR http://www.sane\-project.org/mailing\-lists.html .
|
||||
.PP
|
||||
To obtain debug messages from the backend, please set the
|
||||
environment-variable
|
||||
.B SANE_DEBUG_U12
|
||||
before calling your favorite scan-frontend (i.e.
|
||||
.BR xscanimage (1)),
|
||||
i.e.:
|
||||
|
||||
.br
|
||||
before calling your favorite SANE frontend (e.g.
|
||||
.BR xscanimage (1)):
|
||||
.PP
|
||||
.I export SANE_DEBUG_U12=20 ; xscanimage
|
||||
.PP
|
||||
The value controls the verbosity of the backend.
|
||||
|
|
|
|||
|
|
@ -55,15 +55,15 @@ if you have a kernel with ppdev support.
|
|||
.PP
|
||||
Note that if you don't use the ppdev character device, the backend
|
||||
needs to run as root. To allow user access to the scanner
|
||||
run the backend through the network interface (See
|
||||
run the backend through the network interface (see
|
||||
.BR saned (8)
|
||||
and
|
||||
.BR sane\-net (5)).
|
||||
A more relaxed solution (security wise) is to add suid bit to the frontend
|
||||
(See
|
||||
(see
|
||||
.BR chmod (1)).
|
||||
The backend drop root privileges as soon as it can, right after gaining direct
|
||||
access to IO ports, which lessen risks when being root.
|
||||
The backend drops root privileges as soon as it can, right after gaining direct
|
||||
access to I/O ports, which lessen risks of being root.
|
||||
|
||||
.SH "DEVICE NAMES"
|
||||
This backend expects device names of the form:
|
||||
|
|
@ -73,7 +73,7 @@ This backend expects device names of the form:
|
|||
.RE
|
||||
.PP
|
||||
Where
|
||||
\fBvalue\fR is :
|
||||
\fBvalue\fR is:
|
||||
|
||||
.RS
|
||||
.TP
|
||||
|
|
@ -102,8 +102,8 @@ have to use
|
|||
.TP
|
||||
0x378
|
||||
does direct hardware access on the given
|
||||
address. Usual values are 0x378, 0x278, 0x3BC
|
||||
In this case, you have to run the scanner as
|
||||
address. Usual values are 0x378, 0x278, 0x3BC.
|
||||
In this case, you have to run the backend as
|
||||
root (*BSD and Linux), or with 'IOPL=yes' on
|
||||
OS/2
|
||||
.PP
|
||||
|
|
@ -166,8 +166,7 @@ user provided values.
|
|||
.PP
|
||||
|
||||
Options
|
||||
.B red\-offset
|
||||
,
|
||||
.BR red\-offset ,
|
||||
.B green\-offset
|
||||
and
|
||||
.B blue\-offset
|
||||
|
|
|
|||
|
|
@ -54,7 +54,9 @@ 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 this:
|
||||
time, if
|
||||
.I /etc/fstab
|
||||
contains a line like this:
|
||||
.PP
|
||||
.RS
|
||||
none /proc/bus/usb usbfs defaults 0 0
|
||||
|
|
@ -97,7 +99,9 @@ For the
|
|||
.BR BSDs ,
|
||||
the device files used by libusb are named
|
||||
.IR /dev/ugen* .
|
||||
Use chmod to apply appropriate permissions.
|
||||
Use
|
||||
.BR chmod (1)
|
||||
to apply appropriate permissions.
|
||||
|
||||
.SH "SANE ISSUES"
|
||||
.PP
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ homepage.
|
|||
.SH "GENERAL INFORMATION"
|
||||
The following sections provide short descriptions and links to more
|
||||
information about several aspects of
|
||||
.B SANE.
|
||||
.BR SANE .
|
||||
A name with a number in parenthesis (e.g.
|
||||
.BR sane\-dll (5))
|
||||
points to a manual page. In this case
|
||||
|
|
@ -818,7 +818,7 @@ So now scanning with
|
|||
works and you want to use one of the graphical frontends like
|
||||
.BR xsane (1) ,
|
||||
.BR xscanimage (1) ", or"
|
||||
.B quiteinsane (1)
|
||||
.BR quiteinsane (1)
|
||||
but those frontends don't detect your scanner? One reason may be that you
|
||||
installed two versions of
|
||||
.BR SANE .
|
||||
|
|
|
|||
|
|
@ -316,8 +316,9 @@ to the
|
|||
.BR systemd (1)
|
||||
journal. The
|
||||
.BR systemd (1)
|
||||
support requires compilation with the systemd-devel package
|
||||
installed on the system. This is the preferred option.
|
||||
support requires compilation with the
|
||||
.BR systemd (1)
|
||||
development package installed on the system. This is the preferred option.
|
||||
|
||||
.B saned
|
||||
can be used with
|
||||
|
|
@ -330,14 +331,16 @@ The
|
|||
.BR systemd (1)
|
||||
configuration is different for the 2 options, so both are described below.
|
||||
|
||||
.SH Systemd configuration for saned with systemd support compiled in
|
||||
.SH Systemd configuration for
|
||||
.B saned
|
||||
with systemd support compiled in
|
||||
For
|
||||
.BR systemd (1)
|
||||
configuration we need to add 2 configuration files in
|
||||
.IR /etc/systemd/system .
|
||||
.PP
|
||||
The first file we need to add here is called
|
||||
.I saned.socket.
|
||||
.IR saned.socket .
|
||||
It shall have
|
||||
the following contents:
|
||||
.PP
|
||||
|
|
@ -424,7 +427,7 @@ we need to add 2 configuration files in
|
|||
.IR /etc/systemd/system .
|
||||
.PP
|
||||
The first file we need to add here is called
|
||||
.I saned.socket.
|
||||
.IR saned.socket .
|
||||
It is identical to the version for
|
||||
.BR systemd (1)
|
||||
with the support compiled in.
|
||||
|
|
@ -525,11 +528,12 @@ being searched (in this order).
|
|||
.BR xcam (1),
|
||||
.BR sane\-dll (5),
|
||||
.BR sane\-net (5),
|
||||
.BR sane\-"backendname" (5),
|
||||
.BR inetd (8),
|
||||
.BR xinetd (8),
|
||||
.BR systemd (1)
|
||||
.br
|
||||
Backend-specific man pages.
|
||||
.br
|
||||
.I http://www.penguin-breeder.org/?page=sane\-net
|
||||
.SH AUTHOR
|
||||
David Mosberger
|
||||
|
|
|
|||
|
|
@ -96,9 +96,9 @@ control of the backend code.
|
|||
|
||||
.PP
|
||||
Parameters are separated by a blank from single-character options (e.g.
|
||||
.BI "\-d " epson )
|
||||
.BI "\-d " epson \fR)
|
||||
and by a "=" from multi-character options (e.g.
|
||||
.BR \-\-device\-name =\fIepson\FR ).
|
||||
.BR \-\-device\-name =\fIepson \fR).
|
||||
|
||||
.TP
|
||||
.BR \-d "\fI dev\fR, " \-\-device\-name =\fIdev\fR
|
||||
|
|
@ -232,7 +232,7 @@ is a specific command provided to aid this.
|
|||
.B \-\-batch\-double
|
||||
will automatically set the increment to 2.
|
||||
Equivalent to
|
||||
.BR \-\-batch\-increment =2
|
||||
.BR \-\-batch\-increment =2.
|
||||
|
||||
.TP
|
||||
.B \-\-batch\-prompt
|
||||
|
|
@ -301,7 +301,7 @@ standard output and no scan will be performed.
|
|||
.TP
|
||||
.BR \-v ", " \-\-verbose
|
||||
increases the verbosity of the output of
|
||||
.B scanimage.
|
||||
.BR scanimage .
|
||||
The option may be specified repeatedly, each time increasing the verbosity
|
||||
level.
|
||||
|
||||
|
|
@ -325,7 +325,7 @@ loads. If more information about the version
|
|||
numbers of the backends are necessary, the
|
||||
.B DEBUG
|
||||
variable for the dll layer can be used. Example:
|
||||
.I "SANE_DEBUG_DLL=3 scanimage \-L" .
|
||||
.IR "SANE_DEBUG_DLL=3 scanimage \-L" .
|
||||
.PP
|
||||
As you might imagine, much of the power of
|
||||
.B scanimage
|
||||
|
|
@ -507,8 +507,8 @@ to 127 characters.
|
|||
.BR sane (7),
|
||||
.BR gamma4scanimage (1),
|
||||
.BR xscanimage (1),
|
||||
.BR xcam (1) ,
|
||||
.BR xsane (1) ,
|
||||
.BR xcam (1),
|
||||
.BR xsane (1),
|
||||
.BR scanadf (1),
|
||||
.BR sane\-dll (5),
|
||||
.BR sane\-net (5),
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue