From: sholmes@primenet.com (Steve Holmes)
To: blinux-list@redhat.com
Subject: Linux Documentation accessability
Date: Tue, 26 Nov 1996 18:38:11 GMT [thread overview]
Message-ID: <329c3771.11475260@mailhost.primenet.com> (raw)
I've picked some of the linux documentation and finding that much of
it is in latex, I thought I'd try some of these filters to get it into
something more readable than those God-awful latex commands. I like
both the emacs info mormat and html will certainly do. Well,
latexinfo for emacs gives me errors when I try running (version 1.70),
latex2html looks promising, but it requires latex and some other
utilities. At this point, I don't see an easy way to install latex
without taking up over 30 megs of precious diskspace on my little
linux system. So that leves me to ask on the list to see what others
might have done to make these documents more readable. I suppose
ascii will do, but I rather like the hyper text format due to the
reference nature of these manuals.
Any ideas?
Thanks
--
<Steve> Holmes
Tempe, Arizona USA
next reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes [this message]
` Burchard Steinbild
Lar Kaufman
` Steve Holmes
` Peter Nilsson
` Brian L. Sellden
` Luke Davis
` Alexandre Khalil
` Steve Holmes
` Lar Kaufman
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=329c3771.11475260@mailhost.primenet.com \
--to=sholmes@primenet.com \
--cc=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).