summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html97
1 files changed, 0 insertions, 97 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html
deleted file mode 100644
index 4df95c65f9b..00000000000
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-impgraph.html
+++ /dev/null
@@ -1,97 +0,0 @@
-<head>
-<title>UK TeX FAQ -- question label impgraph</title>
-</head><body>
-<h3>Importing graphics into (La)TeX documents</h3>
-<p/>Knuth, when designing the current version of TeX back in the early
-1980s, could discern no &#8220;standard&#8221; way of expressing graphics in
-documents. He reasoned that this state could not persist for ever,
-but that it would be foolish for him to define TeX primitives that
-allowed the import of graphical image definitions. He therefore
-deferred the specification of the use of graphics to the writers of
-DVI drivers; TeX documents would control the drivers by
-means of
-<a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>.
-<p/>There is therefore a straightforward way for anyone to import graphics
-into their document: read the specification of the <code>\</code><code>special</code>
-commands your driver uses, and &#8216;just&#8217; code them. This is the
-hair-shirt approach: it definitely works, but it&#8217;s not for everyone.
-<p/>Over the years, therefore, &#8220;graphics inclusion&#8221; packages have sprung
-up; most were designed for inclusion of
-
-<a href="FAQ-eps.html">Encapsulated PostScript graphics</a> &#8212;
-which has become the <em>lingua franca</em> of graphics inclusion over
-the last decade or so.
-<p/>Notable examples are the <i>epsf</i> package (distributed with
-<i>dvips</i>) and the <i>psfig</i> package. (Both of these
-packages were designed to work well with both Plain TeX and
-LaTeX 2.09; they are both still available.) All such packages were
-tied to a particular DVI driver (<i>dvips</i>, in
-the above two cases), but their code could be configured for others.
-<p/>The obvious next step was to make the code configurable dynamically.
-The LaTeX standard <i>graphics</i> package and its derivatives
-made this step: it is strongly preferred for all current work.
-<p/>Users of Plain TeX have two options allowing them to use
-<i>graphicx</i>: the <i>miniltx</i> &#8220;LaTeX emulator&#8221; and
-the <i>graphicx.tex</i> front-end allow you to load
-<i>graphicx</i>, and <a href="FAQ-eplain.html">\Eplain</a> allows you to load
-it (using the full LaTeX syntax) direct.
-<p/>The <i>graphics</i> package takes a variety of &#8220;driver
-options&#8221; &#8212; package options that select code to generate the
-commands appropriate to the DVI driver in use. In most cases,
-your (La)TeX distribution will provide a <i>graphics.cfg</i> file
-that will select the correct driver for what you&#8217;re doing (for
-example, a distribution that provides both LaTeX and PDFLaTeX
-will usually provide a configuration file that determines whether
-PDFLaTeX is running, and selects the definitions for it if so).
-<p/>The <i>graphics</i> package provides a toolkit of commands (insert
-graphics, scale a box, rotate a box), which may be composed to provide
-most facilities you need; the basic command, <code>\</code><code>includegraphics</code>,
-takes one optional argument, which specifies the bounding box of the
-graphics to be included.
-<p/>The <i>graphicx</i> package uses the facilities of of
-<i>graphics</i> behind a rather more sophisticated command syntax
-to provide a very powerful version of the <code>\</code><code>includegraphics</code>
-command. <i>graphicx</i>&#8217;s version can combine scaling and
-rotation, viewporting and clipping, and many other things. While this
-is all a convenience (at some cost of syntax), it is also capable of
-producing noticeably more efficient PostScript, and some of its
-combinations are simply not possible with the <i>graphics</i>
-package version.
-<p/>The <i>epsfig</i> package provides the same facilities as
-<i>graphicx</i>, but via a <code>\</code><code>psfig</code> command (also known as
-<code>\</code><code>epsfig</code>), capable of emulating
-the behaviour (if not the bugs) the old <i>psfig</i> package.
-<i>Epsfig</i> also supplies homely support for former users of the
-<i>epsf</i> package. However, there&#8217;s a support issue: if you
-declare you&#8217;re using <i>epsfig</i>, any potential mailing list or
-usenet helper has to clear out of the equation the possibility that
-you&#8217;re using &#8220;old&#8221; <i>epsfig</i>, so that support is slower
-coming than it would otherwise be.
-<p/>There is no rational reason to stick with the old packages, which have
-never been entirely satisfactory in the LaTeX context. (One
-irrational reason to leave them behind is that their replacement&#8217;s
-name tends not to imply that it&#8217;s exclusively related to PostScript
-graphics. The reasoning also excludes <i>epsfig</i>, of course.)
-<p/>A wide variety of detailed techniques and tricks have been developed
-over the years, and Keith Reckdahl&#8217;s <i>epslatex</i> outlines them
-in compendious detail: this highly recommendable document is available
-from CTAN. An invaluable review of the practicalities of
-exchanging graphics between sites,
-
-&#8220;<a href="http://silas.psfc.mit.edu/elec_fig/elec_figures.pdf">Graphics for Inclusion in Electronic Documents</a>&#8221;
-
-has been written by Ian Hutchinson; the document isn&#8217;t on CTAN,
-but may also be
-
-<a href="http://silas.psfc.mit.edu/elec_fig/">browsed on the Web</a>.
-<dl>
-<dt><tt><i>epsf.tex</i></tt><dd><a href="http://mirror.ctan.org/macros/generic/epsf/epsf.tex">macros/generic/epsf/epsf.tex</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/epsf.html">catalogue entry</a>
-<dt><tt><i>epsfig.sty</i></tt><dd>Part of the <a href="http://mirror.ctan.org/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://mirror.ctan.org/macros/latex/required/graphics/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/graphics.html">catalogue entry</a> bundle
-<dt><tt><i>epslatex.pdf</i></tt><dd><a href="http://mirror.ctan.org/info/epslatex.zip">info/epslatex</a> (or <a href="http://mirror.ctan.org/info/epslatex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/epslatex.html">catalogue entry</a>
-<dt><tt><i>graphics.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://mirror.ctan.org/macros/latex/required/graphics/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/graphics.html">catalogue entry</a>
-<dt><tt><i>graphicx.sty</i></tt><dd>Part of the <a href="http://mirror.ctan.org/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (or <a href="http://mirror.ctan.org/macros/latex/required/graphics/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/graphics.html">catalogue entry</a> bundle
-<dt><tt><i>miniltx.tex</i></tt><dd><a href="http://mirror.ctan.org/macros/plain/graphics.zip">macros/plain/graphics</a> (or <a href="http://mirror.ctan.org/macros/plain/graphics/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/graphics-pln.html">catalogue entry</a>
-<dt><tt><i>psfig.sty</i></tt><dd><a href="http://mirror.ctan.org/graphics/psfig.zip">graphics/psfig</a> (or <a href="http://mirror.ctan.org/graphics/psfig/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/psfig.html">catalogue entry</a>
-</dl>
-<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph</a>
-</body>