ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: Wolfgang Schuster <schuster.wolfgang@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: question about linespace adjustment
Date: Mon, 30 Sep 2013 16:22:54 -0400	[thread overview]
Message-ID: <5249DD9E.2050305@sil.org> (raw)
In-Reply-To: <09C77DBA-53B8-4040-971E-B649D2545473@gmail.com>

On 9/26/2013 3:47 PM, Wolfgang Schuster wrote:
> You can use \switchtobodyfont to change the size for certain parts of a text
> but it’s best to keep this to a minimum because \tfa etc. are a  lot faster.
>
> The reason why you don’t need \setupinterlinespace when you use
> \switchtobodyfont is that \setupinterlinespace is already called by
> \switchtobodyfont.
>
> Another thing which shouldn’t be forgotten is that \switchtobodyfont
> controls and changes the sizes for \tfa etc.
>
> Wolfgang

To summarize this, and what I've learned from others on this list over
the last week or two, I've updated the wiki page
http://wiki.contextgarden.net/Font_Switching
It's a pretty substantial change, so I hope someone knowledgeable will
look at it and make sure it's right.

I'm trying to find ways to express the fact that, as I understand it,
there are two distinct concepts of "current font" in effect at any given
time:
1) the bodyfont, which is set by \setupbodyfont or \switchtobodyfont
2) the "effective" font (is there a more standard term for this?) which
is changed by \tfa, \ss, etc.

\tfa etc. change the effective font based on what the bodyfont is.
Anything that changes the bodyfont, such as \switchtobodyfont, also
affects the linespacing.
Just changing the effective font does not affect the linespacing.
Changing the bodyfont changes the effective font.

Does that give an accurate picture?

Thanks,
Lars




___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      parent reply	other threads:[~2013-09-30 20:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 14:36 Lars Huttar
2013-09-24 14:51 ` Aditya Mahajan
2013-09-24 16:01 ` Lars Huttar
2013-09-24 17:45   ` Lars Huttar
2013-09-24 18:18     ` luigi scarso
2013-09-24 21:07       ` Lars Huttar
2013-09-24 21:25         ` Aditya Mahajan
2013-09-25 19:54           ` Lars Huttar
2013-09-25 21:00             ` luigi scarso
2013-09-25 21:02             ` Wolfgang Schuster
2013-09-25 21:45               ` Lars Huttar
2013-09-26 19:47                 ` Wolfgang Schuster
2013-09-27 15:57                   ` Lars Huttar
2013-09-30 20:22                   ` Lars Huttar [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=5249DD9E.2050305@sil.org \
    --to=lars_huttar@sil.org \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@gmail.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).