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
86
87
88
89
90
91
92
93
94
|
This package, derived from Cardo, provides a Bembo-like font family in otf and pfb format plus LaTeX font support files. As Cardo is licensed under the SIL OFL, so are the font files in this package. All other support files are subject to the LaTeX Project Public License. See http://www.ctan.org/tex-archive/help/Catalogue/licenses.lppl.html for the details of that license. Note that Bembo is a name trademarked by Monotype, and Cardo is a reserved name under the OFL, hence the strange name for this package, drawn from the Berry id for the Bembo font family.
Current version: 1.02
Changes in version 1.02
Main change is to provide good versions of the pfb files, which were flawed in the previous version, causing segmentation faults in GhostScript and failing to work correctly in Adobe Reader. The new versions are generated from the otf versions using FontForge instead of cfftot1.
Changes in version 1.01
Revisions of some BoldItalic glyphs and substantial reworking of Italic Small Cap kerning tables.
Changes in version 1.00
Additions to sty file, bringing its capabilities in line with those of garamondx.
Changes in version 0.93:
Many additions and changes to glyphs, especially in bold and bold-italic, and those needed by textcomp.
Changes in version 0.92:
Corrected a number of glyph issues and corrected some faulty lookup tables that in some cases redirected 6 to 5.
Changes in version 0.91:
Reworked some problematic glyphs and corrected a number of issues in kerning tables.
There are without doubt many errors remaining in the font files, especially the kerning tables, and I would appreciate error reports. The BoldItalic style is the most likely to contain errors, having been subjected to the least testing.
The otf fonts contain all the kerning and other tables. Should you wish to modify these yourself, the LaTeX support files may be re-created using the command
/usr/texbin/autoinst --noupdmap --noswash --notitling --noornaments --target=./texmf --encoding=OT1,TS1,T1,LY1 --vendor=public --typeface=fbb *.otf
after cding to the folder containing just the modified otf fonts and a subfolder named texmf. You should replace the newly generated fbb.sty with the one from the distribution in order to preserve its functionality. The names of the encoding files should also be modified appropriately from those assigned by autoinst. I used the following bash shell script, which assumed you are in the directory holding the otf files and a texmf subfolder:
#!/bin/bash
pushd texmf/fonts/map/dvips/fbb
sed -i '' 's/<\[a_/<\[fbb_/g' fbb.map
popd
pushd texmf/fonts/enc/dvips/fbb
for f in *.enc; do mv ${f} fbb${f:1}; done
popd
Installation:
Mac OS X: To install, open a Terminal window and cd to inside the downloaded TDS folder.
Method A (recommended): type
sudo cp -Rfp * /usr/local/texlive/texmf-local
then
sudo mktexlsr
then
sudo -H updmap-sys --enable Map=fbb.map
Method B: If you insist on making your font installations in your home folder, potentially making your personal installation become out of sync with updates to TeXLive, use instead
(i) if you checked Update for All Users in TeXLive utility
cp -Rfp * ~/Library/texmf
then
updmap --enable Map=fbb.map
(ii) otherwise
cp -Rfp * ~/Library/texmf
then
sudo updmap-sys --enable Map=fbb.map
Linux: Very similar to Mac OS X.
MikTeX: Copy the fbb.tds.zip to the root of the folder you use for personal additions to the TeX trees, open a command window, chdir to that folder, and type
unzip fbb.tds.zip
initexmf --update-fndb
initexmf --edit-config-file updmap
The latter command should open updmap.cfg in your default editor, commonly Notepad. Add the line
Map fbb.map
to updmap.cfg, save and close. Then, in the command window, type
initexmf --mkmaps
You can ignore error messages that may occur here. This should result in a properly enabled fbb.
Please send comments and bug reports or suggestions for improvement to
msharpe at ucsd dot edu
|
