From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: followup metapost textext?
Date: Thu, 22 Dec 2005 08:49:40 +0100 [thread overview]
Message-ID: <43AA5A94.7050609@elvenkind.com> (raw)
In-Reply-To: <ABD006A5-E0DC-4E27-8992-F0BDFE2DD994@science.uva.nl>
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
next prev parent reply other threads:[~2005-12-22 7:49 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 [this message]
2005-12-22 17:11 ` Hans van der Meer
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=43AA5A94.7050609@elvenkind.com \
--to=taco@elvenkind.com \
--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).