summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html
blob: 4bb0b64aabc4a0961cce3d82d0df61e86ecc5e39 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
<head>
<title>UK TeX FAQ -- question label instt1font</title>
</head><body>
<h3>Installing a Type 1 font</h3>
<p>The process of installing a Type 1 font set is rather convoluted, but
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
  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
  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
  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>".
<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>
  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,
  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:

<pre>
.pfb,
.pfa  .../fonts/type1/&lt;foundry&gt;/&lt;bname&gt;
.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;
.map  .../dvips/fontinst/&lt;foundry&gt;
</pre>
<li> Regenerate the file indexes (as described in
  <a href="FAQ-instpackages.html">package installation</a>).
<li> Update the <i>dvips</i> and other maps:
  <ul>
  <li> On a teTeX system earlier than version 2.0, edit the file
    <i>$TEXMF/dvips/config/updmap</i> and insert an absolute path for
    the <i>lm.map</i> just after the line that starts
    <code>extra_modules="</code> (and before the closing quotes).
  <li> On a teTeX version 2.0 (or later), execute the command
<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, 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>.
    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.
<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>
</dl>
<p>
<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font</a>
</body>