From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: mptopdf problems
Date: Tue, 31 Oct 2006 20:41:01 +0100 [thread overview]
Message-ID: <92A0672C-3995-4D00-BBEE-8B4215C1451B@uni-bonn.de> (raw)
In-Reply-To: <A49C4AC8-4B15-493A-B8BE-818002FEABD7@uni-bonn.de>
Disregard the message; I just updated ConTeXt with Gerben's latest
installer package, and the problem is gone.
Thomas
On Oct 31, 2006, at 11:34 AM, Thomas A. Schmitz wrote:
> Hi all,
>
> I'm struggling with a new installation here on my MacBook. One
> problem I have is that mptopdf bails out when I have textext code in
> my mpgraphics. There were a couple of similar problems in the mailing
> list a while back, but no real solution. When I compare the
> mpgraph.log output from this new install with the output from a good
> installation, these are the diffs I get:
>
> -(/usr/local/teTeX/share/texmf.local/web2c/natural.tcx)
> **test-mpgraph.mp
> (test-mpgraph.mp
> -{randomseed:=33}
> -write0 = `test-mpgraph.mpo'.
> +{randomseed:=3203}
> -write0 = `test-mpgraph.mpt'.
> +! Extra tokens will be flushed.
> +<to be read again>
> + @@@
> +<argument> ...font [MyAGaramondPrempnum,11pt] "@@@
> +
> string.contextversion
> +graphictextdirective->...graphictextstring&(TEXT0)
> + &CRLF;
> +<to be read again>
> + ;
> +l.19 string contextversion;
> +
> +? x
> - [1]
> -metafun 2006-10-30 22:30
> - )
> -1 output file written: test-mpgraph.1
>
> From what I've understood, metapost seems to be calling the wrong
> text (tex instead of texexec), but where can this be fixed? The
> configuration on both installations is identical (write 18 enabled,
> identical cont-sys.tex).
>
> Thanks
>
> Thomas
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-10-31 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 10:34 Thomas A. Schmitz
2006-10-31 19:41 ` Thomas A. Schmitz [this message]
2006-10-31 19:58 ` Aditya Mahajan
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=92A0672C-3995-4D00-BBEE-8B4215C1451B@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).