summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html22
1 files changed, 22 insertions, 0 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html
new file mode 100644
index 00000000000..d35454526b5
--- /dev/null
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html
@@ -0,0 +1,22 @@
+<head>
+<title>UK TeX FAQ -- question label instmffont</title>
+</head><body>
+<h3>Installing a font provided as Metafont source</h3>
+<p>Metafont fonts are (by comparison with other sorts of font) rather
+pleasingly simple. Nowadays, they are mostly distributed just as the
+Metafont source, since modern TeX distributions are able to produce
+everything the user needs "on the fly"; however, if the distribution
+<em>does</em> include TFM files, do install them, too, since they
+save a little time and don't occupy much disc space. Always distrust
+distributions of PK font bitmap files: there's no way of
+learning from them what printer they were generated for, and naming
+schemes under different operating systems are another source of
+confusion.
+<p>"<a href="FAQ-wherefiles.html">Where to install files</a>"
+specifies where the files should go.
+<p>Further confusion is introduced by font families whose authors devise rules
+for automatic generation of Metafont sources for generating fonts at
+particular sizes; the installation has to know about the rules, as
+otherwise it cannot generate font files.
+<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont</a>
+</body>