From: S.J.Vickers@open.ac.uk
To: categories@mta.ca
Subject: RE: Max's LMS book (out-of-print)
Date: Fri, 15 Dec 2000 09:11:23 -0000 [thread overview]
Message-ID: <ACAB691EBFADD41196340008C7F35585C2BE2C@tesla.open.ac.uk> (raw)
> Why not get it retyped in TeX .... This would only
> be worth it if you can get a "subscription" system to offset that fee
> of course. ...
> R.A.G. Seely
I was thinking of suggesting the same myself - I'd be very interested in
subscribing.
All the better if, assuming Max is willing, you can find subscribers public
spirited enough to allow free electronic availability once it's TeXed.
(Perhaps subscribers get a bound copy signed by the author?)
What would it cost?
Can OCR scanning help the initial input for such texts?
Steve Vickers.
next reply other threads:[~2000-12-15 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 9:11 S.J.Vickers [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-14 6:17 Terminology Max Kelly
2000-12-14 15:05 ` Max's LMS book (out-of-print) Robert A.G. Seely
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=ACAB691EBFADD41196340008C7F35585C2BE2C@tesla.open.ac.uk \
--to=s.j.vickers@open.ac.uk \
--cc=categories@mta.ca \
/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).