summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html
index 3883862df00..b901dfb8c0d 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html
@@ -10,21 +10,21 @@ able to generate its own output, and in this mode of operation has no
need of <code>\</code><code>special</code> commands (which allow the user to pass
information to the driver being used to generate output).
<p>Why does this happen? LaTeX users, nowadays, hardly ever use
-<code>\</code><code>special</code> commands on their own - they employ packages to do the
+<code>\</code><code>special</code> commands on their own &mdash; they employ packages to do the
job for them. Some packages will generate <code>\</code><code>special</code> commands
-however they are invoked: <i>pstricks</i> is an example (it's very
-raison d'&ecirc;tre is to emit PostScript code in a sequence of <code>\</code><code>special</code>
+however they are invoked: <i>pstricks</i> is an example (it&rsquo;s very
+raison d&rsquo;&ecirc;tre is to emit PostScript code in a sequence of <code>\</code><code>special</code>
commands). <i>Pstricks</i> may be dealt with by other means (the
<i>pdftricks</i> package offers a usable technique).
<p>More amenable to correction, but more confusing, are packages (such as
<i>color</i>, <i>graphics</i> and <i>hyperref</i>) that
-specify a "driver". These packages have plug-in modules that
+specify a &ldquo;driver&rdquo;. These packages have plug-in modules that
determine what <code>\</code><code>special</code> (or other commands) are needed to generate
any given effect: the <code>pdftex</code> driver for such packages knows not to
generate <code>\</code><code>special</code> commands. In most circumstances, you can let
the system itself choose which driver you need; in this case
everything will act properly when you switch to using PDFLaTeX. If
-you've been using <i>dvips</i> (and specifying the <code>dvips</code> driver)
+you&rsquo;ve been using <i>dvips</i> (and specifying the <code>dvips</code> driver)
or <i>dvipdfm</i> (for which you have to specify the driver), and
decide to try PDFLaTeX, you <em>must</em> remove the <code>dvips</code> or
<code>dvipdfm</code> driver specification from the package options, and let the