🚀 go-pugleaf

rnichols@cbnewsg.cb.att.com (robert.k.nichols) writes:

>In article <jcmorris.726422810@mwunix> jcmorris@mwunix.mitre.org (Joe Morris) writes:

>>Something to consider is whether the fonts themselves are properly built,
>>rather than assuming that the font engine in Windows is faulty.

>>Who built the fonts which are giving you problems?  Are they commercial
>>products constructed according to the official Apple specifications, or
>>are they el cheapo knockoffs done in someone's basement?  (And note that
>>there are numerous supposedly commercial fonts which do not meet the
>>standard specifications.)

>I believe I was the one who posted about this same problem several
>months ago.  As you can read in the followup that I just posted, yes,
>the fonts I have were indeed converted from fonts generated by Altsys
>Fontographer.  It's a little difficult to examine the fonts to see if
>they meet Apple specifications, since the specifications are
>PROPRIETARY and obtainable only under license.

The specs are available via anonymous ftp from ftp.uu.net, in the
directory vendor/microsoft/TrueType-Info.  The files are generally
revisable Word for Windows documents.

Last time I looked the text wasn't completely current (some changes, for
example, have been made in the license enforcement bits) but the material
describes what you should expect to find in a font file.  I used the
material, for example, to show that the output of the AllType font
converter (aside from carrying that snotty license restriction about
what you can do with the output) fails to properly generate the font 
characteristics data when translating from PostScript to TrueType.

Joe Morris