9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [9fans] troff macros for typesetting books/longer texts
Date: Tue, 22 Mar 2011 11:21:55 -0700	[thread overview]
Message-ID: <alpine.OSX.1.10.1103221100050.15028@rastawifi.orthanc.ca> (raw)
In-Reply-To: <AANLkTimHZoVkTF041aJb5oxdfysc4nXLOtAhH9h8oakf@mail.gmail.com>

> Actually, I know of both mentioned places. But, as far as I know, the
> very macros are not discussed anywhere. But I may be, of course,
> wrong.

My guess is these works fall into two categories:

1) the author uses (say) ms, and extends it with macros in the document 
source code to achieve the bits that pure ms doesn't provide.

2) the author starts with (say) ms, then customizes it for the specific 
task at hand.

In either case, the customizations are locked in with the document source 
and don't get distributed. Or they are so tied in with a specific document 
that they're of no practical use as standalone tools.

I've done both when writing documentation, and in all those years I've 
never come up with a macro package specifically for that task. The reason 
being there is too much variablity in what I need. The effort it would 
require to write a general purpose macro package to encompass all those 
variations would be self defeating. It's considerably faster (for me) to 
do these customizations on a per-document basis.

Over the years I have developed patterns in how I design these one-offs, 
but the results are never quite the same between any two documents.

I usually use ms as the scaffolding, writing additional macros to provide 
the higher level concepts (e.g. chapters).  While it's possible to muck 
around inside the ms macros themselves, the result isn't portable. I've 
learned to be careful not to get too caught up in trying to make ms do 
things it doesn't want to. Sometimes it's easier to just write your own 
macro set for the specific task at hand. (Re-implementing basics like .LP, 
.PP, .IP, .SH, etc. is quite easy if you don't require all the 
generalizations ms provides.)

--lyndon



  reply	other threads:[~2011-03-22 18:21 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 [this message]
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
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=alpine.OSX.1.10.1103221100050.15028@rastawifi.orthanc.ca \
    --to=lyndon@orthanc.ca \
    /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).