> I now have three other scanners, which work, including my scsi Microtek
> Scanmaker e3, which is on the same scsi bus as my Ricoh IS410. I still
> would like to get it going, if you're game. I started from scratch, using
> your latest tarball, which was dated February 2015. It seems to be
> c
Generally, 1200 dpi resolution for text would be overkill unless you have a
document with extremely tiny print (1-2 point instead of 10-12 point).
They used to recommend 150 dpi or even 75 dpi for scanning documents
containing just plain text. But I scan at 300 dpi and also print ordinarily at
I think ghostscript must be writing one dictionary for the whole document
instead of one dictionary per page.
If I take my 16M PDFTK.pdf and re-write it using ghostscript, ghostscript
produces a 8.5M file:
$ gs -q -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=NEW.pdf PDFTK.pdf
War
Hmmm, I guess I learn something new every day.
I wouldn't have suspected that ghostscript writer could concatenate pdf's and
save so much during compression.
So I just did a test, scanning some tax forms
in 8-bit grayscale to z[0001 --- 0019].pdf using xsane
and then combining using both gs and p
The perl application gscan2pdf will probably do what you need:
http://gscan2pdf.sourceforge.net/
I use a shell script "bscan" for scanning to pnm then conversion to e.g. pdf.
Since my scanner scans better in 8-bit grayscale then 2-bit B&W,
I scan in 8-bit grayscale @ 300dpi then convert to bitona
What is OUTDIR set to in your configuration?
set -x; exec 2>$HOME/scanscript/output/pct-scanner-script-process.log
c44 -dpi $SCAN_RES "$1"
"$OUTDIR/scanscript/processing/document-single-page-test.djvu"
grep OUTDIR 50configuration
# OUTDIR="$HOME"
OUTDIR="HOME"
Shouldn't the commented out line
> Have you tried scanning your document using my "bscan" bash script?
>Thanks very much for this, Jeremy, it looks interesting. Unfortunately I
>could not get it to run - it complained about not finding 'gamma4scanimage'.
>As I got some promising suggestions from the hylafax list I did not pursue
On Friday 19 December 2008 11:34:09 gobo wrote:
> for some time now i've been using homemade scripts with scanimage and
> scanadf to scan my paper documents. most of my documents are plain
> text. the results have always been poor and marginally acceptable. i'm
> using suse 10.3 and an hp aio j6450
On Monday 03 November 2008 07:00:04 m. allan noah wrote:
> On Mon, Nov 3, 2008 at 4:44 AM, Rod De Beer
wrote:
> > hi Allan
> >
> > Thanks so much for your reply !
> >
> > A little more info -:
> >
> > i am going with the idea of dropping the windows based scanning system
> > loading Linux
>
Is there any way to scan using xsane
such that it will scan from the ADF until the
ADF is empty.
I've written a shell script for batch scanning
from the ADF using scanadf:
scanimage -v $OPTIONS \
--batch="out.%04d.pnm" \
--batch-start="1"\
--batch-increment="1"
whi
I downloaded the 2006 Samsung Universal Linux Driver and installed.
the new ppd files all seem to pass cupstestppd syntax check which the
ones included in the previous Samsung driver tarball did not. The new
ppd files work fine with cups, unlike the old.
Unfortunately, the install.sh borks xsane a
11 matches
Mail list logo
