From: Guy Worthington <guyw@multiline.com.au>
Cc: "NTG-ConTeXt mailing list" <ntg-context@ntg.nl>
Subject: Re: mfpic and context pdf support files
Date: 12 Jun 2002 09:18:12 +0800 [thread overview]
Message-ID: <ufzztqoq3.fsf@multiline.com.au> (raw)
In-Reply-To: <5.1.0.14.1.20020611183118.032025f8@server-1>
[I posted a bug report due to a conflict between plain tex and
supp-pdf.tex ]
Hans Hagen wrote:
> Looks like you use plain tex (with \newdimen defined as \long
> macro). I have this fixed in latest beta
Thanks Hans, that fixed the \outer problem with \newdimen.
I noticed in the comments for the patch a sigh. I'm too ignorant to
know whether you being constrained by maintaining compatibility with
plain TeX has degraded supp-pdf.tex.
I also posted a report to comp.text.tex, where Dan Luecking (author of
\mfpic), patched the \outer macro \newdimen by replacing it with
\csname newdimen\endcsname
on the two offending lines. If it's helpful, Dan Luecking's patch
does work inside the \beginETEX ... \endETEX definition.
prev parent reply other threads:[~2002-06-12 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 4:11 Guy Worthington
2002-06-11 16:32 ` Hans Hagen
2002-06-12 1:18 ` Guy Worthington [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=ufzztqoq3.fsf@multiline.com.au \
--to=guyw@multiline.com.au \
--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).