ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Kitzmiller <kitz@inradius.net>
To: ntg-context@ntg.nl
Cc: kitz@inradius.net
Subject: mptopdf in minimals
Date: Wed, 17 Apr 2013 16:51:14 -0400	[thread overview]
Message-ID: <A4FA30C9-65C3-42A9-AB00-E26C333A9FB2@inradius.net> (raw)

Is there something extra needed to use mptopdf with only context minimal?

Experimenting with having just context standalone on mac osx:
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     Compiling with just mpost or using a context \startMPcode wrapper works, e.g.:

beginfig(1);
draw origin--(100,100);
endfig;
end

works with command line mpost % 

This is MetaPost, version 1.801 (kpathsea version 6.1.1dev)
(mpost.mp (/users/johnkitzmiller/context/tex/texmf/metapost/base/plain.mp
Preloading the plain mem file, version 1.004) ) (./mwe.mp [1] )
1 output file written: mwe.1
Transcript written on mwe.log.

and...

\starttext
\startMPcode
draw origin--(100,100);
\stopMPcode
\stoptext

works with command context %

But using mptopdf on the first snippet complains:

MPtoPDF 1.4.1 : running 'mpost --mem=mpost  mwe.mp'
This is MetaPost, version 1.801 (kpathsea version 6.1.1dev)
(mpost.mp (/users/johnkitzmiller/context/tex/texmf/metapost/base/plain.mp
Preloading the plain mem file, version 1.004) ) (./mwe.mp [1] )
1 output file written: mwe.1
Transcript written on mwe.log.
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
 \write18 enabled.

kpathsea: Running mktexfmt mptopdf.fmt
/usr/texbin/mktexfmt: line 395: /users/johnkitzmiller/context/tex/texmf/texconfig/tcfmgr: is a directory
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `mptopdf.fmt'!

MPtoPDF 1.4.1 : error while processing tex file


(Note: I do not have TeX Live 2013 installed. The message from line 7 gave me some hints and I created the directory and put mptopdf.fmt from a pdftex --ini mptopdf command … no luck)

Turning $PATH off from ~/context/tex/texmf-osx-64/bin mptopdf % gives:

MPtoPDF 1.4.1 : running 'mpost --mem=mpost  mwe.mp'
This is MetaPost, version 1.504 (kpathsea version 6.1.0)
(mpost.mp (/usr/local/texlive/2012/texmf-dist/metapost/base/plain.mp
Preloading the plain mem file, version 1.004)) (./mwe.mp [1] )
1 output file written: mwe.1
Transcript written on mwe.log.
This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012)
 restricted \write18 enabled.
[MP to PDF] (./mwe.1) [1]
Output written on mwe.pdf (1 page, 1305 bytes).
Transcript written on mwe.log.

MPtoPDF 1.4.1 : mwe is converted to mwe-1.pdf

as I have been using. How to get mptopdf working from command line with just minimals?








 
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2013-04-17 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 20:51 John Kitzmiller [this message]
2013-04-17 21:00 ` Hans Hagen
2013-04-17 22:00   ` John Kitzmiller
2013-04-18  9:04 ` Mojca Miklavec
2013-04-18 13:47 John Kitzmiller

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=A4FA30C9-65C3-42A9-AB00-E26C333A9FB2@inradius.net \
    --to=kitz@inradius.net \
    --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).