From: Clem Cole <clemc@ccc.com>
To: Alec Muffett <alec.muffett@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Archeology: AberMUD, BCPL, ec.
Date: Thu, 31 Jan 2019 09:42:43 -0500 [thread overview]
Message-ID: <CAC20D2NVurm91cv_3KCQPdMdBHSP1yr7LRxiGWQmTjg9K2umtA@mail.gmail.com> (raw)
In-Reply-To: <CAFWeb9Jajw48onyW-_RNV9EU9y0N=Nxj-M60MBo2=S28Bd8-uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
I'm not sure if the old DEC CRL tech reports are still around. At one
time before the Compaq-tion, some folks at CRL and the folks at Boston
Public Library and WGBH were working with video and trying to extract all
sorts of text from it. I do not remember how successful they were, but
there might be some hints in their tech reports. I'll ask around and see
if I can turn anything up. Part of the problem I have is I that don't
remember who was doing that work, but some of my friends might.
Clem
ᐧ
On Thu, Jan 31, 2019 at 2:16 AM Alec Muffett <alec.muffett@gmail.com> wrote:
> Has anyone ever attempted to OCR a video, perhaps by breaking into frames
> and then aggregating the results, using multiple frames to correct each
> other?
>
> On Wed, 30 Jan 2019, 19:51 Richard Salz <rich.salz@gmail.com wrote:
>
>> Some folks are trying to figure out how to get AberMud source online and
>> working; see https://twitter.com/larsbrinkhoff/status/1056823314272960512
>>
>> Sample code at
>> https://raw.githubusercontent.com/larsbrinkhoff/abermud/master/abermud1/text/timelock.b
>>
>>
>>
>>
[-- Attachment #2: Type: text/html, Size: 2586 bytes --]
next prev parent reply other threads:[~2019-01-31 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2019-02-01 4:47 Doug McIlroy
2019-02-01 14:41 ` Nemo
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=CAC20D2NVurm91cv_3KCQPdMdBHSP1yr7LRxiGWQmTjg9K2umtA@mail.gmail.com \
--to=clemc@ccc.com \
--cc=alec.muffett@gmail.com \
--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).