* Strange behavior of framed text
@ 2008-02-21 3:09 Aditya Mahajan
2008-02-21 8:19 ` Wolfgang Schuster
0 siblings, 1 reply; 3+ messages in thread
From: Aditya Mahajan @ 2008-02-21 3:09 UTC (permalink / raw)
To: mailing list for ConTeXt users
Hi,
In core-rul.tex we have
%D We define the general (and original) case by just saying:
\defineframedtext[\v!framedtext]
This gives strange user behavior. Consider the following
\defineframedtext[test][width=broad]
\showframe
\starttext
\starttest
\input tufte
\stoptest
\startframedtext[test]
\input tufte
\stopframedtext
\stoptext
The two framedtext have different widths. Why not say
\def\startframedtext
{\dosingleempty\dostartframedtext}
\def\stopframedtext{\dostopframedtext}
Aditya
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange behavior of framed text
2008-02-21 3:09 Strange behavior of framed text Aditya Mahajan
@ 2008-02-21 8:19 ` Wolfgang Schuster
2008-02-21 14:01 ` Aditya Mahajan
0 siblings, 1 reply; 3+ messages in thread
From: Wolfgang Schuster @ 2008-02-21 8:19 UTC (permalink / raw)
To: mailing list for ConTeXt users
On Thu, Feb 21, 2008 at 4:09 AM, Aditya Mahajan <adityam@umich.edu> wrote:
> Hi,
>
> In core-rul.tex we have
>
> %D We define the general (and original) case by just saying:
> \defineframedtext[\v!framedtext]
This defines
\startframedtext ... \stopframedtext and \framedtext{...}
> This gives strange user behavior. Consider the following
>
> \defineframedtext[test][width=broad]
>
> \showframe
> \starttext
>
> \starttest
> \input tufte
> \stoptest
>
> \startframedtext[test]
> \input tufte
> \stopframedtext
This should be:
\dostartframedtext[test]
...
\dostopframedtext
The "[test]" is interpreted as optional argument for the predefined
\startframedtext ... \stopframedtext environment.
> \stoptext
>
> The two framedtext have different widths. Why not say
>
> \def\startframedtext
> {\dosingleempty\dostartframedtext}
>
> \def\stopframedtext{\dostopframedtext}
Take a look into core-rul.tex,
\startframedtext is a short form for \dostartframedtext[framedtext]
and \starttest for \dostartframedtext[test].
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Strange behavior of framed text
2008-02-21 8:19 ` Wolfgang Schuster
@ 2008-02-21 14:01 ` Aditya Mahajan
0 siblings, 0 replies; 3+ messages in thread
From: Aditya Mahajan @ 2008-02-21 14:01 UTC (permalink / raw)
To: mailing list for ConTeXt users
On Thu, 21 Feb 2008, Wolfgang Schuster wrote:
> On Thu, Feb 21, 2008 at 4:09 AM, Aditya Mahajan <adityam@umich.edu> wrote:
>> Hi,
>>
>> In core-rul.tex we have
>>
>> %D We define the general (and original) case by just saying:
>> \defineframedtext[\v!framedtext]
>
> This defines
>
> \startframedtext ... \stopframedtext and \framedtext{...}
>
>> This gives strange user behavior. Consider the following
>>
>> \defineframedtext[test][width=broad]
>>
>> \showframe
>> \starttext
>>
>> \starttest
>> \input tufte
>> \stoptest
>>
>> \startframedtext[test]
>> \input tufte
>> \stopframedtext
>
> This should be:
>
> \dostartframedtext[test]
> ...
> \dostopframedtext
>
> The "[test]" is interpreted as optional argument for the predefined
> \startframedtext ... \stopframedtext environment.
>
>> \stoptext
>>
>> The two framedtext have different widths. Why not say
>>
>> \def\startframedtext
>> {\dosingleempty\dostartframedtext}
>>
>> \def\stopframedtext{\dostopframedtext}
>
> Take a look into core-rul.tex,
>
> \startframedtext is a short form for \dostartframedtext[framedtext]
> and \starttest for \dostartframedtext[test].
I understand why this is happening. However, I think that the behaviour is
inconsistent with how rest of the things behave, and was asking for a
change in core-rul.tex.
Aditya
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-02-21 14:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-21 3:09 Strange behavior of framed text Aditya Mahajan
2008-02-21 8:19 ` Wolfgang Schuster
2008-02-21 14:01 ` Aditya Mahajan
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).