summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--man/gamma4scanimage.1.html2
-rw-r--r--man/sane-abaton.5.html10
-rw-r--r--man/sane-agfafocus.5.html2
-rw-r--r--man/sane-apple.5.html143
-rw-r--r--man/sane-artec.5.html2
-rw-r--r--man/sane-artec_eplus48u.5.html14
-rw-r--r--man/sane-as6e.5.html2
-rw-r--r--man/sane-avision.5.html4
-rw-r--r--man/sane-bh.5.html16
-rw-r--r--man/sane-canon.5.html2
-rw-r--r--man/sane-canon630u.5.html2
-rw-r--r--man/sane-canon_dr.5.html179
-rw-r--r--man/sane-canon_pp.5.html2
-rw-r--r--man/sane-cardscan.5.html2
-rw-r--r--man/sane-config.1.html2
-rw-r--r--man/sane-coolscan.5.html2
-rw-r--r--man/sane-coolscan2.5.html6
-rw-r--r--man/sane-coolscan3.5.html204
-rw-r--r--man/sane-dc210.5.html2
-rw-r--r--man/sane-dc240.5.html2
-rw-r--r--man/sane-dc25.5.html2
-rw-r--r--man/sane-dll.5.html2
-rw-r--r--man/sane-dmc.5.html2
-rw-r--r--man/sane-epjitsu.5.html8
-rw-r--r--man/sane-epson.5.html15
-rw-r--r--man/sane-epson2.5.html348
-rw-r--r--man/sane-find-scanner.1.html24
-rw-r--r--man/sane-fujitsu.5.html197
-rw-r--r--man/sane-genesys.5.html16
-rw-r--r--man/sane-gphoto2.5.html2
-rw-r--r--man/sane-gt68xx.5.html22
-rw-r--r--man/sane-hp.5.html122
-rw-r--r--man/sane-hp3500.5.html2
-rw-r--r--man/sane-hp3900.5.html4
-rw-r--r--man/sane-hp4200.5.html6
-rw-r--r--man/sane-hp5400.5.html6
-rw-r--r--man/sane-hp5590.5.html3
-rw-r--r--man/sane-hpljm1005.5.html7
-rw-r--r--man/sane-hpsj5s.5.html2
-rw-r--r--man/sane-hs2p.5.html2
-rw-r--r--man/sane-ibm.5.html2
-rw-r--r--man/sane-leo.5.html2
-rw-r--r--man/sane-lexmark.5.html17
-rw-r--r--man/sane-ma1509.5.html10
-rw-r--r--man/sane-matsushita.5.html2
-rw-r--r--man/sane-microtek.5.html16
-rw-r--r--man/sane-microtek2.5.html6
-rw-r--r--man/sane-mustek.5.html26
-rw-r--r--man/sane-mustek_pp.5.html285
-rw-r--r--man/sane-mustek_usb.5.html10
-rw-r--r--man/sane-mustek_usb2.5.html18
-rw-r--r--man/sane-nec.5.html2
-rw-r--r--man/sane-net.5.html4
-rw-r--r--man/sane-niash.5.html2
-rw-r--r--man/sane-pie.5.html2
-rw-r--r--man/sane-pint.5.html67
-rw-r--r--man/sane-pixma.5.html100
-rw-r--r--man/sane-plustek.5.html18
-rw-r--r--man/sane-plustek_pp.5.html4
-rw-r--r--man/sane-pnm.5.html2
-rw-r--r--man/sane-qcam.5.html2
-rw-r--r--man/sane-ricoh.5.html2
-rw-r--r--man/sane-rts8891.5.html160
-rw-r--r--man/sane-s9036.5.html2
-rw-r--r--man/sane-sceptre.5.html2
-rw-r--r--man/sane-scsi.5.html2
-rw-r--r--man/sane-sharp.5.html2
-rw-r--r--man/sane-sm3600.5.html2
-rw-r--r--man/sane-sm3840.5.html4
-rw-r--r--man/sane-snapscan.5.html6
-rw-r--r--man/sane-sp15c.5.html2
-rw-r--r--man/sane-st400.5.html2
-rw-r--r--man/sane-stv680.5.html2
-rw-r--r--man/sane-tamarack.5.html2
-rw-r--r--man/sane-teco1.5.html2
-rw-r--r--man/sane-teco2.5.html2
-rw-r--r--man/sane-teco3.5.html2
-rw-r--r--man/sane-test.5.html2
-rw-r--r--man/sane-u12.5.html4
-rw-r--r--man/sane-umax.5.html2
-rw-r--r--man/sane-umax1220u.5.html6
-rw-r--r--man/sane-umax_pp.5.html8
-rw-r--r--man/sane-usb.5.html6
-rw-r--r--man/sane-v4l.5.html8
-rw-r--r--man/sane-xerox_mfp.5.html75
-rw-r--r--man/scanimage.1.html193
86 files changed, 1742 insertions, 747 deletions
diff --git a/man/gamma4scanimage.1.html b/man/gamma4scanimage.1.html
index 95f09b9..df99669 100644
--- a/man/gamma4scanimage.1.html
+++ b/man/gamma4scanimage.1.html
@@ -71,7 +71,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
Oliver.Rauch@Rauch-Domain.DE
-sane-backends 1.0.19 11 Sep 2002 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
+ 10 Jul 2008 <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-abaton.5.html b/man/sane-abaton.5.html
index 9544b4a..392a6e9 100644
--- a/man/sane-abaton.5.html
+++ b/man/sane-abaton.5.html
@@ -27,8 +27,8 @@
with this backend, or if you own an Abaton scanner that does not work
with this backend, please contact <I>sane-devel@lists.alioth.debian.org</I>
with the model number, so that arrangements can be made to include sup-
- port for it. Have a look at http://www.sane-project.org/mailing-
- lists.html concerning subscription to sane-devel.
+ port for it. Have a look at http://www.sane-project.org/mail-
+ ing-lists.html concerning subscription to sane-devel.
Abaton is out of business, and these scanners are not supported by
Everex (the parent company of Abaton), nor is there any programming
@@ -118,8 +118,8 @@
If you have found something that you think is a bug, please attempt to
recreate it with the SANE_DEBUG_ABATON environment variable set to 255,
- and send a report detailing the conditions surrounding the bug to <I>sane-</I>
- <I>devel@lists.alioth.debian.org</I>.
+ and send a report detailing the conditions surrounding the bug to
+ <I>sane-devel@lists.alioth.debian.org</I>.
</PRE>
@@ -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.19 19 Nov 1998 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-agfafocus.5.html b/man/sane-agfafocus.5.html
index 6896870..7427e6e 100644
--- a/man/sane-agfafocus.5.html
+++ b/man/sane-agfafocus.5.html
@@ -178,7 +178,7 @@
<H2>AUTHOR</H2><PRE>
Ingo Schneider and Karl Anders ?ygard.
-sane-backends 1.0.19 17 Oct 1998 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
+ 10 Jul 2008 <B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-apple.5.html b/man/sane-apple.5.html
index 1870158..1645a7b 100644
--- a/man/sane-apple.5.html
+++ b/man/sane-apple.5.html
@@ -28,9 +28,10 @@
If you own a Apple scanner other than the ones listed above that works
with this backend, please let us know by sending the scanner's model
- name, SCSI id, and firmware revision to <I>sane-</I>
- <I>devel@lists.alioth.debian.org</I>. See http://www.sane-project.org/mail-
- ing-lists.html for details on how to subscribe to sane-devel.
+ name, SCSI id, and firmware revision to
+ <I>sane-devel@lists.alioth.debian.org</I>. See
+ http://www.sane-project.org/mailing-lists.html for details on how to
+ subscribe to sane-devel.
</PRE>
@@ -39,30 +40,30 @@
<I>special</I>
- Where <I>special</I> is either the path-name for the special device that cor-
- responds to a SCSI scanner. For SCSI scanners, the special device name
- must be a generic SCSI device or a symlink to such a device. Under
- Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
+ Where <I>special</I> is either the path-name for the special device that cor-
+ responds to a SCSI scanner. For SCSI scanners, the special device name
+ must be a generic SCSI device or a symlink to such a device. Under
+ Linux, such a device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example.
See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
</PRE>
<H2>CONFIGURATION</H2><PRE>
- The <I>apple.conf</I> file is a list of options and device names that corre-
- spond to Apple scanners. Empty lines and lines starting with a hash
- mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what constitutes
+ The <I>apple.conf</I> file is a list of options and device names that corre-
+ spond to Apple scanners. Empty lines and lines starting with a hash
+ mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> on details of what constitutes
a valid device name.
- Options come in two flavors: global and positional ones. Global
+ Options come in two flavors: global and positional ones. Global
options apply to all devices managed by the backend, whereas positional
- options apply just to the most recently mentioned device. Note that
+ options apply just to the most recently mentioned device. Note that
this means that the order in which the options appear matters!
</PRE>
<H2>SCSI ADAPTER TIPS</H2><PRE>
SCSI scanners are typically delivered with an ISA SCSI adapter. Unfor-
- tunately, that adapter is not worth much since it is not interrupt
+ tunately, that adapter is not worth much since it is not interrupt
driven. It is sometimes possible to get the supplied card to work, but
without an interrupt line, scanning will put so much load on the system
that it becomes almost unusable for other tasks.
@@ -71,7 +72,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d/apple.conf</I>
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/lib/sane/libsane-apple.a</I>
@@ -85,33 +86,33 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
- This environment variable is list of directories where SANE
- looks for the configuration file. Under UNIX directory names
- are separated by a colon (':'), under OS/2 by a semi-colon
- (';'). If SANE_CONFIG_DIR is not set, SANE defaults to search-
- ing the current working directory (".") and then /etc/sane.d.
+ This environment variable is list of directories where SANE
+ looks for the configuration file. Under UNIX directory names
+ are separated by a colon (':'), under OS/2 by a semi-colon
+ (';'). If SANE_CONFIG_DIR is not set, SANE defaults to search-
+ ing the current working directory (".") and then /etc/sane.d.
If the value of $SANE_CONFIG_DIR ends with the separator charac-
- ter, the default directories are searched after the directory
- list. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
+ ter, the default directories are searched after the directory
+ list. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and "/etc/sane.d"
being searched (in that order).
<B>SANE_DEBUG_APPLE</B>
- Controls the debug level. A value of 255 prints all debug out-
- put. Smaller values reduce verbosity. Requires a library com-
+ Controls the debug level. A value of 255 prints all debug out-
+ put. Smaller values reduce verbosity. Requires a library com-
piled with debug support.
</PRE>
<H2>CURRENT STATUS</H2><PRE>
The apple backend is now in version 0.3 (Tue Jul 21 1998). Since I only
- have the AppleScanner and not the other models (OneScanner, ColorOneS-
+ have the AppleScanner and not the other models (OneScanner, ColorOneS-
canner) I can only develop/test for the AppleScanner effectively. How-
ever with this release I almost completed the gui part of all scanners.
- Most of the functionality is there. At least OneScanner should scan at
- the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
+ Most of the functionality is there. At least OneScanner should scan at
+ the AppleScanner's compatible modes (LineArt, HalfTone, Gray16). My
personal belief is that with a slight touch of debugging the OneScanner
- could be actually usable. The ColorOneScanner needs more work. AppleS-
+ could be actually usable. The ColorOneScanner needs more work. AppleS-
canner is of course almost fully supported.
@@ -126,84 +127,84 @@
Cannot up/download halftone patterns or calibration vectors.
<B>ColorOneScanner</B>
- Cannot up/download halftone patterns, calibration vectors, cus-
- tom Color Correction Tables (CCT) and of course custom gamma
+ Cannot up/download halftone patterns, calibration vectors, cus-
+ tom Color Correction Tables (CCT) and of course custom gamma
tables.
<B>Park/UnPark</B> <B>(OneScanner,</B> <B>ColorOneScanner)</B>
The above functionalities are missing because I don't have the hardware
to experiment on. Another reason is my lack of understanding as to how
- or if the SANE API provide means to describe any array type besides
+ or if the SANE API provide means to describe any array type besides
gamma.
</PRE>
<H2>UNSUPPORTED FEATURES</H2><PRE>
- The following "features" will never be supported, at least while I
+ The following "features" will never be supported, at least while I
maintain the sane-apple backend.
<B>NoHome</B> <B>(AppleScanner)</B>
- The scanner lamp stays on and the carriage assembly remains
+ The scanner lamp stays on and the carriage assembly remains
where it stops at the end of the scan. After two minutes, if the
scanner does not receive another SCAN command, the lamp goes off
and the carriage returns to the home position.
<B>Compression</B> <B>(AppleScanner)</B>
- The Scanner can compress data with CCITT Group III one dimen-
+ The Scanner can compress data with CCITT Group III one dimen-
sional algorithm (fax) and the Skip White Line algorithm.
<B>Multiple</B> <B>Windows</B> <B>(AppleScanner)</B>
- AppleScanner may support multiple windows. It would be a cool
+ AppleScanner may support multiple windows. It would be a cool
feature and a challenge for me to code if it could intermix dif-
- ferent options for different windows (scan areas). This way it
- could scan a document in LineArt mode but the figures in it in
- Gray and at a different resolution. Unfortunately this is
+ ferent options for different windows (scan areas). This way it
+ could scan a document in LineArt mode but the figures in it in
+ Gray and at a different resolution. Unfortunately this is
impossible.
<B>Scan</B> <B>Direction</B> <B>(OneScanner)</B>
It controls the scan direction. (?)
<B>Status/Reset</B> <B>Button</B> <B>(OneScanner)</B>
- This option controls the status of the button on the OneScanner
+ This option controls the status of the button on the OneScanner
model. You can also reset the button status by software.
</PRE>
<H2>BUGS</H2><PRE>
- SANE backend bugs are divided in two classes. We have <B>GUI</B> bugs and
+ SANE backend bugs are divided in two classes. We have <B>GUI</B> bugs and
<B>scanner</B> <B>specific</B> 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
+ 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
<B>ftp://ftpdev.info.apple.com/devworld/Technical_Documentation/Peripher-</B>
- <B>als_Documentation/</B> is an interesting exercise. I may have missed some
+ <B>als_Documentation/</B> 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
+ Programming Guide says nothing. I had to assume it is valid only in
LineArt mode.
- Scanner specific bugs are mostly due to mandatory round-offs in order
+ Scanner specific bugs are mostly due to mandatory round-offs in order
to scan. In the documentation in one place states that the width of the
- scan area should be a byte multiple. In another place it says that the
+ scan area should be a byte multiple. In another place it says that the
width of the scan area should be an even byte multiple. Go figure...
- Other sources of bugs are due to scsi communication, scsi connects and
- disconnects. However the classical bugs are still there. So you may
- encounter buffer overruns, null pointers, memory corruption and <B>SANE</B>
+ Other sources of bugs are due to scsi communication, scsi connects and
+ disconnects. However the classical bugs are still there. So you may
+ encounter buffer overruns, null pointers, memory corruption and <B>SANE</B>
API violations.
<B>SIGSEGV</B> <B>on</B> <B>SliceBars</B>
When you try to modify the scan area from the slice bar you have
- a nice little cute core dump. I don't know why. If you select
+ a nice little cute core dump. I don't know why. If you select
the scan area from the preview window or by hand typing the num-
bers everything is fine. The SIGSEGV happens deep in gtk library
(gdk). I really cannot debug it.
<B>Options</B> <B>too</B> <B>much</B>
- It is possible, especially for the ColorOneScanner, for the
+ It is possible, especially for the ColorOneScanner, for the
backend's options panel to extend beyond your screen. It happens
- with mine and I am running my X Server at 1024x768. What can I
+ with mine and I am running my X Server at 1024x768. What can I
say? Try smaller fonts in the X server, or virtual screens.
<B>Weird</B> <B>SCSI</B> <B>behaviour</B>
@@ -211,35 +212,35 @@
&gt;&gt; OS: FreeBSD 2.2.6
&gt;&gt; CC: egcs-1.02
- Just wanted to follow up on this... I recently changed my SCSI
- card from the Adaptec 2940UW to a dual-channel Symbios 786
- chipset. When I started up SANE with your driver, I managed to
+ Just wanted to follow up on this... I recently changed my SCSI
+ card from the Adaptec 2940UW to a dual-channel Symbios 786
+ chipset. When I started up SANE with your driver, I managed to
scan line art drawings okay, but Gray16 scans led to a stream of
- SCSI error messages on the console, ultimately hanging with a
- message saying the scanner wasn't releasing the SCSI bus. This
+ SCSI error messages on the console, ultimately hanging with a
+ message saying the scanner wasn't releasing the SCSI bus. This
may be that the Symbios is simply less tolerant of ancient hard-
ware, or may be bugs in your driver or in SANE itself...
</PRE>
<H2>DEBUG</H2><PRE>
- If you encounter a GUI bug please set the environmental variable
- SANE_DEBUG_APPLE to 255 and rerun the exact sequence of keystrokes and
- menu selections to reproduce it. Then send me a report with the log
+ If you encounter a GUI bug please set the environmental variable
+ SANE_DEBUG_APPLE to 255 and rerun the exact sequence of keystrokes and
+ menu selections to reproduce it. Then send me a report with the log
attached.
If you have an Apple Macintosh with the AppleScanners driver installed,
- reporting to me which options are grayed out (inactive) in what modes
+ reporting to me which options are grayed out (inactive) in what modes
would be very helpful.
- If you want to offer some help but you don't have a scanner, or you
- don't have the model you would like to help with, or you are a SANE
- developer and you just want to take a look at how the apple backend
- looks like, goto to apple.h and #define the NEUTRALIZE_BACKEND macro.
- You can select the scanner model through the APPLE_MODEL_SELECT macro.
+ If you want to offer some help but you don't have a scanner, or you
+ don't have the model you would like to help with, or you are a SANE
+ developer and you just want to take a look at how the apple backend
+ looks like, goto to apple.h and #define the NEUTRALIZE_BACKEND macro.
+ You can select the scanner model through the APPLE_MODEL_SELECT macro.
Available options are APPLESCANNER, ONESCANNER, COLORONESCANNER.
- If you encounter a SCSI bus error or trimmed and/or displaced images
+ 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 the report.
@@ -247,7 +248,7 @@
</PRE>
<H2>TODO</H2><PRE>
<B>Non</B> <B>Blocking</B> <B>Support</B>
- Make sane-apple a non blocking backend. Properly support
+ Make sane-apple a non blocking backend. Properly support
<B>sane_set_io_mode</B> and <B>sane_get_select_fd</B>
<B>Scan</B> Make scanning possible for all models in all supported modes.
@@ -262,11 +263,11 @@
</PRE>
<H2>AUTHOR</H2><PRE>
- The sane-apple backend was written not entirely from scratch by Milon
- Firikis. It is mostly based on the mustek backend from David Mosberger
+ The sane-apple backend was written not entirely from scratch by Milon
+ Firikis. It is mostly based on the mustek backend from David Mosberger
and Andreas Czechanowski
-sane-backends 1.0.19 13 May 1998 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-artec.5.html b/man/sane-artec.5.html
index 258b83a..e52a595 100644
--- a/man/sane-artec.5.html
+++ b/man/sane-artec.5.html
@@ -170,7 +170,7 @@
<H2>AUTHOR</H2><PRE>
Chris Pinkham (cpinkham@corp.infi.net)
-sane-backends 1.0.19 24 Jan 2000 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-artec_eplus48u.5.html b/man/sane-artec_eplus48u.5.html
index a597fcc..68690ec 100644
--- a/man/sane-artec_eplus48u.5.html
+++ b/man/sane-artec_eplus48u.5.html
@@ -23,8 +23,8 @@
using the GT6816 chipset like the Artec E+ 48U. These scanners have a
contact image sensor (CIS) and an USB interface.
- A complete list of supported devices can be found on <I>http://www.sane-</I>
- <I>project.org/sane-supported-devices.html</I>.
+ A complete list of supported devices can be found on
+ <I>http://www.sane-project.org/sane-supported-devices.html</I>.
This is ALPHA software. Especially if you test new or untested scan-
ners, keep your hand at the scanner's plug and unplug it, if the head
@@ -42,8 +42,8 @@
<H2>KERNEL ISSUES</H2><PRE>
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 look at sane-
- <B><A HREF="usb.5.html">usb(5)</A></B>.
+ For setting permissions and general USB information look at
+ <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
When you are using the scanner module, a Linux kernel 2.4.12 or newer
is required.
@@ -171,10 +171,10 @@
Support for buttons is missing due to missing support in SANE.
- Please contact us if you find a bug: <I>http://www.sane-</I>
- <I>project.org/bugs.html</I>.
+ Please contact us if you find a bug:
+ <I>http://www.sane-project.org/bugs.html</I>.
-sane-backends 1.0.19 15 Jan 2006 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-as6e.5.html b/man/sane-as6e.5.html
index 05d1973..e9002d9 100644
--- a/man/sane-as6e.5.html
+++ b/man/sane-as6e.5.html
@@ -50,7 +50,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
yossarian@users.sourceforge.net
-sane-backends 1.0.19 Dec 14th, 2003 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-avision.5.html b/man/sane-avision.5.html
index f3732b2..cf479f9 100644
--- a/man/sane-avision.5.html
+++ b/man/sane-avision.5.html
@@ -166,9 +166,9 @@
</PRE>
<H2>AUTHOR</H2><PRE>
- Ren? Rebe and Meino Christian Cramer
+ Rene Rebe and Meino Christian Cramer
-sane-backends 1.0.19 04 Mar 2003 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-bh.5.html b/man/sane-bh.5.html
index 7839e6d..019605c 100644
--- a/man/sane-bh.5.html
+++ b/man/sane-bh.5.html
@@ -34,11 +34,11 @@
If you have a Bell+Howell scanner and are able to test it with this
backend, please contact <I>sane-devel@lists.alioth.debian.org</I> with the
- model number and testing results. Have a look at http://www.sane-
- project.org/mailing-lists.html concerning subscription to sane-devel.
- Additionally, the author is curious as to the likelihood of using this
- backend with the newer 4000 and 8000 series scanners. If you have such
- a beast, please let me know.
+ model number and testing results. Have a look at
+ http://www.sane-project.org/mailing-lists.html concerning subscription
+ to sane-devel. Additionally, the author is curious as to the likelihood
+ of using this backend with the newer 4000 and 8000 series scanners. If
+ you have such a beast, please let me know.
The Bell+Howell Copiscan II series document scanners are high volume,
high throughput scanners designed for document scanning applications.
@@ -486,8 +486,8 @@
If you have found something that you think is a bug, please attempt to
recreate it with the SANE_DEBUG_BH environment variable set to 255, and
- send a report detailing the conditions surrounding the bug to <I>sane-</I>
- <I>devel@lists.alioth.debian.org</I>.
+ send a report detailing the conditions surrounding the bug to
+ <I>sane-devel@lists.alioth.debian.org</I>.
</PRE>
@@ -502,7 +502,7 @@
Reifschneider of tummy.com ltd. Some 8000 enhancements added by Mark
Temple.
-sane-backends 1.0.19 15 Sep 1999 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
+ 10 Jul 2008 <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-canon.5.html b/man/sane-canon.5.html
index fe98f8e..be524a9 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.19 03 May 2001 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-canon630u.5.html b/man/sane-canon630u.5.html
index 86a3887..bcc5a09 100644
--- a/man/sane-canon630u.5.html
+++ b/man/sane-canon630u.5.html
@@ -117,7 +117,7 @@
<H2>AUTHOR</H2><PRE>
Nathan Rutman
-sane-backends 1.0.19 06 Apr 2002 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-canon_dr.5.html b/man/sane-canon_dr.5.html
new file mode 100644
index 0000000..e9ee718
--- /dev/null
+++ b/man/sane-canon_dr.5.html
@@ -0,0 +1,179 @@
+<HTML>
+<HEAD>
+<TITLE>sane-canon_dr.5</TITLE>
+</HEAD>
+<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
+<H1>sane-canon_dr.5</H1>
+<HR>
+<PRE>
+<!-- Manpage converted by man2html 3.0.1 -->
+<B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
+
+
+</PRE>
+<H2>NAME</H2><PRE>
+ sane-canon_dr - SANE backend for Canon DR-series scanners
+
+
+</PRE>
+<H2>DESCRIPTION</H2><PRE>
+ The <B>sane-canon_dr</B> library implements a SANE (Scanner Access Now Easy)
+ backend which provides access to some Canon DR-series scanners.
+
+ This document describes backend version 26, which shipped with SANE
+ 1.0.20.
+
+
+</PRE>
+<H2>SUPPORTED HARDWARE</H2><PRE>
+ This version has only been tested with a few scanner models. Please see
+ http://www.sane-project.org/sane-supported-devices.html for a more
+ recent list.
+
+ This backend may support other Canon scanners. The best way to deter-
+ mine 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.
+
+
+</PRE>
+<H2>OPTIONS</H2><PRE>
+ Effort has been made to expose most hardware options, including:
+
+ source s
+ Selects the source for the scan. Options may include "Flatbed",
+ "ADF Front", "ADF Back", "ADF Duplex".
+
+ mode m
+ Selects the mode for the scan. Options may include "Lineart",
+ "Halftone", "Gray", and "Color".
+
+ resolution, y-resolution
+ Controls scan resolution. Setting --resolution also sets
+ --y-resolution, though this behavior is overridden by some fron-
+ tends.
+
+ tl-x, tl-y, br-x, br-y
+ Sets scan area upper left and lower right coordinates. These are
+ renamed t, l, x, y by some frontends.
+
+ page-width, page-height
+ Sets paper size. Used by scanner to determine centering of scan
+ coordinates when using ADF and to detect double feed errors.
+
+ Other options will be available based on the capabilities of the scan-
+ ner: enhancement, compression, buttons and sensors, etc.
+
+ 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.
+
+
+</PRE>
+<H2>CONFIGURATION FILE</H2><PRE>
+ The configuration file "canon_dr.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 of scanners, generally only when the frontend starts. If the
+ configuration file is missing, the backend will fail to run.
+
+ Scanners can be specified in the configuration file in 4 ways:
+
+ "scsi CANON DR"
+ Requests backend to search all scsi busses in the system for a
+ device which reports itself to be a scanner made by 'CANON',
+ with a model name starting with 'DR'.
+
+ "scsi /dev/sg0" (or other scsi device file)
+ Requests backend to open the named scsi device. Only useful if
+ you have multiple compatible scanners connected to your system,
+ and need to specify one. Probably should not be used with the
+ other "scsi" line above.
+
+ "usb 0x04a9 0x1603" (or other vendor/product ids)
+ Requests backend to search all usb busses in the system for a
+ device which uses that vendor and product id. The device will
+ then be queried to determine if it is a Canon scanner.
+
+ "usb /dev/usb/scanner0" (or other device file)
+ Some systems use a kernel driver to access usb scanners. This
+ method is untested.
+
+ Besides the 'scsi' and 'usb' lines, the configuration file supports the
+ following 'option' lines:
+
+ "option buffer-size [number of bytes]"
+ Set the number of bytes in the data buffer to something other
+ than the compiled-in default of 4MB. Large values may cause
+ timeouts or hangs, small values may cause slow scans.
+
+ Note: The backend does not place an upper bound on this value,
+ as some users required it to be quite large. Values above the
+ default are not recommended, and may crash your OS or lockup
+ your scsi card driver. You have been warned.
+
+ "option vendor-name [string of text]"
+ "option model-name [string of text]"
+ "option version-name [string of text]"
+ These options can be used collectively to override the values
+ provided by the scanner, or to provide the values when the scan-
+ ner cannot.
+
+ "option padded-read [0|1]"
+ Some scanners prepend all data transmitted to host with 12
+ bytes. Enable this option if the scanner fails to respond to
+ commands.
+
+ Note: 'option' lines may appear multiple times in the configuration
+ file. They only apply to scanners discovered by the next 'scsi/usb'
+ line.
+
+
+</PRE>
+<H2>ENVIRONMENT</H2><PRE>
+ The backend uses a single environment variable, SANE_DEBUG_CANON_DR,
+ which enables debugging output to stderr. Valid values are:
+
+ 5 Errors
+ 10 Function trace
+ 15 Function detail
+ 20 Option commands
+ 25 SCSI/USB trace
+ 30 SCSI/USB detail
+ 35 Useless noise
+
+
+</PRE>
+<H2>KNOWN ISSUES</H2><PRE>
+ This backend was entirely reverse engineered from usb traces of the
+ proprietary driver. Various advanced features of the machines may not
+ be enabled. Many machines have not been tested. Their protocol is
+ unknown.
+
+
+</PRE>
+<H2>CREDITS</H2><PRE>
+ The various authors of the sane-fujitsu backend provided useful code
+ Corcaribe Tecnologia C.A. www.cc.com.ve provided significant funding
+ EvriChart, Inc. www.evrichart.com provided funding and loaned equipment
+ Canon, USA. www.usa.canon.com loaned equipment
+
+
+</PRE>
+<H2>SEE ALSO</H2><PRE>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
+
+
+</PRE>
+<H2>AUTHOR</H2><PRE>
+ m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
+
+ 20 Apr 2009 <B><A HREF="sane-canon_dr.5.html">sane-canon_dr(5)</A></B>
+</PRE>
+<HR>
+<ADDRESS>
+Man(1) output converted with
+<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
+</ADDRESS>
+</BODY>
+</HTML>
diff --git a/man/sane-canon_pp.5.html b/man/sane-canon_pp.5.html
index eaa5a21..211a535 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.19 1 October 2002 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-cardscan.5.html b/man/sane-cardscan.5.html
index a8e15a1..f71a59c 100644
--- a/man/sane-cardscan.5.html
+++ b/man/sane-cardscan.5.html
@@ -100,7 +100,7 @@
<H2>AUTHOR</H2><PRE>
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
-sane-backends 1.0.19 2007-07-14 <B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-config.1.html b/man/sane-config.1.html
index d9f78b0..1acab15 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 &lt;jblache@debian.org&gt;, for
the Debian GNU/Linux system (but may be used by others).
-sane-backends 1.0.19 8 Jan 2004 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
+ 10 Jul 2008 <B><A HREF="sane-config.1.html">sane-config(1)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-coolscan.5.html b/man/sane-coolscan.5.html
index d8e36e1..def4fff 100644
--- a/man/sane-coolscan.5.html
+++ b/man/sane-coolscan.5.html
@@ -131,7 +131,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
andreas.rick@free.fr
-sane-backends 1.0.19 4 July 2000 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-coolscan2.5.html b/man/sane-coolscan2.5.html
index 6237a1e..02df349 100644
--- a/man/sane-coolscan2.5.html
+++ b/man/sane-coolscan2.5.html
@@ -48,7 +48,7 @@
Valid command line options and their syntax can be listed by using
scanimage --help -d coolscan2:&lt;interface&gt;:&lt;device&gt;
where &lt;interface&gt; and &lt;device&gt; specify the device in question, as in
- the configuration file (see next section). The "-d" parameter and its
+ 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
@@ -190,10 +190,10 @@
</PRE>
<H2>AUTHORS</H2><PRE>
- The backend is written and maintained by Andr?s Major
+ The backend is written and maintained by Andras Major
(andras@users.sourceforge.net).
-sane-backends 1.0.19 22/08/2002 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-coolscan3.5.html b/man/sane-coolscan3.5.html
new file mode 100644
index 0000000..995b108
--- /dev/null
+++ b/man/sane-coolscan3.5.html
@@ -0,0 +1,204 @@
+<HTML>
+<HEAD>
+<TITLE>sane-coolscan3.5</TITLE>
+</HEAD>
+<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
+<H1>sane-coolscan3.5</H1>
+<HR>
+<PRE>
+<!-- Manpage converted by man2html 3.0.1 -->
+<B><A HREF="sane-coolscan3.5.html">sane-coolscan3(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-coolscan3.5.html">sane-coolscan3(5)</A></B>
+
+
+</PRE>
+<H2>NAME</H2><PRE>
+ sane-coolscan3 - SANE backend for Nikon Coolscan film scanners
+
+
+</PRE>
+<H2>DESCRIPTION</H2><PRE>
+ The <B>sane-coolscan3</B> 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 <B>beta-quality</B> 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.
+
+ At present, the following scanners are known to work with this backend:
+
+ Model: Connection Type
+ --------------------------- -------------------
+ LS-30 (Coolscan III) SCSI
+ LS-40 ED (Coolscan IV) USB
+ LS-50 ED (Coolscan V) USB
+ LS-2000 SCSI
+ LS-4000 ED IEEE 1394
+ LS-8000 ED IEEE 1394
+
+ Please send mail to sane-devel@lists.alioth.debian.org to report suc-
+ cesses or failures.
+
+
+</PRE>
+<H2>OPTIONS</H2><PRE>
+ The options the backend supports can either be selected through command
+ 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 coolscan3:&lt;interface&gt;:&lt;device&gt;
+ where &lt;interface&gt; and &lt;device&gt; 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
+ options, in the syntax with which they must be supplied to scanimage:
+
+ <I>--frame</I> <I>&lt;n&gt;</I>
+ This option specifies which frame to operate on, if a motorized
+ film strip feeder or APS adapter are used. The frame number <I>&lt;n&gt;</I>
+ ranges from 1 to the number of frames available, which is sensed
+ each time the backend is initialized (usually each time you
+ start the frontend).
+
+ <I>--subframe</I> <I>&lt;x&gt;</I>
+ This option shifts the scan window by the specified amount
+ (default unit is mm).
+
+ <I>--infrared=yes/no</I>
+ 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.
+
+ <I>--depth</I> <I>&lt;n&gt;</I>
+ Here &lt;n&gt; 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
+ 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
+ cannot handle depths greater than 8 bits.
+
+ <I>--autofocus</I>
+ Perform autofocus operation. Unless otherwise specified by the
+ other options ( <I>--focus-on-centre</I> and friends), focusing is per-
+ formed on the centre of the selected scan area.
+
+ <I>--ae-wb</I>
+
+ <I>--ae</I> Perform a pre-scan to calculate exposure values automatically.
+ <I>--ae-wb</I> will maintain the white balance, while <I>--ae</I> will adjust
+ each channel separately.
+
+ <I>--exposure</I>
+ Multiply all exposure times with this value. This allows expo-
+ sure correction without modifying white balance.
+
+ <I>--load</I> Load the next slide when using the slide loader.
+
+ <I>--eject</I>
+ Eject the film strip or mounted slide when using the slide
+ loader.
+
+ <I>--reset</I>
+ 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 <I>--eject</I> does not work.
+
+
+</PRE>
+<H2>CONFIGURATION FILE</H2><PRE>
+ The configuration file /etc/sane.d/coolscan3.conf specifies the
+ device(s) that the backend will use. Owing to the nature of the sup-
+ ported connection types SCSI, USB, and IEEE 1394, the default configu-
+ ration file supplied with the SANE distribution should work without
+ being edited.
+
+ Each line in the configuration file is either of the following, where
+ all entries are case-sensitive:
+
+ <I>blank</I> <I>or</I> <I>starting</I> <I>with</I> <I>a</I> <I>'#'</I> <I>character</I>
+ These lines are ignored, thus '#' can be used to include com-
+ ments.
+
+ <I>containing</I> <I>only</I> <I>the</I> <I>word</I> <I>"auto"</I>
+ 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.
+
+ <I>a</I> <I>line</I> <I>of</I> <I>the</I> <I>form</I> <I>&lt;interface&gt;:&lt;device&gt;</I>
+ Here &lt;interface&gt; can be one of "scsi" or "usb", and &lt;device&gt; 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.
+
+
+</PRE>
+<H2>FILES</H2><PRE>
+ <I>/usr/lib/sane/libsane-coolscan3.a</I>
+ The static library implementing this backend.
+
+ <I>/usr/lib/sane/libsane-coolscan3.so</I>
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+ <I>/etc/sane.d/coolscan3.conf</I>
+ Configuration file for this backend, read each time the backend
+ is initialized.
+
+
+</PRE>
+<H2>ENVIRONMENT</H2><PRE>
+ <B>SANE_DEBUG_COOLSCAN3</B>
+ 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.
+
+
+</PRE>
+<H2>SEE ALSO</H2><PRE>
+ <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>
+
+
+</PRE>
+<H2>BUGS</H2><PRE>
+ Currently, the SANE protocol does not allow automatically updating
+ options whenever the hardware changes. Thus the number of choices for
+ the <B>--frame</B> 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
+ 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
+ later.
+
+ No real bugs currently known, please report any to the SANE developers'
+ list.
+
+
+</PRE>
+<H2>AUTHORS</H2><PRE>
+ coolscan3 written by A. Zummo (a.zummo@towertech.it), based heavily on
+ coolscan2 written by Andras Major (andras@users.sourceforge.net).
+
+ 11 Jul 2008 <B><A HREF="sane-coolscan3.5.html">sane-coolscan3(5)</A></B>
+</PRE>
+<HR>
+<ADDRESS>
+Man(1) output converted with
+<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
+</ADDRESS>
+</BODY>
+</HTML>
diff --git a/man/sane-dc210.5.html b/man/sane-dc210.5.html
index 0c6f4cf..ca246e4 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.19 15 July 2000 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-dc240.5.html b/man/sane-dc240.5.html
index caa040e..e8cdaf1 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.19 23 March 2001 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-dc25.5.html b/man/sane-dc25.5.html
index 78596d5..c0861b7 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.19 12 April 1999 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-dll.5.html b/man/sane-dll.5.html
index 0f4f883..d8d04bb 100644
--- a/man/sane-dll.5.html
+++ b/man/sane-dll.5.html
@@ -148,7 +148,7 @@
David Mosberger
-sane-backends 1.0.19 4 Dec 2002 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-dmc.5.html b/man/sane-dmc.5.html
index 6ced33c..6f6275e 100644
--- a/man/sane-dmc.5.html
+++ b/man/sane-dmc.5.html
@@ -159,7 +159,7 @@
The backend is derived from <B>sane-hp</B> by David Mosberger
-sane-backends 1.0.19 13 May 1998 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-epjitsu.5.html b/man/sane-epjitsu.5.html
index 7a48159..0cd4789 100644
--- a/man/sane-epjitsu.5.html
+++ b/man/sane-epjitsu.5.html
@@ -50,8 +50,8 @@
"Gray", "Color".
resolution, y-resolution
- Controls scan resolution. Setting --resolution also sets --y-
- resolution, though this behavior is overridden by some fron-
+ Controls scan resolution. Setting --resolution also sets
+ --y-resolution, though this behavior is overridden by some fron-
tends.
Other options will be available based on the capabilities of the scan-
@@ -119,7 +119,7 @@
</PRE>
<H2>CREDITS</H2><PRE>
- S300 support funded by Microdea, Inc.
+ S300 support funded by Microdea, Inc. and Archivista, GmbH.
fi-60F support funded by TrueCheck, Inc.
@@ -132,7 +132,7 @@
<H2>AUTHOR</H2><PRE>
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
-sane-backends 1.0.19 2007-12-17 <B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-epson.5.html b/man/sane-epson.5.html
index 7335ac9..7b31c51 100644
--- a/man/sane-epson.5.html
+++ b/man/sane-epson.5.html
@@ -206,8 +206,8 @@
<I>SCSI</I> This is the default, and if nothing else is specified the back-
end software will open a given path as SCSI device. More infor-
- mation about valid syntax for SCSI devices can be found in sane-
- <B><A HREF="scsi.5.html">scsi(5)</A></B>.
+ mation about valid syntax for SCSI devices can be found in
+ <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
Usually SCSI scanners are configured with a line "scsi EPSON" in
this file. In some cases it may be necessary to only use the
string "scsi" (e.g. for the GT-6500).
@@ -246,6 +246,11 @@
E.g., a value of 128 requests all debug output to be printed.
Smaller levels reduce verbosity.
+ <B>SANE_DEBUG_EPSON_SCSI</B>
+ If the library was compiled with debug support enabled, this
+ environment variable controls the SCSI related debug level for
+ this backend. Only a value of 2 is supported.
+
<B>SANE_EPSON_CMD_LVL</B>
This allows to override the function or command level that the
backend uses to communicate with the scanner. The function level
@@ -275,8 +280,8 @@
tions that the scanner may be capable of are accessible.
If the scanner is not even recognized as an Epson scanner this is prob-
- ably because the device name reported by the scanner is not in the cor-
- rect format. Please send this information to the backend maintainer
+ ably because the device name reported by the scanner is not in the
+ correct format. Please send this information to the backend maintainer
(email address is in the AUTHOR section of this man page or in the
AUTHORS file of the SANE distribution).
@@ -289,7 +294,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.19 27-Dec-2000 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-epson2.5.html b/man/sane-epson2.5.html
new file mode 100644
index 0000000..9c73ea8
--- /dev/null
+++ b/man/sane-epson2.5.html
@@ -0,0 +1,348 @@
+<HTML>
+<HEAD>
+<TITLE>sane-epson2.5</TITLE>
+</HEAD>
+<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
+<H1>sane-epson2.5</H1>
+<HR>
+<PRE>
+<!-- Manpage converted by man2html 3.0.1 -->
+<B><A HREF="sane-epson2.5.html">sane-epson2(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-epson2.5.html">sane-epson2(5)</A></B>
+
+
+</PRE>
+<H2>NAME</H2><PRE>
+ sane-epson2 - SANE backend for EPSON scanners
+
+
+</PRE>
+<H2>DESCRIPTION</H2><PRE>
+ The <B>sane-epson2</B> library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to Epson flatbed scanners. This library
+ supports a similar set of scanners as the sane-epson driver but was
+ developed to support a wider range of connections to the scanner;
+ include network access.
+
+ Because <B>sane-epson</B> and <B>sane-epson2</B> drivers support many of the same
+ devices, if one driver gives you problems you may try disabling it to
+ try the other. This can be done by removing the driver name from the
+ <I>dll.conf</I> or perhaps by commenting out the options in <I>epson.conf</I> or
+ <I>epson2.conf.</I>
+
+ At present, the following scanners are known to work with this backend:
+
+ Model: Connection Type
+ --------------------------- -------------------
+ ActionScanner II SCSI, parallel
+ AcuLaser CX11 Series USB, Network
+ AcuLaser CX21 Series USB, Network
+ CX-3200 USB
+ CX-3600 USB
+ CX-3650 USB
+ CX-4050 USB
+ CX-4600 USB
+ CX-4800 USB
+ CX-5000 USB
+ CX-5200 USB
+ CX-5400 USB
+ CX-6300 USB
+ CX-6400 USB
+ CX-6500 USB
+ CX-6600 USB
+ DX-3800 USB
+ DX-5000 USB
+ DX-5050 USB
+ DX-6000 USB
+ DX-7400 USB
+ ES-300C SCSI, parallel
+ ES-300GS SCSI
+ ES-600C parallel
+ ES-1200C parallel
+ Expression 636 SCSI
+ Expression 800 SCSI
+ Expression 1600 USB, SCSI, IEEE-1394
+ Expression 1680 USB, SCSI, IEEE-1394
+ FilmScan 200 SCSI
+ GT-5000 SCSI, parallel
+ GT-5500 SCSI
+ GT-6000 parallel
+ GT-6500 parallel
+ GT-7000 SCSI
+ GT-8000 SCSI
+ GT-8500 SCSI
+ Perfection 610 USB
+ Perfection 636S SCSI
+ Perfection 636U USB
+ Perfection 640 USB
+ Perfection 1200S SCSI
+ Perfection 1200U USB
+ Perfection 1240 USB, SCSI
+ Perfection 1640 USB, SCSI
+ Perfection 1650 USB
+ Perfection 1660 USB
+ Perfection 2400 USB
+ Perfection 2450 USB, IEEE-1394
+ Perfection 3200 USB
+ Perfection 4870 USB
+ Perfection 4990 USB
+ RX-425 USB
+ RX-500 USB
+ RX-600 USB
+ RX-700 USB
+ V700 USB, IEEE-1394
+ V750 USB, IEEE-1394
+ and many more. The official list is on the Sane web site.
+
+ For other scanners the software may or may not work. Please send mail
+ to the sane-backend mailing list to report success with scanners not on
+ the list or problems with scanners that are listed.
+
+
+</PRE>
+<H2>OPTIONS</H2><PRE>
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in pro-
+ grams like xscanimage or xsane.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d epson2
+ Not all devices support all options.
+
+ <I>Scan</I> <I>Mode</I>
+ The <I>--mode</I> switch selects the basic mode of operation of the
+ scanner. Valid choices are Binary, Gray and Color. The Binary
+ mode is black and white only, Gray will produce 256 levels of
+ gray or more depending on the scanner and Color means 24 bit
+ color mode or more depending on the scanner. Some scanners will
+ internally use 36 bit color, their external interface however
+ may only support 24 bits.
+
+ The <I>--depth</I> option selects the bit depth the scanner is using.
+ This option is only available for scanners that support more
+ than one bit depth. Older scanners will always transfer the
+ image in 8bit mode. Newer scanners allow to select either 8
+ bits, 12 or 14 bits per color channel. For a color scan this
+ means an effective color depth of 36 or 42 bits over all three
+ channels. The valid choices depend on the scanner model.
+
+ The <I>--halftoning</I> switch selects the mode that is used in Binary
+ mode. Valid options are "None", "Halftone A (Hard Tone)",
+ "Halftone B (Soft Tone)", "Halftone C (Net Screen)", "Dither A
+ (4x4 Bayer)", "Dither B (4x4 Spiral)", "Dither C (4x4 Net
+ Screen)", "Dither D (8x4 Net Screen)", "Text Enhanced Technol-
+ ogy", "Download pattern A", and "Download pattern B".
+
+ The <I>--dropout</I> switch selects the so called dropout color. Vald
+ options are None, Red, Green and Blue. The default is None. The
+ dropout color is used for monochrome scanning and selects the
+ color that is not scanned. This can be used to e.g. scan an
+ original with a colored background.
+
+ The <I>--brightness</I> switch controls the brightness of the scan.
+ Valid options are integer values from -3 to 3. The default is 0.
+ The larger the brightness value, the brighter the image gets. If
+ a user defined table for the gamma correction is selected, the
+ brightness parameter is not available.
+
+ The <I>--sharpness</I> 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
+ slightly" and 2 "Sharpen".
+
+ The <I>--gamma-correction</I> switch controls the scanner's internal
+ gamma correction. Valid options are "Default", "User defined",
+ "High density printing" "Low density printing" and "High con-
+ trast printing".
+
+ The <I>--color-correction</I> switch controls the scanner's internal
+ color correction function. Valid options are "No Correction",
+ "Impact-dot printers", "Thermal printers", "Ink-jet printers"
+ and "CRT monitors". The default is "CRT monitors".
+
+ The <I>--resolution</I> switch selects the resolution for a scan. Some
+ EPSON scanners will scan in 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 scanim-
+ age.
+
+ The <I>--threshold</I> switch selects the minimum brightness to get a
+ white point.
+
+ The <I>--mirror</I> option controls the way the image is scanned. By
+ reading the image data from right to left the image is mirrored.
+ Valid options are "yes" and "no". The default is "no".
+
+ The <I>--auto-area-segmentation</I> 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 improved.
+ Valid options are "yes" and "no". The default is "yes".
+
+ The <I>--red-gamma-table</I> parameter can be used to download a user
+ defined gamma table for the red channel. The valid options are
+ the same as for --gamma-table.
+
+ The <I>--green-gamma-table</I> parameter can be used to download a user
+ defined gamma table for the green channel. The valid options are
+ the same as for --gamma-table.
+
+ The <I>--blue-gamma-table</I> parameter can be used to download a user
+ defined gamma table for the blue channel. The valid options are
+ the same as for --gamma-table.
+
+ The <I>--wait-for-button</I> parameter can be used to wait until the
+ button on the scanner is pressed to actually start the scan pro-
+ cess.
+
+ The color correction coefficients <I>--cct-1</I> <I>--cct-2</I> <I>--cct-3</I> <I>...</I>
+ <I>--cct-9</I> will install color correction coefficients for the user
+ defined color correction. Values are specified as integers in
+ the range -127..127.
+
+ The <I>--preview</I> option requests a preview scan. The frontend soft-
+ ware automatically selects a low resolution. Valid options are
+ "yes" and "no". The default is "no".
+
+ The geometry options <I>-l</I> <I>-t</I> <I>-x</I> <I>-y</I> 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 param-
+ eters are specified in millimeters.
+
+ The <I>--source</I> option selects the scan source. Valid options
+ depend on the installed options. The default is "Flatbed".
+
+ The <I>--auto-eject</I> option will eject a page after scanning from
+ the document feeder.
+
+ The <I>--film-type</I> option will select the film type for scans with
+ the transparency unit. This option is only activated if the TPU
+ is selected as scan source. Valid options are "Negative Film"
+ and "Positive Film".
+
+ The <I>--focus-position</I> option selects the focus position for all
+ scans. Valid options are "Focus 2.5mm above glass" and "Focus on
+ glass". The focus on the 2.5mm point above the glass is neces-
+ sary for scans with the transparency unit, so that the scanner
+ can focus on the film if one of the film holders is used. This
+ option is only functional for selected scanners, all other scan-
+ ners will ignore this option.
+
+ The <I>--bay</I> option selects which bay to scan
+
+ The <I>--eject</I> option ejects the sheet in the ADF.
+
+ The <I>--adf-mode</I> option selecst the ADF mode (simplex/duplex).
+
+
+</PRE>
+<H2>CONFIGURATION FILE</H2><PRE>
+ The configuration file /etc/sane.d/epson2.conf specifies the device(s)
+ that the backend will use. Possible connection types are:
+
+ <I>SCSI</I> This is the default, and if nothing else is specified the back-
+ end software will open a given path as SCSI device. More infor-
+ mation about valid syntax for SCSI devices can be found in
+ <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
+ Usually SCSI scanners are configured with a line "scsi EPSON" in
+ this file. In some cases it may be necessary to only use the
+ string "scsi" (e.g. for the GT-6500).
+
+ <I>PIO</I> <I>-</I> <I>Parallel</I> <I>Interface</I>
+ 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").
+
+ <I>USB</I> For USB scanners not automatically detect, their VENDOR and
+ PRODUCT ID can be specified manually in the config file. More
+ information about valid syntax for USB devices can be found in
+ <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
+
+ <I>Network</I>
+ Network scanners can be auto-discovered if <I>autodiscovery</I> is
+ specified after <I>net</I> keyword. An IP address to connect to can
+ also be used.
+
+
+</PRE>
+<H2>FILES</H2><PRE>
+ <I>/usr/lib/sane/libsane-epson2.a</I>
+ The static library implementing this backend.
+
+ <I>/usr/lib/sane/libsane-epson2.so</I>
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+</PRE>
+<H2>ENVIRONMENT</H2><PRE>
+ <B>SANE_DEBUG_EPSON2</B>
+ 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.
+
+ <B>SANE_DEBUG_EPSON2_SCSI</B>
+ If the library was compiled with debug support enabled, this
+ environment variable controls the SCSI related debug level for
+ this backend. Only a value of 2 is supported.
+
+ <B>SANE_DEBUG_EPSON2_NET</B>
+ If the library was compiled with debug support enabled, this
+ environment variable controls the network related debug level
+ for this backend. E.g., a value of 128 requests all debug out-
+ put to be printed. Smaller levels reduce verbosity.
+
+ <B>SANE_EPSON2_CMD_LVL</B>
+ This allows to override the function or command level that the
+ backend uses to communicate with the scanner. The function level
+ a scanner supports is determined during the initialization of
+ the device. If the backend does not recognize the function level
+ reported by the scanner it will default to function level B3.
+ Valid function levels are A1, A2, B1, B2, B3, B4, B5, B6, B7,
+ B8, D1 and F5. Use this feature only if you know what you are
+ doing!
+
+
+</PRE>
+<H2>SEE ALSO</H2><PRE>
+ <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>
+
+
+</PRE>
+<H2>BUGS</H2><PRE>
+ None :-) At least none are currently known.
+
+
+</PRE>
+<H2>UNSUPPORTED DEVICES</H2><PRE>
+ The backend may be used with Epson scanners that are not yet listed
+ under the list of supported devices. A scanner that is not recognized
+ may default to the function level B3, which means that not all func-
+ tions that the scanner may be capable of are accessible.
+
+ If the scanner is not even recognized as an Epson scanner this is prob-
+ ably because the device name reported by the scanner is not in the cor-
+ rect format. Please send this information to the backend maintainer
+ (email address is in the AUTHOR section of this man page or in the
+ AUTHORS file of the SANE distribution).
+
+
+</PRE>
+<H2>AUTHOR</H2><PRE>
+ The package is written by Alessandro Zummo and is based on previous
+ work done by Karl Hienz Kremer in the epson package as well as based on
+ work by Christian Bucher and Kazuhiro Sasayama
+
+ 22 Jan 2009 <B><A HREF="sane-epson2.5.html">sane-epson2(5)</A></B>
+</PRE>
+<HR>
+<ADDRESS>
+Man(1) output converted with
+<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
+</ADDRESS>
+</BODY>
+</HTML>
diff --git a/man/sane-find-scanner.1.html b/man/sane-find-scanner.1.html
index 921dc0b..d4b2347 100644
--- a/man/sane-find-scanner.1.html
+++ b/man/sane-find-scanner.1.html
@@ -29,23 +29,23 @@
For <B>SCSI</B> scanners, it checks the default generic SCSI device files
(e.g., <I>/dev/sg0</I>) and <I>/dev/scanner</I>. The test is done by sending a SCSI
inquiry command and looking for a device type of "scanner" or "proces-
- sor" (some old HP scanners seem to send "processor"). So <B>sane-find-</B>
- <B>scanner</B> will find any SCSI scanner connected to those default device
- files even if it isn't supported by any SANE backend.
+ sor" (some old HP scanners seem to send "processor"). So
+ <B>sane-find-scanner</B> will find any SCSI scanner connected to those default
+ device files even if it isn't supported by any SANE backend.
For <B>USB</B> scanners, first the USB kernel scanner device files (e.g.
<I>/dev/usb/scanner0</I>), <I>/dev/usb/scanner</I>, and <I>/dev/usbscanner</I>) are tested.
The files are opened and the vendor and device ids are determined, if
the operating system supports this feature. Currently USB scanners are
only found this way if they are supported by the Linux scanner module
- or the FreeBSD or OpenBSD uscanner driver. After that test, <B>sane-find-</B>
- <B>scanner</B> tries to scan for USB devices found by the USB library libusb
- (if available). There is no special USB class for scanners, so the
- heuristics used to distinguish scanners from other USB devices is not
- perfect. <B>sane-find-scanner</B> also tries to find out the type of USB chip
- used in the scanner. If detected, it will be printed after the vendor
- and product ids. <B>sane-find-scanner</B> will even find USB scanners, that
- are not supported by any SANE backend.
+ or the FreeBSD or OpenBSD uscanner driver. After that test,
+ <B>sane-find-scanner</B> tries to scan for USB devices found by the USB
+ library libusb (if available). There is no special USB class for scan-
+ ners, so the heuristics used to distinguish scanners from other USB
+ devices is not perfect. <B>sane-find-scanner</B> also tries to find out the
+ type of USB chip used in the scanner. If detected, it will be printed
+ after the vendor and product ids. <B>sane-find-scanner</B> will even find USB
+ scanners, that are not supported by any SANE backend.
<B>sane-find-scanner</B> won't find most parallel port scanners, or scanners
connected to proprietary ports. Some <B>parallel</B> <B>port</B> scanners may be
@@ -120,7 +120,7 @@
No support for most parallel port scanners yet.
Detection of USB chipsets is limited to a few chipsets.
-sane-backends 1.0.19 4 Oct 2004 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-fujitsu.5.html b/man/sane-fujitsu.5.html
index a1593ab..6a81176 100644
--- a/man/sane-fujitsu.5.html
+++ b/man/sane-fujitsu.5.html
@@ -20,159 +20,126 @@
The <B>sane-fujitsu</B> library implements a SANE (Scanner Access Now Easy)
backend which provides access to most Fujitsu flatbed and ADF scanners.
- This document describes the rewritten backend versions 1.0.21 and
- greater.
-
- The backend supports lineart, halftone, grayscale, and color scanning
- for most USB and SCSI scanners, depending on hardware capabilities.
- Most simple scanning related features are exposed. This version fea-
- tures at least basic support for many more models. See KNOWN ISSUES.
+ This document describes backend version 93, which shipped with SANE
+ 1.0.20.
</PRE>
-<H2>HARDWARE SUPPORT</H2><PRE>
- The following scanners are thought to have at least basic scanning
- capability, either because they have been tested with a prior version,
- or because documentation indicates they are compatible with a tested
- model.
+<H2>SUPPORTED HARDWARE</H2><PRE>
+ This version supports every known model which speaks the Fujitsu SCSI
+ and SCSI-over-USB protocols. Specifically, the SCSI M309x and M409x
+ series, the SCSI fi-series, most of the USB fi-series, and the USB
+ ScanSnap S5xx scanners are supported. Please see the list at
+ http://www.sane-project.org/sane-supported-devices.html for details.
- WORKGROUP SIZED SCANNERS:
- --------------------------------------
- SCSI: SCSI/USB: USB:
- ------------ ------------ ------------
- M3091DC fi-4120C fi-5110C
- M3092DC fi-4220C fi-5110EOX
- SP-93GX fi-4120C2 fi-5110EOX2
- fi-4220C2 fi-5110EOXM
- fi-5120C S500
- fi-5220C S500M
-
- DEPARTMENTAL SIZED SCANNERS:
- --------------------------------------
- SCSI: SCSI/USB:
- ------------ ------------
- M3093GX/DG fi-4340C
- M3096G/GX fi-4530C
- M3097G+/DG fi-5530C
- fi-4640S
- fi-4750C
-
- PRODUCTION SIZED SCANNERS:
- --------------------------------------
- SCSI: SCSI/USB:
- ------------ ------------
- M3099G/GH/GX fi-5650C
- M4097D fi-5750C
- fi-4750L fi-5900C
- fi-4860C
- M4099D
-
- The following scanners are known NOT to work with this backend, either
- because they have a non-fujitsu chipset, or an unsupported interface
+ This backend may support other Fujitsu scanners. The best way to deter-
+ mine 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.
+
+
+</PRE>
+<H2>UNSUPPORTED HARDWARE</H2><PRE>
+ The following scanners are known NOT to work with this backend, either
+ because they have a non-fujitsu chipset, or an unsupported interface
type. Some of these scanners may be supported by another backend.
- UNSUPPORTED SCANNERS:
--------------------------------------
SCSI: SERIAL: USB:
------------ ------------ ------------
- ScanStation M3093E/DE/EX fi-4110EOX2
+ ScanStation M3093E/DE/EX fi-4110EOX/2
ScanPartner M3096EX fi-4010CU
- SP-Jr M3097E+/DE
- SP-10/10C M3099A/EH/EX
- SP-15C/300C
+ SP-Jr M3097E+/DE S300/S300M
+ SP-10/10C M3099A/EH/EX fi-60F
+ SP-15C/300C fi-5015C
SP-600C/620C
- This backend may support scanners not listed here. The best way to
- determine level of support is to test the scanner directly. Fujitsu
- equipment has historically been good enough to not be damaged by incor-
- rect commands if the scanner is incompatible. Please contact the
- author with test results, positive or negative.
-
</PRE>
<H2>OPTIONS</H2><PRE>
- A modest effort has been made to expose the standard options to the
- API. This allows a frontend to set scanning region, resolution, bit-
- depth, color mode, and enable the automatic document feeder. The
- fujitsu backend supports the following basic options for most scanners:
+ Effort has been made to expose all hardware options, including:
source s
- Selects the source for the scan. Options may include "Flatbed",
+ Selects the source for the scan. Options may include "Flatbed",
"ADF Front", "ADF Back", "ADF Duplex".
mode m
- Selects the mode for the scan. Options may include "Lineart",
+ Selects the mode for the scan. Options may include "Lineart",
"Halftone", "Gray", and "Color".
resolution, y-resolution
- Controls scan resolution. Setting --resolution also sets --y-
- resolution, though this behavior is overridden by some fron-
+ Controls scan resolution. Setting --resolution also sets
+ --y-resolution, though this behavior is overridden by some fron-
tends.
tl-x, tl-y, br-x, br-y
Sets scan area upper left and lower right coordinates. These are
renamed t, l, x, y by some frontends.
- pagewidth, pageheight
- Sets paper size. Used by scanner to determine centering of scan
+ page-width, page-height
+ Sets paper size. Used by scanner to determine centering of scan
coordinates when using ADF and to detect double feed errors.
- Other options will be available based on the capabilities of the scan-
- ner. Use 'scanimage --help' to get a list. Be aware that some options
- may appear only when another option has been set, and that advanced
- options may be hidden by the frontend.
+ Other options will be available based on the capabilities of the scan-
+ ner: machines with IPC or DTC will have additional enhancement options,
+ those with CMP will have compression options, those with a printer will
+ have a group of endorser 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.
</PRE>
<H2>CONFIGURATION FILE</H2><PRE>
- The configuration file "fujitsu.conf" is used to tell the backend how
- to look for scanners, and provide options controlling the operation of
+ The configuration file "fujitsu.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 of scanners, generally only when the frontend starts. If the
- configuration file is missing, the backend will use a set of compiled
+ configuration file is missing, the backend will use a set of compiled
defaults, which are identical to the default configuration file shipped
with SANE.
Scanners can be specified in the configuration file in 4 ways:
"scsi FUJITSU"
- Requests backend to search all scsi busses in the system for a
+ Requests backend to search all scsi busses in the system for a
device which reports itself to be a scanner made by 'FUJITSU'.
"scsi /dev/sg0" (or other scsi device file)
- Requests backend to open the named scsi device. Only useful if
- you have multiple compatible scanners connected to your system,
- and need to specify one. Probably should not be used with the
+ Requests backend to open the named scsi device. Only useful if
+ you have multiple compatible scanners connected to your system,
+ and need to specify one. Probably should not be used with the
other "scsi" line above.
"usb 0x04c5 0x1042" (or other vendor/product ids)
- Requests backend to search all usb busses in the system for a
- device which uses that vendor and product id. The device will
+ Requests backend to search all usb busses in the system for a
+ device which uses that vendor and product id. The device will
then be queried to determine if it is a Fujitsu scanner.
"usb /dev/usb/scanner0" (or other device file)
- Some systems use a kernel driver to access usb scanners. This
+ Some systems use a kernel driver to access usb scanners. This
method is untested.
- The only configuration option supported is "buffer-size=xxx", allowing
- you to set the number of bytes in the data buffer to something other
+ 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 compiled-in default, 65536 (64K). Some users report that their
- scanner will "hang" mid-page, or fail to transmit the image if the
+ scanner will "hang" mid-page, or fail to transmit the image if the
buffer is not large enough.
- Note: This option may appear multiple times in the configuration file.
- It only applies to scanners discovered by 'scsi/usb' lines that follow
+ Note: This option may appear multiple times in the configuration file.
+ It only applies to scanners discovered by 'scsi/usb' lines that follow
this option.
- Note: The backend does not place an upper bound on this value, as some
- users required it to be quite large. Values above the default are not
+ Note: The backend does not place an upper bound on this value, as some
+ users required it to be quite large. Values above the default are not
recommended, and may crash your OS or lockup your scsi card driver. You
have been warned.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
- The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
+ The backend uses a single environment variable, SANE_DEBUG_FUJITSU,
which enables debugging output to stderr. Valid values are:
5 Errors
@@ -185,34 +152,24 @@
</PRE>
-<H2>OLDER VERSIONS</H2><PRE>
- Backend versions prior to this were numbered with a two part version,
- or with no version number at all. At the time this version was written,
- all older versions were retroactively renumbered, 1.0.2 - 1.0.20.
-
- The current backend may have lost support for some feature you were
- using. The last of the "old" backends, 1.0.20, is still available as
- source from:
+<H2>KNOWN ISSUES</H2><PRE>
+ Flatbed units may fail to scan at maximum area, particularly at high
+ resolution.
- http://www.thebility.com/fujitsu/
+ Any model that does not support VPD during inquiry will not function
+ until an override is added to the backend.
- If you find that you need to use the older version, please contact the
- author, to try and get those features restored to a later version.
+ CCITT Fax compression used by older scanners is not supported.
+ Automatic paper size detection (aka auto-cropping) is not supported.
-</PRE>
-<H2>KNOWN ISSUES</H2><PRE>
- All IPC, imprinter options are disabled.
- Most scanner specific 'quirks' are not accounted for, making it
- possible to set some options in ways that the scanner does not
- support.
- Some flatbed options are affected by adf settings.
- Any model that does not support VPD during inquiry will not
- function.
+ JPEG output is supported by the backend, but not by the SANE protocol,
+ so is disabled in this release. It can be enabled if you rebuild from
+ source.
</PRE>
-<H2>HISTORY</H2><PRE>
+<H2>CREDITS</H2><PRE>
m3091 backend: Frederik Ramm &lt;frederik a t remote d o t org&gt;
m3096g backend: Randolph Bentson &lt;bentson a t holmsjoen d o t com&gt;
(with credit to the unnamed author of the coolscan driver)
@@ -220,20 +177,36 @@
Oliver Schirrmeister &lt;oschirr a t abm d o t de&gt;
m3092: Mario Goppold &lt;mgoppold a t tbzpariv d o t tcc-chemnitz dot de&gt;
fi-4220C and basic USB support: Ron Cemer &lt;ron a t roncemer d o t com&gt;
- fi-4120, fi-series color support, backend re-write, current maintainer:
+ fi-4120, fi-series color, backend re-write, jpeg, current maintainer:
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
+ JPEG output support funded by:
+ Archivista GmbH
+ www.archivista.ch
+
+ Endorser support funded by:
+ O A S Oilfield Accounting Service Ltd
+ 1500, 840 - 7th Avenue S.W.
+ Calgary, Alberta
+ T2P 3G2 Canada
+ 1-403-263-2600
+ www.oas.ca
+
+ Hardware donated by Fujitsu Computer Products of America, Inc.
+ http://us.fujitsu.com/fcpa
+
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>,
+ <B><A HREF="sane-epjitsu.5.html">sane-epjitsu(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
m. allan noah: &lt;kitno455 a t gmail d o t com&gt;
-sane-backends 1.0.19 2007-07-14 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
+ 20 Apr 2009 <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-genesys.5.html b/man/sane-genesys.5.html
index 2cbb990..c960567 100644
--- a/man/sane-genesys.5.html
+++ b/man/sane-genesys.5.html
@@ -26,6 +26,7 @@
Medion MD6228
Medion MD6274
Hewlett-Packard HP2300C
+ Visioneer Strobe XP200
Canon LiDE 35/40/50/60
This is stable software for supported models. But if you test new or
@@ -35,7 +36,7 @@
If you own a scanner other than the ones listed above that works with
this backend, please let me know this by sending the scanner's exact
model name and the USB vendor and device ids (e.g. from
- <I>/proc/bus/usb/devices</I> <I>,</I> <I>sane-find-scanner</I> or syslog) to the sane-devel
+ <I>/proc/bus/usb/devices</I>, <I>sane-find-scanner</I> or syslog) to the sane-devel
mailing list. Even if the scanner's name is only slightly different
from the models mentioned above, please let me know.
@@ -115,6 +116,12 @@
</PRE>
+<H2>CREDITS</H2><PRE>
+ Jack McGill for donating several sheetfed scanners, which made possible
+ to add support for them in the genesys backend.
+
+
+</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
@@ -124,22 +131,23 @@
Oliver Rauch
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
Gerhard Jaeger &lt;gerhard@gjaeger.de&gt;
- St?phane Voltz &lt;stef.dev@free.fr&gt;
+ Stephane Voltz &lt;stef.dev@free.fr&gt;
Philipp Schmid &lt;philipp8288@web.de&gt;
Pierre Willenbrock &lt;pierre@pirsoft.dnsalias.org&gt;
</PRE>
<H2>LIMITATIONS</H2><PRE>
- Support for buttons is missing.
Powersaving isn't implemented for gl646 based scanner.
+ Calibration for sheetfed scanners isn't implemented yet.
</PRE>
<H2>BUGS</H2><PRE>
Currently no known bug.
-sane-backends 1.0.19 20 Nov 2005 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
+
+ 13 Jul 2008 <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-gphoto2.5.html b/man/sane-gphoto2.5.html
index 7505082..4dcfd55 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.19 04 September 2001 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-gt68xx.5.html b/man/sane-gt68xx.5.html
index 80242be..64d0ab8 100644
--- a/man/sane-gt68xx.5.html
+++ b/man/sane-gt68xx.5.html
@@ -20,8 +20,8 @@
The <B>sane-gt68xx</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to USB flatbed scanners based on the
Grandtech GT-6801 and GT-6816 chips. A list of supported scanners can
- be found on the gt68xx backend homepage: <I>http://www.meier-</I>
- <I>geinitz.de/sane/gt68xx-backend/</I>.
+ be found on the gt68xx backend homepage:
+ <I>http://www.meier-geinitz.de/sane/gt68xx-backend/</I>.
This is BETA software. Especially if you test new or untested scanners,
keep your hand at the scanner's plug and unplug it, if the head bumps
@@ -36,8 +36,8 @@
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: <I>http://www.meier-</I>
- <I>geinitz.de/sane/gt68xx-backend/adding.html</I>
+ Have a look at the following web page:
+ <I>http://www.meier-geinitz.de/sane/gt68xx-backend/adding.html</I>
</PRE>
@@ -160,9 +160,9 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B>sane-</B>
- <B><A HREF="ma1509.5.html">ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
- <I>/usr/doc/sane-1.0.19/gt68xx/gt68xx.CHANGES</I>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B> <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
+ <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
+ <I>/usr/doc/sane-1.0.20/gt68xx/gt68xx.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/gt68xx</I>
@@ -185,11 +185,11 @@
More detailed bug information is available at the gt68xx backend home-
page <I>http://www.meier-geinitz.de/sane/gt68xx-backend/</I>. Please contact
- us if you find a bug or missing feature: &lt;sane-
- devel@lists.alioth.debian.org&gt;. Please send a debug log if your scanner
- isn't detected correctly (see SANE_DEBUG_GT68XX above).
+ us if you find a bug or missing feature:
+ &lt;sane-devel@lists.alioth.debian.org&gt;. Please send a debug log if your
+ scanner isn't detected correctly (see SANE_DEBUG_GT68XX above).
-sane-backends 1.0.19 29 September 2005 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hp.5.html b/man/sane-hp.5.html
index bd7b8f9..0415bac 100644
--- a/man/sane-hp.5.html
+++ b/man/sane-hp.5.html
@@ -60,8 +60,8 @@
SCL (beside the OfficeJets), the above list of supported scanners is
complete. Other HP scanners are not supported by the "hp" backend, but
might be supported by another one. See <I>http://www.sane-project.org/</I>.
- You can also watch the sane-devel mailing list at <I>http://www.sane-</I>
- <I>project.org/mailing-lists.html</I>.
+ You can also watch the sane-devel mailing list at
+ <I>http://www.sane-project.org/mailing-lists.html</I>.
More details about the hp backend can be found on its homepage
<I>http://www.kirchgessner.net/sane.html</I>.
@@ -81,48 +81,48 @@
that the scanner is connected by USB. For the HP ScanJet Plus the spe-
cial device name must be the device that corresponds to the parallel
interface card that was shipped with the scanner. That is <I>/dev/hpscan</I>.
- A special driver is required for this card. See ftp://rvs.ctrl-
- c.liu.se/pub/wingel/hpscan for details. If the link does not work, try
- ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.
+ A special driver is required for this card. See
+ ftp://rvs.ctrl-c.liu.se/pub/wingel/hpscan for details. If the link does
+ not work, try ftp://sunsite.unc.edu/pub/Linux/kernel/patches/scanners.
</PRE>
<H2>CONFIGURATION</H2><PRE>
- The contents of the <I>hp.conf</I> file is a list of options and device names
+ The contents of the <I>hp.conf</I> file is a list of options and device names
that correspond to HP ScanJet scanners. Empty lines and lines starting
- with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> and <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> on
+ with a hash mark (#) are ignored. See <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> and <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> on
details of what constitutes a valid device name.
- Options specified in front of the first line that contains a device
- name are defaults for all devices. Options specified below a line that
- contains a device name apply just to the most recently mentioned
+ Options specified in front of the first line that contains a device
+ name are defaults for all devices. Options specified below a line that
+ contains a device name apply just to the most recently mentioned
device.
- Supported options are <B>connect-scsi</B>, <B>connect-device</B>, <B>enable-image-</B>
- <B>buffering</B>, and <B>dumb-read</B>.
+ Supported options are <B>connect-scsi</B>, <B>connect-device</B>,
+ <B>enable-image-buffering</B>, and <B>dumb-read</B>.
Option <B>connect-scsi</B> specifies that the scanner is connected to the sys-
- tem by SCSI. Input/output is performed using SCSI-commands. This is
- the default. But if your SCSI device name contains "usb", "uscanner"
- or "ugen", option connect-scsi must be specified. Otherwise it is
+ tem by SCSI. Input/output is performed using SCSI-commands. This is
+ the default. But if your SCSI device name contains "usb", "uscanner"
+ or "ugen", option connect-scsi must be specified. Otherwise it is
assumed that the scanner is connected by USB.
- Option <B>connect-device</B> specifies that the scanner is connected to the
- system by a special device. Input/output is performed by
- read()/write()-operations on the device. This option must be used for
+ Option <B>connect-device</B> specifies that the scanner is connected to the
+ system by a special device. Input/output is performed by
+ read()/write()-operations on the device. This option must be used for
HP ScanJet Plus or scanners connected to USB which are accessed through
a named device (e.g. /dev/usb/scanner0). For device names that contain
"usb", "uscanner" or "ugen", it is not necessary to specify option con-
nect-device.
Option <B>enable-image-buffering</B> stores the scanned image in memory before
- passing it to the frontend. Could be used in case of forward/backward
+ passing it to the frontend. Could be used in case of forward/backward
moving scanner lamp.
Option <B>dumb-read</B> can be used to work around problems with "Error during
device I/O". These problems may occur with certain SCSI-to-USB convert-
- ers or Buslogic SCSI cards. The option should not be used for SCSI
- devices which are working correctly. Otherwise startup of frontends
+ ers 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.
A sample configuration file is shown below:
@@ -132,13 +132,13 @@
/dev/hpscan
option connect-device
- /dev/scanner is typically a symlink to the actual SCSI scanner device.
+ /dev/scanner is typically a symlink to the actual SCSI scanner device.
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d/hp.conf</I>
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/lib/sane/libsane-hp.a</I>
@@ -149,10 +149,10 @@
that support dynamic loading).
<I>$HOME/.sane/calib-hp:&lt;device&gt;.dat</I>
- Calibration data for HP PhotoSmart PhotoScanner that is
- retrieved from the scanner after calibration. The data is
- uploaded to the scanner at start of the backend if it is in
- media mode 'print media' or if the media mode is changed to
+ Calibration data for HP PhotoSmart PhotoScanner that is
+ retrieved from the scanner after calibration. The data is
+ uploaded to the scanner at start of the backend if it is in
+ media mode 'print media' or if the media mode is changed to
'print media'.
@@ -161,25 +161,25 @@
<B>SANE_CONFIG_DIR</B>
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
+ uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
- value of the environment variable ends with the directory sepa-
+ value of the environment variable ends with the directory sepa-
rator character, then the default directories are searched after
- the explicitly specified directories. For example, setting
- <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
- "tmp/config", ".", and "/etc/sane.d" being searched (in this
+ the explicitly specified directories. For example, setting
+ <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
+ "tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
<B>SANE_DEBUG_HP</B>
- 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.
<B>SANE_HOME_HP</B>
- Only used for OS/2 and along with use of HP PhotoSmart Photo-
+ Only used for OS/2 and along with use of HP PhotoSmart Photo-
Scanner. Must be set to the directory where the directory .sane
is located. Is used to save and read the calibration file.
@@ -188,42 +188,42 @@
<B>SANE_HP_KEEPOPEN_USB</B>
<B>SANE_HP_KEEPOPEN_DEVICE</B>
- For each type of connection (connect-scsi, connect-usb, connect-
- device) it can be specified if the connection to the device
+ For each type of connection (connect-scsi, connect-usb, con-
+ nect-device) it can be specified if the connection to the device
should be kept open ("1") or not ("0"). Usually the connections
- are closed after an operation is performed. Keeping connection
- open to SCSI-devices can result in errors during device IO when
- the scanner has not been used for some time. By default, USB-
+ are closed after an operation is performed. Keeping connection
+ open to SCSI-devices can result in errors during device IO when
+ the scanner has not been used for some time. By default, USB-
connections are kept open. Other connections are closed.
<B>SANE_HP_RDREDO</B>
- Specifies number of retries for read operation before returning
- an EOF error. Only supported for non-SCSI devices. Default: 1
+ Specifies number of retries for read operation before returning
+ an EOF error. Only supported for non-SCSI devices. Default: 1
retry. Time between retries is 0.1 seconds.
</PRE>
<H2>BUGS</H2><PRE>
<B>HP</B> <B>PhotoSmart</B> <B>PhotoScanner</B>
- In media mode 'slide' and 'negative', scan resolutions are
- rounded to multiple of 300 dpi. The scanner does not scale the
+ In media mode 'slide' and 'negative', scan resolutions are
+ rounded to multiple of 300 dpi. The scanner does not scale the
data correctly on other resolutions. Some newer models (firmware
- code R030 and later) do not support adjustment of con-
- trast/intensity level and tone map. The backend will simulate
+ code R030 and later) do not support adjustment of con-
+ trast/intensity level and tone map. The backend will simulate
this by software, but only for gray and 24 bit color.
<B>Automatic</B> <B>Document</B> <B>Feeder</B> <B>(ADF)</B>
- For use of the ADF with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, first place paper in the
- ADF and then change option scan source to 'ADF'. Press 'change
- document' to load a sheet. Then press 'scan' to start a scan.
+ For use of the ADF with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, first place paper in the
+ ADF and then change option scan source to 'ADF'. Press 'change
+ document' to load a sheet. Then press 'scan' to start a scan.
Maybe it is sufficient to press 'scan' without 'change document'
- for repeated scans. The use of the preview window is not
+ for repeated scans. The use of the preview window is not
recommended when working with the ADF. Setting a window to scan
from ADF is not supported with <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>. Try <B><A HREF="xsane.1.html">xsane(1)</A></B>.
<B>Immediate</B> <B>actions</B>
- Some actions in <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> (i.e. unload, select media, cali-
- brate) have an immediate effect on the scanner without starting
+ Some actions in <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B> (i.e. unload, select media, cali-
+ brate) have an immediate effect on the scanner without starting
a scan. These options can not be used with scanimage.
@@ -231,17 +231,17 @@
<H2>TODO</H2><PRE>
<B>HP</B> <B>PhotoSmart</B> <B>PhotoScanner</B>
PhotoScanners with firmware release R030 and up have no firmware
- support for contrast/brightness/gamma table. In the current
- backend this is simulated by software on 24 bits data. Simula-
+ support for contrast/brightness/gamma table. In the current
+ backend this is simulated by software on 24 bits data. Simula-
tion on 30 bits should give better results.
<B>Data</B> <B>widths</B> <B>greater</B> <B>than</B> <B>8</B> <B>bits</B>
Custom gamma table does not work.
<B>Parallel</B> <B>scanner</B> <B>support</B>
- Beside the ScanJet Plus which came with its own parallel inter-
- face card, currently only the HP ScanJet 5100C/5200C are sup-
- ported. These scanners are using an internal parallel-to-SCSI
+ Beside the ScanJet Plus which came with its own parallel inter-
+ face card, currently only the HP ScanJet 5100C/5200C are sup-
+ ported. These scanners are using an internal parallel-to-SCSI
converter which is supported by the ppSCSI-driver (see above).
@@ -252,10 +252,10 @@
</PRE>
<H2>AUTHOR</H2><PRE>
- The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
+ The sane-hp backend was written by Geoffrey T. Dairiki. HP PhotoSmart
PhotoScanner support by Peter Kirchgessner.
-sane-backends 1.0.19 27 Mar 2004 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hp3500.5.html b/man/sane-hp3500.5.html
index 4da2b99..d1f0ebe 100644
--- a/man/sane-hp3500.5.html
+++ b/man/sane-hp3500.5.html
@@ -68,7 +68,7 @@
<H2>AUTHOR</H2><PRE>
Troy Rollo &lt;sane@troy.rollo.name&gt;
-sane-backends 1.0.19 27 Nov 2005 <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hp3900.5.html b/man/sane-hp3900.5.html
index ecefb45..00c6fdc 100644
--- a/man/sane-hp3900.5.html
+++ b/man/sane-hp3900.5.html
@@ -27,7 +27,9 @@
HP ScanJet 3970 RTS8822L-01H
HP ScanJet 4070 Photosmart RTS8822L-01H
HP ScanJet 4370 RTS8822L-02A
+ HP ScanJet G2710 RTS8822BL-03A
HP ScanJet G3010 RTS8822L-02A
+ HP ScanJet G3110 RTS8822L-02A
UMAX Astra 4900/4950 RTS8822L-01H *
BenQ 5550 RTS8823L-01E *
@@ -114,7 +116,7 @@
other operating systems and especially on big-endian platforms. The
scanner may get wrong data.
-sane-backends 1.0.19 01 January 2008 <B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B>
+ 06 Jan 2009 <B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hp4200.5.html b/man/sane-hp4200.5.html
index 46e4e1c..8bbd480 100644
--- a/man/sane-hp4200.5.html
+++ b/man/sane-hp4200.5.html
@@ -111,10 +111,10 @@
Scanning is slow due to backtracking.
- Send bug reports to the sane-devel mailing list: sane-
- devel@lists.alioth.debian.org.
+ Send bug reports to the sane-devel mailing list:
+ sane-devel@lists.alioth.debian.org.
-sane-backends 1.0.19 14 August 2005 <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hp5400.5.html b/man/sane-hp5400.5.html
index a3d4348..e1f153c 100644
--- a/man/sane-hp5400.5.html
+++ b/man/sane-hp5400.5.html
@@ -100,8 +100,8 @@
</PRE>
<H2>AUTHOR</H2><PRE>
Martijn van Oosterhout &lt;kleptog@svana.org&gt;, Thomas Soumarmon
- &lt;soumarmt@nerim.net&gt;. Manpage by Henning Meier-Geinitz &lt;henning@meier-
- geinitz.de&gt;.
+ &lt;soumarmt@nerim.net&gt;. Manpage by Henning Meier-Geinitz &lt;hen-
+ ning@meier-geinitz.de&gt;.
</PRE>
@@ -110,7 +110,7 @@
other operating systems and especially on big-endian platforms. The
scanner may get wrong data.
-sane-backends 1.0.19 17 Apr 2003 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hp5590.5.html b/man/sane-hp5590.5.html
index 1a2f3e0..08dd821 100644
--- a/man/sane-hp5590.5.html
+++ b/man/sane-hp5590.5.html
@@ -22,6 +22,7 @@
backend that provides access to the following Hewlett-Packard Work-
group/Document scanners:
+ ScanJet 4570
ScanJet 5550
ScanJet 5590
ScanJet 7650
@@ -76,7 +77,7 @@
<H2>AUTHOR</H2><PRE>
Ilia Sotnikov &lt;hostcc@gmail.com&gt;
-sane-backends 1.0.19 9 Apr 2007 <B><A HREF="sane-hp5590.5.html">sane-hp5590(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hp5590.5.html">sane-hp5590(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hpljm1005.5.html b/man/sane-hpljm1005.5.html
index 958fd30..7f39d7f 100644
--- a/man/sane-hpljm1005.5.html
+++ b/man/sane-hpljm1005.5.html
@@ -7,9 +7,6 @@
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
-XXX
-XXX WARNING: old character encoding and/or character set
-XXX
<B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>
@@ -56,9 +53,9 @@ XXX
</PRE>
<H2>AUTHOR</H2><PRE>
- Philippe R?tornaz &lt;couriousous@mandriva.org&gt;
+ Philippe Retornaz &lt;couriousous@mandriva.org&gt;
-sane-backends 1.0.19 15 Jan 2008 <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hpsj5s.5.html b/man/sane-hpsj5s.5.html
index 840a92d..17273af 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.19 24 Feb 2002 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-hs2p.5.html b/man/sane-hs2p.5.html
index c59b177..c54a339 100644
--- a/man/sane-hs2p.5.html
+++ b/man/sane-hs2p.5.html
@@ -133,7 +133,7 @@
jeremy &lt;jeremy@acjlaw.net&gt;
Maintained by Jeremy Johnson &lt;jeremy@acjlaw.net&gt;
-sane-backends 1.0.19 01 Nov 2007 <B><A HREF="sane-hs2p.5.html">sane-hs2p(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-hs2p.5.html">sane-hs2p(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-ibm.5.html b/man/sane-ibm.5.html
index f8eecec..02f4e80 100644
--- a/man/sane-ibm.5.html
+++ b/man/sane-ibm.5.html
@@ -94,7 +94,7 @@
mf &lt;massifr@tiscalinet.it&gt;
Maintained by Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
-sane-backends 1.0.19 15 Apr 2003 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-leo.5.html b/man/sane-leo.5.html
index 01e175a..220723b 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.
<I>http://www.zago.net/sane/#leo</I>
-sane-backends 1.0.19 16 April 2002 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-lexmark.5.html b/man/sane-lexmark.5.html
index 19d1eb3..9265ef4 100644
--- a/man/sane-lexmark.5.html
+++ b/man/sane-lexmark.5.html
@@ -7,9 +7,6 @@
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
-XXX
-XXX WARNING: old character encoding and/or character set
-XXX
<B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
@@ -51,11 +48,11 @@ XXX
<B>Scan</B> <B>Mode</B> <B>Options</B>
<B>--mode</B> selects the basic mode of operation of the scanner valid choices
- are <I>R</I> <I>Color</I> <I>,</I> <I>Gray</I> and <I>Lineart</I> The default mode is Color. The
- Lineart mode is black and white only (1 bit). Grayscale will
- produce 256 levels of gray (8 bits). Color mode allows for over
- 16 million different colors produced from 24 bits of color
- information.
+ are <I>Color</I>, <I>Gray</I> and <I>Lineart</I> The default mode is Color. The Lin-
+ eart mode is black and white only (1 bit). Grayscale will pro-
+ duce 256 levels of gray (8 bits). Color mode allows for over 16
+ million different colors produced from 24 bits of color informa-
+ tion.
<B>--resolution</B>
selects the resolution for a scan. The horizontal and vertical
@@ -135,7 +132,7 @@ XXX
The backend was originaly written by Fred Odendaal.
<I>http://ca.geocities.com/freshshelf@rogers.com/</I>
- The new version is currently developped by St?phane Voltz.
+ The new version is currently developped by StAphane Voltz.
<I>http://stef.dev.free.fr/sane/lexmark</I>
@@ -146,7 +143,7 @@ XXX
and Dalai Felinto for the time they spent recording USB activity
and testing the experimental version.
-sane-backends 1.0.19 16 April 2007 <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
+ 12 Jul 2008 <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-ma1509.5.html b/man/sane-ma1509.5.html
index 8e53f66..083fb96 100644
--- a/man/sane-ma1509.5.html
+++ b/man/sane-ma1509.5.html
@@ -29,8 +29,8 @@
<I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
Other Mustek USB scanners are supported by the gt68xx, mustek_usb and
- the plustek backends. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> and <B>sane-</B>
- <B><A HREF="plustek.5.html">plustek(5)</A></B> for details.
+ the plustek backends. See <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B> and
+ <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details.
This backend can only work with scanners that are already detected by
the operating system. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
@@ -108,8 +108,8 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B>sane-</B>
- <B><A HREF="mustek_usb.5.html">mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
+ <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
<I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>
@@ -127,7 +127,7 @@
More detailed bug information is available at the MA-1509 backend home-
page <I>http://www.meier-geinitz.de/sane/ma1509-backend/</I>.
-sane-backends 1.0.19 24 Feb 2003 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-matsushita.5.html b/man/sane-matsushita.5.html
index 0b2c72d..f635d2a 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.
<I>http://www.zago.net/sane/#matsushita</I>
-sane-backends 1.0.19 February 11th, 2004 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-microtek.5.html b/man/sane-microtek.5.html
index 528841a..8c4612e 100644
--- a/man/sane-microtek.5.html
+++ b/man/sane-microtek.5.html
@@ -153,20 +153,20 @@
in the configuration file (first one, then both), and see if it helps.
(If it does, report it.)
- Send lengthy bug reports and new scanner information to <B>mtek-</B>
- <B>bugs@mir.com</B>. All bug reports and new scanner inquiries should include
- an error log file. You can generate copious stderr output by setting
- the SANE_DEBUG_MICROTEK environment variable described above. For
- example:
+ Send lengthy bug reports and new scanner information to
+ <B>mtek-bugs@mir.com</B>. All bug reports and new scanner inquiries should
+ include an error log file. You can generate copious stderr output by
+ setting the SANE_DEBUG_MICROTEK environment variable described above.
+ For example:
setenv SANE_DEBUG_MICROTEK 128
More general comments, suggestions, and inquiries about frontends or
SANE should go to <B>sane-devel@lists.alioth.debian.org</B>, the SANE Develop-
- ers mailing list. Have a look at http://www.sane-project.org/mailing-
- lists.html concerning subscription to sane-devel.
+ 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.19 February 8, 2000 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-microtek2.5.html b/man/sane-microtek2.5.html
index 70d7f7f..5167b87 100644
--- a/man/sane-microtek2.5.html
+++ b/man/sane-microtek2.5.html
@@ -254,10 +254,10 @@
<I>/etc/sane.d/microtek2.conf</I>
The backend configuration file.
- <I>/usr/lib64/sane/libsane-microtek2.a</I>
+ <I>/usr/lib/sane/libsane-microtek2.a</I>
The static library implementing this backend.
- <I>/usr/lib64/sane/libsane-microtek2.so</I>
+ <I>/usr/lib/sane/libsane-microtek2.so</I>
The shared library implementing this backend (present on systems
that support dynamic loading).
@@ -285,7 +285,7 @@
Bernd Schroeder (not active anymore)
Karsten Festag karsten.festag@gmx.de
-sane-backends 1.0.19 28 Jan 2002 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-mustek.5.html b/man/sane-mustek.5.html
index d5603b0..06ca3b9 100644
--- a/man/sane-mustek.5.html
+++ b/man/sane-mustek.5.html
@@ -61,8 +61,8 @@
backend but you may be successful using the Mustek parallel port back-
end mustek_pp, see <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>. USB scanners are also not sup-
ported by this backend but the ma1509, mustek_usb, gt68xx, and plustek
- backends include support for some of them, see <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-</B>
- <B><A HREF="mustek_usb.5.html">mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, and <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>.
+ backends include support for some of them, see <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
+ <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, and <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>.
Mustek scanners have no protection against exceeding the physical scan
area height. That is, if a scan is attempted with a height that
@@ -70,17 +70,17 @@
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 <I>/usr/doc/sane-1.0.19/PROBLEMS</I> file.
+ the <I>/usr/doc/sane-1.0.20/PROBLEMS</I> 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-
ner's exact model name (look at the front and back of the scanner) and
a debug output to <I>sane-devel@lists.alioth.debian.org</I>. You can get the
debug output by setting the environment variable <B>SANE_DEBUG_MUSTEK</B> to 5
- and showing the list of available scanners with scanimage -L. Please
- send all of it to the mailing list. You must be subscribed to sane-
- devel before you can send mail to the list. See <I>http://www.sane-</I>
- <I>project.org/mailing-lists.html</I> for details.
+ and showing the list of available scanners with scanimage -L. Please
+ send all of it to the mailing list. You must be subscribed to
+ sane-devel before you can send mail to the list. See
+ <I>http://www.sane-project.org/mailing-lists.html</I> for details.
</PRE>
@@ -107,8 +107,8 @@
what constitutes a valid device name.
The supported options are <B>linedistance-fix</B>, <B>lineart-fix</B>, <B>legal-size</B>,
- <B>buffersize</B>, <B>blocksize</B>, <B>strip-height</B>, <B>disable-double-buffering</B>, <B>disable-</B>
- <B>backtracking</B>, and <B>force-wait</B>.
+ <B>buffersize</B>, <B>blocksize</B>, <B>strip-height</B>, <B>disable-double-buffering</B>, <B>dis-</B>
+ <B>able-backtracking</B>, and <B>force-wait</B>.
Options come in two flavors: global and positional ones. Global
options apply to all devices managed by the backend whereas positional
@@ -309,9 +309,9 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B>sane-</B>
- <B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
- <I>/usr/doc/sane-1.0.19/mustek/mustek.CHANGES</I>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>,
+ <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
+ <I>/usr/doc/sane-1.0.20/mustek/mustek.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/mustek-backend/</I>
@@ -334,7 +334,7 @@
More detailed bug information is available at the Mustek backend home-
page: <I>http://www.meier-geinitz.de/sane/mustek-backend/</I>.
-sane-backends 1.0.19 18 Sep 2005 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-mustek_pp.5.html b/man/sane-mustek_pp.5.html
index 141aa38..153d0cf 100644
--- a/man/sane-mustek_pp.5.html
+++ b/man/sane-mustek_pp.5.html
@@ -30,72 +30,82 @@
The following scanners might work with this backend:
<B>CCD</B> <B>scanners</B>
- lb lb lb lb _ _ _ _ l l l l. Model: ASIC ID: CCD
- Type: works: SE 6000 P 1013 00 yes SM 4800 P
- 1013/1015 04/01 yes SE 1200 ED Plus 1015 01
- no SM 1200 ED Plus 1015 01 no SE 12000 P
- 1505 05 no 600 III EP Plus 1013/1015 00/01
- yes SE 600 SEP 1013 ?? yes 600 II EP
- ???? ?? no MD9848 1015 00 yes
- Gallery 4800 ???? ?? yes Viviscan Compact II 1013
- 00 yes
+ Model: ASIC ID: CCD Type: works:
+ --------------------------------------------------------------
+ SE 6000 P 1013 00 yes
+ SM 4800 P 1013/1015 04/01 yes
+ SE 1200 ED Plus 1015 01 no
+ SM 1200 ED Plus 1015 01 no
+ SE 12000 P 1505 05 no
+ 600 III EP Plus 1013/1015 00/01 yes
+ SE 600 SEP 1013 ?? yes
+ 600 II EP ???? ?? no
+ MD9848 1015 00 yes
+ Gallery 4800 ???? ?? yes
+ Viviscan Compact II 1013 00 yes
<B>CIS</B> <B>scanners</B>
- lb lb lb _ _ _ l l l. Model: ASIC ID: works: Mustek 600
- CP &amp; 96 CP 1015 yes (*) Mustek 1200 CP 1015 yes
- Mustek 1200 CP+ 1015 yes
-
- lb lb lb _ _ _ l l l. OEM versions Original works
+ Model: ASIC ID: works:
+ -----------------------------------------------
+ Mustek 600 CP &amp; 96 CP 1015 yes (*)
+ Mustek 1200 CP 1015 yes
+ Mustek 1200 CP+ 1015 yes
+
+ OEM versions Original works
+ --------------------------------------------------
Medion/LifeTec/Tevion
- MD/LT 9350/9351 1200 CP yes
- MD/LT 9850/9851 1200 CP maybe (**)
- MD/LT 9858 1200 CP probably
- MD/LT 9890/9891 1200 CP yes Targa
- Funline TS12EP 1200 CP yes
- Funline TS6EP 600 CP yes Trust
- Easy Connect 9600+ 600 CP yes Cybercom
- 9352 1200 CP yes (***)
-
- (*) Calibration problems existed with earlier version of this
+ MD/LT 9350/9351 1200 CP yes
+ MD/LT 9850/9851 1200 CP maybe (**)
+ MD/LT 9858 1200 CP probably
+ MD/LT 9890/9891 1200 CP yes
+ Targa
+ Funline TS12EP 1200 CP yes
+ Funline TS6EP 600 CP yes
+ Trust
+ Easy Connect 9600+ 600 CP yes
+ Cybercom
+ 9352 1200 CP yes (***)
+
+ (*) Calibration problems existed with earlier version of this
driver. They seem to be solved now.
- (**) Problems have been reported in the past for the MD/LT9850 type
- (striped scans, head moving in wrong direction at some resolu-
- tions). It is not known whether the current version of the
+ (**) Problems have been reported in the past for the MD/LT9850 type
+ (striped scans, head moving in wrong direction at some
+ resolutions). It is not known whether the current version of the
driver still has these problems.
- <B>IF</B> <B>YOU</B> <B>HEAR</B> <B>LOUD</B> <B>CLICKING</B> <B>NOISES,</B> <B>IMMEDIATELY</B> <B>UNPLUG</B> <B>THE</B> <B>SCANNER</B> <B>!</B>
+ <B>IF</B> <B>YOU</B> <B>HEAR</B> <B>LOUD</B> <B>CLICKING</B> <B>NOISES,</B> <B>IMMEDIATELY</B> <B>UNPLUG</B> <B>THE</B> <B>SCANNER</B> <B>!</B>
(This holds for any type of scanner).
- (***) Possibly, the engine_delay parameter has to be set to 1 ms for
+ (***) Possibly, the engine_delay parameter has to be set to 1 ms for
accurate engine movements.
Please note that this backend is still under construction. Certain mod-
- els are currently not supported and some may never be because the com-
+ els are currently not supported and some may never be because the com-
munication protocol is still unknown (eg., SE 12000 P).
Some scanners work faster when <B>EPP/ECP</B> is enabled in the BIOS. EPP mode
- however may lead to hard-locks on some Linux systems. If that is the
+ however may lead to hard-locks on some Linux systems. If that is the
case for you, you can either disable ECP/EPP in your BIOS or disable it
in the backend itself (see GLOBAL OPTIONS).
- Note that the backend needs to run as root or has to have appropriate
- access rights to /dev/parport* if libieee1284 support is compiled in.
+ Note that the backend needs to run as root or has to have appropriate
+ access rights to /dev/parport* if libieee1284 support is compiled in.
To allow user access to the scanner run the backend through the network
- interface (See <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). Note also that the backend
- <I>does</I> <I>not</I> support <I>parport</I> <I>sharing</I>, i.e. if you try printing while scan-
- ning, your computer may crash. To enable parport sharing, you have to
- enable libieee1284 at compile time. This backend also conflicts with
- the <I>sane-musteka4s2</I> backend. You can only enable one of them in your
- dll.conf. However, you have to enable the backend explicitly in your
+ interface (See <B><A HREF="saned.8.html">saned(8)</A></B> and <B><A HREF="sane-net.5.html">sane-net(5)</A></B>). Note also that the backend
+ <I>does</I> <I>not</I> support <I>parport</I> <I>sharing</I>, i.e. if you try printing while scan-
+ ning, your computer may crash. To enable parport sharing, you have to
+ enable libieee1284 at compile time. This backend also conflicts with
+ the <I>sane-musteka4s2</I> backend. You can only enable one of them in your
+ dll.conf. However, you have to enable the backend explicitly in your
dll.conf, just remove the hash mark in the line "mustek_pp".
</PRE>
<H2>DEVICE DEFINITION</H2><PRE>
- This backend allows multiple devices being defined and configured via
- the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
- connected to different parallel ports). Please make sure to edit this
+ This backend allows multiple devices being defined and configured via
+ the <B>mustek_pp.conf</B> file (even simultaneously, provided that they are
+ connected to different parallel ports). Please make sure to edit this
file <B>before</B> you use the backend.
A device can be defined as follows:
@@ -107,25 +117,25 @@
<B>&lt;name&gt;</B> is an arbitrary name for the device, optionally enclosed by dou-
ble quotes, for instance "LifeTec 9350".
- <B>&lt;port</B> <B>name&gt;</B> is the name of the parallel port to which the device is
- connected. In case libieee1284 is used for communication with
- the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
+ <B>&lt;port</B> <B>name&gt;</B> is the name of the parallel port to which the device is
+ connected. In case libieee1284 is used for communication with
+ the port <I>(default</I> <I>setup)</I>, valid port names are <B>parport0</B>, <B>par-</B>
<B>port1</B>, and <B>parport2</B>.
- In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
- addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>, or
- <B>0x3BC</B>. The mapping of parallel ports (lp0, lp1, and lp2) to these
- addresses can be different for different Linux kernel versions. For
- instance, if you are using a Kernel 2.2.x or better and you have only
- one parallel port, this port is named lp0 regardless of the base
- address. However, this backend requires the base address of your port.
- If you are not sure which port your scanner is connected to, have a
+ In case the backend is configured for raw IO <I>(old</I> <I>setup)</I>, port
+ addresses have to be used instead of port names: <B>0x378</B>, <B>0x278</B>, or
+ <B>0x3BC</B>. The mapping of parallel ports (lp0, lp1, and lp2) to these
+ addresses can be different for different Linux kernel versions. For
+ instance, if you are using a Kernel 2.2.x or better and you have only
+ one parallel port, this port is named lp0 regardless of the base
+ address. However, this backend requires the base address of your port.
+ If you are not sure which port your scanner is connected to, have a
look at your /etc/conf.modules, /etc/modules.conf and/or /proc/ioports.
- If you are unsure which port to use, you can use the magic value <B>*</B> to
+ If you are unsure which port to use, you can use the magic value <B>*</B> to
probe for your scanner.
- <B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
+ <B>&lt;driver&gt;</B> is the driver to use for this device. Currently available
drivers are:
<B>cis600</B> : for 600 CP, 96 CP &amp; OEM versions
@@ -135,17 +145,17 @@
<B>Choosing</B> <B>the</B> <B>wrong</B> <B>driver</B> <B>can</B> <B>damage</B> <B>your</B> <B>scanner!</B>
Especially, using the 1200CP settings on a 600CP can be harmful.
- If the scanner starts making a loud noise, turn it off immedi-
+ If the scanner starts making a loud noise, turn it off immedi-
ately !!!
- Using the cis600 driver on a 1200CP or a 1200CP+ is probably not
- dangerous. The cis1200+ driver also works for the 1200CP, and using the
- cis1200 driver on a 1200CP+ will typically result in scans that cover
+ Using the cis600 driver on a 1200CP or a 1200CP+ is probably not dan-
+ gerous. The cis1200+ driver also works for the 1200CP, and using the
+ cis1200 driver on a 1200CP+ will typically result in scans that cover
only half of the width of the scan area (also not dangerous).
- If unsure about the exact model of your OEM version, check the optical
+ If unsure about the exact model of your OEM version, check the optical
resolution in the manual or on the box: the 600CP has a maximum optical
- resolution of 300x600 DPI, whereas the 1200CP and 1200CP+ have a maxi-
+ resolution of 300x600 DPI, whereas the 1200CP and 1200CP+ have a maxi-
mum optical resolution of 600x1200 DPI.
Examples:
@@ -156,8 +166,8 @@
scanner Mustek_600IIIEP * ccd300
- If in doubt which port you have to use, or whether your scanner is
- detected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all config-
+ If in doubt which port you have to use, or whether your scanner is
+ detected at all, you can use <B>sane-find-scanner</B> <B>-p</B> to probe all config-
ured ports.
@@ -165,20 +175,20 @@
<H2>CONFIGURATION</H2><PRE>
The contents of the <B>mustek_pp.conf</B> file is a list of device definitions
and device options that correspond to Mustek scanners. Empty lines and
- lines starting with a hash mark (#) are ignored. Options have the fol-
+ lines starting with a hash mark (#) are ignored. Options have the fol-
lowing format:
<I>option</I> <I>&lt;name&gt;</I> <I>[&lt;value&gt;]</I>
- Depending on the nature of the option, a value may or may not be
- present. Options always apply to the scanner definition that precedes
- them. There are no global options. Options are also driver-specific:
+ Depending on the nature of the option, a value may or may not be
+ present. 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.
<B>Common</B> <B>options</B>
<B>bw</B> <B>&lt;value&gt;</B>
Black/white discrimination value to be used during lineart scan-
- ning. Pixel values below this value are assumed to be black,
+ ning. Pixel values below this value are assumed to be black,
values above are assumed to be white.
Default value: 127
Minimum: 0
@@ -188,11 +198,11 @@
<B>CIS</B> <B>driver</B> <B>options</B>
<B>top_adjust</B> <B>&lt;value&gt;</B>
- Vertical adjustment of the origin, expressed in millimeter
- (floating point). This option can be used to calibrate the
- position of the origin, within certain limits. Note that CIS
- scanners are probably temperature sensitive, and that a certain
- inaccuracy may be hard to avoid. Differences in offset between
+ Vertical adjustment of the origin, expressed in millimeter
+ (floating point). This option can be used to calibrate the
+ position of the origin, within certain limits. Note that CIS
+ scanners are probably temperature sensitive, and that a certain
+ inaccuracy may be hard to avoid. Differences in offset between
runs in the order of 1 to 2 mm are not unusual.
Default value: 0.0
Minimum: -5.0
@@ -201,14 +211,14 @@
Example: option top_adjust -2.5
<B>slow_skip</B>
- Turns fast skipping to the start of the scan region off. When
+ Turns fast skipping to the start of the scan region off. When
the region to scan does not start at the origin, the driver will
- try to move the scanhead to the start of the scan area at the
- fastest possible speed. On some models, this may not work,
+ try to move the scanhead to the start of the scan area at the
+ fastest possible speed. On some models, this may not work,
resulting in large inaccuracies (up to centimeters). By setting
- this option, the driver is forced to use normal speed during
+ this option, the driver is forced to use normal speed during
skipping, which can circumvent the accuracy problems. Currently,
- there are no models for which these inaccuracy problems are
+ there are no models for which these inaccuracy problems are
known to occur.
By default, fast skipping is used.
@@ -216,22 +226,22 @@
Example: option slow_skip
<B>engine_delay</B> <B>&lt;value&gt;</B>
- Under normal circumstances, it is sufficient for the driver to
+ Under normal circumstances, it is sufficient for the driver to
wait for the scanner signaling that the engine is stable, before
- a new engine command can be transmitted. In rare cases, certain
- scanners and/or parallel port chipsets appear to prevent reli-
+ a new engine command can be transmitted. In rare cases, certain
+ scanners and/or parallel port chipsets appear to prevent reli-
able detection of the engine state. As a result, engine commands
- are transmitted too soon and the movement of the scanner head
- becomes unreliable. Inaccuracies ranging up to 10 cm over the
- whole vertical scan range have been reported. To work around
- this problem, the engine_delay option can be set. If it is set,
+ are transmitted too soon and the movement of the scanner head
+ becomes unreliable. Inaccuracies ranging up to 10 cm over the
+ whole vertical scan range have been reported. To work around
+ this problem, the engine_delay option can be set. If it is set,
the driver waits an additional amount of time after every engine
- command, equal to the engine_delay parameter, expressed in mil-
+ command, equal to the engine_delay parameter, expressed in mil-
liseconds. It practice an engine_delay of 1 ms is usually suffi-
cient. The maximum delay is 100 ms.
- Note that every additional ms of delay can add up to 14 seconds
- to the total scanning time (highest resolution), so an as small
+ 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 preferred.
Default value: 0
@@ -240,11 +250,10 @@
Example: option engine_delay 1
- <B>CCD</B> <B>driver</B> <B>options</B>
-
+ <B>CCD</B> <B>driver</B> <B>options</B>
<B>top</B> <B>&lt;value&gt;</B>
- Number of scanlines to skip to the start of the scan area. The
- number can be any positive integer. Values known to me are 47
+ Number of scanlines to skip to the start of the scan area. The
+ number can be any positive integer. Values known to me are 47
and 56.
Default value: 47
@@ -254,7 +263,7 @@
Example: option top 56
<B>waitbank</B> <B>&lt;value&gt;</B>
- The number of usecs to wait for a bank change. You should not
+ The number of usecs to wait for a bank change. You should not
touch this value actually. May be any positive integer
Default value: 700
@@ -304,15 +313,15 @@
</PRE>
<H2>GLOBAL OPTIONS</H2><PRE>
- You can control the overall behaviour of the mustek_pp backend by
- global options which precede any scanner definition in the
+ You can control the overall behaviour of the mustek_pp backend by
+ global options which precede any scanner definition in the
mustek_pp.conf file.
Currently, there is only one global option:
<B>Global</B> <B>options</B>
- <B>no_epp</B> Disable parallel port mode EPP: works around a known bug in the
- Linux parport code. Enable this option, if the backend hangs
+ <B>no_epp</B> Disable parallel port mode EPP: works around a known bug in the
+ Linux parport code. Enable this option, if the backend hangs
when trying to access the parallel port in EPP mode.
Default value: use EPP
@@ -323,7 +332,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d/mustek</I><B>_</B><I>pp.conf</I>
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/lib/sane/libsane-mustek</I><B>_</B><I>pp.a</I>
@@ -339,45 +348,47 @@
<B>SANE_CONFIG_DIR</B>
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
+ uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
- value of the environment variable ends with the directory sepa-
+ value of the environment variable ends with the directory sepa-
rator character, then the default directories are searched after
- the explicitly specified directories. For example, setting
- <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
- "tmp/config", ".", and "/etc/sane.d" being searched (in this
+ the explicitly specified directories. For example, setting
+ <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
+ "tmp/config", ".", and "/etc/sane.d" being searched (in this
order).
<B>SANE_DEBUG_MUSTEK_PP</B>
- 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.
- lb lb; l l. level debug output - -
- 0 nothing
- 1 errors
- 2 warnings &amp; minor errors
- 3 additional information
- 4 debug information
- 5 code flow (not supported yet)
- 6 special debug information
+ level debug output
+ --------------------------------------
+ 0 nothing
+ 1 errors
+ 2 warnings &amp; minor errors
+ 3 additional information
+ 4 debug information
+ 5 code flow (not supported yet)
+ 6 special debug information
<B>SANE_DEBUG_SANEI_PA4S2</B>
- This variable sets the debug level for the SANE interface for
- the Mustek chipset A4S2. Note that enabling this will spam your
+ This variable sets the debug level for the SANE interface for
+ the Mustek chipset A4S2. Note that enabling this will spam your
terminal with some million lines of debug output.
- lb lb; l l. level debug output - -
- 0 nothing
- 1 errors
- 2 warnings
- 3 things nice to know
- 4 code flow
- 5 detailed code flow
- 6 everything
+ level debug output
+ ----------------------------
+ 0 nothing
+ 1 errors
+ 2 warnings
+ 3 things nice to know
+ 4 code flow
+ 5 detailed code flow
+ 6 everything
</PRE>
@@ -399,41 +410,41 @@
</PRE>
<H2>BUGS</H2><PRE>
- Too many... please send bug reports to <I>sane-</I>
- <I>devel@lists.alioth.debian.org</I> (note that you have to subscribe first to
- the list before you can send emails... see http://www.sane-
- project.org/mailing-lists.html)
+ Too many... please send bug reports to
+ <I>sane-devel@lists.alioth.debian.org</I> (note that you have to subscribe
+ first to the list before you can send emails... see
+ http://www.sane-project.org/mailing-lists.html)
</PRE>
<H2>BUG REPORTS</H2><PRE>
- If something doesn't work, please contact us (Jochen for the CCD scan-
- ners, Eddy for the CIS scanners). But we need some information about
+ If something doesn't work, please contact us (Jochen for the CCD scan-
+ ners, Eddy for the CIS scanners). But we need some information about
your scanner to be able to help you...
<I>SANE</I> <I>version</I>
run "scanimage -V" to determine this
<I>the</I> <I>backend</I> <I>version</I> <I>and</I> <I>your</I> <I>scanner</I> <I>hardware</I>
- run "SANE_DEBUG_MUSTEK_PP=128 scanimage -L" as root. If you
- don't get any output from the mustek_pp backend, make sure a
+ run "SANE_DEBUG_MUSTEK_PP=128 scanimage -L" as root. If you
+ don't get any output from the mustek_pp backend, make sure a
line "mustek_pp" is included into your /etc/sane.d/dll.conf. If
- your scanner isn't detected, make sure you've defined the right
+ your scanner isn't detected, make sure you've defined the right
port address in your mustek_pp.conf.
<I>the</I> <I>name</I> <I>of</I> <I>your</I> <I>scanner/vendor</I>
also a worthy information. Please also include the optical reso-
- lution and lamp type of your scanner, both can be found in the
+ lution and lamp type of your scanner, both can be found in the
manual of your scanner.
<I>any</I> <I>further</I> <I>comments</I>
if you have comments about the documentation (what could be done
- better), or you think I should know something, please include
+ better), or you think I should know something, please include
it.
<I>some</I> <I>nice</I> <I>greetings</I>
- November 17 2003 <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-mustek_usb.5.html b/man/sane-mustek_usb.5.html
index 1566f0b..6d4da6b 100644
--- a/man/sane-mustek_usb.5.html
+++ b/man/sane-mustek_usb.5.html
@@ -34,8 +34,8 @@
The Mustek BearPaw 1200 and 2400 scanners are supported by the plustek
backend. See <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B> for details. The Mustek BearPaw 1200F is
supported by the MA-1509 backend. See <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B> for details. Other
- Mustek USB scanners are supported by the gt68xx backend, see <B>sane-</B>
- <B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>.
+ Mustek USB scanners are supported by the gt68xx backend, see
+ <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>.
This backend can only work with scanners that are already detected by
the operating system. See <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B> for details.
@@ -148,8 +148,8 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>, <B>sane-plus-</B>
<B><A HREF="tek.5.html">tek(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>
- <I>/usr/doc/sane-1.0.19/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
- <I>/usr/doc/sane-1.0.19/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
+ <I>/usr/doc/sane-1.0.20/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.CHANGES</I>,
+ <I>/usr/doc/sane-1.0.20/mustek</I><B>_</B><I>usb/mustek</I><B>_</B><I>usb.TODO</I>
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>
@@ -175,7 +175,7 @@
More detailed bug information is available at the Mustek backend home-
page <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb-backend/</I>.
-sane-backends 1.0.19 3 Mar 2004 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-mustek_usb2.5.html b/man/sane-mustek_usb2.5.html
index 2240bf1..a7a0647 100644
--- a/man/sane-mustek_usb2.5.html
+++ b/man/sane-mustek_usb2.5.html
@@ -22,8 +22,8 @@
Service &amp; Quality SQ113 chipset. At the moment, only the Mustek BearPaw
2448 TA Pro is supported. It's planned to add support for other scan-
ners that are based on the SQ113 and maybe SQ11 chip. For more details,
- see the mustek_usb2 backend homepage: <I>http://www.meier-</I>
- <I>geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>.
+ see the mustek_usb2 backend homepage:
+ <I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>.
This is BETA software. Especially if you test new or untested scanners,
keep your hand at the scanner's plug and unplug it, if the head bumps
@@ -67,9 +67,9 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B>sane-</B>
- <B><A HREF="mustek_usb.5.html">mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
- <I>/usr/doc/sane-1.0.19/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>,
+ <B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>
+ <I>/usr/doc/sane-1.0.20/mustek</I><B>_</B><I>usb2/mustek</I><B>_</B><I>usb2.CHANGES</I>
<I>http://www.meier-geinitz.de/sane/mustek</I><B>_</B><I>usb2-backend/</I>
@@ -81,11 +81,11 @@
</PRE>
<H2>BUGS</H2><PRE>
- Please contact me if you find a bug or missing feature: &lt;henning@meier-
- geinitz.de&gt;. Please send a debug log if your scanner isn't detected
- correctly (see SANE_DEBUG_MUSTEK_USB2 above).
+ Please contact me if you find a bug or missing feature: &lt;hen-
+ ning@meier-geinitz.de&gt;. Please send a debug log if your scanner isn't
+ detected correctly (see SANE_DEBUG_MUSTEK_USB2 above).
-sane-backends 1.0.19 15 Apr 2006 <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>
+ 13 Jul 2008 <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-nec.5.html b/man/sane-nec.5.html
index db00a15..79bf420 100644
--- a/man/sane-nec.5.html
+++ b/man/sane-nec.5.html
@@ -67,7 +67,7 @@
<H2>AUTHORS</H2><PRE>
Kazuya Fukuda
-sane-backends 1.0.19 17 Feb 2000 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-net.5.html b/man/sane-net.5.html
index 152e045..2b3b582 100644
--- a/man/sane-net.5.html
+++ b/man/sane-net.5.html
@@ -30,7 +30,7 @@
<I>host</I>:<I>device</I>
- Where <I>host</I> is the name (or IP address) of the (remote-) host and <I>device</I>
+ Where <I>host</I> is the name (or IP address) of the (remote) host and <I>device</I>
is the name of the device on this host that should be addressed. If
the device name does not contain a colon (:), then the entire string is
treated as the <I>device</I> string for the default host. The default host is
@@ -145,7 +145,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger and Andreas Beck
-sane-backends 1.0.19 24 Oct 2007 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-net.5.html">sane-net(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-niash.5.html b/man/sane-niash.5.html
index eaeaa88..8ed9f10 100644
--- a/man/sane-niash.5.html
+++ b/man/sane-niash.5.html
@@ -81,7 +81,7 @@
Bertrik Sikken &lt;bertrik@zonnet.nl&gt;
-sane-backends 1.0.19 29 July 2004 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-pie.5.html b/man/sane-pie.5.html
index e442120..1b5c9dc 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:
<B>Simon</B> <B>Munton</B> <B>&lt;simon@munton.demon.co.uk&gt;</B>
-sane-backends 1.0.19 7 Sept 2000 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-pint.5.html b/man/sane-pint.5.html
index f73ed54..e377e70 100644
--- a/man/sane-pint.5.html
+++ b/man/sane-pint.5.html
@@ -30,9 +30,10 @@
If have successfully used the PINT driver with your scanner, but it
does not work using this SANE backend, please let us know. To do this,
- send a mail with the relevant information for your scanner to <I>sane-</I>
- <I>devel@lists.alioth.debian.org</I>. Have a look at http://www.sane-
- project.org/mailing-lists.html concerning subscription to sane-devel.
+ send a mail with the relevant information for your scanner to
+ <I>sane-devel@lists.alioth.debian.org</I>. Have a look at
+ http://www.sane-project.org/mailing-lists.html concerning subscription
+ to sane-devel.
</PRE>
@@ -41,16 +42,16 @@
<I>special</I>
- Where <I>special</I> is the UNIX path-name for the special device that corre-
- sponds to the scanner. The special device name must be a PINT device
- or a symlink to such a device. For example, under NetBSD or OpenBSD,
+ Where <I>special</I> is the UNIX path-name for the special device that corre-
+ sponds to the scanner. The special device name must be a PINT device
+ or a symlink to such a device. For example, under NetBSD or OpenBSD,
such a device name could be <I>/dev/ss0</I> or <I>/dev/scan0</I>.
</PRE>
<H2>CONFIGURATION</H2><PRE>
- The contents of the <I>pint.conf</I>. file is a list of device names that
- correspond to PINT scanners. Empty lines and lines starting with a
+ The contents of the <I>pint.conf</I>. file is a list of device names that
+ correspond to PINT scanners. Empty lines and lines starting with a
hash mark (#) are ignored. A sample configuration file is shown below:
/dev/scanner
@@ -61,7 +62,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d/pint.conf</I>
- The backend configuration file (see also description of
+ The backend configuration file (see also description of
<B>SANE_CONFIG_DIR</B> below).
<I>/usr/lib/sane/libsane-pint.a</I>
@@ -77,21 +78,21 @@
<B>SANE_CONFIG_DIR</B>
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
+ uration file is searched in two default directories: first, the
current working directory (".") and then in /etc/sane.d. If the
- value of the environment variable ends with the directory
- separator character, then the default directories are searched
- after the explicitly specified directories. For example, set-
- ting <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directo-
- ries "tmp/config", ".", and "/etc/sane.d" being searched (in
- this order).
+ value of the environment variable ends with the directory sepa-
+ rator character, then the default directories are searched after
+ the explicitly specified directories. For example, setting
+ <B>SANE_CONFIG_DIR</B> to "/tmp/config:" would result in directories
+ "tmp/config", ".", and "/etc/sane.d" being searched (in this
+ order).
<B>SANE_DEBUG_PINT</B>
- 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.
@@ -108,33 +109,33 @@
</PRE>
<H2>BUGS</H2><PRE>
- There are minor roundoff errors when adjusting the ranges, since PINT
- uses units of 1/1200 of an inch, and SANE normally uses millimeters.
- Symptoms of these errors are skewed images. This should really be
+ There are minor roundoff errors when adjusting the ranges, since PINT
+ uses units of 1/1200 of an inch, and SANE normally uses millimeters.
+ Symptoms of these errors are skewed images. This should really be
fixed (no pun intended) as soon as possible, but I just don't know/care
- enough about fixed-point representation and roundoff errors to do this
+ enough about fixed-point representation and roundoff errors to do this
correctly. Workaround: use inches as the scanning unit, and everything
usually works fine.
- The PINT 0.5e interface does not provide a way to determine valid
- ranges for DPI, modes, and scan sizes. So, the SANE backend queries
- the PINT device, and dynamically discovers valid ranges by doing a
- binary search. This means that the driver takes longer to initialize
+ The PINT 0.5e interface does not provide a way to determine valid
+ ranges for DPI, modes, and scan sizes. So, the SANE backend queries
+ the PINT device, and dynamically discovers valid ranges by doing a
+ binary search. This means that the driver takes longer to initialize
than seems necessary.
- Resetting the scanner does not seem to work (at least not on my HP
- ScanJet 4p). For that reason, the driver sends a SCIOCRESTART, then
+ Resetting the scanner does not seem to work (at least not on my HP
+ ScanJet 4p). For that reason, the driver sends a SCIOCRESTART, then
gobbles up any remaining input until it hits EOF.
- Not all of the scanners have been identified (i.e. whether they are
+ Not all of the scanners have been identified (i.e. whether they are
flatbed or handheld).
X and Y resolutions are assumed to be the same.
- No testing has been done on three-pass or handheld scanners, or with
+ No testing has been done on three-pass or handheld scanners, or with
Automatic Document Feeder support.
-sane-backends 1.0.19 13 May 1998 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-pixma.5.html b/man/sane-pixma.5.html
index aac0c79..16d5c5c 100644
--- a/man/sane-pixma.5.html
+++ b/man/sane-pixma.5.html
@@ -19,58 +19,82 @@
<H2>DESCRIPTION</H2><PRE>
The <B>sane-pixma</B> library implements a SANE (Scanner Access Now Easy)
backend that provides access to Canon PIXMA multi-function devices
- (All-in-one printers). Currently, the following models work with this
- backend:
-
- PIXMA MP150, MP160, MP170, MP180, MP450, MP460
- PIXMA MP500, MP510, MP530, MP600, MP600R
- PIXMA MP800, MP800R, MP810, MP830, MP960
+ (All-in-one printers). The backend implements both USB interface and
+ Network LAN interface using Canon's BJNP protocol. Currently, the fol-
+ lowing models work with this backend:
+
+ PIXMA MP140, MP150, MP160, MP170, MP180, MP190
+ PIXMA MP210, MP220, MP240
+ PIXMA MP450, MP460, MP470, MP480
+ PIXMA MP500, MP510, MP520, MP530, MP540
+ PIXMA MP600, MP600R, MP610, MP620, MP630, MP710
+ PIXMA MP800, MP800R, MP810, MP830, MP960, MP970, MP980
+ PIXMA MX300, MX310, MX700, MX850, MX7600
MultiPASS MP700, PIXMA MP750 (no grayscale)
+ ImageCLASS MF4010, MF4018, MF4120, MF4122, MF4140, MF4150
+ ImageCLASS MF4270
- The following models are not well tested and/or the scanner sometimes
+ The following models are not well tested and/or the scanner sometimes
hangs and must be switched off and on.
SmartBase MP360, MP370, MP390
MultiPASS MP730, PIXMA MP760, PIXMA MP780
+ The following models may use the same Pixma protocol as those listed
+ above, but have not yet been reported to work (or not). They are
+ declared in the backend so that they get recognized and activated.
+ Feedback in the Sane-dev mailing list welcome.
+
+ PIXMA MP740
+ PIXMA MP260
+ ImageCLASS MF3110, MF3240
+ ImageCLASS MF5630, MF5650, MF5730, MF5750, MF5770, MF8170c
+
The backend supports
- * resolutions at 75,150,300,600,1200 and 2400 DPI (still buggy),
+ * resolutions at 75,150,300,600,1200,2400 and 4800 DPI (some maybe
+ buggy),
* color and grayscale mode,
- * a custom gamma table and
- * automatic document feeder (only single side).
+ * a custom gamma table,
+ * Automatic Document Feeder (Duplex for some models).
+ * Transparency Unit, 24 or 48 bits depth.
- The device name is in the form pixma:xxxxyyyy_zzzzz where x, y and z
- are vendor ID, product ID and serial number respectively. Example:
+ The device name is in the form pixma:xxxxyyyy_zzzzz where x, y and z
+ are vendor ID, product ID and serial number respectively. Example:
pixma:04A91709_123456 is a MP150.
- This backend is in <B>alpha</B> stage and will stay in this stage until we get
- the programming manual for the hardware. Although we have tested it as
- good as we could, it will not work in every situations. You will find
- an up-to-date status at the project homepage. (See below)
+ This backend, based on cloning original Canon drivers protocols, is in
+ a production stage. Designed has been carried out without any applica-
+ ble manufacturer documentation, probably never available. However, we
+ have tested it as well as we could, but it may not work in every situa-
+ tions. You will find an up-to-date status at the project homepage. (See
+ below). Users feedback is essential to help improve features and per-
+ formances.
</PRE>
<H2>OPTIONS</H2><PRE>
Besides "well-known" options (e.g. resolution, mode etc.) pixma backend
- also provides the following <B>experimental</B> options for button handling,
- i.e. the options might change in the future.
+ also provides the following options for button handling, i.e. the
+ options might change in the future.
+ Button scan is disabled on MAC OS X due to darwin libusb not handling
+ timeouts in usb interrupt reads.
<I>button-controlled</I>
This option can be used in combination with <B><A HREF="scanadf.1.html">scanadf(1)</A></B> and <B>scan-</B>
- <B><A HREF="image.1.html">image(1)</A></B> in batch mode, for example when you want to scan many
+ <B><A HREF="image.1.html">image(1)</A></B> in batch mode, for example when you want to scan many
photos or multiple-page documents. If it is enabled (i.e. is set
- to true or yes), the backend waits before every scan until the
- user presses the "SCAN" button (for MP150) or the color-scan
- button (for other models). Just put the first page in the scan-
- ner, press the button, then the next page, press the button and
+ to true or yes), the backend waits before every scan until the
+ user presses the "SCAN" button (for MP150) or the color-scan
+ button (for other models). Just put the first page in the scan-
+ ner, press the button, then the next page, press the button and
so on. When you finished, press the gray-scan button. (For MP150
you have to stop the frontend by pressing Ctrl-C for example.)
<I>button-update</I> <I>button-1</I> <I>button-2</I>
- These options are interesting for developers. To check button
- status: (1) set <I>button-1</I> and <I>button-2</I> to zero, (2) set <I>button-</I>
- <I>update</I> (Its type is SANE_TYPE_BUTTON.), (3) get <I>button-1</I> and
- <I>button-2</I>. If the result is not zero, the corresponding button
+ These options are interesting for developers. To check button
+ status: (1) set <I>button-1</I> and <I>button-2</I> to zero, (2) set <I>button-</I>
+ <I>update</I> (Its type is SANE_TYPE_BUTTON.), (3) get <I>button-1</I> and
+ <I>button-2</I>. If the result is not zero, the corresponding button
was pressed.
@@ -87,35 +111,37 @@
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_DEBUG_PIXMA</B>
- 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 value increases the verbosity.
0 print nothing (default)
1 print error and warning messages (recommended)
2 print informational messages
3 print debug-level messages
- 10 dump USB traffics
+ 11 dump USB traffics
+ 21 full dump USB traffics
<B>PIXMA_EXPERIMENT</B>
- Setting to a non-zero value will enable the support for experi-
+ Setting to a non-zero value will enable the support for experi-
mental models. You should also set SANE_DEBUG_PIXMA to 10.
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <I>http://home.arcor.de/wittawat/pixma/</I>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <I>http://home.arcor.de/wittawat/pixma/,</I>
+ <I>http://mp610.blogspot.com/</I>
</PRE>
-<H2>AUTHOR</H2><PRE>
- Wittawat Yamwong
+<H2>AUTHORS</H2><PRE>
+ Wittawat Yamwong, Nicolas Martin, Dennis Lou, Louis Lagendijk
- I would like to thank all testers and helpers. Without them I would not
- be able to write subdrivers for models I don't have. See also the
+ We would like to thank all testers and helpers. Without them we could
+ not be able to write subdrivers for models we don't have. See also the
project homepage.
-sane-backends 1.0.19 19 July 2007 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
+ 28 Feb 2009 <B><A HREF="sane-pixma.5.html">sane-pixma(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-plustek.5.html b/man/sane-plustek.5.html
index 1af064e..faf5bb6 100644
--- a/man/sane-plustek.5.html
+++ b/man/sane-plustek.5.html
@@ -118,6 +118,12 @@
----------------------------------------------------------
Q-Scan USB001 LM9832 300x600dpi 42bit 512Kb 0x1000
+ Vendor Visioneer - ID: 0x04A7
+ ----------------------------------------------------------
+ USB Model: ASIC: Properties: Prod-ID
+ ----------------------------------------------------------
+ Strobe XP100 LM9833 600x1200dpi 48bit 512Kb 0x0427
+
</PRE>
<H2>OTHER PLUSTEK SCANNERS</H2><PRE>
@@ -137,8 +143,8 @@
U12 P98003 u12
UT12 P98003 u12
1212U P98003 u12
- For a more complete and up to date list see: <B>http://www.sane-</B>
- <B>project.org/sane-supported-devices.html</B>
+ For a more complete and up to date list see:
+ <B>http://www.sane-project.org/sane-supported-devices.html</B>
</PRE>
@@ -303,7 +309,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>,
- <I>/usr/doc/sane-1.0.19/plustek/Plustek-USB.changes</I>
+ <I>/usr/doc/sane-1.0.20/plustek/Plustek-USB.changes</I>
<I>http://www.gjaeger.de/scanner/plustek/</I>
@@ -326,8 +332,8 @@
The value controls the verbosity of the backend. Please note, that val-
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.
+ could be rather large. The ending of these files is ".raw". For
+ problem reports it should be enough the set the verbosity to 13.
</PRE>
@@ -347,7 +353,7 @@
* Negative/Slide scanning quality is poor.
-sane-backends 1.0.19 15 November 2007 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
+ 25 Aug 2008 <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-plustek_pp.5.html b/man/sane-plustek_pp.5.html
index 32b9a88..acea96a 100644
--- a/man/sane-plustek_pp.5.html
+++ b/man/sane-plustek_pp.5.html
@@ -342,7 +342,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>,
- <I>/usr/doc/sane-1.0.19/plustek/Plustek-PARPORT.changes</I>
+ <I>/usr/doc/sane-1.0.20/plustek/Plustek-PARPORT.changes</I>
<I>http://www.gjaeger.de/scanner/plustek</I><B>_</B><I>pp/</I>
@@ -405,7 +405,7 @@
* The scanning quality of the A3I is poor
-sane-backends 1.0.19 18 June 2004 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-plustek_pp.5.html">sane-plustek_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-pnm.5.html b/man/sane-pnm.5.html
index 913cbdd..67e0e8f 100644
--- a/man/sane-pnm.5.html
+++ b/man/sane-pnm.5.html
@@ -74,7 +74,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
-sane-backends 1.0.19 22 April 2001 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-qcam.5.html b/man/sane-qcam.5.html
index b76036a..6a3cebb 100644
--- a/man/sane-qcam.5.html
+++ b/man/sane-qcam.5.html
@@ -109,7 +109,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>
-sane-backends 1.0.19 25 October 1997 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-ricoh.5.html b/man/sane-ricoh.5.html
index ac6f4f1..ef8d2f1 100644
--- a/man/sane-ricoh.5.html
+++ b/man/sane-ricoh.5.html
@@ -85,7 +85,7 @@
<H2>AUTHOR</H2><PRE>
Feico W. Dillema
-sane-backends 1.0.19 24 Jun 2000 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-rts8891.5.html b/man/sane-rts8891.5.html
new file mode 100644
index 0000000..49756bd
--- /dev/null
+++ b/man/sane-rts8891.5.html
@@ -0,0 +1,160 @@
+<HTML>
+<HEAD>
+<TITLE>sane-rts8891.5</TITLE>
+</HEAD>
+<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
+<H1>sane-rts8891.5</H1>
+<HR>
+<PRE>
+<!-- Manpage converted by man2html 3.0.1 -->
+<B><A HREF="sane-rts8891.5.html">sane-rts8891(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-rts8891.5.html">sane-rts8891(5)</A></B>
+
+
+</PRE>
+<H2>NAME</H2><PRE>
+ sane-rts8891 - SANE backend for rts8891 based scanners
+
+
+</PRE>
+<H2>DESCRIPTION</H2><PRE>
+ The <B>sane-rts8891</B> library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to scanners based on the rts8891 ASIC.
+
+ The scanners that work with this backend are:
+
+ Vendor Model status
+ ---------------------- -----------
+ Umax Astra 4400 untested
+ Umax Astra 4450 untested
+ HP scanjet 4000c good
+ HP scanjet 4470c good
+
+ The options the backend supports can either be selected through command
+ line options to programs like scanimage or through GUI elements in
+ xscanimage or xsane.
+
+ If you have any strange behavior, please report to the backend main-
+ tainer or to the SANE mailing list.
+
+ Valid command line options and their syntax can be listed by using
+ scanimage --help -d rts8891
+
+ <B>Scan</B> <B>Mode</B> <B>Options</B>
+
+ <B>--mode</B> selects the basic mode of operation of the scanner valid choices
+ are <I>R</I> <I>Color</I> <I>,</I> <I>Gray</I> and <I>Lineart</I> The default mode is Color. The
+ Lineart mode is black and white only (1 bit). Grayscale will
+ produce 256 levels of gray (8 bits). Color mode allows for over
+ 16 million different colors produced from 24 bits of color
+ information.
+
+ <B>--resolution</B>
+ selects the resolution for a scan. The horizontal and vertical
+ resolutions are set by the value of this option. The scanner is
+ capable of the following resolutions for the specified option
+ value:
+
+ Value Hor. Resolution Vert. Resolution
+ ----- --------------- -------------------
+ 75 75dpi 75dpi
+ 150 150dpi 150dpi
+ 300 300dpi 300dpi
+ 600 600dpi 600dpi
+ 1200 1200dpi 1200dpi
+
+ <B>--preview</B>
+ requests a preview scan. The resolution used for that scan is 75
+ dpi and the scan area and the scan mode are as specified through
+ their options, or the default if not specified. The default
+ value for preview mode is "no".
+
+ <B>--threshold</B>
+ selects the minimum-brightness to get a white point. The
+ threshold is only used with Lineart mode scans. It is specified
+ as a percentage in the range 0..100% (in steps of 1). The
+ default value of the threshold option is 50.
+
+
+</PRE>
+<H2>CONFIGURATION FILE</H2><PRE>
+ The configuration file <B>/etc/sane.d/rts8891.conf</B> contains the usb device
+ ids of supported scanners (eg usb 0x043d 0x007c) and scanner configura-
+ tion options. Empty lines and lines starting with a hash mark (#) are
+ ignored.
+
+ The options supported are <B>allowsharing</B> , <B>modelnumber</B>
+
+ Option
+
+ <B>allowsharing</B> enables or not the sharing of the scanner between multiple
+ frontends at the same time.
+
+ <B>modelnumber</B> is used to force the reported model by the backend and is
+ only usefull in the case of a scanner which NVRAM has been erased.
+ 0 to report a HP4470c.
+ 1 to report a HP4400c.
+ 2 to report an Astra 4400.
+
+
+</PRE>
+<H2>FILES</H2><PRE>
+ <I>/usr/lib/sane/libsane-rts8891.a</I>
+ The static library implementing this backend.
+
+ <I>/usr/lib/sane/libsane-rts8891.so</I>
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+</PRE>
+<H2>ENVIRONMENT</H2><PRE>
+ <B>SANE_DEBUG_RTS8891</B> <B>SANE_DEBUG_RTS8891_LOW</B> <B>SANE_DEBUG_RTS88XX_LIB</B>
+ If the library was compiled with debug support enabled, these
+ environment variables controls the debug level for this backend.
+ E.g., a value of 255 requests all debug output to be printed.
+ Smaller levels reduce verbosity.
+
+
+</PRE>
+<H2>LIMITATIONS</H2><PRE>
+ Scanners of the same model exist with different sensors, due to lack of
+ data (ie USB logs) some sensors are better supported than others. At
+ least 75 dpi mode is working for any model. Sharing the a scanner
+ between several frontends at the same time (allowsharing option) may
+ not work on some USB controllers.
+
+ XPA is no (yet) supported.
+
+
+</PRE>
+<H2>BUGS</H2><PRE>
+ No bugs currently known.
+
+
+</PRE>
+<H2>SEE ALSO</H2><PRE>
+ <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xsane.1.html">xsane(1)</A></B>, <B><A HREF="sane.7.html">sane(7)</A></B>
+
+
+</PRE>
+<H2>AUTHOR</H2><PRE>
+ This backend has been developped by Stephane Voltz.
+ <I>http://stef.dev.free.fr/sane/rts8891</I>
+
+
+</PRE>
+<H2>CREDITS</H2><PRE>
+ Many thanks go to:
+ Laurent Fournier who donated me a HP4470c. Vladimir Sysoev and
+ "TheUnruly Squash" for the time they spent recording USB activ-
+ ity and testing the experimental version on HP4400 models.
+
+ 8 Dec 2008 <B><A HREF="sane-rts8891.5.html">sane-rts8891(5)</A></B>
+</PRE>
+<HR>
+<ADDRESS>
+Man(1) output converted with
+<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
+</ADDRESS>
+</BODY>
+</HTML>
diff --git a/man/sane-s9036.5.html b/man/sane-s9036.5.html
index 4e60111..9902a2a 100644
--- a/man/sane-s9036.5.html
+++ b/man/sane-s9036.5.html
@@ -83,7 +83,7 @@
Ingo Schneider
-sane-backends 1.0.19 24 Jun 2000 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-sceptre.5.html b/man/sane-sceptre.5.html
index a45cd08..8e01838 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.
<I>http://www.zago.net/sane/#sceptre</I>
-sane-backends 1.0.19 April 21st, 2002 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-scsi.5.html b/man/sane-scsi.5.html
index 373b63b..8a9239b 100644
--- a/man/sane-scsi.5.html
+++ b/man/sane-scsi.5.html
@@ -303,7 +303,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
-sane-backends 1.0.19 28 Oct 2003 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-sharp.5.html b/man/sane-sharp.5.html
index 02ea4b7..4976414 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 <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> by David Mos-
berger-Tang, Andreas Czechanowski and Andreas Bolsch
-sane-backends 1.0.19 21 Nov 2000 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-sm3600.5.html b/man/sane-sm3600.5.html
index ecd9a77..6681209 100644
--- a/man/sane-sm3600.5.html
+++ b/man/sane-sm3600.5.html
@@ -93,7 +93,7 @@
Marian Eichholz (eichholz@computer.org)
Glenn Ramsey (glenn@componic.com)
-sane-backends 1.0.19 16 August 2005 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-sm3840.5.html b/man/sane-sm3840.5.html
index fd036ff..f091eb8 100644
--- a/man/sane-sm3840.5.html
+++ b/man/sane-sm3840.5.html
@@ -45,7 +45,7 @@
<H2>FRONTEND OPTIONS</H2><PRE>
The following options are supported by the sm3840-driver:
- <B>--mode</B> <B>color|gray</B>
+ <B>--mode</B> <B>color|gray|lineart|halftone</B>
Color or grayscale mode.
<B>--resolution</B> <B>150|300|600|1200</B>
@@ -98,7 +98,7 @@
<H2>AUTHOR</H2><PRE>
Earle F. Philhower III (earle@ziplabel.com)
-sane-backends 1.0.19 Mar 15, 2005 <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-snapscan.5.html b/man/sane-snapscan.5.html
index 24a6508..047af41 100644
--- a/man/sane-snapscan.5.html
+++ b/man/sane-snapscan.5.html
@@ -36,8 +36,8 @@
Where <I>special</I> is the path-name for the special device that corresponds
to a SCSI scanner. For SCSI scanners, the special device name must be a
generic SCSI device or a symlink to such a device. Under Linux, such a
- device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See sane-
- <B><A HREF="scsi.5.html">scsi(5)</A></B> for details.
+ device name could be <I>/dev/sga</I> or <I>/dev/sge</I>, for example. See
+ <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> for details.
For USB scanners the devicename must contain the keyword "usb", as in
<I>/dev/usbscanner</I> or <I>/dev/usb/scanner0</I>. For scanners that need a
@@ -114,7 +114,7 @@
Man page by Henning Meier-Geinitz (mostly based on the web pages and
source code).
-sane-backends 1.0.19 26 May 2001 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-sp15c.5.html b/man/sane-sp15c.5.html
index c988939..769c7ea 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.19 17 Apr 2002 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-st400.5.html b/man/sane-st400.5.html
index 8a74d04..6052a82 100644
--- a/man/sane-st400.5.html
+++ b/man/sane-st400.5.html
@@ -153,7 +153,7 @@
<H2>AUTHOR</H2><PRE>
Ingo Wilken &lt;Ingo.Wilken@informatik.uni-oldenburg.de&gt;
-sane-backends 1.0.19 08 Mar 1999 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-stv680.5.html b/man/sane-stv680.5.html
index 28a263b..653455a 100644
--- a/man/sane-stv680.5.html
+++ b/man/sane-stv680.5.html
@@ -162,7 +162,7 @@
pencam2 program
libghoto2 program (camlib stv0680)
-sane-backends 1.0.19 09 June 2006 <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>
+ 11 Jul 2008 <B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-tamarack.5.html b/man/sane-tamarack.5.html
index 5a39bb4..a296401 100644
--- a/man/sane-tamarack.5.html
+++ b/man/sane-tamarack.5.html
@@ -87,7 +87,7 @@
<H2>AUTHOR</H2><PRE>
Roger Wolff
-sane-backends 1.0.19 24 Jun 2000 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-teco1.5.html b/man/sane-teco1.5.html
index 310df0a..987d666 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.19 August 30th, 2002 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-teco2.5.html b/man/sane-teco2.5.html
index 52c192e..3a68bf1 100644
--- a/man/sane-teco2.5.html
+++ b/man/sane-teco2.5.html
@@ -214,7 +214,7 @@
Christoph.Hoeffner for testing the support for the VM3564 (Relisys AVEC
II S3 firmware 1.09).
-sane-backends 1.0.19 29 July 2005 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-teco3.5.html b/man/sane-teco3.5.html
index d0a0453..0879939 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.
<I>http://www.zago.net/sane/#teco3</I>
-sane-backends 1.0.19 25 July 2002 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-test.5.html b/man/sane-test.5.html
index 0f4bc4c..e6b6f19 100644
--- a/man/sane-test.5.html
+++ b/man/sane-test.5.html
@@ -282,7 +282,7 @@
<H2>BUGS</H2><PRE>
- config file values aren't tested for correctness
-sane-backends 1.0.19 2 Jan 2006 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-test.5.html">sane-test(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-u12.5.html b/man/sane-u12.5.html
index 45af32d..43cb741 100644
--- a/man/sane-u12.5.html
+++ b/man/sane-u12.5.html
@@ -128,7 +128,7 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>,
- <I>/usr/doc/sane-1.0.19/u12/U12.changes</I>
+ <I>/usr/doc/sane-1.0.20/u12/U12.changes</I>
<I>http://www.gjaeger.de/scanner/u12/</I>
@@ -159,7 +159,7 @@
* When using libusb, it might be, that the backend hangs. In that
case, reconnect the scanner.
-sane-backends 1.0.19 18 June 2004 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-umax.5.html b/man/sane-umax.5.html
index 209ad90..d13984b 100644
--- a/man/sane-umax.5.html
+++ b/man/sane-umax.5.html
@@ -244,7 +244,7 @@
<H2>EMAIL-CONTACT</H2><PRE>
Oliver.Rauch@Rauch-Domain.DE
-sane-backends 1.0.19 29 november 2002 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-umax1220u.5.html b/man/sane-umax1220u.5.html
index 92c76d0..3b1123b 100644
--- a/man/sane-umax1220u.5.html
+++ b/man/sane-umax1220u.5.html
@@ -21,8 +21,8 @@
The <B>sane-umax1220</B> library implements a SANE (Scanner Access Now Easy)
backend for the the UMAX Astra 1220U and similar scanners.
- For more information on this backend, please visit <I>http://umax1220u-</I>
- <I>sane.sourceforge.net/</I>.
+ For more information on this backend, please visit
+ <I>http://umax1220u-sane.sourceforge.net/</I>.
</PRE>
@@ -130,7 +130,7 @@
bugs, please run the backend with SANE_DEBUG_UMAX1220U set to 10 and
attach a copy of the log messages.
-sane-backends 1.0.19 17 Apr 2006 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-umax_pp.5.html b/man/sane-umax_pp.5.html
index d56b2ab..e8ef2a9 100644
--- a/man/sane-umax_pp.5.html
+++ b/man/sane-umax_pp.5.html
@@ -115,8 +115,8 @@
names that correspond to Umax scanners. Empty lines and lines starting
with a hash mark (#) are ignored.
- The height options supported are <B>red-gain</B>, <B>green-gain</B>, <B>blue-gain</B>, <B>red-</B>
- <B>offset</B>, <B>green-offset</B>, <B>blue-offset</B>, <B>astra</B>, and <B>buffer</B>.
+ The eight options supported are <B>red-gain</B>, <B>green-gain</B>, <B>blue-gain</B>,
+ <B>red-offset</B>, <B>green-offset</B>, <B>blue-offset</B>, <B>astra</B>, and <B>buffer</B>.
Options <B>red-gain</B> , <B>green-gain</B> and <B>blue-gain</B> allow you to adjust the
sensitivy of your scanner for the given color. Values range from 0
@@ -216,7 +216,7 @@
</PRE>
<H2>AUTHOR</H2><PRE>
- St?phane VOLTZ &lt;stef.dev@free.fr&gt;
+ Stephane VOLTZ &lt;stef.dev@free.fr&gt;
</PRE>
@@ -250,7 +250,7 @@
better), or you think I should know something, please include
it.
-sane-backends 1.0.19 23 August 2004 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-usb.5.html b/man/sane-usb.5.html
index b8b538b..e1318cc 100644
--- a/man/sane-usb.5.html
+++ b/man/sane-usb.5.html
@@ -37,7 +37,7 @@
and product ids, you are done. See section <B>SANE</B> <B>ISSUES</B> for details on
how to go on.
- Sane-find-scanner doesn't list your scanner? Does it work as root? If
+ sane-find-scanner doesn't list your scanner? Does it work as root? If
yes, there is a permission issue. See the <B>LIBUSB</B> section for details.
Nothing is found even as root? Check that your kernel supports USB and
@@ -84,7 +84,7 @@
which support dynamic setting of access permissions. SANE comes with
udev and hotplug scripts in the directory tools/udev and tools/hotplug.
They can be used for setting permissions, see
- /usr/doc/sane-1.0.19/README.linux, tools/README and the README in the
+ /usr/doc/sane-1.0.20/README.linux, tools/README and the README in the
tools/hotplug directory for more details.
For the <B>BSDs</B>, the device files used by libusb are named <I>/dev/ugen*</I>.
@@ -151,7 +151,7 @@
<H2>AUTHOR</H2><PRE>
Henning Meier-Geinitz &lt;henning@meier-geinitz.de&gt;
-sane-backends 1.0.19 19 Jun 2006 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-v4l.5.html b/man/sane-v4l.5.html
index f510935..49bf496 100644
--- a/man/sane-v4l.5.html
+++ b/man/sane-v4l.5.html
@@ -95,9 +95,9 @@
<H2>BUGS:</H2><PRE>
If more than one video card is present, a crash may occur. Frequency
and geometry selection is missing.
- Send bug reports to the SANE mailing list: sane-
- devel@lists.alioth.debian.org. You must be subscribed to the list to
- send mail. See http://www.sane-project.org/mailing-lists.html for
+ Send bug reports to the SANE mailing list:
+ sane-devel@lists.alioth.debian.org. You must be subscribed to the list
+ to send mail. See http://www.sane-project.org/mailing-lists.html for
details.
@@ -105,7 +105,7 @@
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>.
-sane-backends 1.0.19 28 Aug 2002 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
+ 14 Jul 2008 <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
</PRE>
<HR>
<ADDRESS>
diff --git a/man/sane-xerox_mfp.5.html b/man/sane-xerox_mfp.5.html
new file mode 100644
index 0000000..53a684e
--- /dev/null
+++ b/man/sane-xerox_mfp.5.html
@@ -0,0 +1,75 @@
+<HTML>
+<HEAD>
+<TITLE>sane-xerox_mfp.5</TITLE>
+</HEAD>
+<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
+<H1>sane-xerox_mfp.5</H1>
+<HR>
+<PRE>
+<!-- Manpage converted by man2html 3.0.1 -->
+<B><A HREF="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B>
+
+
+</PRE>
+<H2>NAME</H2><PRE>
+ sane-xerox_mfp - SANE backend for Xerox Phaser 3200MFP device
+
+
+</PRE>
+<H2>DESCRIPTION</H2><PRE>
+ The <B>sane-xerox_mfp</B> library implements a SANE (Scanner Access Now Easy)
+ backend that provides access to the following Xerox USB multifunction-
+ peripheral:
+
+ Phaser 3200MFP
+
+ If you own a scanner other than the ones listed above that works with
+ this backend, please let us know this by sending the scanner's exact
+ model name and the USB vendor and device ids (e.g. from
+ <I>/proc/bus/usb/devices</I>, <I>sane-find-scanner</I> or syslog) to us. Even if the
+ scanner's name is only slightly different from the models mentioned
+ above, please let us know.
+
+
+</PRE>
+<H2>CONFIGURATION</H2><PRE>
+ None required.
+
+
+</PRE>
+<H2>FILES</H2><PRE>
+ <I>/usr/lib/sane/libsane-xerox</I><B>_</B><I>mfp.a</I>
+ The static library implementing this backend.
+
+ <I>/usr/lib/sane/libsane-xerox</I><B>_</B><I>mfp.so</I>
+ The shared library implementing this backend (present on systems
+ that support dynamic loading).
+
+
+</PRE>
+<H2>ENVIRONMENT</H2><PRE>
+ <B>SANE_DEBUG_XEROX_MFP</B> 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_XEROX_MFP=4
+
+
+</PRE>
+<H2>SEE ALSO</H2><PRE>
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>,
+
+
+</PRE>
+<H2>AUTHOR</H2><PRE>
+ Alex Belkin &lt;abc@telekom.ru&gt;
+
+ 15 Dec 2008 <B><A HREF="sane-xerox_mfp.5.html">sane-xerox_mfp(5)</A></B>
+</PRE>
+<HR>
+<ADDRESS>
+Man(1) output converted with
+<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
+</ADDRESS>
+</BODY>
+</HTML>
diff --git a/man/scanimage.1.html b/man/scanimage.1.html
index 3bbb8e2..66f3f93 100644
--- a/man/scanimage.1.html
+++ b/man/scanimage.1.html
@@ -22,7 +22,7 @@
[<B>--batch</B> [=<I>format</I>]] [<B>--batch-start</B> <I>start</I>] [<B>--batch-count</B> <I>count</I>]
[<B>--batch-increment</B> <I>increment</I>] [<B>--batch-double</B>] [<B>--accept-md5-only</B>]
[<B>-p</B>|<B>--progress</B>] [<B>-n</B>|<B>--dont-scan</B>] [<B>-T</B>|<B>--test</B>] [<B>-h</B>|<B>--help</B>] [<B>-v</B>|<B>--verbose</B>]
- [<B>-B</B>|<B>--buffersize</B>] [<B>-V</B>|<B>--version</B>] [<I>device-specific-options</I>]
+ [<B>-B</B>|<B>--buffer-size</B> [=<I>size</I>]] [<B>-V</B>|<B>--version</B>] [<I>device-specific-options</I>]
</PRE>
@@ -62,8 +62,8 @@
</PRE>
<H2>OPTIONS</H2><PRE>
Parameters are separated by a blank from single-character options (e.g.
- -d epson) and by a "=" from multi-character options (e.g. --device-
- name=epson).
+ -d epson) and by a "=" from multi-character options (e.g.
+ --device-name=epson).
The <B>-d</B> or <B>--device-name</B> options must be followed by a <B>SANE</B> device-name
like '<I>epson:/dev/sg0</I>' or '<I>hp:/dev/usbscanner0</I>'. A (partial) list of
@@ -89,146 +89,147 @@
full device name. You may need to consult your system administrator to
find out the names of such devices.
- The <B>-f</B> or <B>--formatted-device-list</B> option works similar to <B>--list-</B>
- <B>devices</B>, but requires a format string. <B>scanimage</B> replaces the place-
- holders <B>%d</B> <B>%v</B> <B>%m</B> <B>%t</B> <B>%i</B> with the device name, vendor name, model name,
- scanner type and an index number respectively. The command
+ The <B>-f</B> or <B>--formatted-device-list</B> option works similar to
+ <B>--list-devices</B>, but requires a format string. <B>scanimage</B> replaces the
+ placeholders <B>%d</B> <B>%v</B> <B>%m</B> <B>%t</B> <B>%i</B> <B>%n</B> with the device name, vendor name, model
+ name, scanner type, an index number and newline respectively. The com-
+ mand
- <B>scanimage</B> <B>-f</B> <I>"</I> <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
+ <B>scanimage</B> <B>-f</B> <I>"</I> <I>scanner</I> <I>number</I> <I>%i</I> <I>device</I> <I>%d</I> <I>is</I> <I>a</I> <I>%t,</I> <I>model</I> <I>%m,</I>
<I>produced</I> <I>by</I> <I>%v</I> <I>"</I>
will produce something like:
- scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
+ scanner number 0 device sharp:/dev/sg1 is a flatbed scanner,
model JX250 SCSI, produced by SHARP
- The <B>--batch*</B> options provide the features for scanning documents using
- document feeders. <B>--batch</B> [<I>format</I>] is used to specify the format of
- the filename that each page will be written to. Each page is written
- out to a single file. If <I>format</I> is not specified, the default of
- out%d.pnm (or out%d.tif for --format tiff) will be used. <I>format</I> is
- given as a printf style string with one integer parameter. <B>--batch-</B>
- <B>start</B> <I>start</I> selects the page number to start naming files with. If this
- option is not given, the counter will start at 0. <B>--batch-count</B> <I>count</I>
- specifies the number of pages to attempt to scan. If not given, scan-
- image will continue scanning until the scanner returns a state other
- than OK. Not all scanners with document feeders signal when the ADF is
- empty, use this command to work around them. With <B>--batch-increment</B>
- <I>increment</I> you can change the amount that the number in the filename is
- incremented by. Generally this is used when you are scanning double-
- sided documents on a single-sided document feeder. A specific command
- is provided to aid this: <B>--batch-double</B> will automatically set the
- increment to 2. <B>--batch-prompt</B> will ask for pressing RETURN before
- scanning a page. This can be used for scanning multiple pages without
- an automatic document feeder.
-
- The <B>--accept-md5-only</B> option only accepts user authorization requests
- that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
+ The <B>--batch*</B> options provide the features for scanning documents using
+ document feeders. <B>--batch</B> [<I>format</I>] is used to specify the format of
+ the filename that each page will be written to. Each page is written
+ out to a single file. If <I>format</I> is not specified, the default of
+ out%d.pnm (or out%d.tif for --format tiff) will be used. <I>format</I> is
+ given as a printf style string with one integer parameter.
+ <B>--batch-start</B> <I>start</I> selects the page number to start naming files with.
+ If this option is not given, the counter will start at 0.
+ <B>--batch-count</B> <I>count</I> specifies the number of pages to attempt to scan.
+ If not given, scanimage will continue scanning until the scanner
+ returns a state other than OK. Not all scanners with document feeders
+ signal when the ADF is empty, use this command to work around them.
+ With <B>--batch-increment</B> <I>increment</I> you can change the amount that the
+ number in the filename is incremented by. Generally this is used when
+ you are scanning double-sided documents on a single-sided document
+ feeder. A specific command is provided to aid this: <B>--batch-double</B>
+ will automatically set the increment to 2. <B>--batch-prompt</B> will ask for
+ pressing RETURN before scanning a page. This can be used for scanning
+ multiple pages without an automatic document feeder.
+
+ The <B>--accept-md5-only</B> option only accepts user authorization requests
+ that support MD5 security. The <B>SANE</B> network daemon (<B>saned</B>) is capable
of doing such requests. See <B><A HREF="saned.8.html">saned(8)</A></B>.
- The <B>-p</B> or <B>--progress</B> option requests that <B>scanimage</B> prints a progress
- counter. It shows how much image data of the current image has already
+ The <B>-p</B> or <B>--progress</B> option requests that <B>scanimage</B> prints a progress
+ counter. It shows how much image data of the current image has already
been received by <B>scanimage</B> (in percent).
- The <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> only sets the
- options provided by the user but doesn't actually perform a scan. This
+ The <B>-n</B> or <B>--dont-scan</B> option requests that <B>scanimage</B> only sets the
+ options provided by the user but doesn't actually perform a scan. This
option can be used to e.g. turn off the scanner's lamp (if supported by
the backend).
- The <B>-T</B> or <B>--test</B> option requests that <B>scanimage</B> performs a few simple
- sanity tests to make sure the backend works as defined by the <B>SANE</B> API
+ The <B>-T</B> or <B>--test</B> option requests that <B>scanimage</B> performs a few simple
+ sanity tests to make sure the backend works as defined by the <B>SANE</B> API
(in particular the <B>sane_read</B> function is exercised by this test).
- The <B>-h</B> or <B>--help</B> options request help information. The information is
+ The <B>-h</B> or <B>--help</B> options request help information. The information is
printed on standard output and in this case, no attempt will be made to
acquire an image.
- The <B>-v</B> or <B>--verbose</B> options increase the verbosity of the operation of
- <B>scanimage.</B> The option may be specified repeatedly, each time increas-
+ The <B>-v</B> or <B>--verbose</B> options increase the verbosity of the operation of
+ <B>scanimage.</B> The option may be specified repeatedly, each time increas-
ing the verbosity level.
- The <B>-B</B> or <B>--buffersize</B> option changes the input buffersize that <B>scanim-</B>
- <B>age</B> uses from default 32*1024 to 1024*1024 kbytes.
+ The <B>-B</B> or <B>--buffer-size</B> changes the input buffer size from 32KB to the
+ number kB specified or 1M.
- The <B>-V</B> or <B>--version</B> option requests that <B>scanimage</B> prints the program
- and package name, the version number of the <B>SANE</B> distribution that it
- came with and the version of the backend that it loads. Usually that's
- the dll backend. If more information about the version numbers of the
- backends are necessary, the <B>DEBUG</B> variable for the dll backend can be
+ The <B>-V</B> or <B>--version</B> option requests that <B>scanimage</B> prints the program
+ and package name, the version number of the <B>SANE</B> distribution that it
+ came with and the version of the backend that it loads. Usually that's
+ the dll backend. If more information about the version numbers of the
+ backends are necessary, the <B>DEBUG</B> variable for the dll backend can be
used. Example: SANE_DEBUG_DLL=3 scanimage -L.
- As you might imagine, much of the power of <B>scanimage</B> comes from the
+ As you might imagine, much of the power of <B>scanimage</B> comes from the
fact that it can control any <B>SANE</B> backend. Thus, the exact set of com-
- mand-line options depends on the capabilities of the selected device.
- To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a com-
+ mand-line options depends on the capabilities of the selected device.
+ To see the options for a device named <I>dev</I>, invoke <B>scanimage</B> via a com-
mand-line of the form:
<B>scanimage</B> <B>--help</B> <B>--device-name</B> <I>dev</I>
- The documentation for the device-specific options printed by <B>--help</B> is
+ The documentation for the device-specific options printed by <B>--help</B> is
best explained with a few examples:
-l 0..218mm [0]
Top-left x position of scan area.
- The description above shows that option <B>-l</B> expects an option
+ The description above shows that option <B>-l</B> expects an option
value in the range from 0 to 218 mm. The value in square brack-
- ets indicates that the current option value is 0 mm. Most back-
- ends provide similar geometry options for top-left y position
+ ets indicates that the current option value is 0 mm. Most back-
+ ends provide similar geometry options for top-left y position
(-t), width (-x) and height of scan-area (-y).
--brightness -100..100% [0]
Controls the brightness of the acquired image.
- The description above shows that option <B>--brightness</B> expects an
- option value in the range from -100 to 100 percent. The value
- in square brackets indicates that the current option value is 0
+ The description above shows that option <B>--brightness</B> expects an
+ option value in the range from -100 to 100 percent. The value
+ in square brackets indicates that the current option value is 0
percent.
--default-enhancements
Set default values for enhancement controls.
- The description above shows that option <B>--default-enhancements</B>
+ The description above shows that option <B>--default-enhancements</B>
has no option value. It should be thought of as having an imme-
- diate effect at the point of the command-line at which it
+ diate effect at the point of the command-line at which it
appears. For example, since this option resets the <B>--brightness</B>
- option, the option-pair <B>--brightness</B> <B>50</B> <B>--default-enhancements</B>
+ option, the option-pair <B>--brightness</B> <B>50</B> <B>--default-enhancements</B>
would effectively be a no-op.
--mode Lineart|Gray|Color [Gray]
Selects the scan mode (e.g., lineart or color).
- The description above shows that option <B>--mode</B> accepts an argu-
- ment that must be one of the strings <B>Lineart</B>, <B>Gray</B>, or <B>Color</B>.
- The value in the square bracket indicates that the option is
+ The description above shows that option <B>--mode</B> accepts an argu-
+ ment that must be one of the strings <B>Lineart</B>, <B>Gray</B>, or <B>Color</B>.
+ The value in the square bracket indicates that the option is
currently set to <B>Gray</B>. For convenience, it is legal to abbrevi-
- ate the string values as long as they remain unique. Also, the
- case of the spelling doesn't matter. For example, option set-
+ ate the string values as long as they remain unique. Also, the
+ case of the spelling doesn't matter. For example, option set-
ting <B>--mode</B> <B>col</B> is identical to <B>--mode</B> <B>Color</B>.
--custom-gamma[=(yes|no)] [inactive]
Determines whether a builtin or a custom gamma-table
should be used.
- The description above shows that option <B>--custom-gamma</B> expects
+ The description above shows that option <B>--custom-gamma</B> expects
either no option value, a "yes" string, or a "no" string. Spec-
- ifying the option with no value is equivalent to specifying
- "yes". The value in square-brackets indicates that the option
- is not currently active. That is, attempting to set the option
- would result in an error message. The set of available options
- typically depends on the settings of other options. For exam-
- ple, the <B>--custom-gamma</B> table might be active only when a
+ ifying the option with no value is equivalent to specifying
+ "yes". The value in square-brackets indicates that the option
+ is not currently active. That is, attempting to set the option
+ would result in an error message. The set of available options
+ typically depends on the settings of other options. For exam-
+ ple, the <B>--custom-gamma</B> table might be active only when a
grayscale or color scan-mode has been requested.
- Note that the <B>--help</B> option is processed only after all other
- options have been processed. This makes it possible to see the
- option settings for a particular mode by specifying the appro-
- priate mode-options along with the <B>--help</B> option. For example,
+ Note that the <B>--help</B> option is processed only after all other
+ options have been processed. This makes it possible to see the
+ option settings for a particular mode by specifying the appro-
+ priate mode-options along with the <B>--help</B> option. For example,
the command-line:
<B>scanimage</B> <B>--help</B> <B>--mode</B> <I>color</I>
- would print the option settings that are in effect when the
+ would print the option settings that are in effect when the
color-mode is selected.
--gamma-table 0..255,...
@@ -236,23 +237,23 @@
equally affects the red, green, and blue channels
simultaneously (i.e., it is an intensity gamma table).
- The description above shows that option <B>--gamma-table</B> expects
+ The description above shows that option <B>--gamma-table</B> expects
zero or more values in the range 0 to 255. For example, a legal
- value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
- it's cumbersome to specify long vectors in this form, the same
- can be expressed by the abbreviated form "[0]3-[9]12". What
- this means is that the first vector element is set to 3, the
+ value for this option would be "3,4,5,6,7,8,9,10,11,12". Since
+ it's cumbersome to specify long vectors in this form, the same
+ can be expressed by the abbreviated form "[0]3-[9]12". What
+ this means is that the first vector element is set to 3, the
9-th element is set to 12 and the values in between are interpo-
- lated linearly. Of course, it is possible to specify multiple
- such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
- is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
- <B>gamma4scanimage</B> can be used to generate such gamma tables (see
+ lated linearly. Of course, it is possible to specify multiple
+ such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6"
+ is equivalent to "3,3,3,4,5,6,7,10,8,6". The program
+ <B>gamma4scanimage</B> can be used to generate such gamma tables (see
<B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B> for details).
--filename &lt;string&gt; [/tmp/input.ppm]
The filename of the image to be loaded.
- The description above is an example of an option that takes an
+ The description above is an example of an option that takes an
arbitrary string value (which happens to be a filename). Again,
the value in brackets show that the option is current set to the
filename <B>/tmp/input.ppm</B>.
@@ -267,7 +268,7 @@
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/sane.d</I>
- This directory holds various configuration files. For details,
+ This directory holds various configuration files. For details,
please refer to the manual pages listed below.
<I>~/.sane/pass</I>
@@ -275,9 +276,9 @@
user:password:resource
- scanimage uses this information to answer user authorization
- requests automatically. The file must have 0600 permissions or
- stricter. You should use this file in conjunction with the
+ scanimage uses this information to answer user authorization
+ requests automatically. The file must have 0600 permissions or
+ stricter. You should use this file in conjunction with the
--accept-md5-only option to avoid server-side attacks. The
resource may contain any character but is limited to 127 charac-
ters.
@@ -285,23 +286,23 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
- <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B>xcam(1)</B>, <B>xsane(1)</B>,
+ <B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="gamma4scanimage.1.html">gamma4scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B>xcam(1)</B>, <B>xsane(1)</B>,
<B><A HREF="scanadf.1.html">scanadf(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B>sane-"backendname"</B>(5)
</PRE>
<H2>AUTHOR</H2><PRE>
- David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
- many others. For questions and comments contact the sane-devel mail-
+ David Mosberger, Andreas Beck, Gordon Matzigkeit, Caskey Dickson, and
+ many others. For questions and comments contact the sane-devel mail-
inglist (see http://www.sane-project.org/mailing-lists.html).
</PRE>
<H2>BUGS</H2><PRE>
- For vector options, the help output currently has no indication as to
+ For vector options, the help output currently has no indication as to
how many elements a vector-value should have.
-sane-backends 1.0.19 03 Oct 2006 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
+ 10 Jul 2008 <B><A HREF="scanimage.1.html">scanimage(1)</A></B>
</PRE>
<HR>
<ADDRESS>