ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Cc: atl@comp.lancs.ac.uk
Subject: Re: fundamental problem with headings
Date: Fri, 11 Mar 2005 12:33:13 +0100	[thread overview]
Message-ID: <a06210201be572db73b5b@[62.134.77.169]> (raw)

Adam Lindsay <atl@comp.lancs.ac.uk> wrote:

>  Steffen Wolfrum said this at Thu, 10 Mar 2005 23:11:41 +0100:
>
>  >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?
>
>  I'm a bit confused why you're not using \em in this situation, as it
>  adapts to both bold and roman contexts. If you dislike that it defaults
>  to slanted, then there's:
>
>  \setupbodyfontenvironment[default][em=italic]
>  {\bf Hello \em World} Hello \em World
>
>
>  But if you want to follow the path of defining your own, adaptive
>  switches, then you could look at these goodies already defined in font-ini:
>
>  %D \macros
>  %D   {emphbf,emphit,emphsl,emphtf}
>  %D
>  %D The next emphasis alternatives are for \THANH. They adapt
>  %D their style as good as possible.
>
>  \def\emphbf{\groupedcommand{\bf\def\emphit{\bi}\def\emphsl{\bs}}{}}
>  \def\emphit{\groupedcommand{\it\def\emphbf{\bi}\def\emphsl{\sl}}{}}
>  \def\emphsl{\groupedcommand{\sl\def\emphbf{\bs}\def\emphit{\it}}{}}
>  \def\emphtf{\groupedcommand{\tf\def\e
>  mphbf{\bf}\def\emphit{\it}\def\emphsl{\sl}}
>  {}}


Right. I can use \em.

But my workflow of using ConTeXt is typesetting already finished 
books (.doc-files). And so I would like to change the "text" as 
little as possible and instead use an suitable set of typescript and 
setup environment.

That's why I thought I'd need a mysans (or \myrm) defined in the 
typescript to be used in Taco's full-blown bodyfont switch as 
described above:

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



In fact, this is something I would like to have also for other 
purposes (for example to use a second set of oldstyle figures): 
defining my own *myserif* or *mysans* that could be used then in a 
typescriptfile the same way as sans, serif and mono are used there.

But up to now I didn't manage it.

Somebody did and would like to share his/her knowledge?


Thank you,

Steffen

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 11:33 Steffen Wolfrum [this message]
2005-03-11 11:46 ` Adam Lindsay
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 12:45 Steffen Wolfrum
2005-03-10 22:11 Steffen Wolfrum
2005-03-10 23:17 ` 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='a06210201be572db73b5b@[62.134.77.169]' \
    --to=context@st.estfiles.de \
    --cc=atl@comp.lancs.ac.uk \
    --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).