From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: Yatskovsky <yatskovsky@gmail.com>,
"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Why \setupinterlinespace needs [line]?
Date: Mon, 18 Jun 2007 07:57:07 +0200 [thread overview]
Message-ID: <115224fb0706172257la556a1fh541e1bfcffd83b4c@mail.gmail.com> (raw)
In-Reply-To: <996255336.20070616025921@gmail.com>
2007/6/16, Vyatcheslav Yatskovsky <yatskovsky@gmail.com>:
> Hello,
>
> I wonder why one must provide the line argument for \setupinterlinespace?
>
> \setupinterlinespace[line=4ex]
>
> IMHO, it is a tautology. The texshow says that \setupinterlinespace[4ex] (or \setupinterlinespace[big] ) is enough, but I cannot make it work.
>
> Regards,
> Vyatcheslav Yatskovsky
Hi,
the "line"-parameter is used to set the global baselinedistance. You can switch
local to a bigger distance with the "big" or "medium" keywords and back to the
normal distance with "small" or "reset".
\setupinterlinespace[4ex] is not supported, you misunterstod the explanation,
you can only set dimensions for the "line"-parameter.
I made a small example for you:
\starttext
\input knuth\par
\setupinterlinespace[big]
\input knuth\par
\setupinterlinespace[small]
\input knuth\par
\stoptext
Greetings
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-06-18 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1181901601.10289.ntg-context@ntg.nl>
2007-06-15 23:59 ` Vyatcheslav Yatskovsky
2007-06-18 5:57 ` Wolfgang Schuster [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=115224fb0706172257la556a1fh541e1bfcffd83b4c@mail.gmail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=ntg-context@ntg.nl \
--cc=yatskovsky@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).