* betex -etex block parsing bug
@ 2005-12-20 19:59 Willi Egger
2005-12-20 20:53 ` Hans Hagen
0 siblings, 1 reply; 5+ messages in thread
From: Willi Egger @ 2005-12-20 19:59 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Hi,
It seems that there is a problem with parsing betex - etex blocks in the
following situation:
I can not say with which version this has been introduced. (I messed up
my old TeX, so I have only new ones)
I tested this with the version of 19-12-2005 an 30-11-2005.
\setMPtext{1}{CENTER}
\startuseMPgraphic{TEST}
picture Text;
Text := \MPbetex{1};
draw Text;
\stopuseMPgraphic
the betex-etex block will look like 'tex CENTERetex' of course the etex
should be separated by a space.
For testing I attach the minimal file.
Willi
[-- Attachment #2: test.tex --]
[-- Type: text/plain, Size: 452 bytes --]
% TEST betex etex block: BUG parsing ...
% Context file
% filename test.tex
% Willi Egger
% 20-12-2005
\setupoutput[pdftex]
\usemodule[txt]
\setMPtext{1}{CENTER} % remove the space before the right brace, erase the temporary files
% then compile and the run will fale!
\startuseMPgraphic{TEST}
picture Text;
Text := \MPbetex{1};
draw Text ;
\stopuseMPgraphic
\starttext
\startTEXpage
\useMPgraphic{TEST}
\stopTEXpage
\stoptext
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: betex -etex block parsing bug
2005-12-20 19:59 betex -etex block parsing bug Willi Egger
@ 2005-12-20 20:53 ` Hans Hagen
2005-12-20 21:15 ` Willi Egger
0 siblings, 1 reply; 5+ messages in thread
From: Hans Hagen @ 2005-12-20 20:53 UTC (permalink / raw)
Willi Egger wrote:
> Hi,
>
> It seems that there is a problem with parsing betex - etex blocks in
> the following situation:
> I can not say with which version this has been introduced. (I messed
> up my old TeX, so I have only new ones)
> I tested this with the version of 19-12-2005 an 30-11-2005.
>
> \setMPtext{1}{CENTER}
>
> \startuseMPgraphic{TEST}
> picture Text;
> Text := \MPbetex{1};
> draw Text;
> \stopuseMPgraphic
>
> the betex-etex block will look like 'tex CENTERetex' of course the
> etex should be separated by a space.
> For testing I attach the minimal file.
this was the old code:
% \def\MPtext #1{\getvalue{\@@MPT#1}}
% \def\MPstring #1{"\getvalue{\@@MPT#1}"}
% \def\MPbetex #1{btex \getvalue{\@@MPT#1} etex}
but due to some reported problems with undefined texts, it became
\def\MPtext #1{\executeifdefined{\@@MPT#1}\empty}
\def\MPstring #1{"\executeifdefined{\@@MPT#1}\empty"}
\def\MPbetex #1{btex \executeifdefined{\@@MPT#1}\empty etex}
so, let's add a space:
\def\MPbetex #1{btex \executeifdefined{\@@MPT#1}\empty\space etex}
(interesting is that it runs ok here -)
Hans
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: betex -etex block parsing bug
2005-12-20 20:53 ` Hans Hagen
@ 2005-12-20 21:15 ` Willi Egger
2005-12-20 22:20 ` Hans Hagen
0 siblings, 1 reply; 5+ messages in thread
From: Willi Egger @ 2005-12-20 21:15 UTC (permalink / raw)
Hi Hans,
thanks for your immediate reply. Indeed it is strange that it runs ok in
your environment.
But where to put this altered definition?
Cheers
Willi
Hans Hagen wrote:
> Willi Egger wrote:
>
>> Hi,
>>
>> It seems that there is a problem with parsing betex - etex blocks in
>> the following situation:
>> I can not say with which version this has been introduced. (I messed
>> up my old TeX, so I have only new ones)
>> I tested this with the version of 19-12-2005 an 30-11-2005.
>>
>> \setMPtext{1}{CENTER}
>>
>> \startuseMPgraphic{TEST}
>> picture Text;
>> Text := \MPbetex{1};
>> draw Text;
>> \stopuseMPgraphic
>>
>> the betex-etex block will look like 'tex CENTERetex' of course the
>> etex should be separated by a space.
>> For testing I attach the minimal file.
>
>
>
> this was the old code:
>
> % \def\MPtext #1{\getvalue{\@@MPT#1}}
> % \def\MPstring #1{"\getvalue{\@@MPT#1}"}
> % \def\MPbetex #1{btex \getvalue{\@@MPT#1} etex}
>
> but due to some reported problems with undefined texts, it became
>
> \def\MPtext #1{\executeifdefined{\@@MPT#1}\empty}
> \def\MPstring #1{"\executeifdefined{\@@MPT#1}\empty"}
> \def\MPbetex #1{btex \executeifdefined{\@@MPT#1}\empty etex}
>
> so, let's add a space:
>
> \def\MPbetex #1{btex \executeifdefined{\@@MPT#1}\empty\space etex}
>
> (interesting is that it runs ok here -)
>
> Hans
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-12-21 9:26 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-12-20 19:59 betex -etex block parsing bug Willi Egger
2005-12-20 20:53 ` Hans Hagen
2005-12-20 21:15 ` Willi Egger
2005-12-20 22:20 ` Hans Hagen
2005-12-21 9:26 ` Willi Egger
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).