From: Sherlock Holmes <sherlock@rna.nl>
Subject: How do I handle this metapost file?
Date: Mon, 28 May 2001 22:41:48 +0200 [thread overview]
Message-ID: <20010528204214.D51A3AC50@spike.rna.nl> (raw)
I found an example file for metapost named figs.mp that contains
(everything between the dashed lines):
=========================================
input boxes
%% Use LaTeX, not TeX, in btex ... etex,
%% and use PostScript fonts.
%verbatimtex
%\documentclass{article}
%\usepackage{times}
%\usepackage{mathptm}
%\begin{document}
%etex
%% Literal text uses Times-Roman
%defaultfont := "ptmr";
%% Generate EPS
%prologues := 1;
beginfig(1);
pair shadowshift; shadowshift=(1,-1)*bp;
def drawshadowed(text t) =
forsuffixes $=t:
fill bpath$ shifted shadowshift;
unfill bpath$;
drawboxed($);
endfor
enddef;
boxit.a(btex \s8A\s+2 \(lh a etex);
circleit.b(btex $e sup {i omega t}$ etex rotated 20);
b.w - a.e = (10,0)*bp;
drawshadowed(a,b);
draw a.e..b.w;
draw bbox currentpicture dashed evenly;
endfig;
%verbatimtex
%\end{document}
%etex
end
=========================================
mpost figs.mp does not work:
[localhost:~/tmp/figs] sherlock% mpost figs.mp
This is MetaPost, Version 0.641 (Web2C 7.3.1)
(figs.mp
(/usr/local/teTeX/share/texmf/metapost/base/boxes.mp)/usr/local/teTeX/bin/
powerpc-apple-darwin1.3.3/makempx: Command failed: tex mpxerr.tex; see
mpxerr.log
>> figs.mp
>> figs.mpx
! Unable to make mpx file.
l.27 boxit.a(btex
\s8A\s+2 \(lh a etex);
Transcript written on figs.log.
mpxerr.log contains:
This is TeX, Version 3.14159 (Web2C 7.3.1) (format=tex 2001.5.28) 28
MAY 2001 22:38
**mpx3183.tex
(mpx3183.tex
! Undefined control sequence.
<argument> \hbox {\hbox {\s
8A\s +2 \(lh a}\vrule width1sp}
\next #1->\setbox \z@ \hbox {#1
}\finsm@sh
l.2 \s8A\s+2 \(lh a}\vrule width1sp}}
}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
<argument> \hbox {\hbox {\s 8A\s
+2 \(lh a}\vrule width1sp}
\next #1->\setbox \z@ \hbox {#1
}\finsm@sh
l.2 \s8A\s+2 \(lh a}\vrule width1sp}}
}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
! Undefined control sequence.
<argument> \hbox {\hbox {\s 8A\s +2 \(
lh a}\vrule width1sp}
\next #1->\setbox \z@ \hbox {#1
}\finsm@sh
l.2 \s8A\s+2 \(lh a}\vrule width1sp}}
}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
[1] [1] )
Output written on mpx3183.dvi (2 pages, 336 bytes).
Should this file work? And if so, how do I process this if I want to
create pdf from it? Preferably by running pdf(la)tex at some point, not
using dvips and ps2pdf.
Thanks,
SH
next reply other threads:[~2001-05-28 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 20:41 Sherlock Holmes [this message]
2001-05-28 21:19 ` Taco Hoekwater
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=20010528204214.D51A3AC50@spike.rna.nl \
--to=sherlock@rna.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).