diff options
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html')
| -rw-r--r-- | Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html | 39 |
1 files changed, 22 insertions, 17 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html index d489cc3e879..6dbcff59b82 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html @@ -1,55 +1,60 @@ <head> <title>UK TeX FAQ -- question label graphicspath</title> </head><body> -<h3>Importing graphics from "somewhere else"</h3> +<h3>Importing graphics from “somewhere else”</h3> <p>By default, graphics commands like <code>\</code><code>includegraphics</code> look -"wherever TeX files are found" for the graphic file they're being +“wherever TeX files are found” for the graphic file they’re being asked to use. This can reduce your flexibility if you choose to hold your graphics files in a common directory, away from your (La)TeX sources. -<p>The simplest solution is to patch TeX's path, by changing the +<p>The simplest solution is to patch TeX’s path, by changing the default path. On most systems, the default path is taken from the -environment variable <code>TEXINPUTS</code>, if it's present; you can adapt that +environment variable <code>TEXINPUTS</code>, if it’s present; you can adapt that to take in the path it already has, by setting the variable to +<blockquote> <pre> - TEXINPUTS=.:<graphics path(s)>: +TEXINPUTS=.:<graphics path(s)>: </pre> -on a Unix system; on a Windows system the separator will be "<code>;</code>" -rather than "<code>:</code>". The "<code>.</code>" is there to ensure that the current -directory is searched first; the trailing "<code>:</code>" says "patch in the -value of <code>TEXINPUTS</code> from your configuration file, here". +</blockquote><p> +on a Unix system; on a Windows system the separator will be “<code>;</code>” +rather than “<code>:</code>”. The “<code>.</code>” is there to ensure +that the current directory is searched first; the trailing +“<code>:</code>” says “patch in the value of <code>TEXINPUTS</code> from +your configuration file, here”. <p>This method has the merit of efficiency ((La)TeX does <em>all</em> of -the searches, which is quick), but it's always clumsy and may prove +the searches, which is quick), but it’s always clumsy and may prove inconvenient to use in Windows setups (at least). <p>The alternative is to use the <i>graphics</i> package command <code>\</code><code>graphicspath</code>; this command is of course also available to users of the <i>graphicx</i> and the <i>epsfig</i> packages. The -syntax of <code>\</code><code>graphicspath</code>'s one argument is slightly odd: it's a +syntax of <code>\</code><code>graphicspath</code>’s one argument is slightly odd: it’s a sequence of paths (typically relative paths), each of which is enclosed in braces. A slightly odd sample, given in the <i>graphics</i> bundle documentation, is: +<blockquote> <pre> - \graphicspath{{eps/}{tiff/}} +\graphicspath{{eps/}{tiff/}} </pre> +</blockquote><p> however, if the security checks on your (La)TeX system allow, the path may be anything you choose (rather than strictly relative, like -those above). +those above); note that the trailing “<code>/</code>” <em>is</em> required. <p>Be aware that <code>\</code><code>graphicspath</code> does not affect the operations of -graphics macros other than those from the graphics bundle - in +graphics macros other than those from the graphics bundle — in particular, those of the outdated <i>epsf</i> and <i>psfig</i> packages are immune. <p>The disadvantage of the <code>\</code><code>graphicspath</code> method is inefficiency. The package will call (La)TeX once for each entry in the list, which is itself slows things. More seriously, TeX remembers the file name, -thus effectively losing memory, every time it's +thus effectively losing memory, every time it’s asked to look up a file, so a document that uses a huge number of graphical inputs could be embarrassed by lack of memory. <p>If your document is split into a variety of directories, and each directory has its associated graphics, the <i>import</i> package may well be the thing for you; see the discussion -in the question " +in the question “ <a href="FAQ-docotherdir.html">bits of document in other directories</a> -". +”. <dl> <dt><tt><i>graphics bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) <dt><tt><i>import.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a> |