The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] [groff] Brian Kernighan on the evoution of eqn, pic, grap into troff
Date: Mon, 07 May 2018 21:11:50 -0700	[thread overview]
Message-ID: <20180508041157.C9ED9156E510@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 07 May 2018 17:39:58 -0700." <201805080039.w480dwfd005761@darkstar.fourwinds.com>

On Mon, 07 May 2018 17:39:58 -0700 Jon Steinhart <jon at fourwinds.com> wrote:
> 
> IMHO, the tex language is too ugly.  I much prefer troff.  But, and maybe this
> will be a retirement project, giving troff tex's two-dimensional layout smarts
> so that widows and orphans don't have to be handled manually would be nice.
> 
> Remember, we're lucky that Don didn't work on X Windows because he would
> have called it Ech.

You can pronounce TeX as if it is written in Cyrillic: Tiyekh!
And then of course, LyaTiyekh!

Though I vastly prefer TeX/LaTeX/XeLaTeX over troff (unlike
most folks on this list) and find even the source code more
legible than ugly control lines starting with a "." -- In *TeX
I can reformat most parahraphs to balance lines, without
things falling aport.

Now one can avoid most of the hassles for simple documentation
by using markdown or asciidoc & tools that generate .tex,
which can be rendered beautifully. Even here you can typically
use LaTeX formatting for equations.


  parent reply	other threads:[~2018-05-08  4:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06  2:29 Doug McIlroy
2018-05-06  3:36 ` Steve Nickolas
2018-05-08  0:29   ` George Michaelson
2018-05-08  0:39     ` Jon Steinhart
2018-05-08  2:17       ` Dave Horsfall
2018-05-08  2:43         ` Jon Steinhart
2018-05-08  4:11       ` Bakul Shah [this message]
2018-05-08 14:54         ` Nemo
2018-05-08 16:42     ` Paul Winalski

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=20180508041157.C9ED9156E510@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    /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).