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:41:57 -0700 [thread overview]
Message-ID: <20170505054157.C0716124AEA4@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 05 May 2017 15:32:42 +1000." <CAJQxxwkwdBrJ7zJRCgF-rFTYD_Jwh-qFPRPM=3WgvN-cY-gzww@mail.gmail.com>
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
next prev parent reply other threads:[~2017-05-05 5:41 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 [this message]
2017-05-05 5:53 ` Bakul Shah
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=20170505054157.C0716124AEA4@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).