The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] TeX/troff/typesetting markups - Re: SunOS 4 documentation
Date: Sat, 15 Apr 2017 11:27:49 -0400	[thread overview]
Message-ID: <CAC20D2OR5reLm-BD4Ff+9G_vy=O_b=sSSGZ0q-70qNVFCF_7gg@mail.gmail.com> (raw)
In-Reply-To: <b313bd1d-28d3-e498-f72c-692ee27e6ae1@telegraphics.com.au>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]

On Fri, Apr 14, 2017 at 6:24 PM, Toby Thain <toby at telegraphics.com.au>
wrote:
>
>
> No matter how far you tart up the former, Troff and TeX just aren't
> playing the same ballgame.


​Toby - that's a tad inflammatory - at least to my American sensibilities.
Saying one or the other has been "dressed up" (using a derogatory term or
not) is to me the same as the vi/emacs wars or rugby/American Football
argument.   Some people like the taste of one, others do not, and thank
goodness we have choices.   I've used the afore mentioned systems (and
played the games too at a fairly high level in my day); and frankly it is a
matter if taste.  They all have their place.

If you grew up with an affinity for one, you are more likely to find it
more comfortable for your needs.  I find a TeX just as ugly and unreadable
as  the runoff family with troff is a member.   It's just a different view
of beauty.  Frankly, Brian Reid's Scribe on the "Twinex" and VMS was the
"best" document product system I ever really used (for those that do not
know, LaTex was an attempt to bring Scribe-like functions into TeX).    But
as Brian Kernighan points out in his "Page Makeup" paper, even Scribe had
some flaws (it's too bad Scribe seems to have been lost to IP and source
issues - I've often wonder how it would have played out in the modern
world).

Anyway - it fine to say you don't like troff - please feel free to suggest
that you don't think that it can be made to your style/preferences.   But
please don't sling to many insults as the truth is, that troff is still
useful to many people and a lot people do still like it.

In my own case, I'll use TeX if a colleague wants too, but I'm a fair bit
faster with troff than almost any other doc prep system for any document of
almost any size; but particularly when the documents get large such as
book.   But that's me; although I note it is also a lot of other people.
As Brian points out, many of the Pearson and Wiley texts use troff; and of
course you have to note that my old deskmate, Tim O'Reilly founded his
empire on it 😂 (I still have a copy of the his original style manual they
wrote for the Masscomp engineers and doc writers in the mid 80s).
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170415/dde6c3b1/attachment.html>


  parent reply	other threads:[~2017-04-15 15:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 21:54 [TUHS] " Cory Smelosky
2017-04-12 22:55 ` Cory Smelosky
2017-04-12 23:31   ` Larry McVoy
2017-04-13  2:13     ` Toby Thain
2017-04-13  2:16       ` Steve Nickolas
2017-04-13  2:25         ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 14:25           ` Nemo
2017-04-13 15:41           ` Andreas Kusalananda Kähäri
2017-04-13 16:35           ` Toby Thain
2017-04-13  2:20       ` [TUHS] " Larry McVoy
2017-04-13 13:41         ` Steffen Nurpmeso
2017-04-13 15:40           ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-13 23:22             ` Steffen Nurpmeso
2017-04-14  0:40               ` Greg 'groggy' Lehey
2017-04-14  1:59                 ` Nemo
2017-04-14  3:00                   ` Toby Thain
2017-04-14  2:59                 ` Toby Thain
2017-04-14 13:38                 ` Steffen Nurpmeso
2017-04-14 13:56                   ` Michael Kerpan
2017-04-14 16:55                     ` Steffen Nurpmeso
2017-04-14 22:24                     ` Toby Thain
     [not found]                       ` <CAHfSdrVAnPn3hwFR0ie0o-yuqGX0hu+LWweNZngpoY4=efTSaA@mail.gmail.com>
2017-04-15 14:23                         ` Michael Kerpan
2017-04-15 15:09                           ` Toby Thain
2017-04-15 16:07                           ` [TUHS] TeX/troff/typesetting markups - " Mutiny 
2017-04-15 21:48                             ` Dave Horsfall
2017-04-15 22:12                               ` ron minnich
2017-04-16  0:02                                 ` Dave Horsfall
2017-04-15 15:27                       ` Clem Cole [this message]
2017-04-15 17:05                         ` [TUHS] TeX/troff/typesetting markups - " Toby Thain
2017-04-15 17:10                         ` Toby Thain
2017-04-18  4:49                         ` Greg 'groggy' Lehey
2017-04-14 13:07             ` Wolfgang Helbig
2017-04-14 20:56               ` Clem Cole
2017-04-16 13:42               ` Tim Bradshaw
2017-04-13 14:14         ` [TUHS] " Nemo
2017-04-13 16:34           ` Steve Simon
2017-04-13 23:14             ` Steffen Nurpmeso
2017-04-14  8:30               ` Steve Simon
2017-04-14 13:21                 ` Steffen Nurpmeso
2017-04-13 13:28       ` John Labovitz
2017-04-17 18:56 [TUHS] TeX/troff/typesetting markups - " Doug McIlroy

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='CAC20D2OR5reLm-BD4Ff+9G_vy=O_b=sSSGZ0q-70qNVFCF_7gg@mail.gmail.com' \
    --to=clemc@ccc.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).