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
___________________________________________________________________________________
