ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Olivier <billet@eurecom.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mplib errors
Date: Tue, 30 Sep 2008 17:45:28 +0200	[thread overview]
Message-ID: <20080930154528.GA15978@blackowl.org> (raw)
In-Reply-To: <48E1F856.8030501@elvenkind.com>

Taco,

> > So, I guess it would make sense to test the compiler directly:
> > what is the most basic way to trigger mplib from a plain tex file
> > directly run through LuaTeX (i.e. the equivalent of the startMPgraphic
> > if any? (And this might provide some more information on what's going on.)
 
> Just look at mlib-run.lua from the context distribution, it should
> be clear enough.

Thanks for the pointer.  I played a bit with pdfluatex directly which
seems to work. (I'm not to the point of producing figures, because I
would have to rebuild all the functions that are located in mlib-run.lua
and the luatexref-t.tex does not give straightforward example of how the
mplib module should be used, it only describes the functions API. Btw:
could you add in the doc a simple example of how to set up an mplib instance
(loading the format file) and typesetting a minimal graphic, and then
use it from within plain TeX for instance; this is transparent to
conTeXt users since there are files like mlib-run.lua but not easy for
plain TeX users :P  And I'm not advocating the use of plain TeX,
I'm a converted conTeXt user since 2003, but this will help user
understand (a bit) how things work behind the scene.) 

Thanks for your (and all the posters') interest,
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
___________________________________________________________________________________


  reply	other threads:[~2008-09-30 15:45 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 [this message]
2008-10-01  9:14               ` Taco Hoekwater
2008-10-01 13:57                 ` Olivier
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=20080930154528.GA15978@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).