ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: interline spacing, me too
Date: Thu, 15 Oct 2009 23:53:58 +0200	[thread overview]
Message-ID: <06517F4B-9652-4195-905E-A9BDBC3AEC90@uni-koblenz.de> (raw)
In-Reply-To: <4AD77E23.90003@elvenkind.com>


[-- Attachment #1.1: Type: text/plain, Size: 1264 bytes --]


Am 15.10.2009 um 21:55 schrieb Taco Hoekwater:

> Taco Hoekwater wrote:
>> Andreas Harder wrote:
>>>
>>> There is also \setupbodyfontenvironment (Problem with \chapter{…}  
>>> or did I something wrong?). Now I've to use \switchtobodyfont[…]  
>>> instead of \tfa and so on.
>> Why not do that? If you are fiddling with the interline space, it is
>> IMO better to switch the whole bodyfont, just in case.

Okay, thank you for your advise. Why I can't say:
\setupbodyfontenvironment [minion] [14.4pt] [interlinespace=3ex] % \tfa
\setupbodyfontenvironment [minion]  [9.6pt] [interlinespace=4ex] % \tfx
and then use style=\tfa?

> Oh, I see. Somehow the interlinespace setting from the typescript
> doesn't come through. You could do this:
>
> \setuphead
>  [chapter]
>  [style={\switchtobodyfont[18pt]\setupinterlinespace[line=10ex]}]
>
> but it is weird that it does not work out of the box.

Because it works if one set \setupinterlinespace[line=5ex] for the  
whole document … By the way, what happened with \setupinterlinespace 
[big]?

Anyway, thanks for your reply!

PS. I don't want to be too greedy, but could you also have a look at http://archive.contextgarden.net/message/20091014.122329.48e0bcc0.en.html 
  ?

	Andreas

[-- Attachment #1.2: Type: text/html, Size: 2124 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 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:[~2009-10-15 21:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 13:39 Problem with \setupinterlinespace luigi scarso
2009-10-15 13:50 ` Peter Rolf
2009-10-15 13:59   ` luigi scarso
2009-10-15 16:32 ` interline spacing, me too Andreas Harder
2009-10-15 16:54   ` Peter Rolf
2009-10-15 19:46   ` Taco Hoekwater
2009-10-15 19:55     ` Taco Hoekwater
2009-10-15 21:53       ` Andreas Harder [this message]
2009-10-16  6:13         ` Taco Hoekwater
2009-10-16 12:12           ` Hans Hagen
2009-10-16 12:30             ` Andreas Harder
2009-10-16 12:35               ` Hans Hagen
2009-10-16 12:41                 ` Andreas Harder
2009-10-16 13:39                   ` Aditya Mahajan
2009-10-16 13:58                     ` Andreas Harder

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=06517F4B-9652-4195-905E-A9BDBC3AEC90@uni-koblenz.de \
    --to=aharder@uni-koblenz.de \
    --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).