FONTMONGER PATCH

From versions: 1.0, 1.0.1 or 1.0.2
To version: 1.0.3

Copyright (c) 1992 Ares Software Corp.
_____________________________________________________________

TO APPLY THIS PATCH:

1. Place the files PATCH.EXE and PATCH.RTP into the directory
where you installed FontMonger, usually \FMONGER.

If you installed FontMonger in a different directory, you
will need to substitute your directory name in the command
given below.

2. In DOS, type:

CD \FMONGER
PATCH

It takes a couple of minutes to apply the patch.
_____________________________________________________________

FIXED IN VERSION 1.0.3:

* FontMonger no longer crashes intermittently after converting
fonts to TrueType format. (This fix was supposed to be in
1.0.2, but got left out by accident.)

* The number of kerning pairs in a PFM file is set correctly.
(The incorrect number was causing crashes in PageMaker and
Ventura Publisher.)

* Adobe's Bookman Light is recognized as a valid Type 1 font.
_____________________________________________________________

FIXED IN VERSION 1.0.2:

* FontMonger compensates for an arbitrary change made to
TrueType fonts by Windows 3.1. (The result of Windows'
meddling was that the "show spaces" function in Word for
Windows showed spaces as boxes instead of dots.)

* FontMonger can correctly open Nimbus Q fonts generated by
SoftType (as opposed to ones shipped with SoftType) and by
Publishers Type Foundry.

* Changing a composite character to a normal character prior
to outline editing does not set the character width to zero.

* FontMonger no longer crashes intermittently after converting
fonts to TrueType format.

* Macintosh fonts that are generated with the standard Adobe
encoding are correctly flagged as such.

* FontMonger more reliably picks up family names, style names
and other font information from PostScript Type 1 fonts.

* The Find button (in Batch Convert) can be used to scan
write-protected disks.
_____________________________________________________________

FIXED IN VERSION 1.0.1:

* FontMonger starts up correctly when Windows is installed at
the root level of a disk drive.

* All errors during program initialization are reported.

* Saving a FRF file on a drive different from the drive that
has the temporary file directory works properly.

* Pasting multiple characters in place of selected characters
maintains the proper order of the characters from the
clipboard.

* Characters not in the standard Windows ANSI character set
(128, 129, 141, etc) are not lost when saving a FRF file.

* In the character chart view, pasting characters into
positions 128, 129, etc does not cause a GO1 error.

* In the character chart view, attempting to open an Alter
Character window for positions 128, 129, etc does not cause
a GO1 error.

* When reading a PFB font from the PSFONTS directory,
FontMonger does not ignore the PFM file (in the PFM sub-
directory) if there is an AFM file (in the AFM sub-directory).

* The number of kerning pairs in a PFM file is limited to
511, because more kerning pairs may crash ATM.

* Characters in TrueType fonts converted from certain
deficient Type 1 fonts are not "shifted" by one character
position ('a' in place of 'b', 'b' in place of 'c', etc).

* FontMonger correctly notes the character number of the
first character in a WFN font, so that the characters are
encoded correctly when converted to another format.

* FontMonger properly calculates the size of characters in
a WFN font, so that characters don't come out too small
or too large.

* The font name for LXO fonts does not contain duplicate
"bold"/"italic" designators.

* Incorrect "winding" of the data in some LXO fonts is fixed
automatically when the fonts are converted.

* Macintosh Type 1 fonts belonging to the same family are
given non-conflicting names.

* Intellifonts from sources other than Agfa are decoded and
imported correctly.

* The family relationship for a new font -- one created using
New from the File menu -- defaults to "plain member" instead
of "other family member".

* The drop-down list of file types in the Open Font dialog
includes a "Macintosh" entry.

* Copying diagonal fractions to the clipboard (in fonts that
do not contain their own diagonal fraction separator
character) does not cause a SH1 or SH2 error.

* The diagonal fraction separator that FontMonger creates
(in fonts that do no contain their own) is no longer
malformed.

* Entering a fairly large horizontal or vertical move value
in an Alter Character window does not cause the value
to change to an extremely large number.

* Changing the top or bottom components of a fraction does
not cause a SH1 error.
_____________________________________________________________