From: Hans Hagen <pragma@wxs.nl>
Cc: NTG-ConTeXt <ntg-context@ntg.nl>
Subject: Re: Fw: Subsections
Date: Mon, 30 Aug 1999 11:01:57 +0200 [thread overview]
Message-ID: <37CA4885.E8FE7F12@wxs.nl> (raw)
In-Reply-To: <004001bef2bb$28ebc9e0$0c01a8c1@loginbv.com>
Gilbert van den Dobbelsteen wrote:
> Nice challenge, but in the end pretty easy:
>
> \setuphead
> [subsection]
> [alternative=text,
> before={\blank[10pt]},
> after=,
> style=bold,
> command=\mysubsection]
>
> \def\mysubsection#1#2{#2.}
>
> You could also say: number=no, to tell context, that this will not be
> numbered. Though the output is not an different at all, the table of
> contents would be. EXperimenting is the game here.
>
> Now I wonder, would Hans come up with a completely different solution?
No. But it makes me think of adding a 'stopper' (afsluiter) feature.
Because 'subject' inherits from 'section', there is no need for the the
number=no, just use \subsubject. Also, beware of lower level headers
inheriting defaults!
Note: when cross document links are turned on, (see pdftex manuals as an
example of this), text headers are handled ok, even multiple ones, even
when spanning mulriple lines, like in:
[bf: a subsection] [bs: a subsubsection] the text etc
If one wants to see some uncomprehensible horrible tex, take a look at
the code used to do this: typeset, unfold, combine, unwhateverbox, etc.
This is a typical example of nightmare programming.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-08-30 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 7:42 Gilbert van den Dobbelsteen
1999-08-30 9:01 ` Hans Hagen [this message]
1999-08-31 5:16 ` Fw: Subsections (spoke too soon) David Arnold
1999-08-31 7:46 ` Hans Hagen
1999-08-30 19:34 ` Fw: Subsections David Arnold
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=37CA4885.E8FE7F12@wxs.nl \
--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).