Computer Old Farts Forum
 help / color / mirror / Atom feed
From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie)
Date: Mon, 23 Jul 2018 21:01:46 -0700	[thread overview]
Message-ID: <20180724040146.GN28713@mcvoy.com> (raw)
In-Reply-To: <20180724035206.GA87618@eureka.lemis.com>

Back in 1998 or 1999 I was program chair for Linux expo.  Which was
no big deal, it meant I formatted the papers and got the page numbers
right for the proceeedings.  I nudged people towards troff and one
guy went there.  He said "this was so much easier than tex, it is
faster, easier, why don't more people use this?"   What he said.

On Tue, Jul 24, 2018 at 01:52:06PM +1000, Greg 'groggy' Lehey 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:
> >
> >> I agree that roff is awesome, it's a bummer that Latex seems to be
> >> the winner (which I think is purely because the roff/eqn/pic/etc
> >> docs weren't widely available back in the day).
> >
> > I have to disagree with this, however. TeX (and more specifically
> > LaTeX) won out for technical writing because, frankly, it produces
> > nicer output than *roff did. If I were writing a thesis or paper,
> > I'd frankly rather use LaTeX or AMSLaTeX.
> 
> What about a book?  Back in the late 1980s/early 1990s I used TeX and
> LaTeX, but when I started writing "Porting UNIX Software" (O'Reilly),
> they insisted on me using (g)roff with their proprietary macros.  I
> resisted, of course, but it was clear that I didn't have much choice.
> And then I discovered that it was *so* much easier to use, and I've
> never used TeX again, though I made significant modifications to the
> macro set, to the point that it was no more O'Reilly than ms.
> 
> 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).
> 
> Still, TeX has one significant advantage over [gt]roff that I'm aware
> of: it adjusts paragraphs, not lines, and it seems that in some cases
> this give better looking layout.
> 
> This reflects the situation in about 1993 or 1994.  Maybe TeX has
> become more usable since then.  Certainly LaTeX refuses to look at my
> old LaTeX source.
> 
> Greg
> --
> Sent from my desktop computer.
> Finger grog at lemis.com for PGP public key.
> See complete headers for address and phone numbers.
> This message is digitally signed.  If your Microsoft mail program
> reports problems, please read http://lemis.com/broken-MUA



-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 


  reply	other threads:[~2018-07-24  4:01 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 [this message]
2018-07-24 14:43             ` cym224
2018-07-24 10:00           ` ralph
2018-07-27  1:04             ` lm
2018-07-25 21:24           ` perry
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=20180724040146.GN28713@mcvoy.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).