From: Herbert Voss <Herbert.Voss@FU-Berlin.DE>
To: ntg-context@ntg.nl
Subject: Re: \startframed spurious whitespace
Date: Wed, 23 Jul 2014 08:20:29 +0200 [thread overview]
Message-ID: <53CF542D.2090303@FU-Berlin.DE> (raw)
In-Reply-To: <53CF0DC3.8020208@rik.users.panix.com>
Am 23.07.2014 03:20, schrieb Rik Kabel:
> There appears to be a bug with \startframed. In the following example,
> the instance with no optional argument sets correctly, while with the
> use of an optional argument (even empty []) a whitespace is introduced
> before the text.
>
> \starttext
> \startframed[]
> Why a space?
> \stopframed
TeX reads "\startframed[] Why a space? \stopframed"
A linebreak is replaced by a space and spaces at the beginning of
a line are ignored by default. Without the optional []
TeX reads "\startframed Why a space? \stopframed"
The first space is "eaten" by TeX while parsing the macro name.
\startframed[]% ignore the space
Why a space?
\stopframed
It is the same behaviour as for \startframed{} ...
> \startframed
> This is ok.
> \stopframed
> \stoptext
This is also not correct, you should use:
\startframed
This is ok.%
\stopframed
\stoptext
Otherwise you'll get a space after the dot.
Herbert
___________________________________________________________________________________
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 prev parent reply other threads:[~2014-07-23 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 1:20 Rik Kabel
2014-07-23 6:20 ` Herbert Voss [this message]
2014-07-23 13:44 ` Rik Kabel
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=53CF542D.2090303@FU-Berlin.DE \
--to=herbert.voss@fu-berlin.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).