From: Hans Hagen <pragma@wxs.nl>
Subject: Re: How is it possible to include DraTex code in Context?
Date: Fri, 25 Nov 2005 18:39:12 +0100 [thread overview]
Message-ID: <43874C40.2000004@wxs.nl> (raw)
In-Reply-To: <4387296E.8080306@uqam.ca>
Fabrice Larribe wrote
>>
> Thanks for your help. I have put the two files in context/base, and
> use \usemodule. In the log,
> the system inform that the two modules are loaded. But I have the same
> error, "No room for a new \dimen".
> So this is not working. Unless you have others ideas, I guess I have
> to do my figures in plain tex to obtain
> pdf, and then use the pdf in Context. Of course, a better solution is
> to learn metafun....!!
> Thanks for your help.
can you make a small test file that shows the problem?
(when we have it working i'll ask Eitan to fix this, i.e. adapt dratex
to etex usage)
Hans
next prev parent reply other threads:[~2005-11-25 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DA71F8D231E5F40956368B045D89FB4035821C0@calepin.gst.uqam.ca>
2005-11-25 15:10 ` Fabrice Larribe
2005-11-25 17:39 ` Hans Hagen [this message]
2005-11-25 4:55 How is it possible to include DraTex code in Context ? Fabrice Larribe
2005-11-25 14:12 ` 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=43874C40.2000004@wxs.nl \
--to=pragma@wxs.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).