\startframed spurious whitespace

\startframed spurious whitespace

[Rik Kabel]

[-- Attachment #1.1: Type: text/plain, Size: 375 bytes --]

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

    \startframed
    This is ok.
    \stopframed
    \stoptext

-- 
Rik



[-- Attachment #1.2: Type: text/html, Size: 739 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: \startframed spurious whitespace

[Herbert Voss]

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
___________________________________________________________________________________

Re: \startframed spurious whitespace

[Rik Kabel]

On 2014-07-23 02:20, Herbert Voss wrote:
> 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{} ...

Yes. TeX does read it that way. I have written LaTeX packages and know 
the issues. ConTeXt, on the other hand, makes an extra effort, at least 
with the start/stop commands, to do it differently. That is one of the 
primary benefits, to my mind, of using 
\starttexdefinition...\stoptexdefinition instead of \def.

Perhaps I am extending my expectation of that improved behavior to 
\startframed[], but it is not, I think, an unreasonable hope.
>>      \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.

In a real document I would likely use \par or a blank line at that 
point, but I was trying to provide a DWE (demonstrative working 
example), if not a MWE, to show the issue with the leading space. 
Line-feed hiding with % does not belong in the content of the document 
unless one chooses to drop back to TeX instead of writing within the 
ConTeXt package.
> Herbert

-- 
Rik
___________________________________________________________________________________
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
___________________________________________________________________________________