summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
diff options
context:
space:
mode:
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.html48
1 files changed, 40 insertions, 8 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 fc542341fc2..e4abccf5f8a 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
@@ -10,13 +10,45 @@ all know and love (or hate)
There’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
-them, all you can reasonably do is to edit the document. The
-appearance of DVI files that request them is sufficiently rare that
-no-one has undertaken the mammoth task of creating a translation of
-them by means of virtual fonts; however, most drivers let you have a
-configuration file in which you can specify font substitutions. If you
-specify that every <i>am</i> font should be replaced by its corresponding
-<i>cm</i> font, the output should be almost correct.
-<p/>
+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
+rare that no-one has undertaken the mammoth task of creating a
+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;
+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
+<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
+(throughout the text representation of the file) in the middle of that
+round trip.
+<p/>The DTL text is pretty straightforward, for this purpose:
+fontnames are in single quotes at the end of lines, so:
+<blockquote>
+ <code>dv2dt -o</code> &lt;<i>doc.txt</i>&gt; &lt;<i>doc.dvi</i>&gt;<br>
+ (<em>edit the <code>.txt</em> file</code>)<br>
+ <code>dt2dv -o</code> &lt;<i>edited.dvi</i>&gt; &lt;<i>edited.txt</i>&gt;
+</blockquote><p>
+(you have to compile the C programs for this).
+<p/><i>Dviasm</i> is a <i>Python</i> script; its output has font
+names in a section near the start of the document, and then dotted
+about through the body, so:
+<blockquote>
+ <code>python dviasm.py -o</code> &lt;<i>doc.txt</i>&gt; &lt;<i>doc.dvi</i>&gt;<br>
+ (<em>edit the <code>.txt</em> file</code>)<br>
+ <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
+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>)
+<dt><tt><i>dtl</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/dviware/dtl.zip">dviware/dtl</a> (or <a href="http://www.tex.ac.uk/tex-archive/dviware/dtl/">browse the directory</a>)
+</dl>
<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts</a>
</body>