From: Vyatcheslav Yatskovsky <yatskovsky@gmail.com>
To: ntg-context@ntg.nl, Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Subject: Re: One interline space setup trouble
Date: Wed, 17 Feb 2010 02:24:13 +0200 [thread overview]
Message-ID: <4B7B372D.9070509@gmail.com> (raw)
In-Reply-To: <mailman.321.1266365410.26807.ntg-context@ntg.nl>
Hi, Wolfgang,
Thank you for the visual hint. The space around 2th paragraph is equal,
I agree with you. However, why there is only a half of interline space
BELOW 1st paragraph, while 3st paragraph has full space ABOVE it? That
is the root cause of my problem.
\setupinterlinespace[line=28pt]
\definedelimitedtext
[example]
[spacebefore=small,
%spacebefore=medium,
%spaceafter=small,
style=\tfx,
before={\setupinterlinespace[line=12pt]}]
\starttext\ruledvtop{\begstrut Most models we discussing here are
specification of dynamic behaviour of SUI. This behaviour is described
in terms of the interactions over time among some entities. The entities
in question fall into two broad categories: {\em endogenous} (intrinsic
to the SUI itself) and {\em exogenous} (belonging to a system's
environment).\endstrut}
\startexample
\ruledvtop{\begstrut All processes that take place inside Earth (and
other planets) are considered endogenous. These processes make the
continents migrate, push the mountains up, trigger earthquakes and
volcanism, and are driven by the warmth that is produced in the core of
Earth. Exogenous processes are all taking place at the outside of the
Earth. Weathering, erosion, transportation and sedimentation are the
main exogenous processes.\endstrut}
\stopexample
\ruledvtop{\begstrut Constants and parameters serve as names for the
values that do not change during a simulation run. In the case of a {\em
constant}, the assigned value remains invariant over all experiments.
Often it is a physical constant, like $g$ -- force of gravity. In the
case of a {\em parameter}, there normally is an intent to explore the
effect upon behaviour of a range of different values for the
parameter.\endstrut}
\stoptext
Regards,
Vyatcheslav
___________________________________________________________________________________
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
___________________________________________________________________________________
next parent reply other threads:[~2010-02-17 0:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.321.1266365410.26807.ntg-context@ntg.nl>
2010-02-17 0:24 ` Vyatcheslav Yatskovsky [this message]
2010-02-17 0:37 ` Wolfgang Schuster
2010-02-17 9:01 ` Wolfgang Schuster
2010-02-20 18:55 Vyatcheslav Yatskovsky
[not found] <mailman.319.1266356392.26807.ntg-context@ntg.nl>
2010-02-16 23:56 ` Vyatcheslav Yatskovsky
2010-02-17 0:10 ` Wolfgang Schuster
[not found] <mailman.294.1266154797.26807.ntg-context@ntg.nl>
2010-02-14 14:05 ` Vyatcheslav Yatskovsky
2010-02-14 14:17 ` Wolfgang Schuster
2010-02-14 14:57 ` Vyatcheslav Yatskovsky
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=4B7B372D.9070509@gmail.com \
--to=yatskovsky@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.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).