summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html31
1 files changed, 19 insertions, 12 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html
index 7b2273759b1..ed6f705ccf3 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html
@@ -29,26 +29,33 @@ inconvenient to use in Windows setups (at least).
of the <i>graphicx</i> and the <i>epsfig</i> packages. The
syntax of <code>\</code><code>graphicspath</code>&#8217;s one argument is slightly odd: it&#8217;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:
+enclosed in braces. A slightly odd example (slightly modified from one
+given in the <i>graphics</i> bundle documentation) is:
<blockquote>
<pre>
-\graphicspath{{eps/}{tiff/}}
+\graphicspath{{eps/}{png/}}
</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); note that the trailing &#8220;<code>/</code>&#8221; <em>is</em> required.
+which will search for graphics files in subdirectories <i>eps</i> and
+<i>png</i> of the directory in which LaTeX is running. (Note that
+the trailing &#8220;<code>/</code>&#8221; <em>is</em> required.)
+<p/>(Note that some (La)TeX systems will only allow you to use files in
+the current directory and its sub-directories, for security reasons.
+However, <code>\</code><code>graphicspath</code> imposes no such restriction: as far as
+<em>it</em> is concerned, you can access files anywhere.)
<p/>Be aware that <code>\</code><code>graphicspath</code> does not affect the operations of
graphics macros other than those from the graphics bundle &#8212; 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&#8217;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/>The slight disadvantage of the <code>\</code><code>graphicspath</code> method is
+inefficiency. The package will call (La)TeX once for each entry in
+the list to look for a file, which of course slows things. Further,
+(La)TeX remembers the name of any file it&#8217;s asked to look up, thus
+effectively losing memory, so that in the limit a document that uses a
+huge number of graphical inputs could be embarrassed by lack of
+memory. (Such &#8220;memory starvation&#8221; is pretty unlikely with any
+ordinary document in a reasonably modern (La)TeX system, but it
+should be borne in mind.)
<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