9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Postscript and troff
Date: Thu,  4 May 2017 22:53:08 -0700	[thread overview]
Message-ID: <20170505055308.CD5CC124AF25@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 04 May 2017 22:41:57 PDT." <20170505054157.C0716124AEA4@mail.bitblocks.com>

Via http://ftp.cs.stanford.edu/tex/texhax/texhax89.088
So only for -ms or -man.  bwk's way may be better for your purpose.

+----
| Date: Fri, 22 Sep 89 12:30:59 PDT
| From: Phil Farrell <farrell@erebus.Stanford.EDU>
| Subject: Re: TeX, troff, man pages
| Keywords: TeX, troff, man pages
|
| In TeXhax vol 89, issue 85, William LeFebvre says:
| > I've often thought of implementing the troff man macros in TeX.  If
| > that were done, then one could just TeX-off the printed form whenever
| > desired but still have "nroff -man" for the man command.  So what's
| > needed?  First, we need to define "(newline)." as the equivalent of an
| > escape character.  Any takers?
|
| There is another existing way to do this.  The UNIX TeX distribution includes
| a contributed program tr2tex from a former student here at Stanford that
| can convert troff manuscripts that use either -ms or -man macros to LaTeX
| documents.  It doesn't do a perfect job for complicated troff constructions,
| but the simple macros normally used in man pages come through just fine.
|
| This isn't the real answer for replacing troff with TeX on UNIX systems
| because it still requires that you keep nroff around and it still requires
| that you know the -man macros for writing man pages.  What I think is
| needed is a combination of a LaTeX style option that forces the output
| to use a constant-width font and constant line spacing, etc; plus a
| dvi interpreter that can reproduce such a restricted output on a normal
| terminal screen.  For the fairly simple documents that are used as on-line
| documentation (no math and only simple tables that can be done with tabs)
| this would allow regular typesetting via LaTeX for printed copies, but
| also permit viewing on a normal dumb terminal by including the special
| style option and processing through the special dvi interpreter.  I am
| afraid, however, that this would be a rather large project to undertake
| and unfortunately can never imagine having the time to do it myself.
|
| Phil Farrell, Computer Systems Manager
| Stanford University School of Earth Sciences
| farrell@erebus.stanford.edu
+----


On Thu, 04 May 2017 22:41:57 PDT Bakul Shah <bakul@bitblocks.com> wrote:
> https://bima.astro.umd.edu/nemo/man_html/tr2latex.l.html
>
> No idea how good it is though.
>
> On Fri, 05 May 2017 15:32:42 +1000 Bruce Ellis <bruce.ellis@gmail.com> wrote:
> >
> > bwk mentioned that TeX was unworkable for this situation. Maybe it's time
> > for another good TeX hack.
> >
> > :-) brucee
> >
> > On 5 May 2017 at 15:28, Bakul Shah <bakul@bitblocks.com> wrote:
> >
> > > This is an opportunity for someone to implement troff macros in TeX.
> > > Then you can embed EPS easily!
> > >
> > > :-)
> > >
> > > On Fri, 05 May 2017 15:23:39 +1000 Bruce Ellis <bruce.ellis@gmail.com>
> > > wrote:
> > > >
> > > > I asked bwk - troff wizard, and to paraphrase him "there is no good
> > > > solution".
> > > >
> > > > There is the PSPIC macro in groff, but it generates huge files.
> > > >
> > > > For the latest book they used \X to embed markers and a go programs to
> > > > postprocess troff output.
> > > >
> > > > brucee
>



      reply	other threads:[~2017-05-05  5:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJDwFdjZPSzjOJdBc9LBY22x4sN-M61+Kr3v+nbTo785trfStg@mail.gmail.com>
     [not found] ` <CAJDwFdiON+FFjy0SGfn2XE-ZDsyHTAhr+ZGB=5Exjyisdf_CEg@mail.gmail.com>
     [not found]   ` <CAJDwFdijDm7op4hKtLKBEcctJs_YHcVuF7oa+Abe+_L8vHvMvQ@mail.gmail.com>
2017-05-02  3:44     ` Prof Brucee
2017-05-02  8:59       ` Bruce Ellis
2017-05-02  9:29         ` Steve Simon
2017-05-02  9:37           ` Bruce Ellis
2017-05-05  5:23             ` Bruce Ellis
2017-05-05  5:28               ` Bakul Shah
2017-05-05  5:32                 ` Bruce Ellis
2017-05-05  5:41                   ` Bakul Shah
2017-05-05  5:53                     ` Bakul Shah [this message]

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=20170505055308.CD5CC124AF25@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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).