Debian Codegraph @

texmf-dist/doc/fonts/amsfonts/README

raw
1 README for amsfonts 3.04 [2013/01/14]
2
3 Copyright 2001, 2009, 2013 American Mathematical Society.
4
5 This work may be distributed and/or modified under the
6 conditions of the LaTeX Project Public License, either version 1.3c
7 of this license or (at your option) any later version.
8 The latest version of this license is in
9 http://www.latex-project.org/lppl.txt
10 and version 1.3c or later is part of all distributions of LaTeX
11 version 2005/12/01 or later.
12
13 This work has the LPPL maintenance status `maintained'.
14
15 The Current Maintainer of this work is the American Mathematical
16 Society.
17
18 American Mathematical Society
19 Technical Support
20 Publications Technical Group
21 201 Charles Street
22 Providence, RI 02904
23 USA
24 tel: (401) 455-4080
25 (800) 321-4267 (USA and Canada only)
26 fax: (401) 331-3842
27 email: [email protected]
28
29 ========================================================================
30
31 If you have obtained a bundled AMSFonts collection (amsfonts.zip), this
32 will unpack into the standard TeX Directory Structure (TDS) tree.
33 First, determine the local TEXMF directory for your system, which we
34 will call texmf-local in this 00README file; this directory should be
35 identified in the documentation for the TeX distribution you're using.
36 Place the zip file into a convenient directory and unpack it using
37 the texmf-local directory as the "Extract to" target. Some examples:
38
39 WinZIP: Click on "Extract" and then in the "Extract to" box, enter
40 \sw\texmf-local (or whatever the local branch of TEXMF is
41 on your system)
42 unzip: unzip amsfonts.zip -d texmf-local
43
44 See the web page
45 http://tug.org/fonts/fontinstall.html
46 for some general information on identifying your local TEXMF tree and
47 installing fonts on various platforms. (This includes specific details
48 for MikTeX, MacTeX, and other systems based on TeX Live.)
49
50 If your installation is not arranged in a TDS tree, see also the section
51 below, "Installing AMSFonts 3.0 on your system", as well as the user
52 documentation for your TeX distribution.
53
54 ------------------------------------------------------------------------
55
56 What changes were made between AMSFonts 3.03 and AMSFonts 3.04?
57
58 Version 3.04 is a minor update to provide more fluid interoperability
59 with stix.sty. It should be fully compatible with version 3.03.
60
61 ------------------------------------------------------------------------
62
63 What changes were made between AMSFonts 3.02 and AMSFonts 3.03?
64
65 The Type 1 Euler fonts have been upgraded from version 003.002 to
66 003.003 with the following changes:
67
68 1) Some inconsistencies with the character widths in the corresponding
69 TFM files have been fixed.
70
71 2) Minor optimizations were carried out on some of the character
72 outlines.
73
74 The changes affect only the PFB, AFM, and PFM files. Thanks to Taco
75 Hoekwater and Stephen Moye.
76
77 What changes were made between AMSFonts 3.01 and AMSFonts 3.02?
78
79 The internal Unicode-compliant glyph names used for version 3.00 of
80 the Type 1 fonts resulted in a major incompatibility in reusing PDF
81 documents that had the previous version of the fonts embedded. All
82 glyph names have now been reverted to their previous values and some
83 minor inconsistencies in the encoding vectors have been fixed. This
84 affects all PFB and AFM files.
85
86 What changes were made between AMSFonts 3.00 and AMSFonts 3.01?
87
88 The encoding vectors of several of the Type 1 fonts were augmented
89 with some some duplicate entries in the high-bit range (128--255) for
90 compatibility with earlier releases of the fonts and with some older
91 PDF software that had trouble rendering characters with low character
92 codes (0-31). Also, a couple of typos in the latxfont.map file were
93 fixed.
94
95 What changes were made between AMSFonts 2.2d and AMSFonts 3.0?
96
97 The licenses were restated to clarify the copying and redistribution
98 conditions to make them more compatible with third-party collections
99 such as TeX Live. In particular, all Type 1 fonts and those .mf files
100 originally created at AMS are now released under the SIL Open Font
101 License (OFL), a copy of which is included with this distribution.
102
103 .pk files are no longer distributed or supported by the AMS. Where
104 Type 1 fonts are available, modern TeX distributions do not require
105 PK fonts. When PK fonts are required for some specialized purpose,
106 they can easily be generated on the fly.
107
108 In the Computer Modern fonts, some shape changes made by Donald Knuth
109 in 1992 were not included in the Type 1 fonts distributed in version 2.2
110 of the AMSFonts collection. These shape changes have now been made,
111 and all CM glyph shapes should now be identical between Knuth's Metafont
112 sources and the Type 1 fonts. Since Knuth's original changes did not
113 affect the metrics, no metrics were affected by this upgrade, and no
114 changes to the .tfm files were needed. However, owing to the system
115 under which the reference copies of the .tfm files are archived, the
116 original file dates have been lost; recent file dates do not imply
117 any content changes.
118
119 The Euler fonts, designed by Hermann Zapf, were originally released in
120 the 1990s. Zapf reshaped many of the glyphs, with implementation and
121 assistance from Hans Hagen, Taco Hoekwater, and Volker RW Schaa. The
122 updated version 3.0 was presented to Donald Knuth on his birthday,
123 January 10, 2008. These updates were carefully designed to work with
124 the metrics for version 2.2, so no changes to the .tfm files were
125 needed. Since the updates were made directly to the Type 1 files,
126 the (incompatible) .mf files have been removed from the distribution.
127
128 There have been no shape changes to the "extra symbols" or cyrillic.
129
130 Where possible, all glyphs have been given Unicode-compliant names
131 to make them work better with Unicode-aware viewers (e.g.,
132 cut-and-paste of Cyrillic characters should work better).
133
134 Some modifications were made in the LaTeX support files to adapt to
135 the new set of (fully scalable) font sizes. Now that Type 1 fonts
136 are available for all defined sizes, the "psamsfonts" option is no
137 longer needed. This has been implemented in such a way as to ensure
138 that existing LaTeX input calling for this option will still compile.
139 In particular, any support files containing "57" in the file name
140 have been either eliminated or converted to no-ops.
141
142 The location of some files has changed, so if you are installing the
143 new distribution on top of an existing one, be sure to delete the
144 old copies from the previous locations. Remove these directories
145 that are no longer used:
146
147 doc/ams/amsfonts [replaced by doc/fonts/amsfonts]
148 fonts/source/ams [replaced by fonts/source/public/amsfonts]
149 fonts/tfm/ams [replaced by fonts/tfm/public/amsfonts]
150 tex/latex/amsfonts/obsolete [obsolete; not superseded]
151
152 Also remove these files from the indicated areas:
153
154 fonts/source/public/misc/dummy*
155 [replaced by fonts/source/public/amsfonts/dummy]
156 fonts/tfm/public/misc/dummy*
157 [replaced by fonts/tfm/public/amsfonts/dummy]
158
159 The manual (amsfndoc) will be updated later this year. Some of the
160 information it contains is incomplete or obsolete. In particular,
161 Appendix A, Installation Procedures, should be ignored completely;
162 see below for installation procedures if your system is not based on
163 a TDS structure.
164
165 ------------------------------------------------------------------------
166
167 What changes were made between AMSFonts 2.2 and AMSFonts 2.2d?
168
169 No changes were made to the fonts themselves, either to the Metafont
170 sources, the .tfm or .pk files.
171
172 The primary purpose of this upgrade was to fix bugs in the LaTeX
173 support files and to update the User's Guide.
174
175 ------------------------------------------------------------------------
176
177 What changes were made between AMSFonts 2.1 and AMSFonts 2.2?
178
179 The primary change was the inclusion of LaTeX support macro files as
180 part of the AMSFonts distribution. The files in the "latex"
181 subdirectory are compatible with LaTeX2e, the LaTeX standard since
182 1995. Users of LaTeX 2.09 are strongly encouraged to upgrade to
183 LaTeX2e, as AMS no longer supports the use of AMSFonts with LaTeX 2.09.
184
185 The only significant change to the characters in the fonts was a bug
186 fix which corrected an anomaly in the Blackboard Bold N character from
187 the MSBM fonts. That character printed incorrectly at a few resolutions
188 (including 600dpi); it now prints correctly at all resolutions. The
189 metrics for AMSFonts 2.2 were unchanged from those for AMSFonts 2.1.
190
191 There was also a slight change to the file amssym.tex, and very
192 significant changes to the User's Guide.
193
194 ------------------------------------------------------------------------
195
196 INSTALLING AMSFonts 3.0 ON YOUR SYSTEM
197
198 These instructions assume that you were unable to unzip the bundle
199 directly into a TEXMF TDS tree.
200
201 1. Installing the fonts:
202
203 Unzip the bundle into a work area. This will produce a tree with the
204 following structure:
205
206 source
207 source/latex
208 source/latex/amsfonts
209 tex
210 tex/latex
211 tex/latex/amsfonts
212 tex/plain
213 tex/plain/amsfonts
214 fonts
215 fonts/source
216 fonts/source/public
217 fonts/source/public/amsfonts
218 fonts/source/public/amsfonts/cmextra
219 fonts/source/public/amsfonts/cyrillic
220 fonts/source/public/amsfonts/dummy
221 fonts/source/public/amsfonts/symbols
222 fonts/tfm
223 fonts/tfm/public
224 fonts/tfm/public/amsfonts
225 fonts/tfm/public/amsfonts/cmextra
226 fonts/tfm/public/amsfonts/cyrillic
227 fonts/tfm/public/amsfonts/dummy
228 fonts/tfm/public/amsfonts/euler
229 fonts/tfm/public/amsfonts/symbols
230 fonts/type1
231 fonts/type1/public
232 fonts/type1/public/amsfonts
233 fonts/type1/public/amsfonts/cm
234 fonts/type1/public/amsfonts/cmextra
235 fonts/type1/public/amsfonts/cyrillic
236 fonts/type1/public/amsfonts/euler
237 fonts/type1/public/amsfonts/latxfont
238 fonts/type1/public/amsfonts/symbols
239 fonts/afm
240 fonts/afm/public
241 fonts/afm/public/amsfonts
242 fonts/afm/public/amsfonts/cm
243 fonts/afm/public/amsfonts/cmextra
244 fonts/afm/public/amsfonts/cyrillic
245 fonts/afm/public/amsfonts/euler
246 fonts/afm/public/amsfonts/latxfont
247 fonts/afm/public/amsfonts/symbols
248 fonts/map
249 fonts/map/dvips
250 fonts/map/dvips/amsfonts
251 doc
252 doc/fonts
253 doc/fonts/amsfonts
254
255 Move the files in the branch fonts/type1/public/amsfonts/ to the
256 directory where your system expects to find .pfb (Type 1) files.
257
258 Move the files in the branch fonts/tfm/public/amsfonts/ to the
259 directory where your system expects to find .tfm files.
260
261 Update the map files for your device drivers using the .map files in
262 fonts/map/dvips/amsfonts/ ; consult the documentation for your TeX
263 distribution for advice.
264
265 Depending on what TeX system you use, it may also be necessary to update
266 a filename database; see the documentation for your TeX distribution.
267
268 2. Installing the (La)TeX support files:
269
270 There are two sets of files which provide macros necessary for using
271 AMSFonts 3.0 in TeX. One set is for Plain TeX or AMS-TeX, and one set
272 is for LaTeX. If you use Plain TeX or AMS-TeX, then the files in
273 tex/plain/amsfonts/ should be placed in the directory (or a directory
274 in the path) which your implementation of TeX searches for input files.
275 If you use LaTeX, then the files in tex/latex/amsfonts/ should be
276 placed in that directory. (If you use LaTeX 2.09, then we strongly
277 encourage you to upgrade to LaTeX2e; AMS does not provide support for
278 use of AMSFonts in LaTeX 2.09.) If you are likely to use both LaTeX
279 and Plain TeX or AMS-TeX, then install the files from both directories
280 where your TeX will find them for input.
281
282 Depending on what TeX system you use, it may also be necessary to update
283 a filename database; see the documentation for your TeX distribution.
284
285 3. The User's Guide and other documentation:
286
287 You can get a copy of the User's Guide via a link on the web page
288
289 http://www.ams.org/tex/amsfonts.html
290
291 The User's Guide still describes AMSFonts 2.2d; however, processing and
292 printing it from the files in this distribution is a good test of your
293 AMSFonts installation.
294
295 In order to TeX and print the User's Guide, you must first install the
296 fonts. The "source" subdirectory (source/latex/amsfonts/) contains
297 five input files with names beginning with "amsfndoc". When your font
298 installation is complete, process the file "amsfndoc.tex" with Plain
299 TeX (not AMS-TeX or LaTeX). It will input four other "amsfndoc" files:
300 .def, .cyr, .ins and .fnt. The output will be a complete guide to the
301 use of AMSFonts 2.2d. Instructions for the use of the fonts themselves
302 are still valid, though somewhat incomplete; however, the installation
303 instructions in Appendix A are obsolete and should be ignored. The
304 User's Guide is scheduled to be updated later this year.
305
306 The directory source/latex/amsfonts/ contains a file named
307 "amsfonts.faq" in which we will place frequently asked questions about
308 AMSFonts.
309
310 This directory also contains LaTeX .dtx files containing technical
311 commentary on the source code for the LaTeX support files in the
312 AMSFonts distribution. Although these .dtx files are included for
313 reference, most users can ignore them.
314
315 ------------------------------------------------------------------------
316
317 USE OF THE LATEX "amsfonts" PACKAGE
318
319 Version 3.0 of the LaTeX package amsfonts.sty is carefully constructed
320 to allow it to be used for processing pre-existing documents. This
321 means that documents that load amsfonts.sty through statements such
322 as the following should continue to work without change.
323
324 1. \documentclass{amsart}
325
326 2. \documentclass{article}
327 \usepackage{amsfonts}
328
329 3. \documentclass{article}
330 \usepackage{amsmath,amsthm}
331
332 4. \documentclass{article}
333 \usepackage{amssymb}
334
335 There is an exception, however, for the variants 2 and 3: If your
336 document was written a very long time ago AND if it uses any of the
337 symbols
338
339 \square \Box
340 \lozenge \Diamond
341 \vartriangleright \rhd
342 \vartriangleleft \lhd
343 \trianglerighteq \unrhd
344 \trianglelefteq \unlhd
345 \rightsquigarrow \leadsto
346 \Join
347
348 then you may find that those symbol commands now produce "Undefined
349 control sequence" errors. For the symbols in the first column, the
350 easiest way to fix this is to load the amssymb package, i.e. change
351 variants 2 and 3 to
352
353 2a. \documentclass{article}
354 \usepackage{amssymb}
355
356 3a. \documentclass{article}
357 \usepackage{amssymb,amsmath,amsthm}
358
359 For symbols in the second column (\Box, etc.), you have a choice of
360 either adding the latexsym package or defining them in terms of
361 equivalent symbols from the amssymb package.
362
363 If you are using an AMS document class (amsart, amsbook, amsproc), the
364 amsfonts are automatically included; however, you must load the amssymb
365 package to have access to the specific symbol names.