Issues in SANE man pages
Dear SANE maintainer, the manpage-l10n project maintains a large number of translations of man pages both from a large variety of sources (including SANE) as well for a large variety of target languages.
During their work translators notice different possible issues in the original (english) man pages. Sometimes this is a straightforward typo, sometimes a hard to read sentence, sometimes this is a convention not held up and sometimes we simply do not understand the original.
We use several distributions as sources and update regularly (at least every 2 month). This means we are fairly recent (some distributions like archlinux also update frequently) but might miss the latest upstream version once in a while, so the error might be already fixed. We apologize and ask you to close the issue immediately if this should be the case, but given the huge volume of projects and the very limited number of volunteers we are not able to double check each and every issue.
Secondly we translators see the manpages in the neutral po format, i.e. converted and harmonized, but not the original source (be it man, groff, xml or other). So we cannot provide a true patch (where possible), but only an approximation which you need to convert into your source format.
Finally the issues I'm reporting have accumulated over time and are not always discovered by me, so sometimes my description of the problem my be a bit limited - do not hesitate to ask so we can clarify them.
I'm now reporting the errors for your project. If future reports should use another channel, please let me know.
Man page: gamma4scanimage.1
Issue: maxin → B<maxin>
"B<highlight> defines the maximum input value that produces an output value "
"smaller than maxout. highlight has to be in the range [0..maxin], highlight "
"has to be larger than shadow. Its default value is the same as maxin (16383 "
"if not set)."
--
Man page: gamma4scanimage.1
Issue 1: maxin→ B<maxin>
Issue 2: scanimage → B<scanimage>
"B<maxin> defines the size of the gamma table. The size depends on the "
"scanner/backend. If the scanner uses 8 bits gamma input then maxin has to "
"be set to 255, for 10 bits 1023, for 12 bits 4095, for 14 bits 16383. The "
"default is 16383. To find out what value maxin has to be call scanimage "
"with a very large gamma table [0]0-[99999]255 then scanimage prints an error "
"message with the needed size of the gamma table."
--
Man page: gamma4scanimage.1
Issue 1: scanimage -h → B<scanimage -h>
Issue 2: maxout → B<maxout>
"B<maxout> defines the maximum output value. Take a look at the output of "
"scanimage -h to find out what maxout has to be. The default value is 255."
--
Man page: sane.7
Issue 1: Why citation of already formatted terms?
Issue 2: B<scanimage> → B<scanimage>(1)
Issue 3: B<xscanimage> → B<xscanimage>(1)
Issue 4: B<xcam> → B<xcam>(1)
Issue 5: B<scanadf> → B<scanadf>(1)
"The package `B<sane-backends>' contains a lot of backends, documentation, "
"networking support, and the command line frontend `B<scanimage>'. The "
"frontends `B<xscanimage>', `B<xcam>', and `B<scanadf>' are included in the "
"package `B<sane-frontends>'. Both packages can be downloaded from the "
"B<SANE> homepage (I<http://www.sane-project.org/>). Information about other "
"frontends and backends can also be found on the B<SANE> homepage."
msgstr ""
--
Man page: sane.7
Issue: /usr/share/doc/sane-backends/ → I</usr/share/doc/sane-backends/>
"The B<SANE> device lists contain information about the status of B<SANE> "
"support for a specific device. If your scanner is not listed there (either "
"supported or unsupported), please contact us. See section HOW CAN YOU HELP "
"SANE for details. There are lists for specific releases of SANE, for the "
"current development version and a search engine: I<http://www.sane-project."
"org/sane-supported-devices.html>. The lists are also installed on your "
"system at /usr/share/doc/sane-backends/."
--
Man page: sane.7
Issue: Unix → UNIX
"Command-line tool to find SCSI and USB scanners and determine their Unix "
"device files. See B<sane-find-scanner>(1)."
--
Man page: sane.7
Issue: artec_eplus48u → I<artec_eplus48u>
"The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and re-"
"badged models like Tevion MD 9693, Medion MD 9693, Medion MD 9705 and Trust "
"Easy Webscan 19200. See B<sane-artec_eplus48u>(5) for details."
--
Man page: sane.7
Issue: bh → I<bh>
"The bh backend provides access to Bell+Howell Copiscan II series document "
"scanners. See B<sane-bh>(5) for details."
--
Man page: sane.7
Issue: canon → I<canon>
"The canon backend supports the CanoScan 300, CanoScan 600, and CanoScan "
"2700F SCSI flatbed scanners. See B<sane-canon>(5) for details."
--
Man page: sane.7
Issue: canon630u → I<canon630u>
"The canon630u backend supports the CanoScan 630u and 636u USB scanners. See "
"B<sane-canon630u>(5) for details."
--
Man page: sane.7
Issue: canon_dr → I<canon_dr>
"The canon_dr backend supports the Canon DR-Series ADF SCSI and USB scanners. "
"See B<sane-canon_dr>(5) for details."
--
Man page: sane.7
Issue: canon_lide70 → I<canon_lide70>
"The canon_lide70 backend supports the CanoScan LiDE 70 USB scanner. See "
"B<sane-canon_lide70>(5) for details."
--
Man page: sane.7
Issue: canon_pp → I<canon_pp>
"The canon_pp backend supports the CanoScan FB330P, FB630P, N340P and N640P "
"parallel port scanners. See B<sane-canon_pp>(5) for details."
--
Man page: sane.7
Issue: coolscan3 is missing here
"This is a SANE backend for Nikon Coolscan film-scanners. See B<sane-"
"coolscan2>(5) for details."
--
Man page: sane.7
Issue: epjitsu → I<epjitsu>
"The epjitsu backend provides support for Epson-based Fujitsu USB scanners. "
"See B<sane-epjitsu>(5) for details."
--
Man page: sane.7
Issue: epson → I<epson>
"The SANE epson backend provides support for Epson SCSI, parallel port and "
"USB flatbed scanners. See B<sane-epson>(5) for details."
--
Man page: sane.7
Issue: fujitsu → I<fujitsu>
"The fujitsu backend provides support for most Fujitsu SCSI and USB, flatbed "
"and adf scanners. See B<sane-fujitsu>(5) for details."
--
Man page: sane.7
Issue 1: genesys → I<genesys>
Issue 2: forced line breaks due to overlong lines in source code
"The genesys backend provides support for several scanners based on the Genesys Logic\n"
"GL646, GL841, GL843, GL847 and GL124 chips like the Medion 6471 and Hewlett-Packard 2300c.\n"
" See\n"
"B<sane-genesys>(5)\n"
"for details.\n"
--
Man page: sane.7
Issue: gt68xx → I<gt68xx>
"The gt68xx backend provides support for scanners based on the Grandtech "
"GT-6801 and GT-6816 chips like the Artec Ultima 2000 and several Mustek "
"BearPaw CU and TA models. Some Genius, Lexmark, Medion, Packard Bell, "
"Plustek, and Trust scanners are also supported. See B<sane-gt68xx>(5) for "
"details."
--
Man page: sane.7
Issue: hp → I<hp>
"The SANE hp backend provides access to Hewlett-Packard ScanJet scanners "
"which support SCL (Scanner Control Language by HP). See B<sane-hp>(5) for "
"details."
--
Man page: sane.7
Issue: Leo/LEO?
"This backend supports the Leo S3 and the Across FS-1130, which is a re-"
"badged LEO FS-1130 scanner. See B<sane-leo>(5) for details."
--
Man page: sane.7
Issue: ma1509 → I<ma1509>
"The ma1509 backend supports the Mustek BearPaw 1200F USB flatbed scanner. "
"See B<sane-ma1509>(5) for details."
--
Man page: sane.7
Issue: magicolor → I<magicolor>
"The magicolor backend supports the KONICA MINOLTA magicolor 1690MF multi-"
"function printer/scanner/fax. See B<sane-magicolor>(5) for details."
--
Man page: sane.7
Issue: microtek → I<microtek>
"The microtek backend provides access to the \"second generation\" Microtek "
"scanners with SCSI-1 command set. See B<sane-microtek>(5) for details."
--
Man page: sane.7
Issue: microtek2 → I<microtek2>
"The microtek2 backend provides access to some Microtek scanners with a "
"SCSI-2 command set. See B<sane-microtek2>(5) for details."
--
Man page: sane.7
Issue: mustek → I<mustek>
"The SANE mustek backend supports most Mustek SCSI flatbed scanners including "
"the Paragon and ScanExpress series and the 600 II N and 600 II EP (non-"
"SCSI). Some Trust scanners are also supported. See B<sane-mustek>(5) for "
"details."
--
Man page: sane.7
Issue: mustek_pp → I<mustek_pp>
"The mustek_pp backend provides access to Mustek parallel port flatbed "
"scanners. See B<sane-mustek_pp>(5) for details."
--
Man page: sane.7
Issue: mustek_usb → I<mustek_usb>
"The mustek_usb backend provides access to some Mustek ScanExpress USB "
"flatbed scanners. See B<sane-mustek_usb>(5) for details."
--
Man page: sane.7
Issue: mustek_usb2 → I<mustek_usb2>
"The mustek_usb2 backend provides access to scanners using the SQ113 chipset "
"like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See B<sane-"
"mustek_usb2>(5) for details."
--
Man page: sane.7
Issue: nec → I<nec>
"The SANE nec backend supports the NEC PC-IN500/4C SCSI scanner. See B<sane-"
"nec>(5) for details."
--
Man page: sane.7
Issue: niash → I<niash>
"The niash backend supports the Agfa Snapscan Touch and the HP ScanJet 3300c, "
"3400c, and 4300c USB flatbed scanners. See B<sane-niash>(5) for details."
--
Man page: sane.7
Issue: pie → I<pie>
"The pie backend provides access to Pacific Image Electronics (PIE) and "
"Devcom SCSI flatbed scanners. See B<sane-pie>(5) for details."
--
Man page: sane.7
Issue: pixma → I<pixma>
"The pixma backend supports Canon PIXMA MP series (multi-function devices), "
"Canon imageCLASS series (laser devices), Canon MAXIFY series and some Canon "
"CanoScan series. See B<sane-pixma>(5) for details."
--
Man page: sane.7
Issue: plustek → I<plustek>
"The SANE plustek backend supports USB flatbed scanners that use the National "
"Semiconductor LM983[1/2/3] chipset aka Merlin. Scanners using this LM983x "
"chips include some models from Plustek, KYE/Genius, Hewlett-Packard, Mustek, "
"Umax, Epson, and Canon. See B<sane-plustek>(5) for details."
--
Man page: sane.7
Issue: plustek_pp → I<plustek_pp>
"The SANE plustek_pp backend supports Plustek parallel port flatbed "
"scanners. Scanners using the Plustek ASIC P96001, P96003, P98001 and P98003 "
"include some models from Plustek, KYE/Genius, Primax. See B<sane-"
"plustek_pp>(5) for details."
--
Man page: sane.7
Issue: ricoh → I<ricoh>
"The ricoh backend provides access to the following Ricoh flatbed scanners: "
"IS50 and IS60. See B<sane-ricoh>(5) for details."
--
Man page: sane.7
Issue: ricoh2 → I<ricoh2>
"The ricoh2 backend provides access to the following Ricoh flatbed scanners: "
"SG-3100SNw, SP-100SU, and SP-111SU. See B<sane-ricoh2>(5) for details."
--
Man page: sane.7
Issue: s9036 → I<s9036>
"The s9036 backend provides access to Siemens 9036 flatbed scanners. See "
"B<sane-s9036>(5) for details."
--
Man page: sane.7
Issue: sceptre → I<sceptre>
"The sceptre backend provides access to the Sceptre S1200 flatbed scanner. "
"See B<sane-sceptre>(5) for details."
--
Man page: sane.7
Issue: sharp → I<sharp>
"The SANE sharp backend supports Sharp SCSI scanners. See B<sane-sharp>(5) "
"for details."
--
Man page: sane.7
Issue: sm3600 → I<sm3600>
"The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB scanner. "
"See B<sane-sm3600>(5) for details."
--
Man page: sane.7
Issue: sm3840 → I<sm3840>
"The SANE sm3840 backend supports the Microtek ScanMaker 3840 USB scanner. "
"See B<sane-sm3840>(5) for details."
--
Man page: sane.7
Issue: snapscan → I<snapscan>
"The snapscan backend supports AGFA SnapScan flatbed scanners. See B<sane-"
"snapscan>(5) for details."
--
Man page: sane.7
Issue: sane-st400 → I<sane-st400>
"The sane-st400 backend provides access to Siemens ST400 and ST800. See "
"B<sane-st400>(5) for details."
--
Man page: sane.7
Issue: tamarack → I<tamarack>
"The SANE tamarack backend supports Tamarack Artiscan flatbed scanners. See "
"B<sane-tamarack>(5) for details."
--
Man page: sane.7
Issue: teco1, teco2 and teco3 → I<teco1>, I<teco2> and I<teco3>
"The SANE teco1, teco2 and teco3 backends support some TECO scanners, usually "
"sold under the Relisys, Trust, Primax, Piotech, Dextra names. See B<sane-"
"teco1>(5), B<sane-teco2>(5) and B<sane-teco3>(5) for details."
--
Man page: sane.7
Issue: sane-u12 → I<sane-u12>
"The sane-u12 backend provides USB flatbed scanners based on Plustek's ASIC "
"98003 (parallel-port ASIC) and a GeneSys Logics' USB-parport bridge chip "
"like the Plustek OpticPro U(T)12. See B<sane-u12>(5) for details."
--
Man page: sane.7
Issue: sane-umax → I<sane-umax>
"The sane-umax backend provides access to several UMAX-SCSI-scanners and some "
"Linotype Hell SCSI-scanners. See B<sane-umax>(5) for details."
--
Man page: sane.7
Issue: sane-umax_pp → I<sane-umax_pp>
"The sane-umax_pp backend provides access to Umax parallel port flatbed "
"scanners and the HP 3200C. See B<sane-umax_pp>(5) for details."
--
Man page: sane.7
Issue: sane-umax1220u → I<sane-umax1220u>
"The sane-umax1220u backend supports the UMAX Astra 1220U (USB) flatbed "
"scanner (and also the UMAX Astra 2000U, sort of). See B<sane-umax1220u>(5) "
"for details."
--
Man page: sane.7
Issue: sane-xerox_mfp → I<sane-xerox_mfp>
"The sane-xerox_mfp backend supports multiple Samsung-based Samsung, Xerox, "
"and Dell scanners. See B<sane-xerox_mfp>(5) for details."
--
Man page: sane.7
Issue 1: sane-stv680 → I<sane-stv680>
Issue 2: stv680 → I<stv680>
"The sane-stv680 backend provides access to webcams with a stv680 chip. See "
"B<sane-stv680>(5) for details."
--
Man page: sane.7
Issue: sane-dll → B<sane-dll>
"The sane-dll library implements a B<SANE> backend that provides access to an "
"arbitrary number of other B<SANE> backends by dynamic loading. See B<sane-"
"dll>(5)."
--
Man page: sane.7
Issue 1: saned → B<saned>(8)
Issue 2: net → I<net>
"The B<SANE> network daemon saned provides access to scanners located on "
"different computers in connection with the net backend. See B<sane-net>(5) "
"and B<saned>(8)."
--
Man page: sane.7
Issue: they aren't available → it isn't available
"Now your scanner is detected by the operating system but not by B<SANE>? Try "
"B<scanimage -L>. If the scanner is not found, check that the backend's name "
"is mentioned in I</etc/sane.d/dll.conf>. Some backends are commented out by "
"default. Remove the comment sign for your backend in this case. Also some "
"backends aren't compiled at all if one of their prerequisites are missing. "
"Examples include dc210, dc240, canon_pp, hpsj5s, gphoto2, pint, qcam, v4l, "
"net, sm3600, snapscan, pnm. If you need one of these backends and they "
"aren't available, read the build instructions in the B<README> file and the "
"individual manual pages of the backends."
--
Man page: sane.7
Issue 1: B<-L .> → B<-L>.
Issue 2: dll → I<dll>
"If your scanner is still not found, try setting the various environment "
"variables that are available to assist in debugging. The environment "
"variables are documented in the relevant manual pages. For example, to get "
"the maximum amount of debug information when testing a Mustek SCSI scanner, "
"set environment variables B<SANE_DEBUG_DLL>, B<SANE_DEBUG_MUSTEK>, and "
"B<SANE_DEBUG_SANEI_SCSI> to 128 and then invoke B<scanimage> B<-L .> The "
"debug messages for the dll backend tell if the mustek backend was found and "
"loaded at all. The mustek messages explain what the mustek backend is doing "
"while the SCSI debugging shows the low level handling. If you can't find out "
"what's going on by checking the messages carefully, contact the sane-devel "
"mailing list for help (see REPORTING BUGS below)."
--
Man page: sane.7
Issue 1: B<scanimage> → B<scanimage>(1)
Issue 2: B<xscanimage> → B<xscanimage>(1)
Issue 3: B<xsane> → B<xsane>(1)
Issue 4: B<quiteinsane> → B<quiteinsane>(1)
"So now scanning with B<scanimage> works and you want to use one of the "
"graphical frontends like B<xsane>, B<xscanimage>, or B<quiteinsane> but "
"those frontends don't detect your scanner? One reason may be that you "
"installed two versions of B<SANE>. E.g. the version that was installed by "
"your distribution in I</usr> and one you installed from source in I</usr/"
"local/>. Make sure that only one version is installed. Another possible "
"reason is, that your system's dynamic loader can't find the B<SANE> "
"libraries. For Linux, make sure that I</etc/ld.so.conf> contains I</usr/"
"local/lib> and does B<not> contain I</usr/local/lib/sane>. See also the "
"documentation of the frontends."
--
Man page: sane.7
Issue 1: Why citation of already formatted terms?
Issue 2: B<scanimage> → B<scanimage>(1)
"The package `B<sane-backends>' contains a lot of backends, documentation "
"(including the B<SANE> standard), networking support, and the command line "
"frontend `B<scanimage>'. The frontends `B<xscanimage>', `B<xcam>', and "
"`B<scanadf>' are included in the package `B<sane-frontends>'. Both packages "
"can be downloaded from the B<SANE> homepage (I<http://www.sane-project.org/"
">). Information about other frontends and backends can also be found on the "
"B<SANE> homepage."
--
Man page: sane.7
Issue: coolscan3 is missing here
"This is a SANE backend for Nikon Coolscan film-scanners. See B<sane-"
"coolscan2>(5) or I<http://coolscan2.sourceforge.net> for details."
--
Man page: sane.7
Issue 1: genesys → I<genesys>
Issue 2: forced line breaks due to overlong lines in source code
"The genesys backend provides support for several scanners based on the Genesys Logic \n"
"GL646, GL841, GL843, GL847 and GL124 chips like the Medion 6471 and Hewlett-Packard 2300c.\n"
" See\n"
"B<sane-genesys>(5)\n"
"for details.\n"
--
Man page: sane.7
Issue: pixma → I<pixma>
"The pixma backend supports Canon PIXMA MP series (multi-function devices). "
"See B<sane-pixma>(5) or I<http://home.arcor.de/wittawat/pixma/> for details."
--
Man page: sane.7
Issue 1: sane-st680 → I<sane-st680>
Issue 2: st680 → I<st680>
"The sane-st680 backend provides access to webcams with a stv680 chip. See "
"B<sane-st680>(5) for details."
--
Man page: sane.7
Issue: latex → LaTeX
"The B<SANE> standard defines the application programming interface (API) "
"that is used to communicate between frontends and backends. It can be found "
"at I<@DOCDIR@/sane.ps> (if latex is installed on your system) and on the "
"B<SANE> website: I<http://www.sane-project.org/html/> (HTML), or I<http://"
"www.sane-project.org/sane.ps> (Postscript)."
--
Man page: sane.7
Issue: /usr/share/doc/libsane/ → I</usr/share/doc/libsane/>
"The B<SANE> device lists contain information about the status of B<SANE> "
"support for a specific device. If your scanner is not listed there (either "
"supported or unsupported), please contact us. See section HOW CAN YOU HELP "
"SANE for details. There are lists for specific releases of SANE, for the "
"current development version and a search engine: I<http://www.sane-project."
"org/sane-supported-devices.html>. The lists are also installed on your "
"system at /usr/share/doc/libsane/."
--
Man page: sane.7
Issue: /usr/share/doc/sane-backends/ → I</usr/share/doc/sane-backends/>
"The B<SANE> device lists contain information about the status of B<SANE> "
"support for a specific device. If your scanner is not listed there (either "
"supported or unsupported), please contact us. See section HOW CAN YOU HELP "
"SANE for details. There are lists for specific releases of SANE, for the "
"current development version and a search engine: I<http://www.sane-project."
"org/sane-supported-devices.html>. The lists are also installed on your "
"system at /usr/share/doc/packages/sane-backends/."
--
Man page: sane-as6e.5
Issue 1: I<as6edriver> → B<as6edriver>
Issue 2: I<saned> → B<saned>(8)
"The I<as6edriver> program must be in the path for executables ($PATH). "
"Especially if you run I<saned> (the SANE network scanning daemon), take care "
"to setup the path for I<inetd> or I<xinetd> correctly or place the program "
"in a directory that is in the path."
--
Man page: sane-canon.5
Issue: sane-canon_pp and sane-canon630u → B<sane-canon_pp>(5) and B<sane-canon630u>(5)
"Parallel port and USB scanners are not supported by this backend; see the "
"manual pages for sane-canon_pp and sane-canon630u for further information."
--
Man page: sane-canon.5
Issue: The brown base color of the film material (due to the requirements od the C-41 color development process) leads *always* to a blue tint of the positive picture, if it only goes through a simple color conversion.
"Negatives are handled by simple color inversion and may require manual "
"removal of blue discoloration."
--
Man page: sane-canon.5
Issue: Closing bracket is missing
"doc/canon.install2700F.txt (installation of a CanoScan 2700F"
--
Man page: sane-canon630u.5
Issue 1: I<sane-find-scanner> → B<sane-find-scanner>(1)
Issue 2: sane-usb(5) → B<sane-usb>(5)
"The contents of the I<canon630u.conf> file is a list of device names that "
"correspond to Canon USB scanners. Empty lines and lines starting with a "
"hash mark (#) are ignored. Only one device name can be listed in "
"I<canon630u.conf>. The program I<sane-find-scanner> helps to find out the "
"correct device. Under Linux, such a device name could be I</dev/usb/"
"scanner0> for example. See sane-usb(5) for details."
--
Man page: sane-canon630u.5
Issue: /proc/bus/usb/devices → I</proc/bus/usb/devices>
"This product-specific scanner driver uses the lower-level kernel USB driver "
"\"scanner\". Check for \"Driver=usbscanner\" under /proc/bus/usb/devices. "
"If \"Driver=(none)\", try forcing it with \"insmod scanner vendor=0x04a9 "
"product=0x2204\""
--
Man page: sane-canon630u.5
Issue 1: I</proc/bus/usb/devices>, I</proc/pci> → I</proc/bus/usb/devices>, I</proc/pci>
Issue 2: scanner.c → I<scanner.c>
Issue 3: /var/log/messages → I</var/log/messages>
"Some users have reported that this driver doesn't work at all. This seems "
"to be a hardware specific issue, although I don't know what exactly the "
"problem is. If you are having problems, please send me the info in /proc/"
"bus/usb/devices, /proc/pci, the kernel scanner.c driver version from /var/"
"log/messages, and the output from \"SANE_DEBUG_CANON630U=12 scanimage E<gt> /"
"dev/null\""
--
Man page: sane-canon630u.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-cardscan.5
Issue: "cardscan.conf" → I<cardscan.conf>
"The configuration file \"cardscan.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 "
"defaults, which are identical to the default configuration file shipped with "
"SANE."
--
Man page: sane-cardscan.5
Issue: SANE_DEBUG_CARDSCAN → B<SANE_DEBUG_CARDSCAN>
"The backend uses a single environment variable, SANE_DEBUG_CARDSCAN, which "
"enables debugging output to stderr. Valid values are:"
--
Man page: sane-config.1
Issue: --libs → B<--libs>
"Print a short usage message. If OPTION is specified, help for that option (e."
"g. --libs) is printed (if available)."
--
Man page: sane-coolscan2.5
Issue: scanimage → B<scanimage>(1)
"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:"
--
Man page: sane-coolscan2.5
Issue: -d → B<-d>
"This option specifies which frame to operate on, if a motorized film strip "
"feeder or APS adapter are used. The frame number I<E<lt>nE<gt>> 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)."
--
Man page: sane-coolscan2.5
Issue 1: scanimage → B<scanimage>(1)
Issue 2: batch-count=2 → B<--batch-count=2>
"Multiply all exposure times with this value. This allows exposure correction "
"without modifying white balance."
--
Man page: sane-coolscan2.5
Issue: Refers only to SF-200, not to the basic MA-20
"Load the next slide when using the slide loader."
--
Man page: sane-coolscan2.5
Issue: The (basic) slide loader MA-20 can't be ejected using this option. It doesn't have any motor-driven mechanism. Probably it works only with the slide feeder SF-200?
"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> does not work."
--
Man page: sane-coolscan2.5
Issue 1: with know identifiers → with known identifiers
Issue 2: action taken → default action
"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."
--
Man page: sane-coolscan2.5
Issue: frame → B<--frame>
"Currently, the SANE protocol does not allow automatically updating options "
"whenever the hardware changes. Thus the number of choices for the B<--frame> "
"option will be fixed when the backend is initialized (usually when the user "
"runs the frontend). In particular, if there is no film strip in the "
"automatic film strip feeder when the backend is initialized, the frame "
"option will not appear at all. Also, restarting the frontend after swapping "
"film adapters is strongly recommended."
--
Man page: sane-coolscan3.5
Issue: scanimage → B<scanimage>(1)
"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:"
--
Man page: sane-coolscan3.5
Issue: -d → B<-d>
"This option specifies which frame to operate on, if a motorized film strip "
"feeder or APS adapter are used. The frame number I<E<lt>nE<gt>> 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)."
--
Man page: sane-coolscan3.5
Issue 1: scanimage → B<scanimage>(1)
Issue 2: batch-count=2 → B<--batch-count=2>
"Multiply all exposure times with this value. This allows exposure correction "
"without modifying white balance."
--
Man page: sane-coolscan3.5
Issue: Refers only to SF-200, not to the basic MA-20
"Load the next slide when using the slide loader."
--
Man page: sane-coolscan.5
Issue 1: have to set → can set (SCSI doesn't need to setup the permissions in many cases)
Issue 2: sane-scsi → B<sane-scsi>(5)
"The special device name must be a generic SCSI device or a symlink to such a "
"device. To find out to which device your scanner is assigned and how you "
"have to set the permissions of that device, have a look at sane-scsi."
--
Man page: sane-coolscan.5
Issue: Words after colon should be merged with the next Gettext message
"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: "
"SANE_DEBUG_COOLSCAN values"
--
Man page: sane-coolscan.5
Issue: Missing period at the end
"The autofocus command does not work with some SCSI card/driver combinations"
"The dust-removal is not working yet"
--
Man page: sane-escl.5
Issue: _uscan._utcp or _uscans._utcp → I<_uscan._utcp> or I<_uscans._utcp>
"The \"escl\" backend for SANE supports AirScan/eSCL devices that announce "
"themselves on mDNS as _uscan._utcp or _uscans._utcp. If the device is "
"available, the \"escl\" backend recovers these capacities. The user "
"configures and starts scanning. A list of devices that use the eSCL "
"protocol can be found at I<https://support.apple.com/en-us/HT201311>. While "
"these devices are expected to work, your mileage may vary."
--
Man page: sane-find-scanner.1
Issue: Unix → UNIX
"B<sane-find-scanner> is a command-line tool to find SCSI and USB scanners "
"and determine their Unix device files. Its primary aim is to make sure that "
"scanners can be detected by SANE backends."
--
Man page: sane-find-scanner.1
Issue: Superfluous bracket within the device file enumeration
"For B<USB> scanners, first the USB kernel scanner device files (e.g. I</dev/"
"usb/scanner0>), I</dev/usb/scanner>, and I</dev/usbscanner>) 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-scanner> "
"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> 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> will even find USB scanners, that are not supported by "
"any SANE backend."
--
Man page: sane-hp3500.5
Issue: I<sane-find-scanner> → B<sane-find-scanner>(1)
"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<sane-find-scanner> or syslog) to us. Even if the scanner's name is only "
"slightly different from the models mentioned above, please let us know."
--
Man page: sane-hp3900.5
Issue: hp3900 → I<hp3900>
"More details can be found on the hp3900 backend homepage I<http://"
"sourceforge.net/projects/hp3900-series/>."
--
Man page: sane-hp3900.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-hp4200.5
Issue: I<sane-find-scanner> → B<sane-find-scanner>(1)
"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<sane-find-scanner> or syslog) to us. Even if the scanner's name is only "
"slightly different from the models mentioned above, please let us know."
--
Man page: sane-hp4200.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-hp4200.5
Issue: sane-devel@alioth-lists.debian.net → I<sane-devel@alioth-lists.debian.net>
"Send bug reports to the sane-devel mailing list: sane-devel@alioth-lists."
"debian.net."
--
Man page: sane-hp5400.5
Issue: I<sane-find-scanner> → B<sane-find-scanner>(1)
"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<sane-find-scanner> or syslog) to us. Even if the scanner's name is only "
"slightly different from the models mentioned above, please let us know."
--
Man page: sane-hp5400.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-hpljm1005.5
Issue: I<sane-find-scanner> → B<sane-find-scanner>(1)
"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<sane-find-scanner> or syslog) to us. Even if the scanner's name is only "
"slightly different from the models mentioned above, please let us know."
--
Man page: sane-kodakaio.5
Issue: where to find the desc file?
"This version should support models of the Kodak ESP and Hero series, and "
"possibly some Advent AiO scanners. The ESP 5250 and Hero 9.1 were used to "
"develop the backend, but other models may work. Please see the desc file."
--
Man page: sane-kodakaio.5
Issue: "kodakaio.conf" → I<kodakaio.conf>
"The configuration file \"kodakaio.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."
--
Man page: sane-kodakaio.5
Issue: SANE_DEBUG_KODAKAIO → B<SANE_DEBUG_KODAKAIO>
"The backend uses a single environment variable, SANE_DEBUG_KODAKAIO, which "
"enables debugging output to stderr."
--
Man page: sane-kvs20xx.5
Issue: Superfluous period at the end
"sane-kvs20xx - SANE backend for Panasonic KV-S20xxC USB/SCSI ADF scanners."
--
Man page: sane-mustek_usb2.5
Issue: mustek_usb2 → I<mustek_usb2>
"The B<sane-mustek_usb2> library implements a SANE (Scanner Access Now Easy) "
"backend that provides access to USB flatbed scanners based on the Service & "
"Quality SQ113 chipset. At the moment, only the Mustek BearPaw 2448 TA Pro is "
"supported. It's planned to add support for other scanners that are based on "
"the SQ113 and maybe SQ11 chip. For more details, see the mustek_usb2 backend "
"homepage: I<http://www.meier-geinitz.de/sane/mustek_usb2-backend/>."
--
Man page: sane-mustek_usb2.5
Issue: I<sane-find-scanner> → B<sane-find-scanner>(1)
"If you own a scanner other than the ones listed on the mustek_usb2 homepage "
"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<sane-find-scanner> or syslog) to me. Even if the scanner's name is only "
"slightly different from the models already listed as supported, please let "
"me know."
--
Man page: sane-mustek_usb2.5
Issue 1: sane-find-scanner → B<sane-find-scanner>(1)
Issue 2: looks → look
"Please use libusb-0.1.8 or later. Without libusb or with older libusb "
"versions all kinds of trouble can be expected. The scanner should be found "
"by sane-find-scanner without further actions. For setting permissions and "
"general USB information looks at B<sane-usb>(5)."
--
Man page: sane-mustek_usb2.5
Issue: SANE_DEBUG_MUSTEK_USB2 → B<SANE_DEBUG_MUSTEK_USB2>
"Please contact me if you find a bug or missing feature: E<lt>henning@meier-"
"geinitz.deE<gt>. Please send a debug log if your scanner isn't detected "
"correctly (see SANE_DEBUG_MUSTEK_USB2 above)."
--
Man page: sane-nec.5
Issue: Needs to be clarified: Does this refer to other scanners from the MultiReader series or to other series of MultiReader scanners?
"The B<sane-nec> library implements a SANE (Scanner Access Now Easy) backend "
"that provides access to NEC SCSI scanners. This backend should be "
"considered B<alpha-quality> software! In the current state it is known to "
"work with PC-IN500/4C scanners. Another MultiReader scanner series is not "
"supported. PC-IN 500/4C and MultiReader scanner are only sold in Japan."
"(except Multi Reader PetiScan.)"
--
Man page: sane-niash.5
Issue: Superfluous period at the end
"sane-niash - SANE backend for scanners based on the NIASH chipset."
--
Man page: sane-pieusb.5
Issue: pieusb → I<pieusb>
"If available, pieusb supports infrared scans for dirt detection and removal. "
"This must be enabled via the 'Clean image' setting."
"The pieusb backend supports dirt removal based on infrared scan information. "
"Since SANE does not provide post-processing in the backend, pieusb does the "
"scanning and dirt removal during the setup phase. The 'scan' phase is only "
"used to transfer the completed image. Therefore pieusb does not multi-"
"thread making a typical frontend appear as 'blocked'. Also cancel requests "
"are only honored between scans."
--
Man page: sane-ricoh2.5
Issue 1: scanimage → B<scanimage>(1)
Issue 2: xscanimage → B<xscanimage>(1)
Issue 3: xsane → B<xsane>(1)
"The options the backend supports can either be selected through command line "
"options to programs like scanimage or through GUI elements in programs like "
"xscanimage or xsane."
--
Man page: sane-ricoh.5
Issue 1: sane-scsi(5) → B<sane-scsi>(5)
Issue 2: I<sane-find-scanner> → B<sane-find-scanner>(1)
"Where I<special> is the path-name for the special device that corresponds to "
"a SCSI scanner. The special device name must be a generic SCSI device or a "
"symlink to such a device. The program I<sane-find-scanner> helps to find "
"out the correct device. Under Linux, such a device name could be I</dev/sga> "
"or I</dev/sge>, for example. See sane-scsi(5) for details."
--
Man page: sane-ricoh.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-s9036.5
Issue 1: sane-scsi(5) → B<sane-scsi>(5)
Issue 2: I<sane-find-scanner> → B<sane-find-scanner>(1)
"Where I<special> is the path-name for the special device that corresponds to "
"a SCSI scanner. The special device name must be a generic SCSI device or a "
"symlink to such a device. The program I<sane-find-scanner> helps to find "
"out the correct device. Under Linux, such a device name could be I</dev/sga> "
"or I</dev/sge>, for example. See sane-scsi(5) for details."
--
Man page: sane-s9036.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-sm3600.5
Issue: sane-microtek(5) and sane-microtek2(5) → B<sane-microtek>(5) and B<sane-microtek2>(5)
"There are also backends for Microtek scanners with SCSI command set. Refer "
"to sane-microtek(5) and sane-microtek2(5) for details."
--
Man page: sane-sm3600.5
Issue: Microtek2 → I<sm3600>
"The following options are supported by the Microtek2-driver:"
--
Man page: sane-sm3600.5
Issue: syntax seems to be odd and incomplete
"contrast, brightness, control, gamma correction."
--
Man page: sane-sm3600.5
Issue: SANE_DEBUG_SM3600 → B<SANE_DEBUG_SM3600>
"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. "
"To see error messages on stderr set SANE_DEBUG_SM3600 to 1."
--
Man page: sane-sm3840.5
Issue: sane-microtek(5) and sane-microtek2(5) → B<sane-microtek>(5) and B<sane-microtek2>(5)
"There exist backends for Microtek scanners with SCSI command set. Refer to "
"sane-microtek(5) and sane-microtek2(5) for details."
--
Man page: sane-sm3840.5
Issue: sane-sm3600(5) → B<sane-sm3600>(5)
"There also exists a Microtek 3600 series driver, see sane-sm3600(5) for "
"details."
--
Man page: sane-sm3840.5
Issue: earle@ziplabel.com → I<earle@ziplabel.com>
"If you own a Microtek scanner with the SCAN08 chip other than the ones "
"listed above, it may or may not work with SANE. Feel free to contact the "
"backend author (earle@ziplabel.com) to report results with scanners not on "
"the list."
--
Man page: sane-sm3840.5
Issue: SANE_DEBUG_SM3840 → B<SANE_DEBUG_SM3840>
"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. "
"To see error messages on stderr set SANE_DEBUG_SM3840 to 1."
--
Man page: sane-snapscan.5
Issue: sane-scsi(5) → B<sane-scsi>(5)
"Where I<special> 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> or I</dev/sge>, for example. See sane-scsi(5) for "
"details."
--
Man page: sane-snapscan.5
Issue: http://snapscan.sourceforge.net → I<http://snapscan.sourceforge.net>
"For further details read http://snapscan.sourceforge.net."
--
Man page: sane-snapscan.5
Issue: sane-scsi(5) → I<sane-scsi>(5)
"The contents of the I<snapscan.conf> file is a list of device names that "
"correspond to SnapScan scanners. Empty lines and lines starting with a hash "
"mark (#) are ignored. See sane-scsi(5) on details of what constitutes a "
"valid device name."
--
Man page: sane-snapscan.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-snapscan.5
Issue: invalid URL (error 404)
"http://www.cs.ualberta.ca/~charter/SnapScan/snapscan.html"
--
Man page: sane-sp15c.5
Issue: xscanimage → B<xscanimage>(1)
"A modest effort has been made to expose the standard options to the API. "
"This allows frontends such as xscanimage to set scanning region, resolution, "
"bit-depth (and color), and enable the automatic document feeder."
--
Man page: sane-sp15c.5
Issue: xsane → B<xsane>(1)
"Both scanners claim to have separate control of resolution in X and Y "
"directions. I confess I haven't tested this yet. I have found that xsane "
"doesn't even display this capability."
--
Man page: sane-tamarack.5
Issue 1: sane-scsi(5) → B<sane-scsi>(5)
Issue 2: I<sane-find-scanner> → B<sane-find-scanner>(1)
"Where I<special> is the path-name for the special device that corresponds to "
"a SCSI scanner. The special device name must be a generic SCSI device or a "
"symlink to such a device. The program I<sane-find-scanner> helps to find "
"out the correct device. Under Linux, such a device name could be I</dev/sga> "
"or I</dev/sge>, for example. See sane-scsi(5) for details."
--
Man page: sane-tamarack.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-umax1220u.5
Issue: sane-devel@alioth-lists.debian.net → I<sane-devel@alioth-lists.debian.net>
"This backend is also able to drive the UMAX Astra 1600U/2000U/2100U. The "
"2100U is confirmed to work. For the other scanners no reports have been "
"received yet. Please contact us and tell us if your scanner works (sane-"
"devel@alioth-lists.debian.net)."
--
Man page: sane-umax1220u.5
Issue: sane-usb(5) → B<sane-usb>(5)
"See sane-usb(5) for information on how to set the access permissions on the "
"usb device files."
--
Man page: sane-umax1220u.5
Issue: sane_cancel() → I<sane_cancel>()
"There is no way to cancel a scan, since the driver ignores sane_cancel()."
--
Man page: sane-umax1220u.5
Issue: SANE_DEBUG_UMAX1220U → B<SANE_DEBUG_UMAX1220U>
"This backend isn't actively maintained. Nevertheless, bug reports and "
"comments should be sent to the sane-devel mailing list. When reporting "
"bugs, please run the backend with SANE_DEBUG_UMAX1220U set to 10 and attach "
"a copy of the log messages."
--
Man page: sane-v4l.5
Issue: /etc/sane.d → I</etc/sane.d>
"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 by a semi-colon (`;'). If this "
"variable is not set, the configuration 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, setting B<SANE_CONFIG_DIR> "
"to \"/tmp/config:\" would result in directories \"tmp/config\", \".\", and "
"\"/etc/sane.d\" being searched (in this order)."
--
Man page: sane-v4l.5
Issue 1: sane-devel@alioth-lists.debian.net → I<sane-devel@alioth-lists.debian.net>
Issue 2: http://www.sane-project.org/mailing-lists.html → I<http://www.sane-project.org/mailing-lists.html>
"Send bug reports to the SANE mailing list: sane-devel@alioth-lists.debian."
"net. You must be subscribed to the list to send mail. See http://www.sane-"
"project.org/mailing-lists.html for details."
--
Man page: sane-xerox_mfp.5
Issue: (Missing) Markup for URL
"The B<sane-xerox_mfp> library implements a SANE (Scanner Access Now Easy) "
"backend that provides access to several Samsung-based Samsung, Xerox, and "
"Dell scanners. Please see full list of supported devices at http://www.sane-"
"project.org/sane-supported-devices.html"
--
Man page: sane-xerox_mfp.5
Issue: /etc/hosts → I</etc/hosts>
"The B<host_address> is passed through resolver, thus can be a dotted quad or "
"a name from /etc/hosts or resolvable through DNS."
--
Man page: sane-xerox_mfp.5
Issue: separate variable from description
"B<SANE_DEBUG_XEROX_MFP> 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."
--
Man page: sane-xerox_mfp.5
Issue: never → has never
"Multicast autoconfiguration for LAN scanners is not implemented yet. IPv6 "
"addressing never been tested."
--
Man page: sane-xerox_mfp.5
Issue: Missing Markup for URLs
"If you have found a bug or need support please follow open-source way of "
"acquiring support via mail-lists http://www.sane-project.org/mailing-lists."
"html or SANE bug tracker http://www.sane-project.org/bugs.html"
--
Man page: sane-xerox_mfp.5
Issue: missing period at the end
"Samsung SCX-4500W scan over network support by Alexander Kuznetsov "
"E<lt>acca(at)cpan.orgE<gt>"
"Color scanning on Samsung M2870 model and Xerox Cognac 3215 & 3225 models by "
"Laxmeesh Onkar Markod E<lt>m.laxmeesh@samsung.comE<gt>"
--
Man page: scanimage.1
Issue: --device-name=epson → B<--device-name=epson>
"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)."
--
Man page: scanimage.1
Issue: --output-file → B<--output-file>
"The B<--format> I<format> option selects how image data is written to "
"standard output or the file specified by the --output-file option. "
"I<format> can be B<pnm>, B<tiff>, B<png>, or B<jpeg>. If B<--format> is not "
"specified, PNM is written by default."
--
Man page: scanimage.1
Issue 1: --output-path → B<--output-path>
Issue 2: scanimage → B<scanimage>
"The B<--batch*> options provide the features for scanning documents using "
"document feeders. B<--batch> [I<format>] 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> is not specified, the default of out%d.pnm (or "
"out%d.tif for --format tiff, out%d.png for --format png or out%d.jpg for -- "
"format jpeg) will be used. This option is incompatible with the --output-"
"path option. I<format> is given as a printf style string with one integer "
"parameter. B<--batch-start> I<start> selects the page number to start "
"naming files with. If this option is not given, the counter will start at "
"1. B<--batch-count> I<count> 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> I<increment> 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> will "
"automatically set the increment to 2. B<--batch-prompt> will ask for "
"pressing RETURN before scanning a page. This can be used for scanning "
"multiple pages without an automatic document feeder."
--
Man page: scanimage.1
Issue 1: --batch → B<--batch>
Issue 2: --format → B<--format>
"The B<-o> or B<--output-file> option requests that B<scanimage> saves the "
"scanning output to the given path. This option is incompatible with the --"
"batch option. The program will try to guess --format from the file name. If "
"that is not possible, it will print an error message and exit."
--
Man page: scanimage.1
Issue: verbosity of the operation → verbosity of the output
"The B<-v> or B<--verbose> options increase the verbosity of the operation of "
"B<scanimage.> The option may be specified repeatedly, each time increasing "
"the verbosity level."
--
Man page: scanimage.1
Issue: 32KB to 1MB → 32 kB to 1 MB
"The B<-B> option without argument changes the input buffer size from the "
"default 32KB to 1MB. For finer grained control, use B<--buffer-size=> "
"followed by the number of KB."
--
Man page: scanimage.1
Issue: dll → I<dll>
"The B<-V> or B<--version> option requests that B<scanimage> prints the "
"program and package name, the version number of the B<SANE> 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> variable for the dll backend can be "
"used. Example: SANE_DEBUG_DLL=3 scanimage -L."
--
Man page: scanimage.1
Issue: -t, -x, -y → B<-t>, B<-x>, B<-y>
"The description above shows that option B<-l> expects an option value in the "
"range from 0 to 218 mm. The value in square brackets indicates that the "
"current option value is 0 mm. Most backends provide similar geometry options "
"for top-left y position (-t), width (-x) and height of scan-area (-y)."
--
Man page: scanimage.1
Issue: Splitting of Gettext messages due to unneeded .br in source code
msgid " Determines whether a builtin or a custom gamma-table\n"
--
Man page: scanimage.1
Issue 1: scanimage → B<scanimage>
Issue 2: --accept-md5-only → B<--accept-md5-only>
"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 characters."
--
Man page: scanimage.1
Issue: --mode Gray and --mode Grayscale → B<--mode Gray> and B<--mode Grayscale>
"B<Remark:> Parameter are defined by the backends. So are --mode Gray and --"
"mode Grayscale in use. Please read the backend documentation first."Edited by Ralph Little