summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2006-12-14 00:56:47 +0000
committerKarl Berry <karl@freefriends.org>2006-12-14 00:56:47 +0000
commit13328a265ebe4ef58c26ab99e0c071edb0ca0195 (patch)
tree604fbea81411a5bda1ff25d9cd6ee5dd75acd761 /Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html
parentda29691fd87e0073830e9d11a1dccd9725f01cc6 (diff)
3.16c+html
git-svn-id: svn://tug.org/texlive/trunk@2723 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html42
1 files changed, 26 insertions, 16 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html
index 4bb0b64aabc..5d5cf7533ed 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html
@@ -7,42 +7,44 @@ it may be separated into a modest set of stages.
<ul>
<li> Acquire the font. A very small set of Type 1 fonts is installed
in most PostScript printers you will encounter. For those few (whose use
- is covered by the basic PSNFSS package), you don't need the
+ is covered by the basic PSNFSS package), you don&rsquo;t need the
Type 1 font itself, to be able to print using the font.
<p> For all the myriad other Type 1 fonts, to be able to print using
the font you need the Type 1 file itself. Some of these are
- available for free (they've either been donated to the public
+ available for free (they&rsquo;ve either been donated to the public
domain, or were developed as part of a free software project), but
the vast majority are commercial products, requiring you to spend
real money.
-<li> Acquire the fonts' AFM files. AFM files contain
+<li> Acquire the fonts&rsquo; AFM files. AFM files contain
information from the font foundry, about the sizes of the characters
in the font, and how they fit together. One measure of the quality
of a font-supplier is that they provide the AFM files by
default: if the files are not available, you are unlikely to be able
to use the font with (La)TeX.
<li> Rename the AFM files and the Type 1 files to match the
- "
- <a href="FAQ-fontname.html">Berry font naming scheme</a>".
+ <a href="FAQ-fontname.html">Berry font naming scheme</a>.
<li> Generate TeX metric files from the AFM files. The
commonest tool for this task is <i>fontinst</i>; the package
documentation helps, but other guides are available (see below).
The simplest possible script to pass to <i>fontinst</i> is:
<blockquote>
- <code>\latinfamily{xyz}</code><br>
- <code>\bye</code>
- </blockquote>
+<pre>
+\latinfamily{xyz}{}
+\bye
+</pre>
+ </blockquote><p>
where <code>xyz</code> is the Berry name of the font family. This
simple script is adequate for most purposes: its output covers the
- font family in both <code>T1</code> and <code>OT1</code> font encodings. Nevertheless,
+ font family in both T1 and OT1 font encodings. Nevertheless,
with fancier fonts, more elaborate things are possible with
<i>fontinst</i>: see the documentation for details.
<p> <i>Fontinst</i> also generates map files, and LaTeX font
definition (<code>.fd</code>) files.
<li> Install the files, in your <code>texmf</code> tree. All the
strictures about installing non-standard things apply here: be sure
- to put the files in the local tree. Reasonable destinations for the
- various files are:
+ to put the files in the local tree. The list gives reasonable
+ destinations for the various files related to a font whose Berry
+ name is &lt;<i>bname</i>&gt;:
<pre>
.pfb,
@@ -50,6 +52,14 @@ it may be separated into a modest set of stages.
.tfm .../fonts/tfm/&lt;foundry&gt;/&lt;bname&gt;
.vf .../fonts/vf/&lt;foundry&gt;/&lt;bname&gt;
.fd .../tex/latex/fontinst/&lt;foundry&gt;/&lt;bname&gt;
+</pre>
+ The irregular things being <code>.map</code> files: in teTeX 3.0 and
+ later, these should be placed according to the revised TDS as
+<pre>
+.map .../fonts/map/dvips/&lt;foundry&gt;
+</pre>
+and in other (earlier) systems as
+<pre>
.map .../dvips/fontinst/&lt;foundry&gt;
</pre>
<li> Regenerate the file indexes (as described in
@@ -64,18 +74,18 @@ it may be separated into a modest set of stages.
<pre>
updmap --enable Map &lt;xyz&gt;.map
</pre>
- <li> On a MiKTeX system earlier than version 2.2, the "Refresh
- filename database" operation, which you performed after installing
- files, also updates the system's "PostScript resources database".
+ <li> On a MiKTeX system earlier than version 2.2, the &ldquo;Refresh
+ filename database&rdquo; operation, which you performed after installing
+ files, also updates the system&rsquo;s &ldquo;PostScript resources database&rdquo;.
<li> On a MiKTeX system, version 2.2 or later, update
<i>updmap.cfg</i> which is described in MiKTeX
- <a href="http://www.miktex.org/manual/psfonts.html">online documentation</a>.
+ <a href="http://docs.miktex.org/manual/psfonts.html#chgupdmapcfg">online documentation</a>.
Then execute the command <code>initexmf --mkmaps</code>, and the job
is done.
</ul>
</ul>
The whole process is very well (and thoroughly) described in Philipp
-Lehman's guide to font installation, which may be found on CTAN.
+Lehman&rsquo;s guide to font installation, which may be found on CTAN.
<dl>
<dt><tt><i>fontinst.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>)
<dt><tt><i>Type 1 installation guide</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf">info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf</a>