From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: header styles
Date: Thu, 25 Jan 2007 14:36:57 +0100 [thread overview]
Message-ID: <20070125143657.171e5235.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <FBFD1D38-73A9-4BB9-9E3C-742EC856707E@extern.uio.no>
On Wed, 17 Jan 2007 22:55:00 +0100
Rolf Marvin Bøe Lindgren <roffe@extern.uio.no> wrote:
> I've sort of looked around, I believe, but not found a simple way to
> change the size of headings.
>
\setuphead[subject][style={\switchtobodyfont[14pt,sans]},textstyle=\bf]
or
\setuphead[subject][style={\switchtobodyfont[14pt,sans]\bf}]
> \setuphead[subject][style=\ss\bfb] makes a nice medium sized heading,
> but what is the canonical way to set up numbered headings, sans
> serif, boldface, 14pt?
> --
> Rolf Lindgren
> roffe@extern.uio.no
>
Wolfgang
prev parent reply other threads:[~2007-01-25 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 21:55 Rolf Marvin Bøe Lindgren
2007-01-25 13:36 ` Wolfgang Schuster [this message]
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=20070125143657.171e5235.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.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).