From: Hans van der Meer <hansm@science.uva.nl>
Subject: Re: metapost textext?
Date: Thu, 22 Dec 2005 23:44:02 +0100 [thread overview]
Message-ID: <621F0054-058F-46F0-B582-F3B8202A6929@science.uva.nl> (raw)
In-Reply-To: <43A98FC4.4080403@elvenkind.com>
I have another piece of information on my previous 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.
(2) running texexec --mptex on the file gives the correct result.
Would this help locating the problem?
My mpost is according to mpout.log "This is MetaPost, Version 0.901
(Web2C 7.5.3) (mem=mpost 2005.11.12)".
yours sincerely,
dr. H. van der Meer
On Dec 21, 2005, at 18:24, Taco Hoekwater wrote:
> Peter Rolf wrote:
>> Hans Hagen wrote:
>>> Hans van der Meer wrote:
>>>
>>>
>>>> Panic using metapost in context.
>>>> This used to work. I did a file that previously
>>>> (\thisisutilityversion
>>>> {1998.12.20}) had good output but now has "unknown" everywhere
>>>> for textext calls!
>>>>
>>>> \starttext
>>>> \startuseMPgraphic{one}
>>>> draw (0,0)--(100,0)--(100,50)--(50,50)--(50,100)--(0,100)--
>>>> (0,0);
>>>> label (textext("label"), (10,25));
>>>> \stopuseMPgraphic
>>>> \useMPgraphic{one}
>>>> \stoptext
>>>>
>>>> But now I see "unknown" as the text typeset instead of "label"!
>>>> What happened. This is disastrous.
>>>
>>> this normally points to an error in mp processing (unknown is the
>>> fall
>>> back text), not so much to something wrong with context (i hope)
>>>
>>> it runs ok here; how does it runs at other machines?
>>>
>> no problem here (using latest version)
>
> Runs without problems here as well. The most likely cause of problems
> in this subsystem nowadays is a
> "format was written by (pdf)(e)tex"
> error message from a (pdf)(e)tex executable. Unfortunately, I also
> find it hard to trace this stuff. It may help to run the example
> in an isolated directory and zip&mail everything in the directory
> afterwards. I can at least have a look, but cannot give guarantees.
>
> Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-12-22 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 16:13 Hans van der Meer
2005-12-21 16:35 ` Hans Hagen
2005-12-21 16:58 ` Peter Rolf
2005-12-21 17:24 ` Taco Hoekwater
2005-12-22 22:44 ` Hans van der Meer [this message]
2005-12-21 20:53 ` Willi Egger
2005-12-21 19:26 ` David Arnold
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=621F0054-058F-46F0-B582-F3B8202A6929@science.uva.nl \
--to=hansm@science.uva.nl \
--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).