kopia lustrzana https://gitlab.com/sane-project/backends
More spelling fixes from A. Costa.
Julien BLACHE
rodzic
564b275fa7
commit
35e92104c2
|
|
@ -1,9 +1,14 @@
|
|||
2006-03-21 Julien Blache <jb@jblache.org>
|
||||
|
||||
* doc/*.man: More spelling fixes from A. Costa (through Debian).
|
||||
|
||||
2006-02-02 Oliver Schwartz <Oliver.Schwartz@gmx.de>
|
||||
|
||||
* backend/snapscan-scsi.c: Limit inquiry length to 120 bytes if
|
||||
firmware is not yet loaded
|
||||
|
||||
2006-03-18 Julien Blache <jb@jblache.org>
|
||||
|
||||
* doc/sane-apple.man: Applied patch from A Costa (through Debian);
|
||||
english/spelling fixes for sane-apple(5).
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ sane-avision \- SANE backend for original Avision and Avision OEM scanners
|
|||
|
||||
.SH ABOUT THIS FILE
|
||||
|
||||
This file is a short descripton for the avision-backend shipped with SANE.
|
||||
This file is a short description for the avision-backend shipped with SANE.
|
||||
|
||||
.SH DESCRIPTION
|
||||
The
|
||||
|
|
@ -74,8 +74,8 @@ random garbage.
|
|||
Note:
|
||||
Any option above modifies the default code-flow
|
||||
for your scanner. The options should only be used
|
||||
when you encounter problems with the default be-
|
||||
haviour of the backend. Please report the need of
|
||||
when you encounter problems with the default behaviour
|
||||
of the backend. Please report the need of
|
||||
options to the backend-author so the backend can
|
||||
be fixed as soon as possible.
|
||||
|
||||
|
|
@ -149,7 +149,7 @@ to "/tmp/config:" would result in directories "tmp/config", ".", and
|
|||
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.
|
||||
level 7 is the author's preferred value to debug backend problems.
|
||||
|
||||
Example:
|
||||
export SANE_DEBUG_AVISION=7
|
||||
|
|
|
|||
|
|
@ -240,7 +240,7 @@ knowing ahead of time which page will be the last, can cancel batch mode
|
|||
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 --end-count terminates a scanadf session,
|
||||
an extra page will be pulled through the scanner, but is niether read
|
||||
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
|
||||
--batch=no when scanning a fixed number of pages.
|
||||
.TP
|
||||
|
|
@ -340,7 +340,7 @@ the hardware default value which varies based on the scanner model.
|
|||
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 undesireable results.
|
||||
extensively and may produce undesirable results.
|
||||
.TP
|
||||
.B Enhancement:
|
||||
.TP
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ sane-coolscan \- SANE backend for Nikon film-scanners
|
|||
|
||||
.SH ABOUT THIS FILE
|
||||
|
||||
This file is a short descripton of the coolscan-backend for sane!
|
||||
This file is a short description of the coolscan-backend for sane!
|
||||
|
||||
.SH DESCRIPTION
|
||||
|
||||
|
|
@ -14,7 +14,7 @@ The
|
|||
.B sane-coolscan
|
||||
library implements a SANE backend that provides the interface to the following Nikon Coolscan Film scanners: Nikon LS20, LS30, LS1000, LS2000.
|
||||
|
||||
.B Even though the backend has worked for a number of people, there are still some problems, especially in combination with some SCSI card/drivers (AHA-1505/aha152x.o) and the autofocus command. You should consider this backend 'alpha' and be carefull when using it the first time.
|
||||
.B Even though the backend has worked for a number of people, there are still some problems, especially in combination with some SCSI card/drivers (AHA-1505/aha152x.o) and the autofocus command. You should consider this backend 'alpha' and be careful when using it the first time.
|
||||
|
||||
.SH CONFIGURATION
|
||||
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ Peter S. Fales
|
|||
This backend borrows heavily from the dc210 backend by Brian J. Murrell
|
||||
which is based somewhat on the dc25 backend by Peter Fales.
|
||||
.PP
|
||||
The manpage was largeley copied from the dc210 manpage.
|
||||
The manpage was largely copied from the dc210 manpage.
|
||||
|
||||
.SH BUGS
|
||||
The major limitation that I know of is that the backend assumes
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@ The
|
|||
.I --sharpness
|
||||
switch sets the sharpness of the image data. Valid options are integer
|
||||
values from -2 to 2, with -2 meaning "Defocus", -1 "Defocus slightly",
|
||||
0 "Normal", 1 "Sharpen slighly" and 2 "Sharpen".
|
||||
0 "Normal", 1 "Sharpen slightly" and 2 "Sharpen".
|
||||
|
||||
The
|
||||
.I --gamma-correction
|
||||
|
|
@ -124,14 +124,14 @@ options are "No Correction", "Impact-dot printers", "Thermal printers",
|
|||
The
|
||||
.I --resolution
|
||||
switch selects the resolution for a scan. Some EPSON scanners will scan in
|
||||
any resulution between the lowest and highest possible value. The list
|
||||
any resolution between the lowest and highest possible value. The list
|
||||
reported by the scanner can be displayed using the "--help -d epson"
|
||||
parameters to scanimage.
|
||||
|
||||
The
|
||||
.I --mirror
|
||||
option controls the way the image is scanned. By reading the image data
|
||||
from right to left the image is mirored. Valid options are "yes" and
|
||||
from right to left the image is mirrored. Valid options are "yes" and
|
||||
"no". The default is "no".
|
||||
|
||||
The
|
||||
|
|
@ -145,7 +145,7 @@ The
|
|||
switch activates the automatic area segmentation for monochrome scans. The
|
||||
scanner will try to determine which areas are text and which contain
|
||||
images. The image areas will be halftoned, and the text will be
|
||||
impoved. Valid options are "yes" and "no". The default is "yes".
|
||||
improved. Valid options are "yes" and "no". The default is "yes".
|
||||
|
||||
The
|
||||
.I --gamma-table
|
||||
|
|
@ -188,7 +188,7 @@ The geometry options
|
|||
.I -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
|
||||
aea. All parameters are specified in milimeters.
|
||||
area. All parameters are specified in millimeters.
|
||||
|
||||
The
|
||||
.I --quick-format
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ FUJITSU M3092DCd
|
|||
.RE
|
||||
.P
|
||||
The driver supports lineart, halftone, grayscale, and color
|
||||
(3091 and 3092) scanning depending on hardware capabiliites.
|
||||
(3091 and 3092) scanning depending on hardware capabilities.
|
||||
|
||||
The "Fujitsu" driver is a first attempt at integrating support
|
||||
for all Fujitsu scanners \- previously available as different
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ autodetected by
|
|||
.B usb vendor_id product_id
|
||||
statements which are already included into
|
||||
.IR genesys.conf .
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identify the
|
||||
scanner.
|
||||
.PP
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ ignored. A sample configuration file is shown below:
|
|||
The "topfolder" line specifies the "fixed" part of the file path. For
|
||||
example, on the Kodak DC-240, files are stored in the directory
|
||||
/DCIM/100DC240. The /DCIM portion is constant, but 100DC240 will
|
||||
change and must be read from the camers. In this case, the
|
||||
change and must be read from the camera. In this case, the
|
||||
line would read "topfolder=/DCIM"
|
||||
.PP
|
||||
Some cameras don't implement a file structure and store all pictures
|
||||
|
|
@ -105,7 +105,7 @@ sane(7)
|
|||
Peter S. Fales
|
||||
|
||||
.PP
|
||||
The manpage was largeley copied from the dc210 manpage.
|
||||
The manpage was largely copied from the dc210 manpage.
|
||||
|
||||
.SH BUGS
|
||||
Many, no doubt.
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ software that will be uploaded to the scanner's memory. It's usually named
|
|||
.IR 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
|
||||
Mustek scanners, the file can be downloaded from the gt68xx backend homepage. For
|
||||
other scanners, check the CD for .usb files. If you only find *.cab files, try
|
||||
cabextract to unpack. If everything else fails, you must install the Windows
|
||||
driver and get the firmware from there (usually in the
|
||||
|
|
@ -63,7 +63,7 @@ autodetected by
|
|||
.B usb vendor_id product_id
|
||||
statements which are already included into
|
||||
.IR gt68xx.conf .
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identfy the
|
||||
"vendor_id" and "product_id" are hexadecimal numbers that identify the
|
||||
scanner.
|
||||
.PP
|
||||
The
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ complete.
|
|||
Other HP scanners are not supported by the "hp" backend, but might be supported
|
||||
by another one. See
|
||||
.IR http://www.sane-project.org/ .
|
||||
You can also watch the sane-devel mailinglist at
|
||||
You can also watch the sane-devel mailing list at
|
||||
.IR http://www.sane-project.org/mailing-lists.html .
|
||||
.PP
|
||||
More details about the hp backend can be found on its homepage
|
||||
|
|
@ -141,7 +141,7 @@ used in case of forward/backward moving scanner lamp.
|
|||
Option
|
||||
.B dumb-read
|
||||
can be used to work around problems with "Error during device I/O". These
|
||||
problems may occur with certain SCSI-to-USB convertors or Buslogic SCSI cards.
|
||||
problems may occur with certain SCSI-to-USB converters or Buslogic SCSI cards.
|
||||
The option should not be used for SCSI devices which are working correctly.
|
||||
Otherwise startup of frontends and changing parameters might be slower.
|
||||
.PP
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ statements which are already included into
|
|||
.IR ma1509.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
|
||||
identfy the scanner. If this doesn't work, a device name must be placed in
|
||||
identify the scanner. If this doesn't work, a device name must be placed in
|
||||
.I ma1509.conf
|
||||
as described above.
|
||||
.PP
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Agfa StudioScan II, StudioScan IIsi
|
|||
.br
|
||||
Agfa Arcus II (but not the "Arcus")
|
||||
.br
|
||||
Agfa DuoScan (premliminary)
|
||||
Agfa DuoScan (preliminary)
|
||||
.br
|
||||
Vobis "Highscreen Realscan"
|
||||
.br
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ have loaded the scsi_mod and sg modules!
|
|||
.PP
|
||||
If you try your scanner for the first time keep an eye on it. If it gets
|
||||
commands that it doesn't understand the scanhead may go beyond the scan area.
|
||||
The scanner then makes strange noises. In this case immedieately switch off
|
||||
The scanner then makes strange noises. In this case immediately switch off
|
||||
the scanner or disconnect its power cable to prevent damages!
|
||||
.PP
|
||||
If your scanner is a different one than the models mentioned above and it is
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ non-SCSI scanners that have some support at this point is the 600 II N and 600
|
|||
II EP scanners. The former one comes with its own parallel port adapter (i.e.,
|
||||
it does
|
||||
.I not
|
||||
attach to the printer port). Both scanners use the SCSI protocoll internally,
|
||||
attach to the printer port). Both scanners use the SCSI protocol internally,
|
||||
too. More info on how to use these parallel port scanners can be found below in
|
||||
section
|
||||
.BR "PARALLEL PORT SCANNERS" .
|
||||
|
|
@ -314,7 +314,7 @@ setuid root (generally not recommended for safety reasons) or, alternatively,
|
|||
access this backend through the network daemon
|
||||
.BR saned (8).
|
||||
.PP
|
||||
If the Mustek backend blocks while sending the inqiury command to the scanner,
|
||||
If the Mustek backend blocks while sending the inquiry command to the scanner,
|
||||
add the option
|
||||
.B force-wait
|
||||
to
|
||||
|
|
@ -396,7 +396,7 @@ Henning Meier-Geinitz, James Perry (600 II EP).
|
|||
|
||||
.SH BUGS
|
||||
Scanning with the SCSI adapters supplied by Mustek is very slow at
|
||||
high resolutions and wide scanareas.
|
||||
high resolutions and wide scan areas.
|
||||
.PP
|
||||
Some scanners (e.g. Paragon 1200 A3 + Pro, SE A3) need more testing.
|
||||
.PP
|
||||
|
|
|
|||
|
|
@ -224,7 +224,7 @@ ignored. Options have the following format:
|
|||
.RE
|
||||
.PP
|
||||
Depending on the nature of the option, a value may or may not be present.
|
||||
Options always apply to the scanner definition that preceeds them. There
|
||||
Options always apply to the scanner definition that precedes them. There
|
||||
are no global options. Options are also driver-specific: not all drivers
|
||||
support all possible options.
|
||||
|
||||
|
|
@ -296,7 +296,7 @@ maximum delay is 100 ms.
|
|||
.br
|
||||
Note that every additional ms of delay can add up to 14 seconds to the total
|
||||
scanning time (highest resolution), so an as small as possible value is
|
||||
prefered.
|
||||
preferred.
|
||||
.br
|
||||
Default value: 0
|
||||
.br
|
||||
|
|
@ -412,7 +412,7 @@ option top 56
|
|||
.SH GLOBAL OPTIONS
|
||||
.PP
|
||||
You can control the overall behaviour of the mustek_pp backend by global
|
||||
options which preceed any scanner definition in the mustek_pp.conf file.
|
||||
options which precede any scanner definition in the mustek_pp.conf file.
|
||||
.br
|
||||
Currently, there is only one global option:
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ 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
|
||||
identfy the scanner. If this doesn't work, a device name and the option
|
||||
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
|
||||
as described above.
|
||||
|
|
@ -155,7 +155,7 @@ debug levels increase the verbosity of the output.
|
|||
|
||||
.ft CR
|
||||
.nf
|
||||
Value Descsription
|
||||
Value Description
|
||||
0 no output
|
||||
1 print fatal errors
|
||||
2 print important messages
|
||||
|
|
@ -195,10 +195,10 @@ These devices have a hardware bug: Once data is written to them, they can't be
|
|||
reset (toggle = DATA0). That means, any operation that tries to reset the
|
||||
device will result in running into timeouts.
|
||||
|
||||
In earlier versions this backend failed when it is loaded the second time in
|
||||
In earlier versions this backend failed when it was loaded the second time in
|
||||
some configurations. The only choice was to replug the scanner in this case. The
|
||||
backend uses a workaround for that bug now but it's only tested on
|
||||
Linux. Reports for other operating systems are appriciated.
|
||||
Linux. Reports for other operating systems are appreciated.
|
||||
|
||||
.PP
|
||||
More detailed bug information is available at the Mustek backend homepage
|
||||
|
|
|
|||
|
|
@ -193,7 +193,7 @@ detect this by its own. If device is set to
|
|||
then the next matching device is used.
|
||||
.br
|
||||
The following options can be used for a default setup of
|
||||
your device. Most of them are also availaby through
|
||||
your device. Most of them are also available through
|
||||
the frontend.
|
||||
.PP
|
||||
.B
|
||||
|
|
@ -449,12 +449,12 @@ to 16 times the physical resolution. The only scaling
|
|||
is done on resolutions between the physical resolution
|
||||
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
|
||||
so scaling is necessary, because the sensor only delivers
|
||||
600dpi but the motor is capable of performing 1200dpi
|
||||
steps.
|
||||
.PP
|
||||
* Plusteks' model policy is somewhat inconsistent. This
|
||||
means, they sell technical different devices under the
|
||||
* Plusteks' model policy is somewhat inconsistent. They
|
||||
sell technically different devices under the
|
||||
same product name. Therefore it is possible that some
|
||||
devices like the UT12 or U12 won't work \- please check
|
||||
the model list above and compare the product-id to
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ believe it works in all cases yet. Reportedly, acquiring images of
|
|||
certain sizes work fine, but others result in shifted images (sounds
|
||||
like a problem due to byte-padding).
|
||||
.PP
|
||||
The program needs root-priviledges since it needs to be able to access
|
||||
The program needs root-privileges since it needs to be able to access
|
||||
the camera's I/O ports.
|
||||
.SH SEE ALSO
|
||||
sane(7)
|
||||
|
|
|
|||
|
|
@ -41,9 +41,9 @@ scanimage --help -d sceptre
|
|||
.B --mode
|
||||
selects the basic mode of operation of the scanner valid choices are
|
||||
.I Lineart, Halftone, Gray and Color.
|
||||
The Lineart and Haltone mode are black and white only (1 bit). Gray
|
||||
The Lineart and Halftone mode are black and white only (1 bit). Gray
|
||||
will produce 256 levels of gray (8 bits). Color will produce a 24 bits
|
||||
color image. The scanner suports 30 bits internally but it only
|
||||
color image. The scanner supports 30 bits internally but it only
|
||||
exports 24.
|
||||
|
||||
.TP
|
||||
|
|
@ -100,7 +100,7 @@ selected. The default is "no".
|
|||
.B -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 milimeters by default.
|
||||
area. All parameters are specified in millimeters by default.
|
||||
|
||||
|
||||
.SH CONFIGURATION FILE
|
||||
|
|
|
|||
|
|
@ -152,7 +152,7 @@ The scanner probes ok but any attempt to
|
|||
access it
|
||||
.I hangs
|
||||
the entire system. It looks like something is disabling interrupts and
|
||||
then not reenabling them, so it looks like a bug in the FreeBSD
|
||||
then not re-enabling them, so it looks like a bug in the FreeBSD
|
||||
.B aic
|
||||
driver.
|
||||
.TP
|
||||
|
|
@ -267,7 +267,7 @@ You may change the values of the USLEEP macros in drivers/scsi/g_NCR5380.c.
|
|||
Some documentation is in this file and NCR5380.c.
|
||||
.TP
|
||||
NCR/Symbios 810
|
||||
For some scanners it may be necssary to disable disconnect/reconnect. To
|
||||
For some scanners it may be necessary to disable disconnect/reconnect. To
|
||||
achieve this use the option ncr53c8xx="disc:n". Some people reported that
|
||||
their scanner only worked with the 53c7,8xx driver, not the ncr53c8xx. Try
|
||||
both if you have trouble.
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ For the latest information on this backend, please visit
|
|||
|
||||
This backend may also be able to drive the UMAX Astra 2000U.
|
||||
Some people are successful with it, others report that the
|
||||
colors come out terrible. Your milage may vary.
|
||||
colors come out terrible. Your mileage may vary.
|
||||
|
||||
From Stephane (the author of sane-umax_pp), I learned that there
|
||||
are differences in the way the color calibration is performed on
|
||||
|
|
|
|||
|
|
@ -407,7 +407,7 @@ The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB scanner. See
|
|||
for details.
|
||||
.TP
|
||||
.B sm3840
|
||||
The SANE sm3840 backend suppoert the Microtek ScanMaker 3840 USB scanner. See
|
||||
The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB scanner. See
|
||||
.BR sane-sm3840 (5)
|
||||
for details.
|
||||
.TP
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue