Installing fonts for WYSIWYG publishing on Linux is a relatively complex task. It typically involves three steps:
The good news is that most WYSIWYG applications use what is a reasonable solution to this problem. The solution involves constructing some kind of mechanism that maps screen fonts to printer fonts ( this is the main issue. There are also other issues, such as grouping bold, italic and roman variants into ``families'' of fonts ). Unfortunately, there is no standard way to do this. It seems that font management standards which address this issue would greatly simplify the installation of fonts into WYSIWYG publishing systems, because all applications could use a system-wide ( as opposed to application-specific ) configuration.
There are two ways to install fonts into Applixware. One method involves using FontTastic, which is Applixware's ``private'' font server. The other method involves editing Applixware's fontmap, to use a font already installed on the system. Installing into the font server is more convenient, but fonts installed in this manner may only be printed at 300 dpi.
Using FontTastic is the easy way to do it. To install new fonts like this, simply do the following:
This method is more involved, but produces better results. I recommend that this method is used for fonts that are really important, and that you use a lot. There are a few steps to this:
This is explained in the previous section
This is explained in in the previous section
This is the final step in making your fonts available to Applix, and also the most time consuming step. The file fontmap.dir is in under the axdata/fontmetrics of your applix installation. The purpose of this step is basically to tell applix which screen fonts go with which outline fonts. This is in general a very nontrivial problem, because the screen fonts are not always on the same computer that the application is installed.
We describe how to add fonts to fontmap.dir. In this example, we add the font Baskerville Italic.
Slant = 1if the font is italic, and
Weight = 1if the font is bold. If the font is bold and italic, we add both lines. In this example, we need only add the line
Slant = 1
ScreenName = "-paradise-baskerville-medium-i-normal--0-0-0-0-p-0-iso8859-1"The screen name is the name that the X-server uses for the font. We can list font names containing the string ``bask'' by typing
xlsfonts|grep -i bask
MetricsFile = /usr/share/fonts/misc/baskvli.afm Type1FontFileName = /usr/share/fonts/misc/baskvli.pfbIf you are adding a TrueType file, you can use
ttf2pt1to generate an
ttf2pt1 -A foo.ttf - > foo.afm( or get the ttfutils package and use
ttf2afm) Then you use something like this:
MetricsFile = /usr/share/fonts/misc/foo.afmDo not include a
Type1FontFileNamedirective -- let ghostscript take care of this.
That's it. Now after adding the whole family of fonts, you should have something like this:
FontRecord = Baskerville-Normal Family = Baskerville ScreenName = "-paradise-baskerville-medium-r-normal--0-0-0-0-p-0-iso8859-1" PostScriptPrintName = Baskerville-Normal MetricsFile = /usr/share/fonts/misc/baskvl.afm Type1FontFileName = /usr/share/fonts/misc/baskvl.pfb FontRecord = Baskerville-Normal-Italic Family = Baskerville Slant = 1 ScreenName = "-paradise-baskerville-medium-i-normal--0-0-0-0-p-0-iso8859-1" PostScriptPrintName = Baskerville-Normal-Italic MetricsFile = /usr/share/fonts/misc/baskvli.afm Type1FontFileName = /usr/share/fonts/misc/baskvli.pfb FontRecord = Baskerville-Bold Family = Baskerville Weight = 1 ScreenName = "-paradise-baskerville-bold-r-normal--0-0-0-0-p-0-iso8859-1" PostScriptPrintName = Baskerville-Bold MetricsFile = /usr/share/fonts/misc/baskvlb.afm Type1FontFileName = /usr/share/fonts/misc/baskvlb.pfb FontRecord = Baskerville-Bold-Italic Family = Baskerville Weight = 1 Slant = 1 ScreenName = "-paradise-baskerville-bold-i-normal--0-0-0-0-p-0-iso8859-1" PostScriptPrintName = Baskerville-Bold-Italic MetricsFile = /usr/share/fonts/misc/baskvlbi.afm Type1FontFileName = /usr/share/fonts/misc/baskvlbi.pfb
It is possible to do more with this configuration file. The file itself has a glossary which explains the format of the configuration file.
Here, we cover Star Office 5.0. The procedure with Star Office 5.1 is similar, but the utility is called
psetup. It's worth mentioning up front that John McLaughlin's page is an excellent source on this issue, and it inspired most of what follows.
Having tried both Star Office 5.0, and 5.1, I have found that Star Office 5.1 seems to give me less grief when adding new fonts. I was not succesful adding true type fonts to Star Office 5.0, but it proved somewhat easier with Star Office 5.1.
It's good to make a backup in case you inadvertantly hose your configuration. Modifying fonts will impact several files in the
xp3. You should definitely backup the file
xp3/psstd.fonts. I recommend going further and backing up the whole
xp3 directory. You can do this by cd-ing to your Star Office directory, then using
tar cvzf xp3.tgz xp3to create a backup. To restore a backup, delete the
xp3directory and unpack the archive
rm -rf xp3 tar xvzf xp3.tgz
Adding Type1 fonts to Star Office is relatively simple. If you want to use your TrueType fonts with Star Office 5.0, the best thing to do is convert them to Type1 fonts, and then follow the procedure outlined here. If you have Star Office 5.1, you might wish to use the proceedure for installing TrueType fonts instead ( though it is somewhat more difficult ). Firstly, do the usual thing -- make the font available to both X and ghostscript. Once this is done, the font can be installed into Star Office using the
psetup tool. The procedure is as follows:
Adding TrueType fonts to Star Office is nontrivial, but possible. After some hard work, and long hours stareing at John McLaughlin's page page, I finally got them working in Star Office 5.1. Note that this does not work with version 5.0. The following steps are appropriate it you are printing through ghostscript:
afmfiles for the fonts you wish to add. Use
ttf2pt1 -A foo.ttf - > foo.afmto create the
afmfiles. Alternatively, you can get the
ttf2afmThe advantage of this is you can handle several at a time, eg
pfbfiles corresponding to each
ttffile. You can create them with the command
touch foo.pfbActually, Star Office only uses these files for printing purposes. And by enterring the font in the PPD, thus duping Star Office into thinking the fonts are inside your printer ( when they're actually inside ghostscript's rendering system ), you get around needing to use these files. Star Office just seems to require that the
pfbfile exists to install the font.
spadminand install the font(s).
foobar.ttfand the corresponding
foobar.afm, you use the name ``foobar'' for the font in the PPD file. The entry should look something like this:
*Font cloistrk: Standard "(001.002)" Standard ROM
On the other hand, if you are not printing from ghostscript, you have different issues to deal with. In this case, tricking Star Office into thinking that your printer has the fonts is a bad idea, because your printer does not have the fonts in the ROM, so while
gv will display the postscript files nicely, your printer will not be able to print them. If you have a postscript printer, the main differences are as follows:
touch foo.pfbto create empty
pfbfiles, you need the
pfbfiles to be Type42 postscript fonts. A Type42 font is really a ``printer TrueType font''. You don't really notice Type42 fonts even when you use them, because most applications handle them transparently. To create Type42 fonts, you use ttfps to create the files.
ttfps foo.ttf foo.pfb
There are some gotchas. Sometimes, Star Office might not choose the screen font you like. It is sometimes worth checking
xp3/psstd.fonts and possibly editing it to make sure that Star Office is really using the font you had in mind for screen display. Also, Star Office doesn't handle configuration problems gracefully. If there's something wrong with your configuration, it's possible that the word processor will not even start. This is why you should back up your
If you wish to install TrueType fonts in Star Office, you may need to learn how Star Office handles things. When you run
psetup, the following happens:
pfboutline files in your
afmfile is copied into the directory
xp3/psstd.fontsfile. This file stores the names of all the screen fonts used by Star Office ( in particular, it maps the screen fonts to the outline filenames ).
This is why it's good to simply backup the whole
xp3 directory -- it is the only convenient way to restore Star Office to a clean configuration.
Nothing yet. Rod Smith's webpage is the definitive resource regarding installing fonts on Word Perfect.