9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: stanley.lieber@gmail.com (Stanley Lieber)
Subject: [9fans] troff macros for typesetting books/longer texts
Date: Wed, 23 Mar 2011 16:38:40 -0500	[thread overview]
Message-ID: <f44300c7b0a26e80ec46287df8261855@EXAMPLE> (raw)
In-Reply-To: <AANLkTimt8ia6Hs=p7sssbWNhrRePd5LhuSUC9xwsgco+@mail.gmail.com>

> Hello everyone,
> 
> please, does somebody know of any troff macros that were used to typeset books?
> Can one get hold of e.g. macros used to typeset e.g. "The AWK
> Programming Language" by Aho, Kernighan and Weinberger, or ?The Unix
> Programming Environment? by Kernighan and Pike?
> 
> I want to particularly know how headings were programmed. I.e., how
> the name of a chapter that is only to appear on a page gets to its
> heading. I feel that either the file must be processed twice, or one
> must write a heading of a page only when the page is about to be
> completed (one would then back up to the heading position, write it,
> and only then continue).

I'm currently in the process of re-typesetting my books using troff. Once
completed, I plan to make the troff sources and build system available
alongside the output.

The links mentioned in this thread are basically the same documents
I've worked from during this process. In addition, I purchased the Gehani
books a while back; they contain a lot of helpful information, although
Gehani seems to favor mm over ms.

-sl




  parent reply	other threads:[~2011-03-23 21:38 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
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 [this message]
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=f44300c7b0a26e80ec46287df8261855@EXAMPLE \
    --to=stanley.lieber@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).