ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: question about linespace adjustment
Date: Tue, 24 Sep 2013 10:51:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1309241050570.27893@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <5241A380.8050608@sil.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1430 bytes --]

On Tue, 24 Sep 2013, Lars Huttar wrote:

> Hello,
> I'm working through the reference manual trying to understand how things
> work in regard to fonts. I'll be submitting clarifications and
> elaborations to the manual in an attempt to help other non-experts to
> grasp the design of ConTeXt.
>
> There's a point that's confusing to me in section 5.5, Line spacing. On
> page 108 of the manual it says
> "Linespacing alters when a new bodyfont is used or when linespacing is
> defined explicitly by \setupinterlinespace (which is explained later)"
>
> But on the next page it says,
> "When you make a font switch the linespacing is adapted when you give
> the command \setupinterlinespace without any setup parameters and also
> when you add the key reset, for example..."
>
> So here's why I'm confused. When you change fonts, (a) does linespacing
> get changed automatically, or (b) do you have to say
> \setupinterlinespace? If (a), then why does the second quote above seem
> to say you need \setupinterlinespace to make it happen? If (b), then
> isn't the first quote above inaccurate?
>
> Is there a distinction being drawn here between "when a new bodyfont is
> used" and "when you make a font switch", or are those just variant
> phrasings for what is intended to mean the same thing?

Contrast

{\switchtobodyfont[14pt] \input ward \endgraf}

with

{\tfc \input ward \endgraf}

Aditya

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2013-09-24 14:51 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 [this message]
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

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=alpine.LNX.2.02.1309241050570.27893@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --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).