From: David Arnold <davida@pobox.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Fri, 14 Jan 2022 09:19:35 +1100 [thread overview]
Message-ID: <94F48429-0CD7-4C9B-867F-DC75B797DFA8@pobox.com> (raw)
In-Reply-To: <CAEoi9W5h2HvB4mq7DGu8gN9LAH3rQfTWjqEPgk_LB4k+1o47pQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1008 bytes --]
> On 14 Jan 2022, at 03:33, Dan Cross <crossd@gmail.com> wrote:
>
> On Wed, Jan 12, 2022 at 10:32 PM Theodore Ts'o <tytso@mit.edu <mailto:tytso@mit.edu>> wrote:
> Speaking of typesetting equations, how would people compare eqn versus
> LaTeX? I used nroff for man pages, but I never did learn how to use
> eqn for nroff.
>
> I hate to be the one who says this, but when it comes to typesetting non-trivial mathematics, there is no competition: LaTeX beats eqn hands down. eqn is fine up to a point (and the neqn thing is kinda nifty for simple things on the terminal; you can kinda sorta get a rendered sigma for a summation, for example) but it breaks down pretty quickly.
Both FrameMaker and Word have GUI equation editors. They’re pretty capable, but are a separate “world” from the text: they open a new window for editing the equation that floats over the document.
I much preferred (I don’t do a lot of equations these days) the inline nature of LaTeX (and (n)eqn)).
d
[-- Attachment #1.2: Type: text/html, Size: 1940 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2022-01-13 22:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 2:04 josh
2022-01-13 2:03 ` Greg 'groggy' Lehey
2022-01-13 3:24 ` Win Treese
2022-01-13 14:56 ` Clem Cole
2022-01-13 15:08 ` John P. Linderman
2022-01-13 16:06 ` Clem Cole
2022-01-13 16:24 ` Warner Losh
2022-01-13 16:39 ` Harald Arnesen
2022-01-13 18:00 ` Bakul Shah
2022-01-13 15:35 ` Dan Cross
2022-01-13 16:02 ` Warner Losh
2022-01-13 16:20 ` Clem Cole
2022-01-13 16:32 ` Warner Losh
2022-01-13 16:42 ` Lars Brinkhoff
2022-01-13 16:52 ` Larry McVoy
2022-01-13 16:54 ` Clem Cole
2022-01-13 17:06 ` Clem Cole
2022-01-13 18:16 ` Dan Cross
2022-01-13 20:00 ` Larry McVoy
2022-01-13 20:26 ` Chet Ramey
2022-01-13 16:13 ` Charles H Sauer
2022-01-13 22:53 ` David Arnold
2022-01-14 1:53 ` Adam Thornton
2022-01-13 3:26 ` Theodore Ts'o
2022-01-13 16:25 ` Larry McVoy
2022-01-13 16:33 ` Dan Cross
2022-01-13 22:19 ` David Arnold [this message]
2022-01-13 13:54 ` Adam Sampson
2022-01-13 16:37 ` Lars Brinkhoff
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=94F48429-0CD7-4C9B-867F-DC75B797DFA8@pobox.com \
--to=davida@pobox.com \
--cc=coff@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).