The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] ocr'd e03
Date: Wed, 30 Apr 2008 09:01:51 -0400	[thread overview]
Message-ID: <3018.1209560511@mini> (raw)
In-Reply-To: <20080430102120.GA84492@minnie.tuhs.org>


Hi,

I'm new to this (just discovered it - way cool!), so as an experiment I
opened the scanned pdf and cut and pasted e03-01,02,03,04 into gimp,
shrunk them to 3000x3000 and sent them to the tesseract web site.  It
does an amazing job.  A little emacs work and the source looks good.

Anyway, I know e03 is assigned to someone else, but they where not in
the svn.  should I check them in?  (I just did it as an experiment, and
I don't want to step on anyone;)

I'm also curious how we boot strap this.  In the end I assume we need a
binary image which one of the sims can read.  I have 0.5 a mind to write
a quick and dirty assembler which outputs a binary file... 

But I suppose it would be better to use the original as/as2.  Can this
be run with apout? (I'd be curious to hear how people are doing it).

I'm happy to keep plugging through the remaining un-ocr'd pages if no
one screams, sending email first of course.

-brad



  reply	other threads:[~2008-04-30 13:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 10:21 [Unix-jun72] Disassembler in progress Warren Toomey
2008-04-30 13:01 ` Brad Parker [this message]
2008-04-30 17:38   ` [Unix-jun72] ocr'd e03 Tim Newsham
2008-04-30 18:49     ` Brad Parker
2008-04-30 19:19       ` Hellwig Geisse
2008-04-30 19:52         ` Tim Newsham
     [not found]     ` <10901.1209581283@mini>
2008-04-30 19:24       ` Tim Newsham
2008-04-30 20:43         ` Brad Parker
2008-04-30 20:26     ` [Unix-jun72] Mar 72 kernel subroutine description Al Kossow
2008-04-30 20:48       ` Brad Parker
2008-05-01 16:23     ` [Unix-jun72] ocr'd e03 Tim Bradshaw

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=3018.1209560511@mini \
    --to=brad@heeltoe.com \
    /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).