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.html34
1 files changed, 17 insertions, 17 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 0f5d1397ff8..0b536135ab0 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
@@ -1,33 +1,33 @@
<head>
<title>UK TeX FAQ -- question label graphicspath</title>
</head><body>
-<h3>Importing graphics from &ldquo;somewhere else&rdquo;</h3>
+<h3>Importing graphics from &#8220;somewhere else&#8221;</h3>
<p/>By default, graphics commands like <code>\</code><code>includegraphics</code> look
-&ldquo;wherever TeX files are found&rdquo; for the graphic file they&rsquo;re being
+&#8220;wherever TeX files are found&#8221; for the graphic file they&#8217;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&rsquo;s path, by changing the
+<p/>The simplest solution is to patch TeX&#8217;s path, by changing the
default path. On most systems, the default path is taken from the
-environment variable <code>TEXINPUTS</code>, if it&rsquo;s present; you can adapt that
+environment variable <code>TEXINPUTS</code>, if it&#8217;s present; you can adapt that
to take in the path it already has, by setting the variable to
<blockquote>
<pre>
-TEXINPUTS=.:&lt;graphics path(s)&gt;:
+TEXINPUTS=.:&#60;graphics path(s)&#62;:
</pre>
</blockquote><p>
-on a Unix system; on a Windows system the separator will be &ldquo;<code>;</code>&rdquo;
-rather than &ldquo;<code>:</code>&rdquo;. The &ldquo;<code>.</code>&rdquo; is there to ensure
+on a Unix system; on a Windows system the separator will be &#8220;<code>;</code>&#8221;
+rather than &#8220;<code>:</code>&#8221;. The &#8220;<code>.</code>&#8221; is there to ensure
that the current directory is searched first; the trailing
-&ldquo;<code>:</code>&rdquo; says &ldquo;patch in the value of <code>TEXINPUTS</code> from
-your configuration file, here&rdquo;.
+&#8220;<code>:</code>&#8221; says &#8220;patch in the value of <code>TEXINPUTS</code> from
+your configuration file, here&#8221;.
<p/>This method has the merit of efficiency ((La)TeX does <em>all</em> of
-the searches, which is quick), but it&rsquo;s always clumsy and may prove
+the searches, which is quick), but it&#8217;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>&rsquo;s one argument is slightly odd: it&rsquo;s a
+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:
@@ -38,26 +38,26 @@ enclosed in braces. A slightly odd sample, given in the
</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 &ldquo;<code>/</code>&rdquo; <em>is</em> required.
+those above); note that the trailing &#8220;<code>/</code>&#8221; <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 &mdash; in
+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&rsquo;s
+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/>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 &ldquo;
+in the question &#8220;
<a href="FAQ-docotherdir.html">bits of document in other directories</a>
-&rdquo;.
+&#8221;.
<dl>
<dt><tt><i>graphics bundle</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse the directory</a>)
-<dt><tt><i>import.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a>
+<dt><tt><i>import.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/import.zip">macros/latex/contrib/import</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/import/">browse the directory</a>)
</dl>
<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath</a>
</body>