Path: utzoo!attcan!uunet!munnari.oz.au!bruce!monu1!vaxc!cie590l
From: hadgraft@civeng.monash.edu.au (Roger Hadgraft)
Newsgroups: comp.windows.ms
Subject: Re: Crappy Fonts For Windows
Message-ID: <8347@vaxc.cc.monash.edu.au>
Date: 9 Oct 89 06:20:38 GMT
References: <2447@optilink.UUCP>
Sender: cie590l@vaxc.cc.monash.edu.au (Hadgraft)
Organization: Civil Engineering, Monash University, Australia
Lines: 27

In article <2447@optilink.UUCP>, cramer@optilink.UUCP (Clayton Cramer) writes:
> I was wondering why the fonts in Windows look so poor on the screen
> and printer, so I went into Fat Bits mode in Windows Paint and looked
> at the fonts carefully.  They are garbage!  With just a small
> amount of twiddling bits, I was able to dramatically improve the
> looks of the Roman font.  Is there some technical reason related
> to print resolution why they are so poor?  Or is this just Microsoft
> laziness?

Roman is a stroke font that is translated into a bit mapped font for the
particular size that you want. It's not surprising that it looks poor.
The true bit map fonts like Tms Rmn, Courier, Helv look okay because they've
been optimized for particular device resolutions and pitch sizes.

> Is there a font editor out there that knows about Microsoft Windows
> font format?  If so, would adding decent fonts to the Windows
> directory enable those fonts to be used by applications on screen
> and printer?  If not, what is required to do so?

There's a font editor that comes with the Windows developers Toolkit. I've
developed a Symbol (greek characters etc) font with it.

--
Roger Hadgraft                  |  hadgraft@civeng.monash.edu.au
Lecturer in Civil Engineering   |  phone:  +61 3 565 4983
Monash University               |  fax:    +61 3 565 3409
Clayton, Vic. 3168. Australia.  |