Package: libsane Version: 1.0.17-1 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man5/sane-mustek_usb.5.gz', see attached '.diff'. Hope this helps... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages libsane depends on: ii adduser 3.85 Add and remove users and groups ii libc6 2.3.6-3 GNU C Library: Shared libraries an ii libgphoto2-2 2.1.6-6 gphoto2 digital camera library ii libgphoto2-port0 2.1.6-6 gphoto2 digital camera port librar ii libieee1284-3 0.2.10-1 cross-platform library for paralle ii libjpeg62 6b-12 The Independent JPEG Group's JPEG ii libusb-0.1-4 2:0.1.11-6 userspace USB programming library ii makedev 2.3.1-80 creates device files in /dev Versions of packages libsane recommends: ii hotplug 0.0.20040329-25 Linux Hotplug Scripts ii sane-utils 1.0.17-1 API library for scanners -- utilit -- no debconf information
--- sane-mustek_usb.5 2005-12-18 11:20:14.000000000 -0500 +++ /tmp/sane-mustek_usb.5 2006-03-17 06:33:55.000000000 -0500 @@ -87,7 +87,7 @@ .IR mustek_usb.conf . This is only supported with Linux 2.4.8 and higher and all systems that support libsub. "vendor_id" and "product_id" are hexadecimal numbers that -identfy the scanner. If this doesn't work, a device name and the option +identify the scanner. If this doesn't work, a device name and the option specifying the scanner type must be placed in .I mustek_usb.conf as described above. @@ -155,7 +155,7 @@ .ft CR .nf -Value Descsription +Value Description 0 no output 1 print fatal errors 2 print important messages @@ -195,10 +195,10 @@ reset (toggle = DATA0). That means, any operation that tries to reset the device will result in running into timeouts. -In earlier versions this backend failed when it is loaded the second time in +In earlier versions this backend failed when it was loaded the second time in some configurations. The only choice was to replug the scanner in this case. The backend uses a workaround for that bug now but it's only tested on -Linux. Reports for other operating systems are appriciated. +Linux. Reports for other operating systems are appreciated. .PP More detailed bug information is available at the Mustek backend homepage
