From: Olivier <billet@eurecom.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mplib errors
Date: Wed, 1 Oct 2008 15:57:12 +0200 [thread overview]
Message-ID: <20081001135712.GA17826@blackowl.org> (raw)
In-Reply-To: <48E33F7A.80708@elvenkind.com>
Hi Taco,
> Running mplib is easy enough to document, but that is only a part of
> the work: you also have to convert the image to pdf literals, and
> that is more work than I would like to put in the manual.
OK. It could be nice then to simply state this?
> Anyway, attached is a bunch of definitions I stripped out of context
> that will allow you to run mplib in plain tex provided that you also
> have context installed (you need mlib-pdf.lua for the PDF conversion)
Thanks a lot for these. With these hints I am now able to compile
metapost figs from conTeXt through "texexec --luatex" normaly.
To this end, I had to perform two tweaks:
* the files mlib-run.lua, mlib-ctx.lua, and mlib-pdf.lua were *NEVER*
loaded so I added to my conTeXt source file:
\directlua0 { dofile
("/usr/share/texmf/tex/context/base/mlib-ctx.lua") }
\directlua0 { dofile
("/usr/share/texmf/tex/context/base/mlib-run.lua") }
\directlua0 { dofile
("/usr/share/texmf/tex/context/base/mlib-pdf.lua") }
* the format was generated correctly but loaded incorrectly:
I had to add the following line:
ini_version = false,
in the metapost.load function in the mlib-run.lua file.
Now everything is OK. The second thing (an misfortunate typo) is easy
to fix. However, the fact that mlib-*.lua are never loaded is more worrying:
any idea where this error comes from?
Hope this will help Hans as well.
Cheers,
Olivier
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-10-01 13:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 15:55 Olivier
2008-09-29 18:03 ` luigi scarso
2008-09-29 19:44 ` Olivier
2008-09-29 21:45 ` luigi scarso
2008-09-30 8:54 ` Olivier
2008-09-30 9:14 ` luigi scarso
2008-09-29 20:00 ` Hans van der Meer
2008-09-29 20:10 ` Taco Hoekwater
2008-09-29 20:46 ` Olivier
2008-09-29 21:27 ` Taco Hoekwater
2008-09-30 9:40 ` Olivier
2008-09-30 9:58 ` Taco Hoekwater
2008-09-30 15:45 ` Olivier
2008-10-01 9:14 ` Taco Hoekwater
2008-10-01 13:57 ` Olivier [this message]
2008-10-01 14:08 ` Taco Hoekwater
2008-10-01 14:27 ` Olivier
2008-09-29 21:57 ` Hans van der Meer
2008-09-30 7:35 ` Taco Hoekwater
2008-09-30 9:27 ` Ulrike Fischer
2008-09-30 9:37 ` Olivier
2008-09-30 10:10 ` Ulrike Fischer
2008-09-30 10:57 ` Hans Hagen
2008-09-30 12:11 ` 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=20081001135712.GA17826@blackowl.org \
--to=billet@eurecom.fr \
--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).