ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Cc: taco@elvenkind.com
Subject: Re: fundamental problem with headings
Date: Thu, 10 Mar 2005 23:11:41 +0100	[thread overview]
Message-ID: <a06210200be566c4e7362@[83.176.133.146]> (raw)

>  Steffen Wolfrum wrote:
>  > Hi,
>  >
>  > Each kind of "emphasizing" - like \it \bf \cap \sc etc. -
>   > lets the respective phrase fall back to the documents
>   > bodyfont (see example below).
>  >
>  > How can I avoid this bug?
>
>  not a bug, this is the expected behaviour of \definefont.
>
>  > Do I use wrong code?
>
>  Yes. \definefont defines a single font (hence it's name).
>
>  What you actually need is a full-blown bodyfont switch:
>
>     \def\SectionStyle{%
>       \switchtobodyfont[rm,20pt]
>       \setupinterlinespace[line=30pt]
>     }
>
>  Greetings, Taco


OK, so my example changes to
\starttext

\def\Textit{\groupedcommand\it\/}

% \definefont[SectionFont][SerifBold at 20pt]
% \def\SectionStyle{\SectionFont\setupinterlinespace[line=30pt]}

  \def\SectionStyle{%
    \switchtobodyfont[rm,20pt]
    \setupinterlinespace[line=30pt]
  }

\setuphead[section]
[alternative=paragraph,style=\SectionStyle]

text

\section{heading \Textit{italic} heading}

text

\stoptext




But if the heading should be set in general in a bold face what do I 
use instead of \rm so that italic parts of he heading will be typeset 
in bold-italic (and \sc parts to bold-smallcaps)?
I guess something (next to serif, sans, mono, ...) like serifbold 
(\brm?) should be defined in my typescript?

Thank you,


Steffen

             reply	other threads:[~2005-03-10 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 22:11 Steffen Wolfrum [this message]
2005-03-10 23:17 ` Adam Lindsay
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 12:45 Steffen Wolfrum
2005-03-11 11:33 Steffen Wolfrum
2005-03-11 11:46 ` Adam Lindsay
2005-01-24 14:27 Steffen Wolfrum
2005-01-24 10:46 Steffen Wolfrum
2005-01-24 11:09 ` Taco Hoekwater
2005-01-24 19:15   ` Willi Egger
2005-01-24 19:11 ` Willi Egger

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='a06210200be566c4e7362@[83.176.133.146]' \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).