From: Steffen Wolfrum <xmailings@estfiles.de>
Subject: Re: Re: Two questions on \setupinterlinespace
Date: Thu, 11 Sep 2003 16:28:38 +0200 [thread overview]
Message-ID: <a05210603bb86363d3192@[217.184.17.48]> (raw)
Patrick Gundlach <pg@levana.de> wrote:
> Steffen Wolfrum <xmailings@estfiles.de> writes:
>
> > 1. If I define \setupinterlinespace at the beginning of my document
> > then all "elements" (like bodytext,foonotes, chapter, section etc.)
> > are affected. How can I define the interlinespaces for each
> > individually?
>
> Does chapter 6 of "Fonts in ConTeXt" (mfonts.pdf) help?
>
> Patrick
No, it doesn't - or at least my brain is too latexy to understand how
this should look in ConTeXt:
\renewcommand{\normalsize}{\fontsize{10pt}{13pt}\selectfont}
\renewcommand{\footnotesize}{\fontsize{8.5pt}{10pt}\selectfont}
\newcommand{\heading_1}{\fontsize{14}{20}\selectfont}
\newcommand{\heading_2}{\fontsize{12}{14}\selectfont}
Maybe you can help translating?
Steffen
reply other threads:[~2003-09-11 14:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='a05210603bb86363d3192@[217.184.17.48]' \
--to=xmailings@estfiles.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).