9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rudolf.sykora@gmail.com (Rudolf Sykora)
Subject: [9fans] troff macros for typesetting books/longer texts
Date: Tue, 22 Mar 2011 22:00:12 +0100	[thread overview]
Message-ID: <AANLkTimhoGFD54C31_fgVDwND3Mbv2q8Abz+C32=K+HM@mail.gmail.com> (raw)
In-Reply-To: <32490607a1a7ec830a162035c0ca2219@ladd.quanstro.net>

> the Te?book may be authoratative, but it's by no means short.

This is the argument I'd stand by.
I read the TeXBook and used (plain)Tex much before ever touching
troff, thus I have a good idea about how it is written and explained.
Being a physicist, I use latex for writing articles. I have discovered
troff much later, basically because of plan9 (I had known of troff's
existence, sure, but never thought of trying it out). Basically,
seeing the conciseness and lucidity of works by Kernighan (eqn, tbl
documentation)---few extremely nice pages you can read over a
coffee---made me plunge into the troff's waters.

As I said many times, TeX is superior in (mainly math) quality.
However, troff and its preprocessors (eqn, tbl, grap,...) seem smaller
and more elegant to me. Eqn input is rather legible in the source
(even more with the ability to use utf-8 letters in place of e.g.
alpha; but this I think is now possible in some versions of TeX, too,
I believe).

Note, that neither plainTex nor troff handle cross-references,
automatic equation numbering, footnote numbering, table of contents,
etc. Nonetheless, mainly these listed features are often so needed.
One way out has been latex, which shows, in my opinion, how things
should not be done. There is also eplain, a much better choice for me
(plain extended with the mentioned almost always wanted features, and
some most frequent latex macros like graphix). What I am trying to get
is something like eplain, but for troff. And I wanted to have a look
at how some things are to be done. And to not invent a wheel, I asked
for some *simple* macros, which must have been used e.g. in the
mentioned books in my 1st contribution.

Just now I am reading "Unix Text Processing" by Dale Dougherty and Tim
O'Reilly, a freely available book (pmartin proposes it as well). There
are several chapters on the topic, so perhaps I'll get what I want in
the end.

Thanks
Ruda



  parent reply	other threads:[~2011-03-22 21:00 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 [this message]
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
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='AANLkTimhoGFD54C31_fgVDwND3Mbv2q8Abz+C32=K+HM@mail.gmail.com' \
    --to=rudolf.sykora@gmail.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).