From: Uwe Koloska <koloska@voiceinterconnect.de>
Subject: Re: Linespacing in startstop
Date: Thu, 20 Jun 2002 17:18:01 +0200 [thread overview]
Message-ID: <3D11F229.1090900@voiceinterconnect.de> (raw)
In-Reply-To: <200206200635.40418.ishamid@attbi.com>
Idris S Hamid wrote:
> On Thursday 20 June 2002 01:56, Uwe Koloska wrote:
>
>> Idris S Hamid wrote:
>>
>>> The following two ways of defining the linespacing inside
>>> a startstop environment don't seem to work:
>>
>> This is a version that works (but can be improved):
>
>
> Strange, it does not work at all here (there is still no
> proper interlineline spacing), and the <,after=> gets echoed
> in the output. This is under the default format file with a
> recent ConTeXt. Thanks for trying though. Here is the
> definition again:
>
> \definestartstop [test] [commands={\switchtobodyfont[18pt]
> \setupinterlinespace[line=36pt]}]%,after={\blank[big]}}]
There is (besides the commenting out) an unmatched brace.
\switobodyfont and \setupinterlinespace have to grouped by
braces (to ty them to commands) and \blank[big] has to be
surrounded by braces. The curly braces [] are from commands to
the end of \blank[big].
And have you honoured the blank line _before_ \stoptest? This
is important cause TeX switches linespacing at the end of a
paragraph. (Normally \setupinterlinespace forces this within
the paragraph -- but it seems to fail here)
Uwe
--
voiceINTERconnect www.voiceinterconnect.de
... smart speech applications from germany
next prev parent reply other threads:[~2002-06-20 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 15:48 Idris S Hamid
2002-06-20 7:56 ` Uwe Koloska
2002-06-20 12:35 ` Idris S Hamid
2002-06-20 15:18 ` Uwe Koloska [this message]
2002-06-20 17:12 ` Idris S Hamid
2002-06-21 20:32 ` Patrick Gundlach
2002-06-23 22:00 ` Hans Hagen
2002-06-21 21:48 ` Patrick Gundlach
2002-06-23 11:07 ` Hans Hagen
2002-06-23 23:05 ` Idris S Hamid
2002-06-25 19:30 ` Hans Hagen
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=3D11F229.1090900@voiceinterconnect.de \
--to=koloska@voiceinterconnect.de \
/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).