9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com (tlaronde at polynum.com)
Subject: [9fans] troff macros for typesetting books/longer texts
Date: Tue, 22 Mar 2011 20:22:12 +0100	[thread overview]
Message-ID: <20110322192212.GA4348@polynum.com> (raw)
In-Reply-To: <20110322190821.C8BFCB835@mail.bitblocks.com>

On Tue, Mar 22, 2011 at 12:08:21PM -0700, Bakul Shah wrote:
> 
> Most TeX users are actually latex users, not raw TeX so the
> TeXbook is not terribly useful. But there are good books on
> latex and there is a wealth of material online (& many
> packages that work with latex).  With TeXworks and TeXshop on
> the Mac writing latex docs has become more pleasant.
> 
> Still, it is much easier to learn to use troff (speaking as a
> user; never tried writing a macro package for it). A lot of
> things "just work".

I'm not an integrist, and as long as someone is comfortable with troff,
I don't see why he should switch to TeX. The converse is true.

But most of the "difficulties" with TeX come precisely because this is
not "plain" TeX: plain TeX (i.e. the macros from D.E. Knuth) just work
too. But TeX is hidden---see the comments I received at first: "why do
you want to make a TeX package? People only use LaTeX..."

And I think that I have the right to say that if some people had really
grasped TeX and al., they would never have done the mess the
distributions of the system are now.
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C




  reply	other threads:[~2011-03-22 19:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 17:10 Rudolf Sykora
2011-03-22 17:30 ` Lyndon Nerenberg
2011-03-22 17:44   ` Rudolf Sykora
2011-03-22 18:21     ` Lyndon Nerenberg
2011-03-22 18:46       ` tlaronde at polynum.com
2011-03-22 18:48         ` tlaronde at polynum.com
2011-03-22 18:48           ` erik quanstrom
2011-03-22 18:59             ` tlaronde at polynum.com
2011-03-22 19:23               ` erik quanstrom
2011-03-22 21:00             ` Rudolf Sykora
2011-03-22 21:35               ` tlaronde at polynum.com
2011-03-22 21:50                 ` Rudolf Sykora
2011-03-22 21:51               ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-22 22:06                 ` Rudolf Sykora
2011-03-22 22:09               ` Brian L. Stuart
2011-03-22 22:31                 ` Rudolf Sykora
2011-03-22 22:55                   ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-03-22 23:42                   ` Steve Simon
2011-03-22 23:47                     ` erik quanstrom
2011-03-22 19:08         ` Bakul Shah
2011-03-22 19:22           ` tlaronde at polynum.com [this message]
2011-03-22 19:50         ` Jacob Todd
2011-03-22 20:08           ` Anthony Sorace
2011-03-22 21:23           ` Steve Simon
2011-03-22 20:26 ` pmarin
2011-03-23 21:38 ` Stanley Lieber
2011-03-24  6:18 Allan Heim
2011-03-24 13:16 ` hiro
2011-03-24 13:55   ` Gabriel Diaz
2011-03-25 11:50     ` Aharon Robbins
2011-03-25 12:25       ` erik quanstrom
2011-03-25 12:37         ` Lucio De Re
2011-03-25 15:10         ` pmarin
2011-03-25 15:23           ` dexen deVries
2011-03-25 15:32           ` John Floren
2011-03-25 15:41             ` John Floren
2011-03-25 20:21             ` Michael Kerpan
2011-03-25 16:48         ` Bakul Shah

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=20110322192212.GA4348@polynum.com \
    --to=tlaronde@polynum.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).