From: Tobias Burnus <burnus@gmx.de>
Cc: conTeXt <ntg-context@ntg.nl>
Subject: Re: (newbie) Figure not found when outputting PDF
Date: Thu, 04 Jan 2001 15:49:04 +0100 [thread overview]
Message-ID: <3A548D60.C9C573E8@gmx.de> (raw)
In-Reply-To: <20010104151835.A2354@wouter.verheijen.nl>
Hallo Wouter,
> The file test.eps is in the same directory. I am using Linux.
> The first line of my document is: % output=pdf
> The figure included normally when I output a DVI file!!
The problem is that the portable document format (PDF) doesn't support
all Postscript (PS) constructs and a embedded postscript (EPS) file can
still -- at least theoretically -- use all postscript structures (well
not all, but all than cannot be converted without a RIP).
Since pdfTeX is not a complete Postscript RIP it cannot read the EPS and
convert it into PDF constructs. (VTeX which is free for Linux can.)
The solution is simple: You have to convert the EPS file into a PDF
file. During this convertion some information must be preserved
(bounding box). The best methode is:
RUN THIS:
texutil --figures --epstopdf filename
this calls Ghostscript to convert the EPS into PDF. Now you can run
texexec --pdf again to produce your PDF -- now with the graphics
included.
A tip: The newer the Ghostscript the better the result. You should use
version 6.0 or higher (6.50 is the current non-beta version) if your EPS
contains fonts. The reason is that older Ghostscripts are unable to
embed the fonts (Type 1 etc.) into the PDF file and convert them into
bitmaps (XObjects in <=5.0, Type 3 in 5.50).
With warm regards,
Tobias
--
This above all: To thine own self be true / And it must follow as
the night the day / Thou canst not then be false to any man.
prev parent reply other threads:[~2001-01-04 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 14:18 Wouter Verheijen
2001-01-04 14:49 ` Tobias Burnus [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=3A548D60.C9C573E8@gmx.de \
--to=burnus@gmx.de \
--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).