From: John Culleton <john@wexfordpress.com>
Subject: \filbreak OK--TOC again--dupes in index.
Date: Thu, 29 Apr 2004 19:14:10 -1000 [thread overview]
Message-ID: <200404291914.10852.john@wexfordpress.com> (raw)
1. Is it OK to use the plain tex command \filbreak in a
Context run? If not OK is there a Context command that has
the same effect (preventing a section of text from being
split between pages)?
2. Also, I have tried several changes to my TOC code but it
still yields a blank line between items. Yet the TOC of
some manuals are single spaced. I cannot spot the anomaly.
3. Finally, I notice an anomaly in the indexing capability
of Context. For many years I have relied on makeindex,
which among other things prevents dupicative entries (the
same page number printed twice on the same entry.) However
Context seems to allow that. I can of course revert to the
eplain indexing macros and makeindex, but it seems to me
that Context should not print the same page number twice in
the index.
--
John Culleton
Able Typesetters and Indexers
http://wexfordpress.com
reply other threads:[~2004-04-30 5:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200404291914.10852.john@wexfordpress.com \
--to=john@wexfordpress.com \
--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).