From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Archeology: AberMUD, BCPL, ec.
Date: Thu, 31 Jan 2019 23:47:09 -0500 [thread overview]
Message-ID: <201902010447.x114l9kX046939@tahoe.cs.Dartmouth.EDU> (raw)
> I have tried to OCR program listings before, with rather
> poor results.
I OCR'd a sizable manuscript written on a pretty shabby portable typewriter.
I scanned each page twice, making sure to move the paper between scans.
Then I ran both diff (by words, not lines) and spell to smoke out trouble.
The word list for a program listing is quite short and easy to generate.
(Print a list of all the apparent words and visually eliminate the nonsense.)
And a spell check is an easy pipeline of standard utilities.
doug
next reply other threads:[~2019-02-01 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 4:47 Doug McIlroy [this message]
2019-02-01 14:41 ` Nemo
-- strict thread matches above, loose matches on Subject: below --
2019-01-30 19:51 Richard Salz
2019-01-31 7:15 ` Alec Muffett
2019-01-31 7:28 ` Lars Brinkhoff
2019-01-31 14:42 ` Clem Cole
2019-01-31 19:34 ` Lawrence Stewart
2019-01-31 19:45 ` Lawrence Stewart
2019-02-01 5:08 ` Jason Stevens
2019-02-01 8:09 ` Steve Nickolas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201902010447.x114l9kX046939@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).