From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] eqn
Date: Fri, 04 Oct 2019 21:59:01 -0400 [thread overview]
Message-ID: <201910050159.x951x1nh023003@tahoe.cs.Dartmouth.EDU> (raw)
> does anyone have some eqn input and output that they can share?
I have a quite elaborate document that uses eqn, pic, and tbl. In
fact one table contains both pic and eqn entries (but not subtables;
Latex beats roff in being recursive). Take a look at
www.cs.dartmouth.edu/~doug/wallpaper.pdf. If you think you'd like
to see the source, just holler.
> he maybe should do Latex
Sadly, math journals often demand Latex, but I've also run into
journals that require Word. I wanted to submit the document above
to a cartography journal until I found out they were in the
Word camp. I was, however, able to convert it to Latex.
At one point the American Instutute of Physics took only roff
(and retypeset other manuscripts--in roff). I don't know what
their practice is q
now.
> Maybe v0 didn't have any manuals?
> I understand they weren't in roff anyways.
No manuals, true. But if there had been they would have been
in some version of roff, just as all Research Unix manuals were.
Doug
next reply other threads:[~2019-10-05 1:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 1:59 Doug McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-04 4:20 Larry McVoy
2019-10-04 4:35 ` Dave Horsfall
2019-10-04 5:12 ` George Michaelson
2019-10-04 13:43 ` Nemo
2019-10-04 14:57 ` aksr
2019-10-04 15:52 ` U'll Be King of the Stars
2019-10-04 16:12 ` Jon Forrest
2019-10-04 17:24 ` Adam Thornton
2019-10-04 18:55 ` Kurt H Maier
2019-10-04 17:43 ` Steffen Nurpmeso
2019-10-06 8:03 ` arnold
2019-10-04 19:02 ` Larry McVoy
2019-10-07 17:26 ` Seth J. Morabito
2019-10-07 19:14 ` Adam Thornton
2019-10-08 21:11 ` Seth Morabito
2019-10-04 19:25 ` Fabio Scotoni
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=201910050159.x951x1nh023003@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
--cc=tuhs@tuhs.org \
/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).