From: Matthew Baker <Matthew.Baker@gmd.de>
Subject: Re: texexec --pdf not finding figures when texexec does.
Date: Sun, 3 Oct 1999 12:17:54 +0200 [thread overview]
Message-ID: <Pine.SGI.4.04.9910031217000.72215-100000@urizen> (raw)
In-Reply-To: <19991002230452.A2648@vasili.rlf.org>
On Sat, 2 Oct 1999, Thomas Porter wrote:
> Hello,
>
> I downloaded the samples.zip from the Pragma site to play with.
>
> Running pdftex 14.c,
> ConTeXt ver: 1999.9.13 fmt: 1999.9.29 int: english mes: english
>
> When I `texexec figs` producing dvi output, all works just fine, but when I
> `texexec --pdf figs` I get:
>
> "figures : figure cd can not be found" in the log
>
> for the cd.eps in the directory where I have figs.tex.
>
> Relevent line in figs.tex:
>
> \externalfigure[cd.eps][width=1cm]
Hi Thomas,
Pdftex is unable to read EPS files, thus your problem. Try converting it
to PDF with the command
texutil --figures --epstopdf cd.eps
and change your \externalfigure line to
\externalfigure[cd][width=1cm]
If you ommit the filename extension, the most appropriate file will
usually be selected. I'm not sure if texexec can do this automatically.
I always use texutil myself for this.
Hans: This reminds me, the output for the above includes the lines
eps file : cd.eps
pdf file : cd.eps
Should the latter be "cd.pdf"?
> This may be a FAQ, but I figure this must have to do with pdftex processing in
> some way. Am I missing a PATH setting in a config file, perhaps? All
docume$
> tex and graphic files are in the directory where I ran texexec.
There is no FAQ yet, but there will be a mail archive soon...
Cheers,
Matthew
--
Dr. Matthew Baker matthew.baker@gmd.de
GMD - FIT.MMK http://fit.gmd.de/hci/pages/matthew.baker.html
next prev parent reply other threads:[~1999-10-03 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 3:04 Thomas Porter
1999-10-03 10:17 ` Matthew Baker [this message]
1999-10-03 23:32 ` 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=Pine.SGI.4.04.9910031217000.72215-100000@urizen \
--to=matthew.baker@gmd.de \
/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).