diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html | 65 |
1 files changed, 65 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html new file mode 100644 index 00000000000..8689aa5a640 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-repeatgrf.html @@ -0,0 +1,65 @@ +<head> +<title>UK TeX FAQ -- question label repeatgrf</title> +</head><body> +<h3>Repeated graphics in a document</h3> +<p/>A logo or “watermark” image, or any other image that is repeated in +your document, has the potential to make the processed version of the +document unmanageably large. The problem is, that the default +mechanisms of graphics usage add the image at every point it’s to be +used, and when processed, the image appears in the output file at each +such point. +<p/>Huge PostScript files are embarrassing; explaining <em>why</em> such a file +is huge, is more embarrassing still. +<p/>The <a href="FAQ-tutbitslatex.html"><i>epslatex</i> graphics tutorial</a> +describes a technique for avoiding the problem: basically, one +converts the image that’s to be repeated into a PostScript subroutine, and +load that as a <i>dvips</i> prologue file. In place of the image, +you load a file (with the same bounding box as the image) containing +no more than an invocation of the subroutine defined in the prologue. +<p/>The <i>epslatex</i> technique is tricky, but does the job. Trickier +still is the neat scheme of converting the figure to a one-character +Adobe Type 3 outline font. While this technique is for the “real +experts” only (the author of this answer has never even tried it), it has +potential for the same sort of space saving as the <i>epslatex</i> +technique, with greater flexibility in actual use. +<p/>More practical is Hendri Adriaens’ <i>graphicx-psmin</i>; you load +this <em>in place</em> of <i>graphicx</i>, so rather than: +<blockquote> +<pre> +\usepackage[<options>]{graphicx} +</pre> +</blockquote><p> +you will write: +<blockquote> +<pre> +\usepackage[<options>]{graphicx-psmin} +</pre> +</blockquote><p> +and at the start of your document, you write: +<blockquote> +<pre> +\loadgraphics[<bb>]{<list of graphics>} +</pre> +</blockquote><p> +and each of the graphics in the list is converted to an “object” for +use within the resulting PostScript output. (This is, in essence, an +automated version of the <i>epslatex</i> technique described above.) +<p/>Having loaded the package as above, whenever you use +<code>\</code><code>includegraphics</code>, the command checks if the file you’ve asked for +is one of the graphics in <code>\</code><code>loadgraphics</code>’ list. If so, the +operation is converted into a call to the “object” rather than a new +copy of the file; the resulting PostScript can of course be <em>much</em> smaller. +<p/>Note that the package requires a recent <i>dvips</i>, version +5.95b (this version isn’t — yet — widely distributed). +<p/>If your PostScript is destined for conversion to PDF, either by a +<i>ghostscript</i>-based mechanism such as <i>ps2pdf</i> or by +(for example) <i>Acrobat</i> <i>Distiller</i>, the issue isn’t +so pressing, since the distillation mechanism will amalgamate graphics +objects whether or not the PostScript has them amalgamated. PDFTeX does +the same job with graphics, automatically converting multiple uses +into references to graphics objects. +<dl> +<dt><tt><i>graphicx-psmin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.zip">macros/latex/contrib/graphicx-psmin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/graphicx-psmin/">browse</a>) +</dl> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf</a> +</body> |