From: Ricardo Sanchez Carmenes <carmenes@bioquimica.uniovi.es>
Subject: supp-mps.tex minor bugs found and their fixes
Date: Sat, 10 Nov 2001 19:30:25 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0111101929170.9924-100000@bioinf.medicina.uniovi.es> (raw)
Dear Hans:
I have found some bugs in supp-mps.tex that are shown when using
this module with plain (i.e., without loading the whole context
package).
The supp-mps.tex file included in your latest beta/cont-tmf.zip
contains a minor bug that shows up when trying to use metapost
from tex->dvips->ps2pdf. The following diff fixes this bug:
diff -u beta/supp-mps.tex fix/supp-mps.tex
--- beta/supp-mps.tex Thu Aug 30 18:06:00 2001
+++ fix/supp-mps.tex Sat Nov 10 13:12:08 2001
@@ -545,9 +545,9 @@
\def\nouseMPbox#1%
{\setxvalue{#1}%
{\noexpand\forgetall
\noexpand\loadMPgraphic{\MPgraphicfile.\the\currentMPgraphic}{}%
- \deallocateMPslot\currentMPgraphic
+ \noexpand\deallocateMPslot\currentMPgraphic
\noexpand\placeMPgraphic}}
\ifCONTEXT \else \let\douseMPbox=\nouseMPbox \fi
\ifCONTEXT \else \let\doifobjectssupportedelse=\relax \fi
Additionally, either the beta and the current official releases
of supp-mps.tex try to check the value of \pdfoutput, even from
classic-tex. The following, placed early in the file, may solve
the problem without harming:
% supp-mps.tex checks \pdfoutput, even if undefined!
\ifx\pdftexversion\undefined\def\pdfoutput{0}\fi
And, finally, \startreusableMPgraphic uses the \ifundefined macro,
which is itself undefined! The following addition could solve the
problem:
% \startreusableMPgraphic needs this (yet) undefined macro:
\ifx\ifundefined\undefined
\def\ifundefined#1{\expandafter\ifx\csname#1\endcsname\relax}
\fi
Regards,
Ricardo.
next reply other threads:[~2001-11-10 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 18:30 Ricardo Sanchez Carmenes [this message]
[not found] <Pine.LNX.4.33.0111101929170.9924-100000@bioinf.medicina.un iovi.es>
2001-11-12 9:58 ` Hans Hagen
2001-11-15 9:47 Ricardo Sanchez Carmenes
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=Pine.LNX.4.33.0111101929170.9924-100000@bioinf.medicina.uniovi.es \
--to=carmenes@bioquimica.uniovi.es \
/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).