summaryrefslogtreecommitdiff
path: root/testsuite/sanei/data/umax_pp.conf
diff options
context:
space:
mode:
authorJörg Frings-Fürst <debian@jff-webhosting.net>2019-07-31 16:59:49 +0200
committerJörg Frings-Fürst <debian@jff-webhosting.net>2019-07-31 16:59:49 +0200
commit1687222e1b9e74c89cafbb5910e72d8ec7bfd40f (patch)
treed78102ce30207c63e7608eeba743efd680c888dc /testsuite/sanei/data/umax_pp.conf
parent58912f68c2489bcee787599837447e0d64dfd61a (diff)
New upstream version 1.0.28upstream/1.0.28
Diffstat (limited to 'testsuite/sanei/data/umax_pp.conf')
-rw-r--r--testsuite/sanei/data/umax_pp.conf6
1 files changed, 3 insertions, 3 deletions
diff --git a/testsuite/sanei/data/umax_pp.conf b/testsuite/sanei/data/umax_pp.conf
index 69cc47d..eb84f74 100644
--- a/testsuite/sanei/data/umax_pp.conf
+++ b/testsuite/sanei/data/umax_pp.conf
@@ -8,12 +8,12 @@ option buffer 1048576
# DEVICES #
-# specify the port your scanner is connected to.
+# specify the port your scanner is connected to.
#
# the value 'auto' will make the backend find the correct value
# by itself, it will scan ppdev, ppi device, then hardware address
# 'safe-auto' will do the same but won't do direct hardware access
-# on linux systems, you may provide the device name of the ppdev character
+# on linux systems, you may provide the device name of the ppdev character
# device : /dev/parport0, /dev/parport1, ......
#
# on *BSD, you may provide the device name of the ppi device: /dev/ppi0,
@@ -58,7 +58,7 @@ option blue-offset 6
# valid values are 610, 1220, 1600 and 2000
#
# by default, no model, we rely on autodetection
-# in case you have black or 'inverted' scans,
+# in case you have black or 'inverted' scans,
# you may override detection by providing the
# model number
option astra 1600