Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!ucbvax!NRI.RESTON.VA.US!rdroms From: rdroms@NRI.RESTON.VA.US Newsgroups: comp.protocols.tcp-ip Subject: Re: Decrypting RFC 1125 Message-ID: <8912071248.aa10868@NRI.NRI.Reston.VA.US> Date: 7 Dec 89 17:48:50 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 24 I've written two .sty files that might be of interest to this discussion. The first, rfc.sty, generates RFC-style output (title page, headers, footers, etc.) from LaTeX. The second, txt.sty, generates a .dvi file that can be run through dvi2tty to produce well-formatted (IMHO, better than stock dvi2tty or dvidoc) ASCII output. I generated the PostScript and ASCII versions of the Dynamic Host Configuration Internet Draft using these .sty files. At present, txt.sty still needs more work, primarily to track down and eliminate all the rubber vertical glue. Dvi2tty could also use some work to improve spacing of characters in both dimensions. For example, horizontal and vertical bars (actually, rules in general) are not handled well. Is there general interest in these .sty files? How many RFCs or other documents might actually be produced in both PostScript and ASCII from TeX? I'd like to know if it's worth my time to put more effort into fine-tuning these tools. - Ralph Droms (On leave from Bucknell University) NRI rdroms@nri.reston.va.us 1895 Preston White Drive, Suite 100 (703) 620-8990 Reston, VA 22091 (703) 620-0913 (fax)