From: Guy Worthington <guyw@multiline.com.au>
Subject: Re: Inserting a mini toc into the chapter heading
Date: 13 Feb 2003 11:04:18 +0800 [thread overview]
Message-ID: <uheb851al.fsf@multiline.com.au> (raw)
In-Reply-To: <uisvprixv.fsf@multiline.com.au>
Just following up on my own post. The following code has the effect I
was after. If you want to use it as a template, you'd be advised to
read my method in constructing such ugliness.
To remind you, I want to increase the font weight of the chapter
number, but not increase the font weight of the chapter title. Thus,
facing my usual dilemma -- so many commands and no f*cking clues, I
added the \string command immediately before the parameter containing
the chapter number, #1, to see what #1 actually contained.
If you do this, you'll see that #1 contains something else, infact #1
starts out as ``dostartattributes@@ko ... ''. I've no idea how to
read the source code, so at this point, I decided to redefine my
chapter style parameter \BigHeadFont locally, before #1 is expanded.
And so, if you read the code, you'll see a font definition
\definefont[BigHeadFont][SerifBold at 40pt]
buried deep within the code. This seems to work, although redefining
font definitions on the fly is probably not good practice.
I also wanted to move the chapter number, up to the top right hand
corner of the main text area. I did this increasing the amount of
glue until the number was pushed outside its box.
Here is the code:
%% chapter head layout
\setupcolors[state=start]
\setuplist[section]
[style=boldslanted,
align=right,
interaction=all,
symbol=1,
width=0.5em,
pagenumber=no,
before=,
after=]
\setuphead[chapter]
[header=empty,
style=BigHeadFont,
alternative=command,
command=\ContentsHead,
page=right,
after={\blank[2*big]}]
\definefont[BigHeadFont][Serif at 24.9pt]
\def\ContentsHead#1#2%
{\setupframed[frame=off]
\framed[width=\hsize,offset=overlay]
{\placesidebyside
{\doifelsenothing{#1}
{\framed[width=.6\hsize]{}} % dummy
{\framed
[width=.6\hsize,offset=1em,strut=no,align=right,background=screen]
{{\tfa In this chapter:} \blank
\placelist[section][criterium=chapter]}}}
{\framed
[width=.4\hsize,strut=no,align=left]
{\definefont[BigHeadFont][SerifBold at 40pt]
%% Typeset Chapter Number
\hbox{%
\vbox to 24.9pt{% size of BigHeadFont
\vss
#1}}}
\vfilll}}
%% Typeset Chapter Title
\llap{\lower29.9pt\hbox{#2\hskip1em}}} % 24.9pt x 1.2
\starttext
%\showmakeup
\chapter {Berend}
\section {Botje}
\section {Botje}
\section {Botje}
\stoptext
next prev parent reply other threads:[~2003-02-13 3:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 7:55 Guy Worthington
2003-02-11 9:51 ` Patrick Gundlach
2003-02-12 9:01 ` Guy Worthington
2003-02-12 10:15 ` Willi Egger
2003-02-12 11:15 ` Hans Hagen
2003-02-11 12:06 ` Hans Hagen
2003-02-12 8:39 ` Guy Worthington
2003-02-13 3:04 ` Guy Worthington [this message]
2003-02-13 16:52 ` Hans Hagen
2003-02-14 11:51 ` Guy Worthington
2003-02-14 13:10 ` Guy Worthington
2003-02-14 13:32 ` Hans Hagen
2003-02-14 13:50 ` Bruce D'Arcus
2003-02-14 13:52 ` Adam Lindsay
2003-02-14 20:15 ` Willi Egger
2003-02-17 1:23 ` 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=uheb851al.fsf@multiline.com.au \
--to=guyw@multiline.com.au \
--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).