summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2010-04-07 22:47:28 +0000
committerKarl Berry <karl@freefriends.org>2010-04-07 22:47:28 +0000
commit3f1971c9b7717818766692c9aa497e20e7472f2c (patch)
tree678de0190b6643b1b21fd9441fa1387bce180726 /Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
parentc7c3b090320a234149dbe23315e2a15a2773ac79 (diff)
FAQ-en 3.19d (7apr10)
git-svn-id: svn://tug.org/texlive/trunk@17742 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
index e4abccf5f8a..9aa1632b47f 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
@@ -3,13 +3,13 @@
</head><body>
<h3>Where are the <code>am</code> fonts?</h3>
<p/>One <em>still</em> occasionally comes across a request for the <i>am</i>
-series of fonts. The initials stood for &lsquo;Almost [Computer] Modern&rsquo;,
+series of fonts. The initials stood for &#8216;Almost [Computer] Modern&#8217;,
and they were the predecessors of the Computer Modern fonts that we
all know and love (or hate)
.
-There&rsquo;s not a lot one can do with these
+There&#8217;s not a lot one can do with these
fonts; they are (as their name implies) almost (but not quite) the
-same as the <i>cm</i> series; if you&rsquo;re faced with a document that requests
+same as the <i>cm</i> series; if you&#8217;re faced with a document that requests
them, the only reasonable approach is to edit the document to replace
<i>am*</i> font names with <i>cm*</i>.
<p/>The appearance of DVI files that request them is sufficiently
@@ -18,10 +18,10 @@ translation of them by means of virtual fonts.
<p/>You therefore have to fool the system into using <i>cm*</i> fonts
where the original author specified <i>am*</i>.
<p/>One option is the font substitutions that many
-DVI drivers provide via their configuration file &mdash;
+DVI drivers provide via their configuration file &#8212;
specify that every <i>am</i> font should be replaced by its
corresponding <i>cm</i> font.
-<p/>Alternatively, one may try DVI editing &mdash; packages
+<p/>Alternatively, one may try DVI editing &#8212; packages
<i>dtl</i> (DVI Text Language) and <i>dviasm</i>
(DVI assembler) can both provide round trips from DVI to
text and back to DVI. One therefore edits font names
@@ -44,7 +44,7 @@ about through the body, so:
<code>python dviasm.py -o</code> &lt;<i>edited.dvi</i>&gt; &lt;<i>edited.txt</i>&gt;
</blockquote><p>
Both routes seem acceptable ways forward; it is a matter of taste
-which any particular user may choose (it&rsquo;s not likely that it will be
+which any particular user may choose (it&#8217;s not likely that it will be
necessary very often...).
<dl>
<dt><tt><i>dviasm.py</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/dviasm.zip">dviware/dviasm</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/dviasm/">browse the directory</a>)