ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: ntg-context@ntg.nl
Subject: Re: `\setupinterlinespace` and `\{start, stop}standardmakeup`
Date: Wed, 27 Jul 2011 17:16:02 +0200	[thread overview]
Message-ID: <1311779762.18419.27.camel@mattotaupa> (raw)
In-Reply-To: <B78BADA9-E169-491C-88ED-AED4EEC6DD62@googlemail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1397 bytes --]

Am Dienstag, den 26.07.2011, 22:55 +0200 schrieb Wolfgang Schuster:
> Am 26.07.2011 um 18:20 schrieb Paul Menzel:

> > following Wolfgang’s advise [1] (Thank you, Wolfgang!) I learned about `
> > \{start,stop}standardmakeup`.
> > 
> > Am Samstag, den 05.02.2011, 19:34 +0100 schrieb Wolfgang Schuster:
> > 
> > […]
> > 
> >> \starttext
> >> 
> >> \startstandardmakeup[align=middle]
> >> \definedfont[Serif at 30pt]Titlepage
> >> \stopstandardmakeup
> >> 
> >> …
> >> 
> >> \stoptext
> > 
> > Now I am having a title consisting of more than one line and I noticed
> > the space between those lines seems to be too small. Trying to increase
> > the space using `\setupinterlinespace` [2] it did not work. I had to use
> > `\blank` in between. Is that expected? Is it documented somewhere when
> > `setupinterlinespace` has no effect?
> 
> Put \setupinterlinespace after \definedfont, e.g.
> 
>   \definedfont[Serif at 30pt]\setupinterlinespace …
> 
> or
> 
>   \definedfont[Serif at 30pt]\setupinterlinespace[2]…

Wolfgang, thank you very much again! That indeed works.

I settled with `\setstrut \strut` as in the example in the Wiki page
»Simple Cover Page« [3].

Although I do get different line spaces when `\setstrut` is left out,
which I also do not understand.


Thanks,

Paul


[3] http://wiki.contextgarden.net/Simple_Cover_Page

[-- Attachment #1.1.2: strut.pdf --]
[-- Type: application/pdf, Size: 6126 bytes --]

[-- Attachment #1.1.3: strut.tex --]
[-- Type: text/x-tex, Size: 267 bytes --]

\starttext
\startstandardmakeup[align=middle]
\definedfont[Serif at 30pt]\strut This is a multiline title with over one line.
\blank[2*big]
\definedfont[Serif at 30pt]\setstrut \strut This is a multiline title with over one line.
\stopstandardmakeup
\stoptext

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- 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:[~2011-07-27 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 16:20 Paul Menzel
2011-07-26 20:55 ` Wolfgang Schuster
2011-07-27 15:16   ` Paul Menzel [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=1311779762.18419.27.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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).