From: "Patrick Gundlach" <pg@levana.de>
Subject: Re: metafun installation problem
Date: 04 May 2002 20:23:14 +0200 [thread overview]
Message-ID: <87u1pnlqlp.fsf@gundla.ch> (raw)
In-Reply-To: <3CD41FE4.E75F57F8@lamel.bo.cnr.it>
Eros Albertazzi <eros@lamel.bo.cnr.it> writes:
Hello Eros,
> I am new to context and tried to set it up and, hopefully, use it. I
> have tetex...
It looks as if you try to use the context from the tetex installation.
This is not a good idea... see below:
> --> texexec --make metafun
> TeXExec 1.9 - ConTeXt / PRAGMA ADE 1997-2000
> fmtutil: no info for format `cont-metafun'.
the texexec is way too old. The best thing is to download a new
context distribution. See http://www.pragma-ade.com/ and the context
download is at http://www.pragma-ade.com/context/cont-tmf.zip. I do
not think that it makes any sense to stick with the old tools.
You could of course generate a metafun format with
inimpost metafun
if you use tetex with linux (which I guess). And put this metafun.mem
in a path that will be searched by kpathsea (try 'kpsepath mem').
Patrick
--
I'll fade into the darkness
prev parent reply other threads:[~2002-05-04 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 17:52 Eros Albertazzi
2002-05-04 18:23 ` Patrick Gundlach [this message]
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=87u1pnlqlp.fsf@gundla.ch \
--to=pg@levana.de \
/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).