Article View: comp.os.ms-windows.setup
Article #1351Re: TrueTypeFont-Bug!
From: robert.k.nichols
Date: Sat, 09 Jan 1993 02:34
Date: Sat, 09 Jan 1993 02:34
42 lines
2712 bytes
2712 bytes
In article <1993Jan09.000215.12630@microsoft.com> blakeco@microsoft.com (Blake Coverett) writes: >In article <1993Jan8.003555.4939@cbfsb.cb.att.com> rnichols@cbnewsg.cb.att.com (robert.k.nichols) writes: >>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. > >Huh? This is one of the reasons Microsoft and Apple chose TrueType over >Type-1, an open standard. > >All of the specs are on ftp.uu.net in /vendor/microsoft/TrueType-Info. >In particular have a look at ttspec[1-3].zip for WFW formatted docs >or tt-help.zip for a WinHelp version. You'll also find ttfdump.zip >which will let you analyze TT fonts and ttfparse.zip which includes >C source for parsing TTF files. What more could anyone ask for? My thanks to all who directed me to these files. A large part of my aggravation came from my unsuccessful attempts to find this. When I first had the problem, asked a Microsoft support person (who was being pretty helpful, actually) where I could get information about the file formats. I was told that Microsoft had this information under a nondisclosure agreement, and that I would have to contact Apple. After several calls to Apple, I finally found someone who at least knew what I was talking about, but who told me that the file format was proprietary and available only under license (for a substantial fee). I made it quite clear all along that I simply wanted documentation on the file format, and not any sort of development kit. Oh, well... >>TrueType sucks! >> > >Tsk, tsk, name calling won't get you anywhere. Alright, then, it's functionally impaired. I never seem to run into problems with PostScript fonts. I have yet to see a working implementation of a really complex TrueType font. Bob Nichols AT&T Bell Laboratories rnichols@ihlpm.ih.att.com
Technical Details
Message-ID:
<1993Jan9.023408.28608@cbfsb.cb.att.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!wupost!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsk!cbnewsj!att-out!cbfsb!cbnewsg.cb.att.com!rnicholsReferences:
<jcmorris.726422810@mwunix> <1993Jan8.003555.4939@cbfsb.cb.att.com> <1993Jan09.000215.12630@microsoft.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.ms-windows.setup Path: arc1-ca.pugleaf.net!sparky!uunet!wupost!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsk!cbnewsj!att-out!cbfsb!cbnewsg.cb.att.com!rnichols From: rnichols@cbnewsg.cb.att.com (robert.k.nichols) Subject: Re: TrueTypeFont-Bug! Message-ID: <1993Jan9.023408.28608@cbfsb.cb.att.com> Sender: news@cbfsb.cb.att.com Organization: AT&T References: <jcmorris.726422810@mwunix> <1993Jan8.003555.4939@cbfsb.cb.att.com> <1993Jan09.000215.12630@microsoft.com> Date: Sat, 9 Jan 1993 02:34:08 GMT Lines: 42