home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 15
/
CD_ASCQ_15_070894.iso
/
vrac_os2
/
fntf11.zip
/
FONTFOLD.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1994-06-10
|
61KB
|
1,687 lines
ΓòÉΓòÉΓòÉ 1. FontFolder Overview ΓòÉΓòÉΓòÉ
FontFolder provides an easy, efficient way to manage Adobe Type 1 fonts (also
known as ATM fonts) in OS/2. Once a font is registered with the FontFolder
Master Library, the font can be loaded and unloaded in OS/2 from the FontFolder
main window with simple point and click operations. With FontFolder you only
need to keep loaded those fonts that you are currently using. This saves time
and resources since OS/2 only needs to load a small number of fonts on bootup
and keep a small number of fonts in memory at any one time. Applications that
load all the installed fonts when starting will also start faster.
FontFolder provides added convenience by allowing you to groups fonts in a
named collection called a FontPack. A FontPack can be loaded and unloaded as a
single item, and all the fonts in the FontPack will be loaded or unloaded for
you. By creating FontPacks that contain all the fonts required for specific
tasks, you can easily keep just those fonts loaded that are required for the
work at hand.
By removing from the user the task of specifying where font files are to be
placed when fonts are loaded in OS/2, FontFolder provides great flexibility in
organizing your fonts into meaningful directory structures. In addition to
allowing fonts to be used from any directory on a local hard drive, FontFolder
supports fonts residing on network servers and helps manage adding fonts to
your system from diskettes or CDROMs.
See the following for additional information.
Topics:
o Overview of ATM Fonts
o Overview of OS/2 Fonts
o Installing FontFolder
o Using FontFolder
o Removing FontFolder
o Creating and Maintaining the Master Library
o Installing Fonts in OS/2
o Removing fonts from OS/2
o Using and Maintaining FontPacks
o Using Fonts on Network Drives
o FontFolder Settings Notebook
o FontFolder Menus
o FontFolder Dialogs
o Selecting items in listboxes
o Error Recovery
ΓòÉΓòÉΓòÉ 2. Overview of ATM Fonts ΓòÉΓòÉΓòÉ
ATM font is the popular name for an Adobe Type 1 font, originated by Adobe
Systems Incorporated. These fonts are scalable, meaning the system can
accurately generate font characters in a wide range of sizes from one font
description. This is in contrast to bit-mapped fonts, where there must be a
complete, separate font description for each size. ATM fonts can be used for
both display and printing and are supported on numerous operating systems in
addition to OS/2. As a result thousands of fonts are available from a wide
variety of sources. There are also programs available that allow you to
generate your own ATM font design.
An ATM font comes from the supplier as a collection of files. There is always
a file with a name of the form filename.PFB which contains the detailed
information needed to construct the font characters. There will be one or more
additional files for each font as well. Fonts shipped by Adobe contain a
filename.AFM file and a filename.INF file in addtion to the filename.PFB file.
For use in OS/2, the PFB file and the AFM file are required. Microsoft Windows
(and hence WinOS2) requires the PFB file and a file called filename.PFM. The
ATM Control Panel used to install ATM fonts in Windows can use the AFM file and
the INF file to construct a PFM file.
Some font vendors aiming solely at the Windows market have unfortunately taken
to shipping ATM fonts with only the PFB and PFM files. Such fonts are not
immediately usable in OS/2. The first recourse is to contact the vendor to
attempt to obtain the corresponding AFM file. Vendors such as Adobe are
usually quite willing to supply these for free, in fact Adobe has provided a
large number of AFM files for their type library in the ADOBE and DTPFORUM
forum libraries on Compuserve. There are also font editing programs that will
produce an AFM file from the PFB and PFM file and some utilities that attempt
to convert a PFM file to an AFM file.
ΓòÉΓòÉΓòÉ 3. Overview of OS/2 Fonts ΓòÉΓòÉΓòÉ
OS/2 uses both bit-mapped fonts and ATM fonts for displaying characters.
FontFolder does not deal with the OS/2 bit-mapped fonts. OS/2 ships with a
basic set of ATM fonts whose files can be found in the \PSFONTS directory on
the OS/2 boot drive.
An ATM font for OS/2 must have both a filename.AFM and a filename.PFB file. In
order for OS/2 to recognize these files they most both reside in the same
directory. However, different fonts can reside in different directories. OS/2
keeps a record in the OS2.INI file of the path to each installed font.
Note: One consequence of this is that the user must not move the files
for an installed font to a different location without first uninstalling
the font from OS/2. Once the files are moved, the font can be reinstalled
in OS/2.
OS/2 requires that the font files for an installed font reside on a hard
drive. One reason for this is that OS/2 reads these files on bootup to
generate the required information on installed fonts. As a result, when a
font is installed in OS/2 from a removable drive such as a floppy drive or
CDROM drive the font files must be copied to a directory on a hard drive. The
OS/2 Font Pallete defaults to \PSFONTS as the location for these files, but
the user can change this to any directory. FontFolder copies these files to a
user-designated hard drive location when registering a font with the Master
Library from a removable drive. After this, FontFolder never moves the files
again when installing and uninstalling the font in OS/2. This gives the user
the freedom to organize fonts in directory structures that are meaningful from
the user's perspective. For example, all fonts obtained from a specific
source might be grouped in their own directory, or fonts might be grouped by a
common characteristic (e.g. calligraphic fonts), etc.
When an ATM font is installed in OS/2, a compressed equivalent of the AFM file
named filename.OFM is generated and placed in the same directory as the PFB
file. The OS/2 Font Pallete does not use the AFM file except for
installation, and does not copy the AFM file to the target directory.
FontFolder copies both the AFM file and the PFB file to the target directory
when registering the font with the Master Library from a removable drive. The
first time the font is installed in OS/2 FontFolder puts the OFM file created
in the existing directory with the AFM and PFB file for the font. FontFolder
does not at this time offer the option of automatically erasing the AFM file
at this point, however the user is free to erase the AFM file once the OFM
file has been created (FontFolder shows the OFM file has been created by
changing the font filename entry in the Master Library from AFM to OFM).
ΓòÉΓòÉΓòÉ 3.1. Windows Fonts in OS/2 ΓòÉΓòÉΓòÉ
OS/2 uses and manage ATM fonts in WinOS2 in the same way as Windows. This
means that OS/2 requires either a filename.PFM file or a filename.INF file in
addition to the filename.PFB file to install the font in WinOS2. When the font
is installed in WinOS2 via the ATM Control Panel (FontFolder does not manage
ATM fonts for Windows), ATM will move the PFM file to a subdirectory named PFM
under the directory containing the PFB file, creating the subdirectory if
necessary. OS/2 and WinOS2 can share the same PFB file using a directory
structure as shown below
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γö£ΓöÇΓöÇΓö¼ΓöÇΓöñMYFONTDIRΓöé
Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé
Γö£ΓöÇ filename.afm (ofm)
Γöé
Γöé
Γö£ΓöÇ filename.pfb
Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓööΓöÇΓö¼ΓöÇΓöñ PFM Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé
ΓööΓöÇ filename.pfm
When FontFolder registers a font with the Master Library from a removable
drive, it will also copy either the WinOS2 filename.PFM file to a PFM
subdirectory, creating the directory if necessary, or if it finds a
filename.INF file but no PFM file, the filename.INF file to the directory
containing the AFM and PFB files, provided the user has checked the Copy
Windows Font Files box.
ΓòÉΓòÉΓòÉ 4. Installing FontFolder ΓòÉΓòÉΓòÉ
This section provides a description of what files and system file entries are
created when FontFolder is installed and first opened, and the system resources
used by FontFolder.
To continue in this section choose one of the following:
o FontFolder Files
o FontFolder Memory Requirements
o Other FontFolder Resource Requirements
ΓòÉΓòÉΓòÉ 4.1. FontFolder Files ΓòÉΓòÉΓòÉ
The only files required to use FontFolder are FONTFOLD.EXE and FONTFOLD.HLP.
FONTFOLD.EXE can be installed anywhere on the system. FONTFOLD.HLP can be
installed either in the same directory as FONTFOLD.EXE or in any directory
specified in the set HELP= line in the OS/2 CONFIG.SYS file. It is recommended
that FONTFOLD.HLP be kept in the same directory as FONTFOLD.EXE.
The first time FontFolder starts it asks the user to provide paths to use to
store two sets of files that FontFolder generates during operation. The
default in both cases is to store them in the same directory as FONTFOLD.EXE.
The first of these sets contains one file, FONTFOLD.INI, which keeps key
information about the user preferences for FontFolder such as size and screen
position of the main window, etc., and is created the first time FontFolder is
closed. One case where one might place this file in a separate directory is if
FontFolder is being shared on a network. If the user chooses to place
FONTFOLD.INI in a location other than the default, then FontFolder writes this
location to OS2.INI. If FONTFOLD.INI is left in the default directory then no
entry is made in OS2.INI.
The second set of files that FontFolder creates as part of its operation is its
data files. These include MASTLIB.FF1, which contains information identifying
all the fonts registered with the FontFolder Master Library. FontFolder creates
this file the first time it is closed or when the user chooses Save Master
Library from the Master Library menu. The location of this file is kept in
FONTFOLD.INI. FontFolder will also maintain one generation of backup of
MASTLIB.FF1 called MASTLIB.BAK in the same directory as MASTLIB.FF1. The
combined size of these files should be no more than about 200KB in the worst
case.
The data files also include files of the form FNTPKnnn.FP1, which contain
information identifying all the fonts included in the different FontPacks the
user creates. There will be backup files of the form FNTPKnnn.BAK for these
files also. Unless the user creates a very large number of FontPacks, these
files will take up much less space than the Master Library file.
The Font Cache Directory
An optional feature of FontFolder permits the user to keep the fonts registered
with the Master Library on a Network Drive, thus allowing many users to share
fonts across a LAN. Because font files need to reside on a local hard drive
when the font is actually installed in OS/2, FontFolder maintains a local hard
drive directory, referred to as a Font Cache, where it temporary moves font
files from Network Drives while the font is installed in OS/2. Each installed
font has associated files that are 50-100 KB in size. While this space
requirement is no different for a font installed from a Network Drive than for
a font installed from a local drive, the user needs to be aware of the
potential space requirements for the Font Cache directory if this feature is
used. See the help on establishing the path to the Font Cache for additional
details.
ΓòÉΓòÉΓòÉ 4.2. FontFolder Memory Requirements ΓòÉΓòÉΓòÉ
When in use FontFolder keeps the Master Library and OS/2 Installed Fonts
information in linked lists that require about 560 bytes of memory per font
entry. Sufficient memory is allocated to allow storing over 1200 fonts in the
Master Library, while the number of fonts actually installed in OS/2 should
normally be less than 100 (for performance reasons). Thus maximum use would
require somewhat less than one megabyte of memory beyond what the program
normally takes. This limit is unlikely to be reached in practice because of the
OS/2 limit on listbox contents. Since FontFolder uses OS/2's sparse memory
allocation methodology, only enough memory is committed to hold the actual font
information.
The largest potential consumption of memory by FontFolder will occur when the
user browses fonts in the Master Library using the Font Information Window.
This facility allows the user to quickly examine sample text for very large
numbers of fonts. Memory usage will grow in proportion to the number of fonts
examined. A rough empirical formula is (500 + 11*fonts) KB, where fonts is the
number of fonts browsed. A user browsing hundreds of fonts can quickly consume
several megabytes of memory. See the help on using the Font Information Window
for additional details.
ΓòÉΓòÉΓòÉ 4.3. Other FontFolder Resource Requirements ΓòÉΓòÉΓòÉ
FontFolder uses the standard OS/2 listboxes to display the Master Library and
Installed Fonts lists. In OS/2 2.1 the total contents of all listboxes in the
system is limited to 64 KB. In the worst case of displaying the fully qualified
path name view of these lists each entry can be up to 260 bytes, so the total
number of fonts that could be displayed in this worst case condition would be
around 250 fonts if no other open applications are using listboxes. However,
this only applies if the user has specified very long directory paths for the
font files. In a more typical case of perhaps 50 characters per path name,
FontFolder would be able to display over 1300 fonts. If you have a large number
of fonts and run in to this limit, see the Listbox error help for directions on
how to recover.
ΓòÉΓòÉΓòÉ 5. Using FontFolder ΓòÉΓòÉΓòÉ
FontFolder works on the principle of keeping two separate lists of ATM fonts
which are displayed side-by-side in the main FontFolder window.
1. The OS/2 Installed Fonts list
The Installed Fonts list is simply the list of fonts that are actually
installed in OS/2 and available for use. It is the same list one sees
from the OS/2 Font Pallete or from the Font Dialog of an OS/2 application.
2. The Master Library list
The Master Library list of fonts is a larger list of all fonts that
FontFolder knows about, whether they are currently installed in OS/2 or
not. In normal operation this list will be larger than the number of
Installed Fonts, in some cases substantially so. The user creates this
list by registering fonts with the Master Library using FontFolder's
editing capability available from the Master Library pulldown on the menu
bar. The only limit to registering fonts with the Master Library other
than resource limits (see Installing FontFolder ) is that this list may
only contain font files that reside on a nonremovable local or network
hard drive.
Note: The user may still register fonts residing on removable media with
the Master Library. FontFolder will copy the necessary files to a
user-designated directory on a local hard drive as part of the
registration process.
In addition to these basic lists of fonts, FontFolder provides the user the
facility to create named collections of the Master Library fonts called
FontPacks. A FontPack can be treated just like a single font for the purpose
of installing it in OS/2 or removing it from OS/2, and FontFolder will handle
the installation and removal of the all the fonts in the FontPack. The
FontFolder main window also displays a list of all the FontPacks created, and
a means is provided for the creation and maintenance of the fonts included in
each FontPack.
For further information on using FontFolder see the following:
o Starting FontFolder for the first time
o Everyday FontFolder use
ΓòÉΓòÉΓòÉ 5.1. Starting FontFolder for the first time ΓòÉΓòÉΓòÉ
Once FontFolder has been installed by copying FONTFOLD.EXE and FONTFOLD.HLP to
the system, FontFolder is ready for use. The first time FontFolder is started
it will display the FontFolder Setup Dialog which asks for three pieces of
information:
o The Drive letters of all the removable drives on the system
o The location to store the initialization file FONTFOLD.INI
o The location to store the data files created by FontFolder, MASTLIB.FF1 and
FNTPKnnn.FP1
See the FontFolder Setup Dialog Help for details on the meaning and values for
these settings.
Note: While these are the basic settings that are required to use FontFolder,
there are many other settings that allow the user to customize
FontFolder or take advantage of optional additional function. See the
help on the Settings Notebook for the details.
The first thing FontFolder does on startup is to read in the list of fonts
already installed in OS/2 from OS2.INI. It is possible for this list to
include corrupted font files. If FontFolder encounters a file that it can not
successfully read to obtain the required font information, it displays a
dialog box giving the details of the suspect font and offering the user the
option to remove it from OS2.INI. The user should normally take this option
since FontFolder can not deal with this file (and OS/2 can not use it) and
will redisplay this error message on every startup until the font is removed.
In any case FontFolder will not list the font in the Installed Fonts list.
See the Load Installed Fonts List Dialog Help for details.
On the first startup FontFolder generates an initial Master Library by copying
the list of fonts already installed in OS/2 to the Master Library list. From
this point on the user is free to add or delete entries in the Master Library
independent of what fonts are actually installed in OS/2.
ΓòÉΓòÉΓòÉ 5.2. Everyday FontFolder use ΓòÉΓòÉΓòÉ
Once a font is registered with the Master Library the user can install the
font in OS/2 by selecting the font from the Master Library list and clicking on
the Install button. Multiple selections are permitted. To remove (uninstall) a
font from OS/2 the user selects the font in the Installed Fonts list and clicks
on the Remove button. Installing and removing fonts in this manner has no
effect on the Master Library list. Separate editing facilities are provided
for maintaining the Master Library.
When a font is registered with the Master Library, FontFolder creates an entry
which contains both the name of the font (e.g. Courier Bold) and the fully
qualified path to the font files. If the source for the files is a removable
medium such as a diskette or a CDROM, FontFolder copies the files to a
user-designated directory on a hard drive at the time of registration. It is
this hard drive location that is stored in the Master Library. When a font
already residing on a local hard drive is installed in OS/2 from the Master
Library, no files are moved. FontFolder simply provides OS/2 with the
information on where to find the font files. Similarly, when such a font is
removed from OS/2, no files are moved. Only the entries in OS/2 referring to
these files are deleted. This means that the user has complete freedom in
organizing font files in whatever directory organizations make sense.
The user has the option of Saving the Master Library at any point. If the
Master Library has been changed but not saved when FontFolder is closed, the
user is prompted as to whether the Master Library changes should be saved or
discarded. FontFolder keeps one level of backup of the Master Library file,
and there is provision for the user to Revert to the backup copy of the Master
Library.
The Installed Fonts information is always saved as soon as a font is installed
or removed from OS/2.
Advanced FontFolder Features In addition to the basic FontFolder operations
described above, FontFolder also offers advanced features that provide more
powerful ways to organize and manage fonts. FontPacks allow the user to create
a collection of fonts that can be installed or removed as a single unit. In
addition to storing the Master Library font files on a local hard drive,
FontFolder supports having these font files reside on a Network Drive so that
font files can be shared by many users. FontFolder automatically manages the
movement of these files to and from a local hard drive as required when then
are installed or removed from OS/2.
For details on using FontFolder see
o Registering Fonts with the Master Library
o Deleting Fonts from the Master Library
o Saving the Master Library
o Reverting the Master Library
o Installing Fonts in OS/2
o Removing Fonts from OS/2
o Using and Maintaining FontPacks
o Using Fonts on Network Drives
o Views of Fonts
o FontFolder Settings Notebook
ΓòÉΓòÉΓòÉ 6. Removing FontFolder ΓòÉΓòÉΓòÉ
FontFolder can be removed from the system by finding and deleting the following
files
o FONTFOLD.EXE
o FONTFOLD.HLP
o FONTFOLD.INI
o MASTLIB.FF1
o MASTLIB.BAK
o FNTPKnnn.FP1
o FNTPKnnn.BAK
If the user has never changed the default settings, all of these files should
be in the same directory. If the user specified other paths for the
FONTFOLD.INI file or for the data files, these paths must be searched as well.
If the FontFolder Settings for these paths were changed multiple times while
FontFolder was installed, there could be copies of these files in each of
these paths.
If a path other than the default was specified for FONTFOLD.INI, this
information was recorded in OS2.INI under the application name FontFolder.
This entry can be removed from OS2.INI by resetting the FONTFOLD.INI path to
the same directory as FONTFOLD.EXE using the Settings Notebook.
There are no other changes that FontFolder makes to the system.
ΓòÉΓòÉΓòÉ 7. Creating and Maintaining the Master Library ΓòÉΓòÉΓòÉ
FontFolder is built around the concept of a Master Library in which the user
registers all the fonts that are available for installation in OS/2. Once a
font is registered with the Master Library, the user can install it in OS/2
with simple point and click operations from the FontFolder main window.
When a font is registered with the Master Library, FontFolder creates an entry
which contains both the name of the font (e.g. Courier Bold) and the fully
qualified path to the font files. If the source for the files is a removable
medium such as a diskette or a CDROM, FontFolder copies the files to a
user-designated directory on a local hard drive at the time of registration.
It is this hard drive location that is stored in the Master Library. When a
font is installed in OS/2 from the Master Library from a local hard drive, no
files are moved. FontFolder simply provides OS/2 with the information on where
to find the font files. Similarly, when such a font is removed from OS/2, no
files are moved. Only the entries in OS/2 referring to these files are
deleted. This means that the user has complete freedom in organizing font
files in whatever directory organizations make sense.
FontFolder also allows the user to have fonts whose files reside on Network
Drives registered with the Master Library. In this case, the network location
of the font files is stored in the Master Library. FontFolder automatically
manages moving the font files to and from a temporary local hard drive location
when a font is installed in or removed from OS/2.
In addition to the basic Master Library list of fonts, FontFolder provides the
user the facility to create named collections of the Master Library fonts
called FontPacks. A FontPack can be treated just like a single font for the
purpose of installing it in OS/2 or removing it from OS/2, and FontFolder will
handle the installation and removal of all the fonts in the FontPack.
Deleting a font from OS/2 has no effect on the Master Library entry.
For additional details see the following:
o Creating the Master Library
o Maintaining the Master Library
ΓòÉΓòÉΓòÉ 7.1. Creating the Master Library ΓòÉΓòÉΓòÉ
On the first startup FontFolder generates an initial Master Library by copying
the list of fonts already installed in OS/2 to the Master Library list. From
this point on the user is free to add or delete entries in the Master Library
independent of what fonts are actually installed in OS/2.
ΓòÉΓòÉΓòÉ 7.2. Maintaining the Master Library ΓòÉΓòÉΓòÉ
Maintenance of the Master Library is done by selecting Master Library from the
main window menu bar or opening the popup menu associated with the Master
Library listbox. The popup menu is opened by clicking Mouse Button 2 anywhere
in the Master Library listbox. Throughout this documentation these alternative
ways of accessing the Master Library menu items will be referred to
collectively as the Master Library menus.
The Master Libary menus allow the user to perform the following:
o Register fonts
o Delete fonts
o Save the Master Library to disk
o Revert to a previous version of the Master Library
o Open a Font Information window that displays the information stored in the
Master Library for any Master Library font along with sample text for the
font.
The user has the option of Saving the Master Library at any point. If the
Master Library has been changed but not saved when FontFolder is closed, the
user is prompted as to whether the Master Library changes should be saved or
discarded. FontFolder keeps one level of backup of the Master Library file,
and there is provision for the user to revert to the backup copy of the Master
Library.
ΓòÉΓòÉΓòÉ 8. Installing Fonts in OS/2 ΓòÉΓòÉΓòÉ
In order to install a font in OS/2 the font must first be registered with the
Master Library.
To install one or more fonts in OS/2, first mark the fonts to be installed in
the Master Library list. Then click on the Install button.
Multiple fonts are marked/unmarked by holding down the Ctrl key while marking.
A consecutive set of fonts in the list can be marked by dragging the mouse in
the list. See Selecting items in listboxes for additional information.
Once a font is installed in OS/2 from FontFolder it is immediately available
for use by applications. Some applications may need to be restarted in order
to see the newly installed fonts. A few applications manage their own font
lists. These applications may or may not see all fonts installed in OS/2. If
a newly installed font does not show up in your application, try opening the
OS/2 Font Pallete and looking in the list of fonts shown via the Edit font
button. If the font shows up in the Font Pallete list it is properly installed
in OS/2. In this case you should contact your application vendor to find out
how they are managing fonts.
In addition to this basic mechanism for installing fonts in OS/2, FontFolder
provides a means to create a named collection of Master Library fonts called a
FontPack. All the fonts in a FontPack can be installed in a single action by
selecting and installing the FontPack from a FontPacks listbox in a manner
identical to that used to install a single font. See Using and Maintaining
FontPacks for additional information.
ΓòÉΓòÉΓòÉ 9. Removing Fonts from OS/2 ΓòÉΓòÉΓòÉ
To remove one or more fonts from OS/2, first mark the fonts to be removed in
the OS/2 Installed Fonts listbox. Then click on the Remove button.
Multiple fonts are marked/unmarked by holding down the Ctrl key while marking.
A consecutive set of fonts in the list can be marked by dragging the mouse in
the list. See Selecting items in listboxes for additional information.
In addition to this basic mechanism for removing fonts from OS/2, FontFolder
provides a means to create a named collection of Master Library fonts called a
FontPack. All the fonts in a FontPack can be removed in a single action by
selecting and removing the FontPack from the OS/2 Installed Fonts listbox in a
manner identical to that used to install a single font. See Using and
Maintaining FontPacks for additional information.
Removing fonts from OS/2 is a complicated operation. It is best understood by
thinking of OS/2 keeping two lists of fonts.
o The first OS/2 list is the long term list, kept in OS2.INI, which tells OS/2
which fonts to load on bootup. FontFolder always updates this list when a
font is removed from OS/2, so the font will be gone on the next OS/2 bootup.
o The other OS/2 font list is the list of fonts currently loaded and available
in memory. This is the font list one sees from the OS/2 Font Palette or
when opening the Font Dialog in an application that uses the standard OS/2
Font Dialog.
Since multiple applications can be running in OS/2 simultaneously, OS/2 must
protect one application from another application unloading a font that the
first application is currently using. OS/2's mechanism for accomplishing
this protection is to only permit a font to be unloaded by the process that
loaded it. If an application is started, loads a font, is stopped, and then
restarted, it is now running a difference process so it can no longer unload
the font it originally loaded. On bootup, OS/2 loads all the fonts listed
in OS2.INI in the Workplace Shell process. Thus only applications which run
in the Workplace Shell process can unload these fonts while OS/2 is running.
The OS/2 Font Palette is such an application; FontFolder is not. Therefore
FontFolder can not remove these fonts from the list of fonts currently
available in memory.
FontFolder takes the view that if the user said to unload the font, it
should be shown in the OS/2 Installed Fonts listbox as unloaded, so the OS/2
Installed Fonts listbox is updated and the font removed from the list even
if FontFolder was unable to unload the font from OS/2 memory. As noted
above, the font will be gone the next time OS/2 boots because FontFolder
updates OS2.INI.
Successfully Managing Fonts using FontFolder
The strategy for successfully managing fonts using FontFolder is to keep
loaded in OS/2 only those basic fonts that should always be available to all
applications. When OS/2 boots, these should be the only fonts loaded by the
Workplace Shell process. Then as fonts are needed, they can be loaded by
FontFolder and then unloaded by FontFolder when they are no longer needed.
For this to be successful, FontFolder must be kept loaded (not stopped and
restarted). For users who expect to be regularly loading and unloading a
large number of fonts during a single OS/2 session, it makes sense to include
FontFolder in the OS/2 Startup Folder.
ΓòÉΓòÉΓòÉ 10. Font Information Window ΓòÉΓòÉΓòÉ
The Font Information Window is an independent PM window that displays
information and sample text for any font in the Master Library. To open this
window, either double-click on a font in the Master Library listbox, or
highlight the font and then select Font Information from the Master Library
menus.
The Font Information Window shows the Font Name and Font Pathname of the
selected font and also displays sample text for the selected font. The sample
text display can be varied in content and point size by the user. The content
can be switched between a user-supplied text string up to 512 characters in
length and a display of the ASCII character set. If a character in the sample
text is highlighted, clicking Mouse Button 2 in the sample text window will pop
up the ASCII code (decimal) for the highlighted character.
All main window functions are available while the Font Information Window is
open. For example, it is possible to review a font in the Font Information
Window and then either install the font in OS/2 or delete it from the Master
Library without having to close the Font Information window.
Both the size and location of the Font Information Window can be changed by the
user. Any size changes in the Font Information Window are taken up by the
Sample Text window, so the user can adjust the area available for displaying
sample text (for instance to accomodate the display of larger point sizes).
The font displayed will change as the selection in the main window Master
Library listbox is changed, so the user can browse the Master Library fonts by
leaving the Font Information Window open while moving the selection in the
Master Library listbox (for example by using the keyboard up and down arrow
keys).
WARNING! Browsing fonts can use considerable memory. The first few fonts
browsed will consume around 50K bytes per font. Continued browsing will
consume an additional 10-15K bytes per font. Browsing hundreds of fonts can
cause your swap file to grow by several megabytes. This memory is not released
until FontFolder is closed (closing the Font Information Window does not
release the memory). If you are short of swap file space, be careful how much
font browsing you do!
Changing the Content of the Sample Text Window
The sample text can either be a user-defined text string or it can be a
display of all the displayable characters in the font. The choice is
controlled by radio buttons to the right of the sample text window. In
UserText mode the text string can be modified by directly editing it in the
sample text window.
Changing the Point Size of the Sample Text
The point size of the sample text can be changed via the spin button located
to the right of the sample text window. The sizes available can range from 1
to 99 points, and can be modified by the user via the Settings Notebook.
All changes made to the Font Information Window are stored for use in
subsequent sessions. This includes size and position, user text string, point
size and user text/character set selection.
ΓòÉΓòÉΓòÉ 11. Using and Maintaining FontPacks ΓòÉΓòÉΓòÉ
A FontPack is a named collection of fonts that can be installed and removed as
a single unit. The user creates and manages FontPacks in much the same way as
he or she manages the fonts installed in OS/2. Choosing New under FontPacks on
the menu bar or from the FontPacks popup menu places FontFolder in FontPack
Edit mode, which allows fonts to be added to and removed from the FontPack. In
this mode the FontFolder main window changes the right hand listbox to display
the FontPack Fonts listbox, which shows the fonts currently installed in the
FontPack. Once the appropriate fonts have been installed in the FontPack, it
can be saved by choosing Save or Save As from the menu bar or the FontPack
Fonts popup menu. The user is prompted to give the FontPack a name, which can
be any string up to 29 characters in length. Once it is named and saved, the
FontPack is available for installation in OS/2.
All currently existing FontPacks are listed in the FontPacks listbox in the
FontFolder Main window. To install a FontPack, the user highlights the FontPack
name in the FontPacks listbox, and clicks on the Install button to the right of
the FontPacks listbox. All of the fonts in the FontPack are installed in OS/2,
and in addition the name of the FontPack is added to the OS/2 Installed Fonts
listbox. The name is enclosed in brackets to signal that it is a FontPack, e.g.
<My FontPack>. To remove a FontPack and all its fonts from OS/2, the user
highlights the FontPack name in the OS/2 Installed Fonts listbox, and clicks on
the Remove button. The FontPack and all its fonts are removed from OS/2.
FontPack menu items can be found both under FontPacks on the main menu bar and
on the popup menus for the FontPacks listbox and the FontPack Fonts listbox
which appears as the listbox on the right side of the main window when in
FontPack Edit mode. The popup menus each contain a subset of the main menu
commands that are appropriate to the parent listbox. Throughout this Help
material, this collection of menus is referred to as the FontPack menus.
For further information on using FontPacks, see the following:
o Installing a FontPack in OS/2
o Removing a FontPack from OS/2
o Creating a FontPack
o Editing an existing FontPack
o Saving a FontPack (Save and Save As)
o Deleting a FontPack
o Reverting a FontPack to the backup version
o Quitting FontPack Edit mode
ΓòÉΓòÉΓòÉ 11.1. Installing a FontPack in OS/2 ΓòÉΓòÉΓòÉ
To install a FontPack in OS/2, first click on the FontPack name in the
FontPacks listbox in the FontFolder main window to select the FontPack, and
then click on the Install button to the right of of the FontPacks listbox. All
of the fonts in the FontPack will be installed in OS/2. In addition, the
FontPack name will be added to the OS/2 Installed Fonts listbox to indicate
that the FontPack is installed. The name will be enclosed in angle brackets,
Example If a FontPack named My FontPack is installed in OS/2, the OS/2
Installed Fonts listbox will contain an entry of the form
<My FontPack>
All installed FontPack names will appear at the beginning of the list in the
OS/2 Installed Fonts listbox, before the individual font names.
Note: If all the fonts in the FontPack are already installed in OS/2, the
FontPack name will not be listed in the OS/2 Installed Fonts listbox.
This presumption here is that since all the fonts were installed prior
to installing the FontPack, the user would not want the fonts to be
removed when the FontPack is removed. The only way to accomplish this
is by not adding the FontPack name to the OS/2 Installed Fonts listbox.
If the user wishes the name to be added (and the fonts to be removed
when the FontPack is removed), first remove any one of the fonts
contained in the FontPack from OS/2, and then install the FontPack.
Since now one of the fonts in the FontPack is new, the FontPack name
will be added to the OS/2 Installed Fonts listbox.
ΓòÉΓòÉΓòÉ 11.2. Removing a FontPack from OS/2 ΓòÉΓòÉΓòÉ
To remove a FontPack (and all its fonts) from OS/2, first click on the FontPack
name in the OS/2 Installed Fonts listbox in the FontFolder Main Window to
select the FontPack, and then click on the Remove button below the OS/2
Installed Fonts listbox. All of the fonts in the FontPack will be removed from
OS/2. The FontPack name will also be removed from the OS/2 Installed Fonts
listbox.
Note: It is possible for a given font to be "installed" in OS/2 multiple times
as a result of being installed as an individual font and/or being
installed because it is part of one or more FontPacks. When a FontPack
is removed from OS/2, all the fonts that are part of the FontPack are
removed, even if a font has also been installed individually or as part
of another FontPack. This does not cause a problem for FontFolder or
OS/2, but it can cause the user a problem if he or she mistakenly
believes the font is still installed. The list of installed fonts in
the OS/2 Installed Fonts listbox is always correct, but the fact that a
given FontPack is shown as installed can not be relied on in this case.
It is a good idea when creating FontPacks to try as much as possible to avoid
having the same fonts included in FontPacks which might be installed at the
same time.
If in doubt, the user can make certain all the fonts in a given FontPack are
installed by installing the FontPack again. The FontPack does not have to be
removed prior to reinstallation.
ΓòÉΓòÉΓòÉ 11.3. Creating a FontPack ΓòÉΓòÉΓòÉ
To create a new FontPack, click on New under FontPacks in the menu bar or in
the FontPacks popup menu. The FontFolder Main Window will change to FontPack
Edit mode, replacing the OS/2 Installed Fonts listbox in the right hand portion
of the screen with the FontPack Fonts listbox. The text above the listbox
changes to say Editing FontPack on the first line. The second line shows the
name of the FontPack being edited. For a new FontPack the name shown is
Untitled. The listbox shows the fonts currently installed in the FontPack.
For a new FontPack the list is empty.
Adding one or more fonts to the FontPack is accomplished in exactly the same
way as installing fonts in OS/2. Select one or more fonts in the Master Library
listbox by clicking on them, and then click on the Install button located
adjacent to the Master Library listbox. The selected fonts will be added to
the FontPack Fonts listbox.
To remove fonts from the FontPack, first select the fonts to be removed in the
FontPack Fonts listbox, and then click on the Remove button below the listbox.
Once the FontPack contains the desired fonts, the FontPack can be named and
saved by clicking on either Save or Save As from the FontPack menus. Since the
FontPack has not yet been named, both Save and Save As will display a dialog
box where the user can enter a name for the FontPack. The name can be any text
string up to 29 characters long. Spaces and other special characters are
permitted, although it is recommended not to use backslashes (\) or angle
brackets (< >) as these have special meanings.
Example Names Basic Fonts
FontPack # 5
Calligraphic Fonts
Spreadsheet Fonts
Monthly Sales Report Fonts
Once the name has been entered, click the OK button. The FontPack will be
saved in the directory identified in the Path to FontFolder data files. See
Saving a FontPack for more details.
After saving the FontPack, the user can either quit FontPack Edit mode by
choosing Close from the FontPack menus, or edit another FontPack by choosing
New or Open from the FontPack menus or by double-clicking on an existing
FontPack name in the FontPacks listbox.
If the user chooses Close before saving the FontPack, the user will be
prompted as to whether the FontPack should be saved before quiting. Choosing
No will end FontPack Edit mode without creating the FontPack.
ΓòÉΓòÉΓòÉ 11.4. Editing an existing FontPack ΓòÉΓòÉΓòÉ
To edit an existing FontPack, either first highlight the FontPack in the
FontPacks listbox and then select Open from the FontPack menus, or else
double-click on the FontPack in the FontPacks listbox. The FontFolder main
window will change to FontPack Edit mode, replacing the OS/2 Installed Fonts
listbox in the right hand portion of the screen with the FontPack Fonts
listbox. The text above the listbox changes to say Editing FontPack on the
first line. The second line shows the name of the FontPack being edited, and
the listbox shows the fonts currently installed in the FontPack.
When in FontPack edit mode, you can also change to editing a different FontPack
by double-clicking on the new FontPack name in the FontPacks listbox or
choosing New or Open from the FontPack menus.
Adding one or more fonts to the FontPack is accomplished in exactly the same
way as installing fonts in OS/2. Select one or more fonts in the Master Library
listbox by clicking on them, and then click on the Install button located
adjacent to the Master Library listbox. The selected fonts will be added to
the FontPack Fonts listbox.
To remove fonts from the FontPack, first select the fonts to be removed in the
FontPack Fonts listbox, and then click on the Remove button below the listbox.
Once the FontPack editing is complete, the FontPack can be saved by clicking on
Save in the FontPack menus. If the user wishes to change the name of the
FontPack, this can be done by clicking on Save As in the FontPack menus. A
dialog box will prompt for a name for the FontPack. Once a name is supplied,
clicking the OK button will save the FontPack with the new name. The old
FontPack will still be available under the original name. If the old FontPack
is no longer wanted, it can be deleted (See Deleting FontPacks).
After saving the FontPack, the user can either quit FontPack Edit mode by
choosing Close from the FontPack menus, or edit another FontPack by choosing
New or Open from the FontPack menus or by double-clicking on an existing
FontPack name in the FontPacks listbox.
If the user chooses Close before saving the FontPack, the user will be prompted
as to whether the FontPack should be saved before quiting. Choosing No will
end FontPack Edit mode without saving the changes to the FontPack.
ΓòÉΓòÉΓòÉ 11.5. Saving a FontPack (Save and Save As) ΓòÉΓòÉΓòÉ
When in FontPack Edit mode, a FontPack can be saved by clicking on either Save
or Save As in the FontPack menus. Save is used to save an already existing
FontPack under its present name. Save As is used to either save a new (as yet
unnamed) FontPack, or to save an existing FontPack under a new name. If Save
is clicked for a new FontPack, Save As will be invoked instead. Once the
FontPack has been saved, the user is returned to FontPack Edit mode. The name
of the FontPack currently being edited shows above the FontPack Fonts listbox.
If Save As was chosen and the FontPack name modified, the FontPack being edited
will be the one named in Save As.
Save
Clicking on Save for an existing FontPack will immediately save the current
contents of the FontPack Fonts listbox to the file corresponding to the
FontPack name. The existing version of the file will first be saved as a
backup version. To access the backup version of the FontPack, see Reverting a
FontPack to the backup version.
If the FontPack has not yet been named, clicking on Save will invoke Save As
instead.
Save As
Clicking on Save As opens a dialog box which prompts the user to provide a
name for the FontPack. If the FontPack has not yet been named, Untitled will
appear in the entry field already highlighted so that it can be replaced. A
FontPack can not be saved with the name Untitled. An attempt to do so will be
rejected.
The user can enter any text string of up to 29 characters. Spaces and other
special characters are permitted, although it is recommended not to use
backslashes (\) or angle brackets (< >) as these have special meanings.
Example Names Basic Fonts
FontPack # 5
Calligraphic Fonts
Spreadsheet Fonts
Monthly Sales Report Fonts
Once the name has been entered, click the OK button. The FontPack will be
saved in the directory identified in the Path to FontFolder data files.
If the FontPack already has a valid name, this name will appear in the entry
field.
If the FontPack name is not modified, then clicking OK will cause the
FontPack to be saved to the existing FontPack file as if the user had
chosen Save instead of Save As.
If the FontPack name is modified, then clicking OK will cause a new,
additional FontPack to be created under the new name. This new name will
be added to the FontPacks listbox. The original FontPack will still be
available under its old name. If the user no longer wants this old
FontPack, it can be deleted (See Deleting a FontPack).
A FontPack file with a filename of the form FNTPKnnn.FP1 will be created to
store the list of fonts in the FontPack. nnn is a number from 0 to 99 that
is managed by FontFolder to assure that there is a unique filename for
every FontPack. FontFolder is currently limited to a maximum of 100
simultaneously defined FontPacks.
If the user chooses Cancel from the Save As dialog box, the user is returned
to FontPack Edit mode and the FontPack is not saved. Changes to the FontPack
name are discarded.
ΓòÉΓòÉΓòÉ 11.6. Deleting a FontPack ΓòÉΓòÉΓòÉ
To delete a FontPack, first select the FontPack to be deleted in the FontPacks
listbox, and then click Delete in the FontPack menus. This operation can not
be performed while FontFolder is in FontPack Edit mode. The user will be
prompted to confirm that he or she wants to delete the indicated FontPack.
Choosing Yes will delete the FontPack. Choosing No cancels the operation. Once
a FontPack is deleted, all records of it are erased from FontFolder, the
associated FontPack files are deleted, and the filename corresponding to the
FontPack is returned to the FontFolder pool of unused FontPack filenames.
ΓòÉΓòÉΓòÉ 11.7. Reverting a FontPack to the backup version ΓòÉΓòÉΓòÉ
Once a FontPack has been saved at least twice, FontFolder maintains a backup
copy of the FontPack file that contains the immediately previous version of the
FontPack. If the user wants to revert to the previous version of the FontPack,
this can be done by choosing Revert from the FontPack menus when in FontPack
Edit mode (Revert is only available in FontPack Edit mode). The user will be
prompted to confirm the operation. Choosing Yes will replace the existing
version of the FontPack with the previous version. At the same time, the
existing version will now be made the backup version, so another Revert will
restore the FontPack to the original version. Choosing No from the
confirmation dialog will cancel the operation.
ΓòÉΓòÉΓòÉ 11.8. Quitting FontPack Edit mode ΓòÉΓòÉΓòÉ
To quit FontPack Edit mode, choose Close from the FontPack menus. If the
currently open FontPack has changed since the last Save or Save As, the user
will be asked if the FontPack should be saved before quitting. Choosing Yes or
closing the dialog box without making a choice will result in the FontPack
being saved before quiting FontPack Edit mode. If the FontPack has not yet
been named (name shown as Untitled), the Save As dialog procedure will be
invoked. In this case choosing Cancel or closing the dialog box without making
a choice will result in the FontPack not being saved.
ΓòÉΓòÉΓòÉ 12. Using Fonts on Network Drives ΓòÉΓòÉΓòÉ
With FontFolder Version 1.1, users can now keep their font libraries on Network
Drives provided those drives have drive letter aliases. UNC Names are NOT
SUPPORTED and will cause problems if used.
Prior to Version 1.1, fonts on a Network Drive needed to be moved to a local
hard drive to be registered with the Master Library since they must be
available when OS/2 boots. (There are some utilities which permit delaying the
bootup of OS/2 until LAN logon has been accomplished. If these utilities
interrupt the OS/2 boot process before OS/2 loads its fonts, then it is not
necessary to move fonts to a local hard drive to use them.) With Version 1.1,
FontFolder can be told that certain drive letters are network drives and it
will make sure that the fonts actually installed in OS/2 are available locally
so that OS/2 can access them on bootup. FontFolder does this by maintaining a
Font Cache on a local hard drive, designated by the user. When the user
installs a font in OS/2, FontFolder examines the drive letter of the font file
and if the drive has been designated as a network drive then FontFolder copies
the necessary files to the Font Cache and installs them in OS/2 from that
location. If the font is later removed from OS/2, FontFolder recognizes that
the font being removed is a Font Cache font and deletes the font files from the
Font Cache.
Note: There is a problem in OS/2 if a font is installed, removed and then
reinstalled in OS/2 all in the same session. To circumvent this problem,
FontFolder saves the OFM file in the Font Cache in case the user wants to
reinstall the font in the same session. OFM files are typically around 5 KB,
so the space consumed is minimal. These OFM files are erased when FontFolder
is closed.
Identifying Network Drives to FontFolder:
To use the Network Drives capability of FontFolder the user must identify a
drive as a Network Drive on the Drives Page of the FontFolder Settings
Notebook. Once this has been done, FontFolder will automatically manage all
fonts on this drive as Font Cache fonts.
ΓòÉΓòÉΓòÉ 13. Settings Notebook ΓòÉΓòÉΓòÉ
FontFolder uses an OS/2 style Settings Notebook to maintain various application
settings. The Settings Notebook can be opened either by clicking on Settings
under Options on the main window menu bar, or by clicking Mouse Button 2
anywhere in the background of the FontFolder main window to bring up the
Options popup menu.
Settings are updated when the Settings Notebook is closed.
For details of the pages in the Settings Notebook, see the following:
o Paths page
o Drives page
o Other page
ΓòÉΓòÉΓòÉ 13.1. Settings Notebook - Paths Page ΓòÉΓòÉΓòÉ
The Paths page of the Settings Notebook contains the following entries:
o Path to FontFolder INI file
The first time FontFolder is closed it creates a file called FONTFOLD.INI
and writes a set of information about its state to the file. Examples of
the type of information are the size and location of the FontFolder windows
on the screen, the Removable Drive Letters setting, and the location of the
Master Library file.
The default is to create this file in the same directory as FONTFOLD.EXE.
However the user may want to locate the file in a different directory. For
example, if FontFolder resides on a network server and is shared by several
users, each user needs an individual copy of FONTFOLD.INI. In this case the
user should change the path to the FontFolder INI file to point to a
location on the local workstation.
If the path to the FontFolder INI file is changed, an entry is made in
OS2.INI specifying where this file is located.
o Path to FontFolder data files
FontFolder uses this path to determine where to store its data files. The
default is for these files to reside in the same directory as the
FONTFOLD.EXE file, but the user can change the path to point to another
location. The Path to FontFolder data files information is stored in
FONTFOLD.INI. The following files are kept in the directory specified in
this path:
- The Master Library data file, MASTLIB.FF1, contains the font registration
information for the Master Library.
- The FontPack data files, FNTPKnnn.FP1, contain the font registration
information for the fonts included in the FontPacks.
- One backup copy of each of the above files, of the form MASTLIB.BAK and
FNTPKnnn.BAK respectively.
One consideration in deciding where to locate the these files is their size.
The size will vary depending on the number of fonts registered with the
Master Library and the number of fonts in FontPacks. For the largest
library that FontFolder can currently support the size of MASTLIB.FF1 would
be approximately 100KB. Since one backup copy, MASTLIB.BAK, is also
maintained, the maximum total space requirement for the Master Library files
is approximately 200KB. However, this assumes the font file information
stored includes maximum length path names. In actual practice the Master
Library files will probably only be 20-30% of this size. The FontPack files
will normally be much smaller.
o Path to Font Cache
If the user has identified any drive letters to FontFolder as Network
Drives, then FontFolder will copy any font files located on these drives to
a special directory on a local hard drive when these fonts are installed in
OS/2. This is done so that OS/2 can access these font files when booting,
since the network drive may not yet be available. This special directory is
known as the Font Cache.
If there are Network Drives identified to FontFolder, the user must provide
a path to the directory on a local hard drive where the Font Cache should be
located. It is not necessary to provide this path if no Network Drives are
identified. The default is for the Font Cache to be located in the same
directory as the FontFolder data files. FontFolder will create a
subdirectory with the name FFCACHE at the location identified by this path.
If the user adds FFCACHE to the end of the path supplied, FontFolder will
use this path without adding an additional FFCACHE to the path.
The FFCACHE directory will contain the font files for all fonts currently
installed in OS/2 that originated on network drives. As fonts are removed
from OS/2, these font files will be erased from the FFCACHE directory. Each
network font installed in OS/2 will typically have associated files that
consume 50-100 KB of space. If the user maintains the number of fonts
installed in OS/2 to around 50, then if all the installed fonts are network
fonts, the space needed for the Font Cache will be of the order of 2.5-5 MB.
Users should take this into account when deciding on where to locate the
Font Cache.
ΓòÉΓòÉΓòÉ 13.2. Settings Notebook - Drives Page ΓòÉΓòÉΓòÉ
FontFolder takes special actions with a font depending on what kind of drive
the font's files reside on. The first time FontFolder is started, it analyzes
the drives attached to the system and automatically sets defaults for Removable
Drive Letters and Network Drive Letters. All other drive letters are treated as
local hard drives. The user should review these settings and make appropriate
changes if required. After the first startup FontFolder keeps these drives
settings in the FONTFOLD.INI file and does not repeat the automatic analysis.
The user can have FontFolder repeat the analysis and reset the drive letters to
their defaults by clicking on the Default button on the Drives page.
The Drives page of the Settings Notebook contains the following entries:
o Removable Drive Letters
When the user trys to register a font with the FontFolder Master Library,
FontFolder needs to check whether the source location for the font files is
on a removable medium such as a diskette or a CDROM. If the font files are
on a removable medium, FontFolder must copy them to a location on a local
nonremovable drive (a hard drive) as part of the registration process. OS/2
requires that fonts reside on a hard drive when installed.
FontFolder uses the Removable Drive Letters entry to identify the removable
drives. The user should enter the drive letters of all the removable drives
on the system in the Removable Drive Letters entry field. The form of the
entry is the drive letters with no spacing or other punctuation.
Example: If the system has two diskette drives, A and B, and a CDROM drive
identified as F, then the Removable Drive Letters entry would be
ABF
Failure to properly identify the removable drives can lead to unpredictable
results.
o Network Drive Letters
If a drive is identified to FontFolder as a Network Drive, fonts residing on
this drive are first copied to the Font Cache before they are installed in
OS/2. See Using Fonts on Network Drives for a detailed description of this
feature. FontFolder uses the Network Drive Letters entry to identify
Network Drives.
The user should enter the drive letters of all the network drives on the
system in the Network Drive Letters entry field. The form of the entry is
the drive letters with no spacing or other punctuation.
Example: If drives L and N are remote drives on a LAN, then the Network
Drives entry would be
LN
If a network drive is not identified to FontFolder as such, FontFolder will
treat it as a local hard drive. This can lead to problems with fonts not
being available in OS/2 if the network drive is not available during OS/2
bootup.
ΓòÉΓòÉΓòÉ 13.3. Settings Notebook - Other Page ΓòÉΓòÉΓòÉ
The Other page of the Settings Notebook contains the following miscellaneous
FontFolder settings:
o Copy Windows Font Files checkbox
When the font that a user registers with the Master Library resides on a
removable drive such as a diskette or CDROM drive, FontFolder must copy the
font files to a hard drive location in order for OS/2 to use them. If the
Copy Windows Font Files checkbox is checked then FontFolder will also copy
the appropriate Windows font files to the hard drive at the same time.
o Sample Text Pt Sizes
The Font Information Window allows the user to view sample text of a Master
Library font in various point sizes. The point size displayed is set via a
spin button in the Font Information window. In turn, the sizes that appear
on the spin button are determined by the entries in the Sample Text Pt Sizes
setting. The user can enter a point size from 1 to 99 points (a point is
approximately 1/72 of an inch) in each of the 10 entry boxes. As the spin
button is changed, the point size entries in the Sample Text Pt Sizes field
will be presented in left to right, top to bottom order. After the last
entry is presented the spin button will cycle back to the first entry.
ΓòÉΓòÉΓòÉ 14. FontFolder Menus. ΓòÉΓòÉΓòÉ
The menu items available in FontFolder are shown below. Most menu items are
available either from the main menu bar or from popup menus associated with the
main window itself and with the main window listboxes. Popup menus are
activated by clicking Mouse Button 2 on the appropriate element. Throughout
this documentation, these alternative means of accessing menu items will be
referred to collectively as the (Menu name) menus, e.g. the Master Library menu
items will be referred to as available on the Master Library menus. In the menu
list below, the following symbols indicate which popup menu each menu item
appears on:
MW Main Window
ML Master Libary Listbox
FP FontPacks Listbox
FPF FontPack Fonts Listbox (in Edit FontPacks mode)
Click on the appropriate item for further information.
o Master Library
- Register Fonts ML
- Delete Fonts ML
- Save Master Library ML
- Revert Master Library ML
- Font Information ML
o FontPacks
- New FontPack FP FPF
- Open FontPack FP
- Save FontPack FPF
- Save FontPack as... FPF
- Delete FontPack FP
- Revert FontPack FPF
- Close FontPack FPF
o Options
- View MW
- Settings MW
ΓòÉΓòÉΓòÉ 14.1. Master Library Menu ΓòÉΓòÉΓòÉ
The choices on the Master Library menu are
o Register Fonts
o Delete Fonts
o Save Master Library
o Revert Master Library
o Font Information
ΓòÉΓòÉΓòÉ 14.1.1. Register Fonts ΓòÉΓòÉΓòÉ
Select this menu item to register one or more fonts with the Master Library.
When selected, a Register Fonts file dialog panel will appear which allows the
user to select the drive and directory on which the fonts to be registered are
located (the source location). Fonts are represented in the file dialog by
their PFB file. Multiple font files may be selected.
If the source location is on a removable drive an additional Copy Fonts to Hard
Drive dialog panel will be displayed where the user can specify where to place
the selected fonts on a hard drive (the target location). The user can also
specify on this panel whether or not to copy any companion Windows font files
that are found.
If the operation is successful the fonts selected will appear in the Master
Library list. This list must be saved to make these additions permanent.
ΓòÉΓòÉΓòÉ 14.1.2. Delete Fonts ΓòÉΓòÉΓòÉ
First mark one or more fonts in the Master Library list for deletion and then
select this menu item from the Master Library menus to delete the marked fonts
from the Master Library. FontFolder will prompt the user to confirm the
deletion or cancel the operation. Upon confirmation the fonts will be deleted
from the Master Library list. This list must be saved to make these deletions
permanent.
If no font has been marked before Delete Fonts is selected an error message is
displayed and the operation is cancelled.
No font files are deleted from the hard drive when a font is deleted from the
Master Library list. Use the standard OS/2 file management facilities to
delete the font files if desired.
ΓòÉΓòÉΓòÉ 14.1.3. Save Master Library ΓòÉΓòÉΓòÉ
Select this menu item from the Master Library menus to save a copy of the
current Master Library list to disk in the file MASTLIB.FF1. If MASTLIB.FF1
already exists it will be converted to MASTLIB.BAK before the new copy is
written.
ΓòÉΓòÉΓòÉ 14.1.4. Revert Master Library ΓòÉΓòÉΓòÉ
Select this menu item from the Master Library menus to make the backup copy of
the Master Library file, MASTLIB.BAK, the current copy.
Note: The existing current copy, MASTLIB.FF1, will in turn be made the backup
copy, so two Revert operations cancel the operation.
The current Master Library list held in memory and seen on the screen is reset
to show the contents of the new current copy of the Master Library.
ΓòÉΓòÉΓòÉ 14.2. FontPacks Menu ΓòÉΓòÉΓòÉ
The choices on the FontPacks menu are
o New FontPack
o Open FontPack
o Save FontPack
o Save FontPack as...
o Delete FontPack
o Revert FontPack
o Close FontPack
ΓòÉΓòÉΓòÉ 14.2.1. New FontPack ΓòÉΓòÉΓòÉ
Choose New FontPack from the FontPacks menus to create a new FontPack.
See the Creating a FontPack help for more details.
ΓòÉΓòÉΓòÉ 14.2.2. Open FontPack ΓòÉΓòÉΓòÉ
Choose Open FontPack from the FontPacks menus to edit an existing FontPack.
See the Editing an existing FontPack help for more details.
ΓòÉΓòÉΓòÉ 14.2.3. Save FontPack ΓòÉΓòÉΓòÉ
Choose Save FontPack from the FontPacks menus to save an existing FontPack
under its current name.
See the Saving a FontPack (Save and Save As) help for more details.
ΓòÉΓòÉΓòÉ 14.2.4. Save FontPack as ΓòÉΓòÉΓòÉ
Choose Save FontPack as from the FontPacks menus to name and save a new
FontPack or to save an existing FontPack under a new name.
See the Saving a FontPack (Save and Save As) help for more details.
ΓòÉΓòÉΓòÉ 14.2.5. Delete FontPack ΓòÉΓòÉΓòÉ
Choose Delete FontPack from the FontPacks menus to delete an existing FontPack.
See the Deleting a FontPack help for more details.
ΓòÉΓòÉΓòÉ 14.2.6. Revert FontPack ΓòÉΓòÉΓòÉ
Choose Revert FontPack from the FontPacks menus to revert a FontPack to the
backup copy.
See the Reverting a FontPack help for more details.
ΓòÉΓòÉΓòÉ 14.2.7. Close FontPack ΓòÉΓòÉΓòÉ
Choose Close FontPack from the FontPacks menus to close FontPack Edit mode and
return to the Install Fonts mode.
See the Quitting FontPack Edit mode help for more details.
ΓòÉΓòÉΓòÉ 14.3. Options Menu ΓòÉΓòÉΓòÉ
The choices on the Options menu are shown below:
o View
o Settings
ΓòÉΓòÉΓòÉ 14.3.1. View ΓòÉΓòÉΓòÉ
The View menu option allows the user to change how the font lists are displayed
in the main FontFolder window. The default display lists the fonts by their
font names (e.g. Courier Bold). The user can also choose to have the lists
display the fonts by their file names (COURB.OFM) or by their fully qualified
path names (C:\PSFONTS\COURB.OFM). In each view the font lists are sorted
alphabetically by the currently displayed names.
Note: One way in which an alternate view is useful is that the path names view
groups all fonts residing in the same directory together in the list so
a user who wants to move a font directory for space or other reasons and
needs to discover which font files from that directory are currently
loaded in OS/2 can easily find them.
All FontFolder functions are fully operational from whatever view is currently
displayed.
To select a new view, choose the View menu item from the Options menus, then
choose the appropriate view from the submenu.
ΓòÉΓòÉΓòÉ 14.3.2. Settings ΓòÉΓòÉΓòÉ
Choose the Settings menu item from the Options menus to bring up the FontFolder
Settings Notebook. From this dialog the user can change various settings that
FontFolder uses to customize its operation.
See the FontFolder Settings Notebook help for more details.
ΓòÉΓòÉΓòÉ 14.4. Help Menu Help ΓòÉΓòÉΓòÉ
Help is available for the following Help menu items:
o Keys Help
o Product information
ΓòÉΓòÉΓòÉ 14.4.1. Keys Help ΓòÉΓòÉΓòÉ
The following are the FontFolder shortcut keys. When the names of two keys are
shown joined by a plus (+) sign, press both keys simultaneously.
Main Window Shortcut Keys
Key Purpose
Ctrl+M Tab to Master Library list in Main Window
Ctrl+O Tab to OS/2 Installed Fonts list in Main Window
Ctrl+I Install font in OS/2
Ctrl+U Remove(Uninstall) font from OS/2
Menu Item Shortcut Keys
Key Purpose
Ctrl+R Register font with Master Library
Ctrl+D Delete font from Master Library
F2 Save Master Library
Shift+F2 Revert Master Library
Ctrl+Q Master Library font information
Ctrl+A Create new FontPack
Ctrl+B Open existing FontPack
Ctrl+C Save FontPack
Ctrl+E Save As... Font Pack
Ctrl+G Delete Font Pack
Ctrl+H Revert Font Pack
Ctrl+J Quit FontPack edit mode
Ctrl+N View fonts by fontname
Ctrl+F View fonts by filename
Ctrl+P View fonts by pathname
Ctrl+S View/Change Settings
ΓòÉΓòÉΓòÉ 14.4.2. Product Information ΓòÉΓòÉΓòÉ
Selecting this menu item displays product related information such as the
version number, author and date of production of FontFolder.
ΓòÉΓòÉΓòÉ 15. FontFolder Dialogs ΓòÉΓòÉΓòÉ
Help is available for the following FontFolder dialogs:
o Setup Dialog
o Load Installed Fonts List Dialog
o Register Fonts Dialog
ΓòÉΓòÉΓòÉ 15.1. Setup Dialog ΓòÉΓòÉΓòÉ
The FontFolder Setup Dialog is displayed when first starting FontFolder and in
any case when FontFolder cannot find the FONTFOLD.INI file on startup.
This dialog presents the user with key choices that must be made before
FontFolder can run. They are
o Removable Drive Letters
When the user trys to register a font with the FontFolder Master Library,
FontFolder needs to check whether the source location for the font files is
on a removable medium such as a diskette or a CDROM. If the font files are
on a removable medium, FontFolder must copy them to a location on a
nonremovable drive (a hard drive) as part of the registration process. OS/2
requires that fonts reside on a hard drive when installed.
FontFolder uses the Removable Drive Letters entry to identify the removable
drives. The user should enter the drive letters of all the removable drives
on the system in the Removable Drive Letters entry field. The form of the
entry is the drive letters with no spacing or other punctuation.
Example: If the system has two diskette drives, A and B, and a CDROM drive
identified as F, then the Removable Drive Letters entry should be
ABF
Failure to properly identify the removable drives can lead to unpredictable
results.
o Path to FontFolder INI file
The first time FontFolder is closed it creates a file called FONTFOLD.INI
and writes a set of information about its state to the file. Examples of
the type of information are the size and location of the FontFolder window
on the screen, the Removable Drive Letters setting, and the location of the
Master Library file.
The default is to create this file in the same directory as FONTFOLD.EXE.
However the user may want to locate the file in a different directory. For
example, if FontFolder resides on a network server and is shared by several
users, each user needs an individual copy of FONTFOLD.INI. In this case the
user should change the path to the FontFolder INI file to point to a
location on the local workstation.
If the path to the FontFolder INI file is changed, an entry is made in
OS2.INI specifying where this file is located.
o Path to FontFolder data files
FontFolder creates several data files during operation.
The Master Library data file, MASTLIB.FF1, contains the font registration
information for the Master Library. The default is for this file to reside
in the same directory as the FONTFOLD.EXE file, but the user can change the
path to point to another location. The Path to FontFolder date files
information is stored in FONTFOLD.INI.
One consideration in deciding where to locate the Master Library data file
is the size of this file. The size will vary depending on the number of
fonts registered with the Master Library. For the largest library that
FontFolder can currently support the size of MASTLIB.FF1 would be
approximately 100KB. Since one backup copy, MASTLIB.BAK, is also
maintained, the maximum total space requirement for the Master Library files
is approximately 200KB. However, this assumes the font file information
stored includes maximum length path names. In actual practice the Master
Library files will probably only be 20-30% of this size.
The data files also include files of the form FNTPKnnn.FP1, which contain
information identifying all the fonts included in the different FontPacks
the user creates. There will be backup files, of the form FNTPKnnn.BAK for
these files also. Unless the user creates a very large number of FontPacks,
these files will take up much less space than the Master Library file.
ΓòÉΓòÉΓòÉ 15.2. Copy Fonts to Hard Drive Dialog ΓòÉΓòÉΓòÉ
When the font that a user registers with the Master Library resides on a
removable drive such as a diskette or CDROM drive, FontFolder must copy the
font files to a hard drive location in order for OS/2 to use them. The Copy To
Hard Drive dialog will be displayed, and the user must enter the path to the
directory on the hard drive where the fonts should be copied. A checkbox gives
the user the option of making the path entered the default for future Copy
Fonts to Hard Drive dialogs.
The user also may change the Copy Windows Font Files setting as shown in the
Copy Windows Font Files checkbox. If the Copy Windows Font Files checkbox is
checked then FontFolder will also copy the appropriate Windows font files to
the hard drive. This setting may also be changed from the Settings Notebook.
ΓòÉΓòÉΓòÉ 15.3. Load Installed Fonts List Dialog ΓòÉΓòÉΓòÉ
This dialog box appears during FontFolder startup when FontFolder encounters a
font already installed in OS/2 that is either unreadable by OS/2 or for which
the OS/2 font information is corrupt. It is possible to add such fonts to the
list of OS/2 Installed Fonts using the OS/2 Font Pallete. However, OS/2 cannot
use such fonts, and they do not show up in the Font Pallete. FontFolder
rejects these fonts.
The Load Installed Fonts List dialog shows the name of the unusable font file,
and gives the user the option of either removing it from the list of Installed
Fonts or leaving it alone. In either case, FontFolder will not show this font
on its list of Installed Fonts. Normally the user should choose to Remove the
font. The only case where one might choose otherwise is if the user wants to
temporarily leave it alone while the user investigates to understand what the
problem might be with the font file.
If the user chooses the Leave Alone option, this dialog box will reappear every
time FontFolder is started, until the user chooses Remove.
ΓòÉΓòÉΓòÉ 15.4. Register Fonts Dialog ΓòÉΓòÉΓòÉ
Use this dialog box to mark the font files that you want to register with the
FontFolderMaster Libary. First select the Drive on which the font files are
located from the Drive: box, then select the Directory on which the font files
are located by doubleclicking on the correct directory in the Directory: box.
The File: box will fill with the names of all the font PFB files in the
selected directory. FontFolder uses the font PFB files to identify the fonts,
unlike the OS/2 Font Pallete, which uses the font AFM files. Mark all the font
files you want to register and then click OK. Multiple files can be marked by
holding down the control key while marking. Consecutive files can be marked by
dragging the mouse in the list of files while holding down Mouse Button 1 (and
the control key if required).
Selecting Cancel will return you to the Main FontFolder Window.
ΓòÉΓòÉΓòÉ 16. Selecting Items in Listboxes ΓòÉΓòÉΓòÉ
Many of the listboxes in FontFolder use an OS/2 selection style known as
Extended Selection which permits multiple consecutive items to be selected by
dragging the mouse in the listbox. The listboxes which use this selection
style are:
o Master Library listbox
o OS/2 Installed Fonts listbox
o FontPack Fonts listbox
o File selection listbox in the Register Fonts dialog
The methods for selection and deselection in these listboxes is as follows:
Selection
o To select a single item simply click Mouse Button 1 on that item. Any
items previously selected will be deselected.
o To select multiple consecutive items in the list. Hold down Mouse Button
1 while dragging the mouse through the items to be selected.
o To select multiple isolated items, hold down the Ctrl key while clicking
Mouse Button 1 on each of the items.
o To select multiple blocks of consecutive items that are separated in the
list, hold down the Ctrl key while dragging the mouse through each
separate block of items.
Deselection
o To deselect all items but one in the list, click Mouse Button 1 on that
item. All previously selected items will be deselected.
o To deselect one or more items from a list of multiple selected items,
hold down the Ctrl key while clicking Mouse Button 1 on each of the items
to be deselected.
o To deselect consecutive items from a list of multiple selected items,
hold down the Ctrl key while dragging the mouse through the items to be
deselected.
ΓòÉΓòÉΓòÉ 17. Error Recovery ΓòÉΓòÉΓòÉ
See the following for help with specific errors:
o Listbox Error
ΓòÉΓòÉΓòÉ 17.1. Listbox Error ΓòÉΓòÉΓòÉ
Error Message:
OS/2 can not insert any more items in the listbox name listbox. Your data
should be safe. Refer to the Help section on Error Recovery for
instructions on how to recover from this error.
Explanation:
This error occurs when OS/2 has reached its limit of 64K bytes of listbox text
for all listboxes in the system. In FontFolder this usually only occurs when
in full pathname view mode and the font directory paths are very long. If you
have large numbers of fonts stored in directories with long path names, try
the following:
1. If you are not already in Pathname view mode, switch to this mode,
ignoring the error message.
2. Select all the entries in the Master Library listbox that are located in
the directory with the long path name.
3. Select Delete from the Master Library menu.
4. Select Pathname view mode again from the Options menu to refresh the
listboxes and repeat steps 2 and 3. Do this as many times as is required
to purge all the items for the long path name directory.
5. Save the Master Library. You should now be able to switch in and out of
the Pathname view mode without encountering the Listbox error. If not,
you may have to repeat the above steps for another directory.
6. If any of the fonts you have just removed are installed in OS/2, uninstall
them.
7. Close FontFolder and reboot the system. The reboot may not be necessary,
but you should do it anyway as a safety precaution.
8. Reorganize your font directories so that they have shorter path names, and
then re-register the fonts with FontFolder.
If after doing the above, you still get the Listbox error message, you have
reached the limit of the total number of fonts you can register in FontFolder.
Remove fonts using the above procedure until the error message no longer
occurs.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
FontFolder uses the term register in the sense that information about the font
and where to find the font files is added to the library. This term is used in
preference to add to try to make the point that no files are added to the
system as part of the registration process. The exception to this is when the
files reside on a removable drive, in which case FontFolder both registers them
and adds them to the system.