From: Hans van der Meer <hansm@science.uva.nl>
Subject: Re: followup metapost textext?
Date: Thu, 22 Dec 2005 18:11:21 +0100 [thread overview]
Message-ID: <3348E759-04FA-42C1-A361-E255D137AA79@science.uva.nl> (raw)
In-Reply-To: <43AA5A94.7050609@elvenkind.com>
I am surprised, but somehow the problem seems to be gone.
In my cont-sys.tex I had
\runMPgraphicstrue
%\runMPTEXgraphicstrue
Trying everything seemingly connected to metapost I tried diverse
combinations with these macros either commented-out or not-commented-
out.
At one moment texexec started functioning.
I was thinking both these macros were for efficiency only, or is that
a wrong thought? Because the comment in cont-sys.tex after these
lines says "% This saves some runtime,...".
But the \runMPTEXgraphicstrue seems crucial.
Would you please answer the next questions too:
(1) Although my outer font is Lucida, these are used in textext
(normal) but not used in textext($math$) where lm- en cm-math fonts
are used; these mixed fonts make the pictures ugly.
(2) I would like to have standalone pictures, as produced by "texexec
--mptex" but then I do not know how to set the fonts. Is there a
simple way to export the pictures from a ConTeXt run with embedded MP-
graphics? Or keep intermediate pdf's?
yours sincerely,
dr. H. van der Meer
On Dec 22, 2005, at 8:49, Taco Hoekwater wrote:
> Hans van der Meer wrote:
>> Followup to my previous post (see below)
>> I executed the code on the "live tex site" and, mirabile dictu,
>> there it works.
>> The difference I can see is a much older pdfetex (Version
>> 3.141592-1.21a-2.2 (Web2C 7.5.4)) on the live site, whereas I have
>> a newer one (Version 3.141592-1.30.4-2.2 (Web2C 7.5.5)).
>> Could that be the problem or must I dig deeper?
>
> It is not likely that this is the problem, unless you have
> 'stray' pdfetex executables floating around (with different
> version numbers) in other folders.
>
> It is more likely there is some interference with your pre-existing
> teTeX 3, but without the actual output and log files I do not know
> what to suggest as next step.
>
> Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-12-22 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 18:01 Hans van der Meer
2005-12-22 7:49 ` Taco Hoekwater
2005-12-22 17:11 ` Hans van der Meer [this message]
2005-12-22 22:05 ` Hans van der Meer
2005-12-22 22:22 ` Hans Hagen
2005-12-22 22:49 ` Hans van der Meer
2005-12-22 23:05 ` Taco Hoekwater
2005-12-22 23:26 ` 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=3348E759-04FA-42C1-A361-E255D137AA79@science.uva.nl \
--to=hansm@science.uva.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).