From: Vincent Hennebert via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Vincent Hennebert <vhennebert@gmail.com>
Subject: Rendering Standalone MetaPost Graphics with ConTeXt
Date: Thu, 19 May 2022 10:23:45 +0200 [thread overview]
Message-ID: <CAMUWKuoYRkvEvxsDg6GLk9mhuA35WDKyY28UEAcCZHgDVfamMg@mail.gmail.com> (raw)
I’d like to use MetaPost to generate all sorts of standalone graphics
(ultimately converted to SVG). For various reasons (among others,
MetaFun and advanced text processing) I want to use MetaPost as
embedded in ConTeXt rather than a standalone installation.
---- metapost.mp ----
fill fullcircle scaled 10cm;
----
Whether I run
context metapost.mp
or
mtxrun --script metapost metapost.mp
I get a PDF document that contains no page.
The mtxrun version generates the following temp file:
---- mptopdf-temp.tex ----
\starttext
\startMPinclusions
fill fullcircle scaled 10cm;
\stopMPinclusions
\stoptext
----
Looking at the wiki, it seems that \startMPinclusions is not meant to
actually render any content, just to include MetaPost code like
function definitions. I guess I would have expected \startMPpage
instead.
Am I doing something wrong, or is that an error in ConTeXt?
Thanks,
Vincent
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-05-19 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 8:23 Vincent Hennebert via ntg-context [this message]
2022-05-19 8:53 ` śrīrāma via ntg-context
2022-05-19 16:22 ` Vincent Hennebert via ntg-context
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=CAMUWKuoYRkvEvxsDg6GLk9mhuA35WDKyY28UEAcCZHgDVfamMg@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=vhennebert@gmail.com \
/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).