From: cdl@mpl.ucsd.edu (Carl Lowenstein)
Subject: [TUHS] UNIX/32V
Date: Mon, 20 Oct 2003 09:02:06 -0700 (PDT) [thread overview]
Message-ID: <200310201602.h9KG26L12551@opihi.ucsd.edu> (raw)
> Date: Sun, 19 Oct 2003 22:35:32 +1300
> From: Wesley Parish <wes.parish at paradise.net.nz>
> Subject: Re: [TUHS] UNIX/32V
> To: tuhs at tuhs.org
>
> On Sun, 19 Oct 2003 21:20, Norman Wilson wrote:
> > Wesley Parish:
> >
> > I was wondering as well, are there any VAX assembler manuals online, in
> > an easily-copyable form?
> >
> > I've encountered html ones, but that isn't quite what I mean.
> >
> > What do you mean, then? In what way isn't HTML suitable?
> > I don't mean to be obstreperous; I just think it would be
> > easier to help if you made it clearer what you need and
> > what you don't.
>
> I'm a bit more used to using PDF for that purpose, since PDF data
> resides in a single file - ergo, easier downloads.
Download all the html. (use wget)
Make a list of the files in the order that they should appear in
the PDF file.
Use htmldoc < www.easysw.com/htmldoc/ > to make PDF or PostScript.
Htmldoc is interesting software -- it works well and is available in
source form with the caveat "here it is, take it and don't bother us
unless you want to buy a support contract".
carl
next reply other threads:[~2003-10-20 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 16:02 Carl Lowenstein [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-19 8:20 Norman Wilson
2003-10-19 9:35 ` Wesley Parish
2003-10-18 9:19 nao
2003-10-18 16:21 ` Robert Brockway
2003-10-19 6:46 ` Wesley Parish
2003-10-19 6:55 ` Robert Brockway
2003-10-19 13:00 ` Kroumovi, Ivaylo & Mladena
2003-10-20 7:45 ` Wesley Parish
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=200310201602.h9KG26L12551@opihi.ucsd.edu \
--to=cdl@mpl.ucsd.edu \
/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).