summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html20
1 files changed, 10 insertions, 10 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html
index 11fda9ca8b7..7e44cafe153 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html
@@ -1,37 +1,37 @@
<head>
<title>UK TeX FAQ -- question label eps</title>
</head><body>
-<h3>What is "Encapsulated PostScript"</h3>
+<h3>What is &ldquo;Encapsulated PostScript&rdquo; (&ldquo;EPS&rdquo;)</h3>
<p>PostScript has over the years become a <em>lingua franca</em> of
powerful printers; since PostScript is also a powerful graphical
programming language, it is commonly used as an output medium for
drawing (and other) packages.
<p>However, since PostScript <em>is</em> such a powerful language, some
rules need to be imposed, so that the output drawing may be included
-in a document as a figure without "leaking" (and thereby destroying
+in a document as a figure without &ldquo;leaking&rdquo; (and thereby destroying
the surrounding document, or failing to draw at all).
<p>Appendix H of the PostScript Language Reference Manual (second
and subsequent editions), specifies a set of rules for PostScript to
be used as figures in this way. The important features are:
<ul>
-<li> certain "structured comments" are required; important ones are
+<li> certain &ldquo;structured comments&rdquo; are required; important ones are
the identification of the file type, and information about the
- "bounding box" of the figure (i.e., the minimum rectangle
+ &ldquo;bounding box&rdquo; of the figure (i.e., the minimum rectangle
enclosing it);
-<li> some commands are forbidden - for example, a <code>showpage</code>
+<li> some commands are forbidden &mdash; for example, a <code>showpage</code>
command will cause the image to disappear, in most TeX-output
environments; and
-<li> "preview information" is permitted, for the benefit of things
- such as word processors that don't have the ability to draw
- PostScript in their own right - this preview information may be in
+<li> &ldquo;preview information&rdquo; is permitted, for the benefit of things
+ such as word processors that don&rsquo;t have the ability to draw
+ PostScript in their own right &mdash; this preview information may be in
any one of a number of system-specific formats, and any viewing
program may choose to ignore it.
</ul>
A PostScript figure that conforms to these rules is said to be in
-"Encapsulated PostScript" format. Most (La)TeX packages for
+&ldquo;Encapsulated PostScript&rdquo; (EPS) format. Most (La)TeX packages for
including PostScript are structured to use Encapsulated PostScript;
which of course leads to much hilarity as exasperated (La)TeX users
struggle to cope with the output of drawing software whose authors
-don't know the rules.
+don&rsquo;t know the rules.
<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps</a>
</body>