From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Indexing macros
Date: Tue, 03 Dec 2002 17:57:51 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021203175703.00a93aa8@server-1> (raw)
In-Reply-To: <200212031333.47102.john@wexfordpress.com>
At 01:33 PM 12/3/2002 +0000, you wrote:
>useful. For example attributes attached to the page reference # can be
>passed through the system. An entry, subentry etc. can be sorted out
you can use attributes:
Copied from the manual source:
Most of the time the layout of a register is rather simple.
Some manuals may need some form of differentiating between
entries. The definition of several registers may be a
solution. However the layout can contribute to a better use
of the register:
\starttyping
\index {entry}
\index[key] {entry}
\index[form::] {entry}
\index[form::key]{entry}
\index {form::entry}
\index[key] {form::entry}
\index[form::] {form::entry}
\index[form::key]{form::entry}
\stoptyping
The first two alternatives are known, but the rest is new and
offers some control over the way the entry itself is
typeset. The specification between
\setchars\ relates to the pagenumber, the specification
in front of the entry relates to the entry itself.
\starttyping
\setupregister[index][form][pagestyle=bold,textstyle=slanted]
\stoptyping
Without any problems we can use different appearances
for pagenumber and entry.
\starttyping
\setupregister[index][nb][pagestyle=bold]
\setupregister[index][hm][pagestyle=slanted]
\stoptyping
With for example:
\starttyping
\index[nb::]{squareroot}
\index[hm::root]{$\srqt{2}$}
\stoptyping
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-12-03 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 16:20 John Culleton
2002-12-02 16:41 ` Taco Hoekwater
2002-12-03 13:33 ` John Culleton
2002-12-03 16:57 ` Hans Hagen [this message]
2002-12-03 16:59 ` Hans Hagen
2002-12-04 14:30 ` Gour
2002-12-02 16:51 ` Hans Hagen
2002-12-03 14:18 ` John Culleton
2008-09-11 20:58 width of cell in TABLE Peter Münster
2008-09-12 8:27 ` span ROWS in \starttables? Alan BRASLAU
2008-09-12 13:37 ` Aditya Mahajan
2008-09-15 12:49 ` Indexing macros Alan BRASLAU
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=5.1.0.14.1.20021203175703.00a93aa8@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).