Computer Old Farts Forum
 help / color / mirror / Atom feed
From: perry at piermont.com (Perry E. Metzger)
Subject: [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie)
Date: Wed, 25 Jul 2018 17:24:40 -0400	[thread overview]
Message-ID: <20180725172440.0a27e0e9@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <20180724035206.GA87618@eureka.lemis.com>

On Tue, 24 Jul 2018 13:52:06 +1000 Greg 'groggy' Lehey
<grog at lemis.com> wrote:
> On Monday, 23 July 2018 at 12:41:46 -0400, Dan Cross wrote:
> > On Mon, Jul 23, 2018 at 11:56 AM Larry McVoy <lm at mcvoy.com> wrote:
> My big issue was that it produces nicer output than TeX.  In those
> days at any rate you could tell TeX output a mile off because of the
> excessive margins and the Computer Modern fonts.  Neither is
> required, of course, but it seems that it must have been so much
> more difficult to change than it was with [gt]roff (or that the
> authors just didn't care).

It's a single command most of the time to change font.

   \usepackage{palatino}

for example. (That's at the start of many of my documents.)

It's also a single command to change your margins. Similar complexity,
a dozen chars and you're done.

I don't love TeX's command language, it's gross, but it's not hard to
do simple things like that, and the typesetting results are kind of
remarkable if you know what you're doing. The most beautiful books in
the world (by a lot) are typeset in modern TeX. I don't even think you
can do microtypography in any troff that I've seen, and forget things
like having both lining and text figures in the same
document.

Perry
-- 
Perry E. Metzger		perry at piermont.com


  parent reply	other threads:[~2018-07-25 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8ECDA62D-1B54-4391-A226-D3E9ABEE4C07@planet.nl>
     [not found] ` <CACXZuxeJ3igMtfbLs1iUPMLhomQUG0dEjpaHHmV0L7hF0bvo4g@mail.gmail.com>
     [not found]   ` <CAC20D2OTsR0ZxqeUk2EBpZnWy2k4LVf8=VPKzitWhkT3n_vL8g@mail.gmail.com>
     [not found]     ` <20180723155552.GB19635@mcvoy.com>
2018-07-23 16:41       ` [COFF] [TUHS] Looking for final C compiler by Dennis Ritchie crossd
2018-07-24  3:52         ` [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie) grog
2018-07-24  4:01           ` lm
2018-07-24 14:43             ` cym224
2018-07-24 10:00           ` ralph
2018-07-27  1:04             ` lm
2018-07-25 21:24           ` perry [this message]
2018-07-26  4:22             ` grog
2018-07-26  6:38               ` bakul
2018-07-26 12:22               ` perry
2018-07-27  1:28                 ` grog
2018-07-27  2:52                   ` cym224

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=20180725172440.0a27e0e9@jabberwock.cb.piermont.com \
    --to=coff@minnie.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).