Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!uwvax!astroatc!nicmad!madnix!perry
From: perry@madnix.UUCP (Perry Kivolowitz)
Newsgroups: comp.sys.amiga.tech
Subject: Re: FastFonts (was Re: Windows/Fonts)
Message-ID: <430@madnix.UUCP>
Date: 28 Jan 89 21:48:49 GMT
References: <6080.AA6080@heimat> <671@intvax.UUCP>
Reply-To: perry@madnix.UUCP (Perry Kivolowitz)
Distribution: usa
Organization: ASDG Incorporated
Lines: 21

With all this discussion about FF not working on this or that font I am getting
the feeling the message Aaron Avery posted about a coding error in FF and it's
solution might not have made it off of Madnix.

In short, FF (every version ever released I believe) contains a bug in which
the font flag bits are incorrectly tested to see if a given font is ok to use.
The net effect is that a lot of fonts which are ok to use cannot be used.

I will email Aaron to repost his message (with binary fix). 

It is interesting to see how far and how long FF has been distributed (as
an independent commercial product, as a giveaway commercial product and as
a Commodore supported item) considering that it doesn't work with MOST fonts
even though it should. It gives one pause for wonder...


-- 
Perry Kivolowitz, ASDG Inc.
                          
ARPA: madnix!perry@cs.wisc.edu   {uunet|ncoast}!marque!
UUCP:   {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!perry