This should really be fixed (no pun intended) as soon as possible, but I just don't know/care enough about fixed-point representationĪnd roundoff errors to do this correctly. Symptoms of theseĮrrors are skewed images. There are minor roundoff errors when adjusting the ranges, since PINT uses units of 1/1200 of an inch, and SANE normally uses millimeters. Gordon Matzigkeit, adapted from existing backends written by David Mosberger. E.g., a value of 128 requestsĪll debug output to be printed. SANE_DEBUG_PINT If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result inĭirectories "tmp/config", ".", and "/etc/sane.d" being searched (in this order).
If the value of the environment variable ends with the directory separator character, then theĭefault directories are searched after the explicitly specified directories. The current working directory (".") and then in /etc/sane.d. If this variable is not set, the configuration file is searched in two default directories: first, (':'), under OS/2, they are separated by a semi-colon (' '). Under UNIX, the directories are separated by a colon SANE_CONFIG_DIR This environment variable specifies the list of directories that may contain the configuration file. usr/lib*/sane/libsane-pint.so The shared library implementing this backend (present on systems that support dynamic loading). usr/lib*/sane/libsane-pint.a The static library implementing this backend. etc/sane.d/nf The backend configuration file (see also description of SANE_CONFIG_DIR below). A sample configuration file is shown below: Empty lines and lines starting with a hash mark (#)Īre ignored. file is a list of device names that correspond to PINT scanners. For example, under NetBSD or OpenBSD, such a device name could be /dev/ss0 or /dev/scan0. The special device name must be a PINT device or a Special Where special is the UNIX path-name for the special device that corresponds to the scanner. This backend expects device names of the form: The relevant information for your scanner to Have a look at
TWAIN SANE INTERFACE DRIVER
If have successfully used the PINT driver with your scanner, but it does not work using this SANE backend, please let us know. Single-pass scanners, and more work will probably be required to get it to use other scanner types successfully. However, this backend has only been tested with flatbed PINT is designed to provide an ioctl(2) interface to many different scanner types. The PINT driver is being actively developed on the OpenBSD platform, and has been ported to a few other *nix-like The sane-pint library implements a SANE (Scanner Access Now Easy) backend that provides generic access to hand-held and flatbed scanners using the
0 kommentar(er)
