From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Uppercase headings
Date: Fri, 31 Mar 2006 19:16:27 +0200 [thread overview]
Message-ID: <442D63EB.4090509@elvenkind.com> (raw)
In-Reply-To: <B8B26F211A66434887C806A8DEE3577BFD35@kpsrv1.kpatents.local>
Ville Voipio wrote:
>
> I started to edit an old document with capitalized headings. Making the
> headings was rather difficult (as can be seen on this list about a year
> ago), and now it seems to have broken again.
>
> I have:
>
> \setuphead[title]
> [page=yes,
> before={\strut\blank[5*big]},
> after={\textrule\blank},
> align=middle,
> style=\tfb,
> textcommand=\WORD
> ]
>
> This worked fine in the past. Not anymore:
Something like this is why there is a new syntax:
\setuphead[title]
[deeptextcommand=\WORD]
Does that work?
Taco
next prev parent reply other threads:[~2006-03-31 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 15:55 Ville Voipio
2006-03-31 16:48 ` Hans Hagen
2006-03-31 16:51 ` Hans Hagen
2006-03-31 17:16 ` Taco Hoekwater [this message]
2006-03-31 17:06 Ville Voipio
2006-03-31 17:25 Ville Voipio
2006-03-31 21:31 ` Hans Hagen
2006-03-31 21:49 ` Hans Hagen
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=442D63EB.4090509@elvenkind.com \
--to=taco@elvenkind.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).