diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html | 64 |
1 files changed, 64 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html new file mode 100644 index 00000000000..e7a74af855f --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-unkgrfextn.html @@ -0,0 +1,64 @@ +<head> +<title>UK TeX FAQ -- question label unkgrfextn</title> +</head><body> +<h3>“Unknown graphics extension”</h3> +<p/>The LaTeX graphics package deals with several different types of +DVI (or other) output drivers; each one of them has a potential +to deal with a different selection of graphics formats. The package +therefore has to be told what graphics file types its output driver +knows about; this is usually done in the <<i>driver</i>><code>.def</code> file +corresponding to the output driver you’re using. +<p/>The error message arises, then, if you have a graphics file whose +extension doesn’t correspond with one your driver knows about. Most +often, this is because you’re being optimistic: asking +<i>dvips</i> to deal with a <code>.png</code> file, or PDFTeX to deal with +a <code>.eps</code> file: the solution in this case is to transform the graphics +file to a format your driver knows about. +<p/>If you happen to <em>know</em> that your device driver deals with the +format of your file, you are probably falling foul of a limitation of +the file name parsing code that the graphics package uses. Suppose +you want to include a graphics file <i>home.bedroom.eps</i> using the +<i>dvips</i> driver; the package will conclude that your file’s +extension is <code>.bedroom.eps</code>, and will complain. +<p/>The <i>grffile</i> package deals with the last problem (and +others — see the package documentation); using the package, you may +write: +<blockquote> +<pre> +\usepackage{graphicx} +\usepackage{grffile} +... +\includegraphics{home.bedroom.eps} +</pre> +</blockquote><p> +or you may even write +<blockquote> +<pre> +\includegraphics{home.bedroom} +</pre> +</blockquote><p> +and <i>graphicx</i> will find a <code>.eps</code> or <code>.pdf</code> +(or whatever) version, according to what version of (La)TeX you’re +running. +<p/>If for some reason you can’t use <i>grffile</i>, you have three +unsatisfactory alternatives: +<ul> +<li> Rename the file — for example <i>home.bedroom.eps</i>-> + <i>home-bedroom.eps</i> +<li> Mask the first dot in the file name: +<pre> +\newcommand*{\DOT}{.} +\includegraphics{home\DOT bedroom.eps} +</pre> +<li> Tell the graphics package what the file is, by means of options + to the <code>\</code><code>includegraphics</code> command: + +<pre> +\includegraphics[type=eps,ext=.eps,read=.eps]{home.bedroom} +</pre> +</ul> +<dl> +<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) collection +</dl> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn</a> +</body> |