From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: staticMPfigure problem with \runMP[TEX]graphicsfalse
Date: Fri, 05 Jan 2007 02:38:08 +0000 [thread overview]
Message-ID: <E1H2ey8-0001IU-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Thu, 04 Jan 2007 22:44:12 +0100." <459D752C.5010204@wxs.nl>
> you can test the beta
I used the same test file:
\starttext
\startstaticMPfigure{fig:ellipse}
path p;
p := fullcircle scaled 2in yscaled 0.5;
label(btex hello etex, origin);
draw p;
\stopstaticMPfigure
\placefigure[right,none]{}{\usestaticMPfigure[fig:ellipse]}
\input tufte
\stoptext
No luck with ver: 2007.01.04 17:37 MK II. With all three settings
(the two runMP... ones and shell_escape) false, the static figure is
about 1pt wide. The tufte text has a slight indentation in the right
margin to make room for it.
With all three settings true, it works fine.
With the run* settings true but shell_escape false, the whitespace
allocated is a block for a 'dummy' rectangle (with grey background).
So it looks like the same behavior as before.
With all the settings false, this is the texexec.tex produced:
\setupoutput[pdftex]
\setupcolors[state=start]
\global \loadfontfileoncetrue \readfile {cont-en.tmp}{}{}\starttext
\startMPpage
beginfig(1);
path p;
p := fullcircle scaled 2in yscaled 0.5;
label(btex hello etex, origin);
draw p;
endfig; \stopMPpage
\stoptext
Running 'texexec texexec.tex' produces the right pdf file, so I don't
know what's going on. But off-list I'm sending you a tar.gz file that
has the two runs, each in a separate directory, and then the recursive
diff of them.
-Sanjoy
`Not all those who wander are lost.' (J.R.R. Tolkien)
prev parent reply other threads:[~2007-01-05 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 7:33 Sanjoy Mahajan
2007-01-04 9:35 ` Taco Hoekwater
2007-01-04 13:49 ` Sanjoy Mahajan
2007-01-04 15:37 ` Hans Hagen
2007-01-04 17:28 ` Sanjoy Mahajan
2007-01-04 21:44 ` Hans Hagen
2007-01-05 2:38 ` Sanjoy Mahajan [this message]
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=E1H2ey8-0001IU-00@skye.ra.phy.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--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).