From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: followup metapost textext?
Date: Fri, 23 Dec 2005 00:05:41 +0100 [thread overview]
Message-ID: <43AB3145.4050904@elvenkind.com> (raw)
In-Reply-To: <510D86FE-7251-40A4-AE35-CC02EB4686A5@science.uva.nl>
Hans van der Meer wrote:
> Sorry, my last posting ran into another, earlier thread. In order to
> prevent confusion I take the liberty to repeat my findings on the code
> below as reply to Hans Hagen's last posting.
>
> When I take the mpgraph mp-input for metapost produced by the ConTeXt
> run I see:
>
> (1) running "system(mpost -progname=mpost -mem=metafun standalone2-
> mpgraph)...executed." as the log shows gives the wrong metafont output.
> I also ran mpost with those parameters standalone on that mp- file and
> got the same bad result.
The input and output (+ log) from that incorrect run should pinpoint
the problem. Can you email or post these files please?
Taco
next prev parent reply other threads:[~2005-12-22 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 18:01 Hans van der Meer
2005-12-22 7:49 ` Taco Hoekwater
2005-12-22 17:11 ` Hans van der Meer
2005-12-22 22:05 ` Hans van der Meer
2005-12-22 22:22 ` Hans Hagen
2005-12-22 22:49 ` Hans van der Meer
2005-12-22 23:05 ` Taco Hoekwater [this message]
2005-12-22 23:26 ` Hans Hagen
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=43AB3145.4050904@elvenkind.com \
--to=taco@elvenkind.com \
--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).