9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lyndon@orthanc.ca (Lyndon Nerenberg (VE6BBM/VE7TFX))
Subject: [9fans] troff macros for typesetting books/longer texts
Date: Tue, 22 Mar 2011 14:55:55 -0800	[thread overview]
Message-ID: <a18f047652f56d17a878af315213d2bf@gandalf.orthanc.ca> (raw)
In-Reply-To: <AANLkTinbA=qyDdB1LRE47Ogd+rkyogEDMNdjXv3rERgT@mail.gmail.com>

> I have only hesitated over the way (as described in my original, 1st,
> post) how references that *depend on physical placement* of certain
> text are to be coped with. (As with my page headings; or---probably
> even harder so that at least 2-runs of troff are
> inevitable---references to page numbers where sth is mentioned. But I
> really need just the headings now.)

For page headers and footers, the tutorial section in the Troff paper
should have enough to get you going (/sys/doc/troff.ps, pages 34 on).

For section and index cross-references to page numbers, you pretty
much have to do two passes, writing the xref data to an external file
that gets read in the table of contents or index sections as
appropriate.  (You read and write the xref data file from inside troff
itself using .so and .tm.)

For what it's worth, spending a couple of days studying the ms macro
package source code should give you a lot of ideas.  And a headache
;-)

--lyndon




  reply	other threads:[~2011-03-22 22:55 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) [this message]
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=a18f047652f56d17a878af315213d2bf@gandalf.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).